A Technical SEO Checklist Before You Launch

Most launch-day SEO problems are not clever, hidden mistakes. They are ordinary oversights: a page that accidentally tells Google not to index it, a title copied onto every page, a sitemap that lists redirected URLs. The good news is that each of them is cheap to prevent before launch and surprisingly expensive to diagnose afterwards, when you are waiting weeks for Google to recrawl. This checklist walks through the technical foundations in the order we verify them on real projects, with the reasoning behind each item so you can adapt it to your own site.

1. Make sure the site can be crawled and indexed

Before anything else, confirm that search engines are allowed to see your pages. Three places can block them, and it is common to forget one of them after a staging site goes live.

First, check robots.txt. It should allow your public pages and block only things that genuinely should not be crawled, such as internal API routes. A leftover Disallow: / from the staging environment is one of the most damaging launch mistakes there is.

Second, check the robots meta tag and the X-Robots-Tag header. A noindex directive on a page tells Google to keep it out of the index, even if the page is in your sitemap. Staging sites often ship with noindex on purpose, and it must be removed for production.

Third, make sure important content is present in the HTML that the server returns, not only after JavaScript runs. Google can render JavaScript, but rendering is queued and slower, and other crawlers may not do it at all. Frameworks that render on the server or at build time avoid this problem by default. If you want to understand why this matters, our article on why Next.js suits business websites explains the difference in detail.

2. Give every page a unique title and description

The title tag is the strongest on-page signal you fully control, and it is also the headline people see in search results. Every page needs its own title that describes that page specifically. Keep the primary topic near the beginning, keep the whole title short enough to avoid being cut off (roughly 50 to 60 characters is a safe target), and add your brand name once at the end rather than twice.

The meta description is not a direct ranking factor, but it influences whether someone clicks. Write it as a short pitch for the page, around 120 to 155 characters, and make it different for every URL. Google may rewrite it if it thinks another snippet fits the query better, so do not obsess over it, but a good one still improves your click-through rate. Ignore the old meta keywords tag entirely; search engines stopped using it years ago.

3. Structure headings and content clearly

Each page should have exactly one main heading (h1) that states what the page is about, followed by h2 and h3 headings that break the content into logical sections. Headings are not a place to stuff keywords. They are how both readers and crawlers understand the outline of the page. If you find yourself unable to write clear headings, the page probably tries to cover too many topics and would be stronger split in two.

Also check that a page has enough genuine substance to deserve indexing. Very short pages that repeat what other pages already say are the most common reason a new site sees pages marked as crawled but not indexed. Depth, specific examples and original detail matter more than word count on its own, but thin pages rarely earn a place in the index.

4. Set canonical URLs and clean up duplicates

A canonical URL tells Google which address is the preferred version of a page. Every indexable page should have a self-referencing canonical tag that points to its own final URL. Problems appear when the same content is reachable at several addresses: with and without www, with and without a trailing slash, over HTTP and HTTPS, or with tracking parameters. Pick one version, redirect the others to it with a permanent redirect, and make sure your canonical tags and internal links all agree.

One classic mistake deserves its own warning: a canonical tag defined in a shared layout that ends up pointing every page to the homepage. Always set canonicals per page, and inspect the rendered source of a few different page types after building.

5. Publish a correct sitemap

Your sitemap.xml should list every page you want indexed, and only those. Do not include redirected URLs, pages marked noindex, or addresses that return errors. Google has said it ignores the priority and change frequency fields, so the fields that matter are the URL itself and an honest last-modified date. If you run a bilingual site, adding alternate-language links inside the sitemap helps search engines pair the versions.

Reference the sitemap in robots.txt and submit it in Google Search Console. The report there will tell you how many submitted URLs were discovered and indexed, which is the fastest feedback loop you will get.

6. Add structured data that matches the page

Structured data uses the Schema.org vocabulary to describe your content in a machine-readable way. For a business site, the useful starting set is Organization for the company, WebSite, BreadcrumbList for navigation paths, Article for blog posts and Service or Product where relevant. Structured data does not guarantee rich results, and it never replaces visible content, but it removes ambiguity about who you are and what each page is.

The rule that matters most: the markup must describe what is really on the page. Marking up content that users cannot see, or exaggerating details, can lead to the markup being ignored. Validate it with Google's Rich Results Test before launch.

7. Check speed and Core Web Vitals

Speed is both a ranking input and a conversion factor. Google measures real-user experience with three Core Web Vitals: loading (LCP), responsiveness (INP) and visual stability (CLS). Before launch, test your key templates on a mid-range phone with a throttled connection, not only on your fast development machine. Compress images, serve modern formats such as WebP, size images explicitly so the layout does not jump, and avoid animating the largest element above the fold. Our guide to Core Web Vitals and conversion covers each metric and the fixes that usually help most.

8. Confirm mobile usability and HTTPS

Google indexes the mobile version of your site, so the mobile experience is the one that counts. Check that text is readable without zooming, that tap targets are not too close together, and that no content is hidden on mobile that exists on desktop. Make sure every URL is served over HTTPS, that HTTP redirects to HTTPS, and that no mixed-content warnings appear. Security headers are a natural companion to this step; see our guide to security headers every business website should have.

9. Handle multilingual setup properly

If your site exists in more than one language, each version needs its own URL and a matching set of hreflang annotations. The links must be reciprocal: if the Persian page points to the English page, the English page must point back. Include a self-reference and, if you have a default, an x-default entry. Set the lang and dir attributes on the HTML element correctly for each language, which matters for accessibility and for right-to-left layouts.

10. Build a solid internal linking and error-handling layer

Every important page should be reachable through normal links within a few clicks of the homepage, and related pages should link to each other with descriptive anchor text. Custom 404 pages should return a real 404 status code, and any URL that has moved should return a permanent redirect to its new address. Broken internal links waste crawl attention and frustrate visitors.

11. Verify after launch, do not assume

Once the site is live, open Google Search Console, verify ownership and submit your sitemap. Use the URL Inspection tool on your homepage and a few key pages to confirm that Google can fetch and render them. Over the following weeks, watch the indexing report: pages excluded as duplicates point to canonical problems, while pages that are crawled but not indexed usually point to thin or overly similar content.

A technical foundation does not rank a site by itself. What it does is remove the obstacles, so that your content and reputation can do the work. If you would like an expert review of your launch setup, our SEO service includes a full technical audit, and you can also try the free SEO analyzer for a quick first look.