A website migration changes the technology, location or structure of a site. The SEO job is to preserve useful pages, make any URL changes unambiguous and spot mistakes before they become a traffic problem. A new design is not a reason to throw away addresses that people still use.
This checklist is for business owners and SEO teams replacing a CMS, moving hosting or changing domains. It separates those jobs because they do not require the same treatment. The worked URL map is illustrative, not a client result. Google's documentation was checked on 9 November 2026; no traffic-retention guarantee is implied.
First decide what is actually changing
If you replace WordPress but keep the domain and page paths, you do not need a redirect for every page. The existing address should serve the corresponding content directly. If you change a path or domain, the old address needs a reviewed destination. Moving hosting without changing URLs is an infrastructure move, not a domain move.
Write a one-page scope before touching anything: domain, protocol, CMS, paths, content, media and tracking. Separate changes where practical. Google's site-move guidance recommends changing one thing at a time; combining a redesign, domain change and major content removal makes diagnosis harder.
For this site's WordPress replacement, retaining article addresses is a deliberate constraint. That is a preservation decision, not evidence that search performance has improved or that the final domain switch is complete.
Build an inventory beyond your sitemap
A sitemap is a starting point, not a complete historical record. Combine the CMS export, crawl results, Search Console landing pages, analytics landing pages, linked URLs and any available server logs. Include categories, pagination, older campaign pages, images and downloads. Keep the raw inventory before removing duplicates so you can trace where an address came from.
Give each URL a decision: retain, move, consolidate or retire. Add its current status, destination, reason, owner and validation result. Mark commercially important pages and pages with known visits or external links for early testing. Unknown data should remain unknown rather than become a zero-priority score.
Create a reviewed URL map
The following map is a fictional training example. The paths are not links or claims about this site's redirects.
| Old path | Decision | Intended outcome |
|---|---|---|
| /seo-training/ | Retain | Same address serves the training page with 200 |
| /old-audit-service/ | Move | Permanent redirect to /seo-audit/ |
| /audit-basics-part-one/ | Consolidate | Redirect to a combined guide that contains its useful material |
| /expired-event-2011/ | Retire | Genuine 404 or 410 if there is no useful replacement |
| /downloads/checklist.pdf | Retain | Download remains accessible at its original path |
Do not send unrelated retired articles to the homepage merely to eliminate 404s. Google warns that irrelevant redirects may be treated as soft 404s. A real missing-page response is more honest than a destination that does not answer the original request.
Where an address genuinely moves, use a server-side permanent redirect, normally 301 or 308, to the final relevant destination. Avoid chains and loops. Keep redirects for as long as possible; Google's general recommendation is at least one year, with indefinite retention potentially useful for people following old links.
Test the replacement before the switch
Protect the development copy from unintended public access. Authentication is stronger protection than relying on a crawl rule. Maintain an explicit list of any temporary noindex or crawl blocks so the final public site does not inherit them.
For retained pages, compare old and new titles, headings, main content, publication dates, internal links and image availability. If the site has language or regional alternatives, use the hreflang guide to check equivalent destinations and return references. Check the canonical URL against the intended public address, not the development hostname. For changed pages, test the old URL and inspect the final page, not just the first redirect response.
A redirect returning 301 is not enough: its destination must load successfully and match the old page's purpose. Test important routes directly, through navigation and after refreshing. Check enquiry forms on a phone; preserving rankings is of little use if visitors cannot contact you.
Use a launch gate, not a hopeful checklist
Stop the launch if an important page disappears, the public site is blocked from indexing, canonical tags point at development, redirects loop or the enquiry form fails. Treat these as actionable defects with an owner, rather than something to watch after launch.
For lower-risk issues, document the impact and a correction date. There is no universal acceptable percentage of broken URLs: one lost revenue page can matter more than dozens of intentionally retired historical pages.
Capture the final baseline before switching: Search Console clicks and impressions by page and query, analytics traffic and enquiries where measured, and the current crawl. Record the launch time and every significant change. Compare like-for-like periods and preserve longer history for seasonal businesses.
Monitor after launch without confusing correlation and cause
Immediately check public access, critical pages, forms, canonical tags and the actual redirect map. Then monitor indexing reports, errors, page-level search performance and enquiries. Temporary ranking fluctuations can occur while Google recrawls changes; that does not excuse a reproducible technical fault.
Use matched comparison periods and segment by page group, country and device. A site-wide total can hide a service page losing visibility while an unrelated article gains it. If many retained pages fall together, check crawl access and templates first. If one page falls, inspect that page's content, canonical and redirects.
Do not repeatedly reverse a migration because a single day's traffic looks weak. Reproduce the fault, compare it with the baseline and choose a targeted fix. A rollback must restore a coherent URL and redirect state, not leave both versions competing.
Questions that matter before signing off
Do I need Change of Address in Search Console? Google says it is for domain or subdomain moves. It is not needed for changing CMS while retaining URLs, HTTP-to-HTTPS changes or path changes within the same domain.
Will a migration improve rankings? Not automatically. It can remove obstacles and improve usability, but a move is not a ranking guarantee. Judge technical preservation separately from later content gains.
Can I cancel the old hosting immediately? Only once every required redirect, file, verification method and recovery need has a dependable home. A domain change may still depend on the old infrastructure serving redirects.
Your next step and sources
Start with the URL inventory and give every important address a reviewed decision. Use the Search Console opportunity guide to build your measurement baseline and the internal-linking tutorial to plan links to retained pages. If you need help reviewing migration risks, enquire about an SEO audit; that is an enquiry, not an instant booking.
Sources checked 9 November 2026: Google: site moves with URL changes, Google: moves without URL changes and Google: getting started with Search Console. The monitoring sequence is a practical editorial checklist, not a claim that Google requires a particular review timetable.

