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.
WORKFLOW / PRE-LAUNCH WEBSITE CHECK
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 /
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.
02 /
Staging restrictions are often copied into production. Inspect discovery, canonicalization, internal navigation, and presentation signals on the exact final URLs users will visit.
03 /
FAQ /
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.
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.
No. A sitemap helps discovery and communicates preferred URLs, but search engines still evaluate accessibility, canonicalization, content quality, duplication, and other signals.