Few projects make a marketing manager sweat quite like a website migration. Whether you are refreshing your brand, switching CMS providers, or moving to a shorter, sharper domain, the risk to your organic visibility is real. That is why a proper seo migration checklist is not a nice-to-have in 2026, it is the safety net that keeps your hard-won rankings intact when the development team flips the switch. This guide walks UK business owners and marketing managers through every stage, from pre-launch auditing to post-launch QA, with a particular focus on how migrations now affect AI search engines as well as traditional Google results.
The High Stakes of Website Migration in 2026
Understanding the Risks of Major Digital Projects
Migrations sit at the dangerous intersection of marketing, design and engineering, which is precisely why so many of them go wrong. Industry analysis suggests over sixty percent of website migrations experience traffic drops directly linked to poor structural planning. That is not a minor wobble, it is months of lost revenue while your team scrambles to diagnose why Google has dropped half your pages from the index.
The risks have only grown sharper in 2026. Search no longer means a single blue-link results page. Your content also needs to be discoverable by AI engines, conversational interfaces, and large language models that pull from indexed structured data. A botched migration does not just hurt your Google traffic, it can wipe your visibility across the wider answer ecosystem too.
Distinguishing Redesigns, Replatforms, and Domain Moves
Before you plan anything, get clear on what kind of project you are actually running. Redesigns alter aesthetics and usually keep URLs intact. Replatforms swap the CMS or backend, which often changes URL patterns and template structures. Domain moves change the primary web address itself, sometimes combined with one or both of the above.
Each carries different risk profiles. A pure cosmetic redesign rarely tanks rankings unless content is rewritten carelessly. Replatforms and domain moves, however, almost always trigger URL changes, redirect chains and crawl disruptions. Whatever the project, establish baseline metrics for organic visibility, keyword ranks, and organic conversions before changing anything. Without a baseline, you cannot prove recovery, and you cannot diagnose damage.
Budgeting for Success: Factoring Migration into SEO Pricing Packages
Why Migration Support is a Specialist SEO Investment
Most UK businesses underestimate the cost of doing a migration properly. The figure to remember: fixing a failed site migration after launch can cost up to three times more than booking pre-launch consulting in the first place. That post-launch recovery work usually involves the same tasks you should have done initially, plus emergency content recovery, redirect rebuilding and reputation repair with stakeholders.
Treat migration support as a specialist line item rather than something bundled vaguely into a retainer. Ask your agency to scope it separately, with hours, deliverables and sign-off points clearly defined.
What Standard SEO Pricing Packages Should Include for Site Moves
Safe migrations require technical hours for redirect mapping, database audits, schema preservation and launch-day monitoring. When you compare UK seo pricing packages, look for proposals that explicitly split out pre-migration auditing, launch-day support and post-launch QA. If those line items are missing, the agency is either absorbing the cost (unlikely) or ignoring the work entirely (likely).
A robust quote should cover crawl comparisons, redirect documentation, staging environment review, structured data validation, and at least sixty days of post-launch monitoring. If the migration involves a brand-new domain, expect extra hours for outreach to update high-value backlinks at source rather than relying on redirects alone.
Stage 1: The Pre-Launch SEO Migration Checklist
Auditing and Crawling the Legacy Website
Start with a deep crawl of your existing site using a tool such as Screaming Frog or Sitebulb. This reveals orphaned pages, hidden archives and old landing pages that still attract organic value but never appear in your CMS navigation. You cannot redirect what you do not know exists.
Export the full URL list and cross-reference it with Google Search Console data, server logs and analytics. Tag every URL by traffic, conversions, backlinks and ranking keywords. This becomes your value map, the document that tells you which pages absolutely must survive the move.
Creating the 301 Redirect Mapping Document
Your redirect map is the most important file in the entire project. Every old high-value URL must be paired with its exact or closest equivalent on the new site. Never blanket-redirect everything to the homepage, that is the fastest way to flush ranking equity down the drain.
For complex replatforms and domain moves, the Google Search Central site move documentation is required reading. It walks through how Google interprets URL changes, the role of canonical signals, and how to structure your transition for the smoothest possible reindexing.
Setting up the Staging Environment Safely
Staging sites are notorious for leaking into Google’s index, which then competes with your live site and dilutes rankings. Keep staging environments strictly non-indexable by blocking them with a robots.txt disallow rule, applying password protection, or both. Belt and braces.
Before launch day, run a complete crawl of staging to compare against your legacy crawl. Look for missing pages, broken internal links, duplicate meta data and unintended noindex tags. Validate that structured schema markup has been carried across, not just visual elements. This is the step where most LLM-readiness problems are caught.
Stage 2: The Launch-Day SEO Migration Checklist
Executing DNS Updates and Monitoring Server Status
Launch day is not the time for surprises. Schedule DNS updates during a low-traffic window, typically early hours UK time mid-week. Search engines can take days or weeks to process domain changes, so initial speed and stability matter enormously. Slow server responses during the propagation window can compound delays.
Have a live dashboard monitoring uptime, response codes and Core Web Vitals. Assign one person, not a committee, to call go or no-go decisions in the first six hours.
Verifying Server-Side Redirects Live
Once the new site is live, immediately test redirects in bulk. Always use server-side 301 redirects rather than client-side JavaScript or meta-refresh alternatives. Only server-side 301s reliably pass full ranking equity. The W3C server-side redirect techniques documentation explains why this approach is also the accessibility standard, which matters for users and crawlers alike.
For deeper technical context on how search engines interpret different redirect types, the Google guidance on redirects remains the definitive reference. Test a sample of two hundred or more URLs across high, medium and low traffic tiers, and confirm each returns a single 301 hop rather than a chain.
Updating Google Search Console Properties
If your domain has changed, use the Change of Address tool in Search Console as soon as both properties are verified. Submit the new XML sitemap immediately to trigger crawling of the new URLs. Resubmit the old sitemap too, briefly, so Google can rediscover redirects on legacy pages it has not crawled recently.
Reconnect Search Console to Google Analytics 4, Looker Studio and any other reporting tools. Lost data connections during launch week are a common reason teams panic about phantom traffic drops that are actually just broken dashboards.
Stage 3: The Post-Launch QA and Optimisation Checklist
Performing a Full Technical Audit on the Live Site
Within forty-eight hours of launch, run a full crawl of the live site and compare it against both your legacy crawl and your staging crawl. Hunt for redirect chains, soft 404s, missing canonical tags, and any noindex directives that slipped through from staging. The live environment always reveals issues staging cannot.
Monitoring Crawl Errors and Ranking Fluctuations
Post-launch monitoring should continue for at least sixty days to catch delayed indexing anomalies. Set up alerts for crawl error spikes, indexing drops and significant ranking shifts. Expect some volatility for the first two to four weeks, that is normal. What you are watching for is sustained decline in your priority page set.
Document every issue and resolution. This log is invaluable for future migrations and for justifying agency hours to internal stakeholders.
Optimising SEO for ChatGPT and Modern LLM Engines
Here is where most migration checklists fall short. Legacy authority must be preserved so AI search models, including ChatGPT, Perplexity and Google’s AI Mode, can crawl and cite your new structure. If your old URLs were referenced in LLM training data or live retrieval indexes, broken redirects will quietly erase your presence from AI answers.
Use structured schema data on the new site to ensure SEO for ChatGPT and AI search optimisation is maximised during crawler transitions. Maintain Organization, Article, Product, FAQ and HowTo schemas wherever they existed before. If you are unfamiliar with how AI engines now influence search behaviour, our breakdown of Google AI Mode SEO tips covers the practical adjustments worth making during a redesign.
It is also worth understanding the broader shift in agency work around this area, which we explore in how AI is impacting SEO agencies and the future of search. Migration projects in 2026 are no longer just about Google, they are about preserving citations across an entire answer ecosystem.
Final Thoughts
A migration done well is invisible to your customers and seamless to search engines. A migration done badly can take six months of remedial work to recover from, assuming you recover at all. Build your seo migration checklist around three stages: prepare thoroughly, launch carefully, and monitor relentlessly. Budget for specialist support, protect your structured data, and treat AI search visibility with the same seriousness you give traditional Google rankings. Do that, and your next redesign, replatform or domain move will be a growth opportunity rather than a recovery project.