Post-launch SEO checklist
The new site is live. Now verify actual responses instead of assuming the staging review covers production. Work from your saved baseline and approved URL map.
Check old URLs and redirects
Request the old URLs, not just the new pages. Each planned move should start with a permanent 301 or 308, reach the approved destination and avoid loops or long chains. Confirm that intentionally removed pages return their expected 404 or 410. An access error or timeout is untested, not verified.
If the map is incomplete, return to the redirect mapping guide before treating the migration as finished.
Check live pages and indexability
- Confirm mapped destinations return a successful response rather than 404, 410 or a server error.
- Look for noindex in page metadata and response headers where indexing is intended.
- Review robots.txt restrictions on production; pages blocked from crawling may not have been tested.
- Check that canonical URLs point to the intended production page, not staging or an unrelated page.
These signals should be read on production. Staging settings are not evidence of live behavior.
Review content signals and links
Compare titles and main headings against the baseline. Changed wording may be intentional; ask the owner to approve it rather than treating every change as a defect. Check internal links for missing pages and redirecting URLs, then update links to final destinations.
Separate tested from untested
Count discovered, requested, fetched and compared pages separately. Note budget exclusions, robots restrictions, access denial and timeouts. If a fix was made, rerun the check and preserve the earlier finding so there is a trace of what changed.
PixelReplica scans public HTML up to the configured page budget, not JavaScript-rendered content, private staging areas or every URL on the web. Search performance and indexing should be monitored separately; a migration check cannot guarantee rankings or traffic.
Hand off a clear record
Save the approved mapping, evidence for open issues, verified resolutions, and a report with explicit coverage and limitations. The full migration checklist covers how to prepare this record before launch.
Put the checklist to work
Compare public HTML pages and keep a record of what was checked.