A website migration SEO checklist covers old URLs, relevant new destinations, permanent redirects, canonical and language links, sitemaps and post-launch monitoring. Record important addresses before release and begin tests from old links. A working new homepage alone does not show that previous service pages and enquiry journeys remain accessible.
Record what is changing before planning the switch
A simultaneous domain, URL structure, platform and content change makes it harder to identify the cause of a problem. Google's guidance on migrations with URL changes recommends separating major changes when practical. If your project requires a combined release, track each change explicitly instead of hiding everything under “new website”.
Build the existing-page inventory from more than the navigation. Include organic entry pages, enquiry sources, linked resources and URLs shared by your sales team. Remember downloads, language variants and campaign destinations. This protects business uses that may be invisible to the design team.
Give each old address a relevant destination
Map each old URL to a destination, content decision, expected status and test result. For permanently moved content, implement an appropriate server-side 301 or 308 directly to the final destination. A consolidated page must cover the old content; avoid sending every URL to the homepage.
Do not move content with no equivalent to an unrelated page; consider an appropriate 404 or 410 and a useful alternative route. Update internal links, campaign destinations and profiles you control. Google recommends keeping redirects for at least a year and, where practical, longer.
Use observable evidence for the launch decision
Adapt this checklist to the project and add an owner, test example and result to each row. As the release approaches, replace a vague “SEO is done” statement with evidence of the items actually checked.
| Stage | Check | Evidence |
|---|---|---|
| Preparation | Important old URLs and new destinations | Content-owner-approved mapping |
| Launch | Permanent 301/308 and final response | Old URL reaches relevant working destination directly |
| Launch | Canonical and language pairs | New destinations in live source |
| Launch | Noindex, robots and sitemap | Production instructions and submission record |
| Launch | Enquiry, call or purchase journey | Test record reaches the correct recipient |
| Monitoring | Old and new URL errors and performance | Dated report for consistent page groups |
Start launch testing from old links too
Build tests from old organic landing pages, linked articles, advertisements and files shared by sales. Start from the old URL and verify the redirect, final response, content and contact action. A working redirect does not complete the journey if the new form notifies the wrong recipient.
Check production for staging noindex or robots blocks, canonicals pointing to the old host and incorrect language links. Submit the new sitemap in Search Console. Review property verification and Change of Address requirements for domain or subdomain changes; the tool is not for path-only moves within one domain.
Assign ownership beyond release day
Google notes that search visibility can fluctuate during a migration; do not promise a fixed recovery date. Investigate access, errors, indexing signals and enquiries by page group before interpreting the entire change through one total-traffic chart.
Monitor both old and new addresses, record evidence for important problems and retest each correction. Someone must own that issue list. Development, content and marketing teams need an agreed handover so the period immediately after launch does not become an accountability gap.