A new website can look better, load faster and still cost you a serious amount of organic traffic. That usually happens because the build has been treated as a design or development project, while the SEO website migration checklist was left until the end. By then, high-value pages may have disappeared, redirects may be missing, and Google has been given no clear route from the old site to the new one.
For a business that relies on enquiries, this is not a technical nuisance. It can mean fewer calls, fewer quote requests and a drop in revenue that is difficult to explain after launch. The aim of a migration is not simply to get a new website live. It is to improve the site without throwing away the visibility you have already earned.
What counts as a website migration?
A migration is any significant change that affects how search engines access, understand or index your website. A full redesign is the obvious example, but it also includes moving to a new CMS, changing domains, switching from HTTP to HTTPS, merging websites, altering URL structures, or rebuilding service and location pages.
The level of risk depends on what is changing. A like-for-like rebuild on the same domain is generally more controllable than a domain change combined with a new platform, new navigation and rewritten content. But even a modest redesign can cause damage if important URLs, page copy or internal links are removed without checking their value first.
Do not measure success by whether the homepage looks polished on launch day. Measure it by whether qualified organic traffic, rankings, enquiries and conversion rates hold up or improve.
SEO website migration checklist: before development starts
The best migrations begin before a designer opens a wireframe or a developer installs a theme. SEO requirements need to shape the new site structure, not be bolted on once templates are already fixed.
Benchmark what is working now
Export performance data from Google Search Console and your analytics platform. Record organic clicks, impressions, landing-page sessions, conversions and the search queries that bring commercially relevant visitors to the site.
Rankings are useful context, particularly for priority services, but they are not the whole story. A page ranking in position three that produces no enquiries matters less than a page ranking in position nine that regularly brings in the right prospects. Identify pages by commercial value, not by traffic alone.
Also take a full crawl of the current website. This creates a record of live URLs, title tags, meta descriptions, headings, canonicals, status codes, image assets and internal links. Without this baseline, it is very easy to miss a useful page when the old site is switched off.
Agree the URL plan before building pages
Every important old URL needs a clear destination on the new website. In an ideal migration, the old page redirects to the closest equivalent new page using a permanent 301 redirect.
Avoid the lazy approach of redirecting dozens of old service pages, articles or location pages to the homepage. It creates a poor user experience and tells Google very little about where the original content has gone. A page about a specific service should point to that service page, not a generic landing page.
Put the mapping into a shared spreadsheet with the old URL, proposed new URL, page purpose, redirect status and notes. Include high-performing blog posts, downloadable resources and old campaign pages if they have backlinks or still attract relevant visitors. It is usually better to retain a valuable page and improve it than delete it because it no longer matches the new design.
Protect content that supports visibility
Website projects often lose rankings because pages are shortened into vague marketing copy. A new page may be cleaner, but if it removes the practical detail that made the old page useful, it can lose relevance for the searches that mattered.
Retain or improve the core information on successful pages: what you do, who it is for, locations served where relevant, process, proof, common questions and clear next steps. This also helps with AI-led search results, where well-structured, specific answers are more useful than generic claims.
Build the new site without creating avoidable problems
A staging site should not be indexable. Use password protection where possible and apply a noindex directive during development. Do not rely on one method alone if the staging environment can be accessed publicly.
At the same time, do not accidentally carry the noindex setting into launch. This is one of the most common and most damaging migration errors. A site can be live for days or weeks before anyone notices that Google has been instructed not to index it.
Check the technical foundations
Before launch, crawl the staging site as if it were live. Look for broken links, redirect chains, pages returning errors, duplicate title tags, missing headings and canonical tags pointing to the wrong domain or environment.
Review the XML sitemap too. It should include the important, indexable URLs you want Google to find, not old redirects, staging URLs, thin search pages or pages blocked from indexing. Make sure the robots.txt file is not blocking essential sections of the site.
Mobile usability and page speed deserve attention, but keep the priority clear. Chasing a perfect performance score while cutting useful content or functionality is not a commercial win. The site needs to load sensibly, work properly on mobile and allow users to enquire without friction.
Test the conversion journey, not just the templates
A migration can preserve rankings and still reduce leads if forms fail, phone numbers are wrong, tracking is missing or key calls to action have been buried under design choices. Test the journey a real prospect would take.
Submit every main enquiry form. Check confirmation messages, notification emails, CRM integrations, click-to-call buttons, booking links and downloadable resources. Verify that consent tools do not prevent analytics or conversion tracking from functioning as intended.
If paid campaigns also send traffic to the website, involve whoever manages them before launch. Changed URLs, new landing pages and altered conversion events can affect advertising performance as well as SEO.
Launch day: make the switch carefully
Migration day is not the moment for improvisation. Schedule the launch when the people who can fix technical problems are available, rather than late on a Friday when everyone has logged off.
Once the new site is live, run through the essentials immediately:
- Confirm the correct domain resolves on both www and non-www versions, with one preferred version selected.
- Test the 301 redirects from the URL mapping file, especially high-value pages and URLs with backlinks.
- Check that pages return the correct status codes and that noindex tags have been removed from pages intended for search.
- Submit the new XML sitemap through Google Search Console and review the robots.txt file.
- Confirm analytics, Search Console, conversion tracking and call tracking are collecting data.
This is one of the few occasions where a short checklist is better than relying on memory. A missed setting can undo months of planning.
The first 30 days after migration matter most
Do not declare the project a success because the site launched without obvious errors. Google needs time to crawl redirects, process new URLs and reassess pages. Some short-term movement is normal, particularly after a major structural change. A sustained decline needs investigation, not reassurance.
Monitor Search Console for indexing issues, crawl errors, excluded pages and unexpected changes in clicks or impressions. Compare organic landing-page traffic and enquiries against the pre-launch baseline, allowing for seasonality where relevant. A business with quieter summer demand should not compare August with March and assume the migration is at fault.
Pay close attention to pages that previously generated leads. If a priority page loses visibility, check its redirect, canonical tag, internal links, content depth and whether the new version still matches the original search intent. Often the fix is straightforward, but only if someone is watching the data.
Also check for redirect chains. If an old URL redirects to an intermediate URL and then to the final page, simplify it. Each important legacy URL should redirect directly to its final destination wherever possible.
When a migration needs specialist input
A small brochure site with limited organic traffic may only need disciplined planning and careful checks. A larger site with hundreds of URLs, established rankings, multiple locations, ecommerce functions or a domain change carries more risk. The cost of getting it wrong can quickly exceed the cost of involving SEO expertise before development begins.
The key point is simple: SEO is not a post-launch tidy-up task. It is part of the migration specification. Developers need a clear redirect plan, content teams need to know what cannot be removed, and decision-makers need reporting that focuses on traffic quality and enquiries rather than a vague statement that the site is now live.
A good migration should leave you with a faster, clearer website and the same or better route to qualified enquiries. If the launch plan cannot show how valuable pages, rankings and conversions will be protected, it is not ready to launch.