A practical decision guide
Changing a platform, domain or URL structure can affect both visitors and search visibility. A migration checklist helps you see what must be preserved, who checks it and what happens if something fails. It cannot promise unchanged rankings.
A new host with the same URLs is different from a new domain or a redesigned site with renamed pages. Write down changes to domains, URLs, content, templates, forms, files and analytics. Where practical, separate unrelated changes so a problem is easier to trace. Agree the release owner and recovery decision before launch.
Gather current page URLs, important files and the pages that receive visits, links or inquiries. Record each page’s purpose, title and intended destination. Include URLs outside the main menu and valuable downloadable documents. Keep a copy of the existing content and settings so the team has something concrete to compare with the new site.
Use a permanent server-side redirect when a page has permanently moved and a suitable replacement exists. Match the page’s purpose rather than sending every old address to the homepage. A fictional example: /garden-design.html becomes /services/garden-design/, while /contact-us/ becomes /contact/. A retired page with no replacement needs a deliberate removal decision, not an unrelated redirect.
Check important pages and customer tasks in the new environment. Compare headings, titles, descriptions, internal links, images and downloads. Confirm which URLs should be canonical and indexable after launch. Staging restrictions should protect the preview, but they must not accidentally block the live release. Record the expected setting rather than relying on memory.
Open the new pages and representative old URLs. Check the final destination and response, not just whether something appears in a browser. Confirm that redirects do not loop, important links avoid unnecessary chains, the sitemap lists intended live URLs and the contact journey still works. Keep both the test result and the time it was checked.
Google advises monitoring both old and new URLs during a move. Review Search Console alongside site errors and your own inquiry or purchase measurements. Search changes can take time to settle. Keep the old-domain and redirect arrangements working as planned rather than cancelling them as soon as the new homepage looks right.
Document where the previous release or backup is, who can restore it and what could be lost by reverting. A form issue may need a focused repair; a broken routing system may need a different response. Agree how to assess the problem rather than promising that every migration can be reversed with one click.
No. A careful plan reduces avoidable problems, but search systems still need to process changes and rankings can fluctuate.
No. Match a relevant replacement where one exists. Treat genuine removals separately rather than redirecting unrelated pages.
No. It is one part of the move. Redirects, live access, internal links, content and post-launch checks still need attention.
Official guidance checked 2026-10-26.
Tell us what you have in mind. A little context is enough to start a useful conversation.
