NERDTOOLS / DOMAIN DIAGNOSTICS

WORKFLOW / PRE-LAUNCH WEBSITE CHECK

Launch with the public surface checked.

A successful deployment can still fail at DNS, HTTPS, crawler access, metadata, or redirects. Work through the public signals in dependency order before announcing the site or asking search engines to recrawl it.

01 /

Validate the route to production.

Check the infrastructure first. Later SEO tests are misleading when DNS points to the wrong origin, the certificate does not cover the hostname, or redirect behavior differs between URL variants.

  • Verify apex, www, IPv4, IPv6, and authoritative nameserver records resolve as intended.
  • Confirm the production certificate covers every public hostname and serves a complete, currently valid chain.
  • Test supported TLS protocols and the HTTP-to-HTTPS and preferred-host redirect path.
  • Review security headers only after the final production response is reachable.

02 /

Open the right pages to crawlers.

Staging restrictions are often copied into production. Inspect discovery, canonicalization, internal navigation, and presentation signals on the exact final URLs users will visit.

  • Remove accidental noindex directives, authentication gates, and production-wide robots.txt blocks.
  • Publish the preferred canonical URLs in a fetchable XML sitemap and declare it in robots.txt.
  • Check titles, descriptions, headings, canonical tags, structured data, image alternatives, and social metadata.
  • Crawl important navigation paths for broken links, then submit the sitemap and inspect priority URLs in Search Console.

03 /

Choose the signal you need.

FAQ /

Operational detail.

When should I run this website launch checklist?

Run it against an externally reachable preview when possible, again immediately after DNS or routing changes, and once more after caches and CDN configuration have settled.

Should a staging website be indexable?

Usually not. Protect staging with authentication when possible. Before launch, confirm those restrictions, noindex directives, and robots rules have not been copied to the production site.

Does submitting a sitemap guarantee indexing?

No. A sitemap helps discovery and communicates preferred URLs, but search engines still evaluate accessibility, canonicalization, content quality, duplication, and other signals.