Technical SEO checklist for a business website launch

A technical SEO launch check asks a practical question: can search engines discover the right pages, fetch their content, and understand which URL represents each page? It is separate from deciding whether that content deserves to rank.

Use this checklist before launching a business website or changing its structure. Keep a simple spreadsheet of URLs, expected status codes, titles, and canonical destinations. Record failures so they can be retested after fixes.

Start with the pages that matter

List your homepage, main services, contact page, and useful articles. Open each directly in a fresh browser tab. A page should not depend on navigating from the homepage first.

Inspect the initial HTML as well as the visible page. Server-rendered content makes this check straightforward: the document should contain its title, main heading, and useful body text. Test the actual production deployment because local success does not prove that a proxy or host is configured correctly.

Check status codes and canonical URLs

Use a request such as:

curl -I https://example.com/services/seo
curl -I https://example.com/a-page-that-does-not-exist

Replace the domain with your own. A normal public page should return a successful response. A missing page should return a real 404, even when its design matches the rest of the site. For moved content, use an intentional permanent redirect to the closest relevant replacement.

Check the canonical link in the HTML. It should identify the intended public URL, not localhost, a staging domain, or an unrelated page. Also inspect HTTP-to-HTTPS and preferred-host behavior at the deployment layer.

Make the sitemap accurate

Include canonical public pages and published articles. Exclude draft previews, admin screens, broken links, and duplicate parameter variations. A sitemap helps discovery; it does not guarantee indexing.

Only include a lastmod value when it reflects a meaningful page update. Google ignores the sitemap's priority and changefreq fields. Read Google's sitemap guidance for supported formats, then submit the production sitemap in Search Console after verifying the property.

Understand robots and noindex

The robots.txt file controls crawling, not reliable removal from search results. A blocked URL can still be known to Google. A noindex instruction must be discoverable by the crawler to take effect.

Keep private content behind authentication. Do not treat robots rules as access control. Google's robots introduction explains the distinction. Check that a staging restriction has not accidentally been copied onto your live site.

Review the content and links

Give each service page a distinct purpose and descriptive title. Use one clear main heading, then section headings that follow the document's structure. Write descriptions for people deciding whether to click, rather than repeating the same keyword in every sentence.

Connect articles to the relevant service and to useful follow-up reading. Avoid sending every internal link to the homepage. Our guide to clearer service structure explains how to reduce overlap without casually deleting valuable pages.

Measure after launch

Use Search Console to inspect important URLs, review indexing reports, and monitor actual queries. Track qualified enquiries alongside traffic. If a page is indexed but receives little relevant attention, revisit its usefulness and search intent before adding more decorative copy.

Google's SEO starter guide is a useful baseline. For a review of your site's specific priorities, start with our SEO service. No checklist or agency can promise a particular ranking position.