Technical SEO Checklist for Developers Before Launching a Business Website

You have spent weeks building the website. The design is clean, the code is solid, and the client is happy with how it looks. But here is the problem — a website that looks great can still be invisible to search engines if the technical foundation is broken. Crawlers cannot read it, indexers cannot process it, and users never find it. This is why technical SEO should be treated as a pre-launch requirement, not an afterthought. This checklist covers the critical checks every developer should complete before any business website goes live.

Crawlability, Indexability, and HTTPS Checks

These are two different things that developers often confuse, and the distinction matters.

Crawlability is about whether Google can access your pages at all. Your robots.txt file controls this. A misconfigured file — something as simple as a leftover Disallow: / from your staging environment — will block Googlebot from crawling the entire site.

Example of a staging robots.txt that should NOT go live
User-agent: *
Disallow: /

Check this file carefully before launch and make sure it only restricts pages you genuinely do not want crawled.

Indexability is about whether Google will include your pages in search results. A page can be perfectly crawlable but still excluded from the index if it carries a noindex meta tag:

Developers often add noindex during development and forget to remove it. Audit every important page before go-live.

Also verify your canonical tags are pointing to the correct URLs and that no staging domain URLs have leaked into production:

Finally, confirm your SSL certificate is active and the site loads cleanly on HTTPS. An HTTP site in 2026 creates trust issues and removes a basic page-experience advantage from day one. Also watch for mixed content errors after switching to HTTPS — these occur when a page loads over HTTPS but still references HTTP resources like images, scripts, or stylesheets. Browsers will block or flag these, and they can silently break parts of your page.

URL, Meta, and Heading Structure

Clean URLs are short, readable, and descriptive. Avoid dynamic parameters, unnecessary subfolders, or auto-generated slugs that mean nothing to a human reader. A URL like /services/seo-consulting is indexable and understandable. A URL like /page?id=482&ref=nav is neither. Use hyphens to separate words, keep everything lowercase, and remove stop words where they add no meaning.

Every important page needs a unique meta title and meta description. Meta titles are usually around 50–60 characters — Google truncates based on pixel width rather than a fixed character count, so treat this as a guideline rather than a hard rule. Include the primary keyword naturally, preferably near the beginning. Duplicate titles across pages confuse search engines about which page to rank for a given query — a common problem on sites with templated page builders where the default title carries over across multiple pages without anyone noticing.

Meta descriptions do not directly influence rankings, but they influence click-through rates. A well-written description that reflects the page content and gives the user a reason to click is worth writing carefully for every key page. Leaving them blank means Google will pull whatever text it finds on the page, which is often not what you would choose.

Each page should have exactly one H1 that reflects the primary topic. Subheadings should follow a logical H2 and H3 hierarchy throughout the content. Use H2s to introduce major subtopics and H3s to break down the detail within them — this helps crawlers map the structure of your content and makes long pages easier to navigate for users. A page with multiple H1s or a heading structure that skips levels signals poor content organization to both users and crawlers, and creates accessibility issues for screen readers as well.

Speed, Mobile Performance, and Core Web Vitals

Google uses Core Web Vitals as its standardized way of measuring page speed and user experience as ranking signals. Rather than evaluating raw load time alone, Core Web Vitals break performance down into three specific metrics that reflect how a page feels to a real user:

• LCP (Largest Contentful Paint) — how fast the main content loads. Target under 2.5 seconds.
• INP (Interaction to Next Paint) — how quickly the page responds to user input. Target under 200ms.
• CLS (Cumulative Layout Shift) — how much the page layout shifts unexpectedly during load. Target under 0.1.

To improve these scores: compress and properly size images, eliminate render-blocking scripts, defer non-critical JavaScript, and use a CDN where possible. Test using Google PageSpeed Insights and Lighthouse before launch — both give actionable diagnostics broken down by issue.

Broken Links, Redirects, and 404 Handling

Broken internal links hurt both user experience and crawl efficiency. Run a full crawl of your staging environment using Screaming Frog or Ahrefs Webmaster Tools before launch and fix every broken link you find. Pay particular attention to navigation menus, footers, and sidebars — these appear across every page and multiply the damage if broken.

If the website is a redesign or migration, map out every old URL that is changing and set up 301 redirects to the correct new destination. A 301 tells both users and search engines that the page has permanently moved and passes link equity to the new URL. This is especially important for any pages that have accumulated backlinks over time.

Avoid the common mistake of redirecting everything to the homepage. Google treats this as a soft 404 and discounts the redirect. Map old URLs to their closest matching new equivalents instead.

Set up a custom 404 page before launch. It will not help your rankings, but it keeps users on the site when they land on a missing page and looks considerably more professional than a blank server error.

Sitemap and Search Console Setup

Your XML sitemap should list only the pages you want to see in search results — no noindex pages, no low-value paginated archives, no thin utility pages. Keep it clean. A bloated sitemap weakens the signal of which pages on your site actually matter.

Submit the sitemap to Google Search Console and verify ownership of the domain before launch. Once verified, go to the Sitemaps report under the Index section, paste your sitemap URL, and hit Submit. Search Console is how Google communicates crawl errors, indexing issues, and manual actions directly to you. Setting it up after launch means you may miss early signals that something is wrong.

Schema Markup and Tracking Setup

Schema markup helps search engines understand the context of your content and can unlock rich results in the SERP. For most business websites, the most relevant schema types are:

• Organization — for the business name, logo, and contact details
• LocalBusiness — if the business serves a specific geographic area
• Article — for blog content
• FAQ — for pages with question-and-answer format content

Always implement schema using JSON-LD — it is Google's preferred format and easier to maintain than microdata. JSON-LD is typically added inside a <script> tag in the <head> of the page, or injected through your CMS or template layer:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "LocalBusiness",
  "name": "Your Business Name",
  "url": "https://yourdomain.com"
}
</script>

Once added, test every schema implementation using Google's Rich Results Test before the site goes live.

On the tracking side, confirm Google Analytics 4 is firing correctly on all pages using GA4 DebugView or Google Tag Assistant — both let you verify events are firing in real time before the site goes live. Also confirm Search Console is linked to your GA4 property, form submissions are tracked as conversion events, and phone number clicks are tracked if the business relies on call leads.

Final Pre-Launch SEO Checklist

• [ ] robots.txt is not blocking important pages
• [ ] No noindex tags left on pages that should rank
• [ ] HTTPS is active and all pages load securely
• [ ] No mixed content errors on HTTPS pages
• [ ] Canonical tags point to the correct production URLs
• [ ] Meta titles and descriptions are unique across all pages
• [ ] One H1 per page, logical heading hierarchy throughout
• [ ] Core Web Vitals checked with special attention to mobile performance
• [ ] No broken internal links or 404 errors
• [ ] 301 redirects in place for any changed URLs
• [ ] XML sitemap is clean and submitted to Search Console
• [ ] Schema markup added and tested in Rich Results Test
• [ ] GA4 and conversion tracking confirmed firing correctly

Conclusion

Technical SEO is not something you fix after launch — it is something you build correctly before it. A website with broken crawlability, missing metadata, or untracked conversions starts its life at a disadvantage that takes months to recover from. Get the foundation right before the first visitor arrives, and the site has a genuine chance to perform in search from day one. If you want to go beyond checklists and develop a working understanding of how search engines actually evaluate websites, investing in proper [SEO training in Nepal] is a practical next step worth considering.