SEO checklist for website migration: before and after launch

A developer told his client the new site was ready to launch on Friday afternoon. The client approved it over the phone. By Monday morning, rankings for a cluster of pages had dropped sharply. Nobody had mapped the old URLs to the new ones. Nobody had checked whether Google could read the new site at all. The developer called it a settling period. Three months later, most of those positions hadn't returned. The cost wasn't a technical glitch; it was a skipped checklist.

What is a website migration checklist?

A website migration checklist is a structured list of SEO tasks you work through before, during, and after moving a website to a new platform, domain, or URL structure. It tells you what to audit before you touch anything, what to verify the moment the new site goes live, and what to monitor in the weeks following. Without it, ranking losses preventable at the outset become permanent.

Key Takeaways

• Ranking losses after a migration are almost always preventable, not inevitable.
• Your pre-launch audit is the most important stage: fix problems on the old site before they follow you to the new one.
• Every old URL needs a destination on the new site, and set up that connection before launch, not after.
• Analytics and Google Search Console must be confirmed as working before the new site goes live, so you have a complete record of what changes after the switch.
• Post-launch monitoring for the first four to eight weeks isn't optional; it is where you catch what the pre-launch audit missed.
• A slow migration done carefully beats a fast migration done carelessly, every time.

Audit the existing site before you move anything

The most common migration mistake is treating the old site as something to escape rather than something to understand. Before you change a single URL or copy a single page, you need a clear record of what you currently have and what it is doing for your rankings.

Start by crawling the existing site with a tool such as Screaming Frog or a similar crawler. This gives you a full list of every live URL, every page title, every meta description, and every internal link. Export it, save it, and treat it as your baseline. Without this list before launch, you have no way of knowing what you lost after it.

Next, open Google Search Console, Google's free tool showing which of your pages appear in search results and how often people click on them, and export your top-performing pages by clicks and impressions. These are the pages carrying your rankings. They need the most careful handling in the migration. According to WordPress VIP's migration guidance, measuring what counts before launch gives you a reliable record for post-migration comparison. Without that baseline, you're comparing the new site's performance against nothing.

Also record your current backlink profile. A backlink is a link from another website pointing to yours. Each one acts like a recommendation in Google's eyes, and the links pointing to your old URLs need somewhere to go on the new site.

Build your redirect map before launch day

Redirect mapping is the single most critical pre-launch task in any website migration. A redirect is an instruction telling Google and a visiting browser: "This URL has moved. Go here instead." Without redirects, every old URL no longer in existence returns a 404 error, a dead end, and Google treats it as a page ceasing to exist.

The redirect map is a spreadsheet matching every old URL to its equivalent new URL. This isn't a task you can do quickly on launch day. A site with two hundred pages needs two hundred mapped destinations. The Semrush migration checklist recommends recording the final site status and creating a content backup before migration, so the map is built from accurate data rather than from memory.

Where an old page maps directly to a new page covering the same topic, the redirect is straightforward. Where old pages are being merged or removed, decide what the closest equivalent destination is and redirect there. A redirect to the homepage is a last resort, not a solution. Use it only for pages with no reasonable equivalent. Google's guidance on site moves with URL changes sets out the same order: map old URLs to new ones first, then start the move by redirecting the old URLs to the new ones. The moment the new site is live, traffic arrives, and it needs somewhere to go.

Check the new site is technically sound before it goes live

Once the new site exists in a staging environment (a private copy of the site search engines cannot reach yet), work through these checks before you flip the switch.

Technical checks to run on the staging site

The Moz migration guide notes a migration is an opportunity to improve your site's structure, but only if you're fixing known problems rather than importing them unchanged. If your old site had duplicate content issues, correct them on the new site before launch, not after.

Google's own guidance from a domain migration at scale confirms an SEO audit ahead of a migration, covering the sitemap, metadata, and redirect plan, makes the process significantly smoother. Pre-migration SEO basics from Google's own team reinforce that keeping old links working through redirects and getting the metadata right are preparation steps, not post-launch corrections.

Confirm analytics and Search Console before flipping the switch

You can't measure what changes after the migration if your measurement tools aren't confirmed as working before it. This step sounds obvious. It gets skipped constantly.

Before launch, confirm Google Analytics, or whichever analytics tool you use to measure how many people visit your site, is installed on the new site and recording data correctly. Then confirm Google Search Console is connected to the new domain or URL structure. If your migration involves a domain change, you need to verify the new domain in Search Console and submit the new sitemap there.

Search Console takes several weeks to accumulate meaningful data after a migration. Setting it up after launch rather than before leaves your first month of post-migration data incomplete, and you'll be trying to diagnose ranking changes without the information needed to understand them. Analytics setup and measurement confirmed before migration is the practical standard the industry works to, not an optional extra.

The moment the new site is live, submit the XML sitemap to Search Console and request indexing (the process by which Google adds your pages to its list of sites it can show in search results) for your most important pages. Don't wait for Google to find them on its own.

The post-launch monitoring window: the first eight weeks

The launch isn't the finish line. It is the starting point for a monitoring period running at least four to eight weeks. This is where you find the problems your pre-launch audit didn't catch.

In the first 48 hours, check your redirects are working correctly by testing a sample of old URLs. If an old URL now returns a 404 error instead of redirecting, the redirect either wasn't set up or is broken. Fix these immediately; every hour a redirect is missing is an hour Google is finding a dead end instead of your new page.

Check crawl errors in Google Search Console daily for the first two weeks. Crawl errors appear when Google tries to visit a page on your site and can't reach it properly. A spike in these errors after launch signals something in the technical setup is wrong. The post-migration monitoring process requires checking crawl statistics for anomalies and reviewing Search Console issue reports as a core ongoing task, not a one-time check.

After the first two weeks, compare your traffic and ranking data against the baseline you recorded before the migration. Some movement in either direction is normal in the first few weeks; Google takes time to re-evaluate pages after a migration, and minor fluctuations aren't a crisis. A sharp and sustained drop in a specific cluster of pages is a signal worth investigating. It usually points to a missing redirect, a broken canonical tag, or a page accidentally left off the new sitemap.

What to do if rankings drop after the migration

A ranking drop after a migration isn't a sign the migration has failed permanently. It is a diagnostic signal, and most causes are correctable.

The Focus Reactive migration checklist outlines the most common post-migration ranking problems as tracing back to redirect errors, missing or incorrect canonical tags, and pages excluded from the sitemap. Work through these in that order.

First, audit your redirects again. Use a crawler to check every redirect chain resolves correctly and doesn't loop back on itself or result in a chain longer than two steps. Long redirect chains slow down the process by which Google follows links through your site, and they dilute the ranking value passed from the old URL to the new one.

Second, check your canonical tags on the pages dropping in rankings. A canonical tag is a piece of code on a page telling Google which version of that page is the "real" one when duplicates exist. A misconfigured canonical tag can tell Google to treat your new page as a duplicate of your old, now-deleted page, making it invisible in search results even though it exists.

Third, check your sitemap for completeness. If pages are missing from the sitemap submitted to Search Console, Google may be slow to find and re-evaluate them. Add them, resubmit, and request indexing for the specific pages involved.

Ranking drops rooted in these three causes tend to recover within four to eight weeks of the fix being applied, provided the underlying content and the redirect mapping are sound. Where they don't recover, the cause is usually a structural problem in the content, not in the migration mechanics.

Closing Reflection

A website migration is one of the highest-risk events in an SEO programme. The risk isn't in the new platform or the new design; it is in the gap between what was working on the old site and what survives the move. Most of that gap is preventable. The checklist above isn't a guarantee of zero ranking loss; some disruption is normal and expected. What it protects against is the kind of permanent, unnecessary loss coming from skipping the audit, forgetting the redirects, or launching before the measurement tools are confirmed as working.

You shouldn't have to guess which migration steps protect your rankings and which ones are optional. With Zahavah Studio you won't.

Contact Zahavah Studio to plan a migration keeping the rankings you have earned and giving the new site the right foundation from launch day.

If the checklist above raises questions about your own upcoming or recent migration, the answers below cover the issues coming up most often.

Frequently Asked Questions

What are the key issues to consider in a website migration checklist?

The key issues in a website migration checklist fall into three groups: what to audit before you start, what to verify before launch, and what to monitor after. Pre-migration, the critical concerns are your redirect map, your baseline data from analytics and Search Console, and a full crawl of the existing site. Without these, you have no record to compare against and no safety net if something breaks.

At the launch stage, the most common failures are a robots.txt file accidentally blocking Google from the new site, missing or incorrect redirects, and analytics tools not configured on the new platform. Any of these can cause immediate, measurable ranking damage.

Post-launch, your priority is monitoring crawl errors and comparing traffic against your baseline. Most migration problems surface within the first two to four weeks, and the sooner you catch a broken redirect or a missing canonical tag, the less ranking ground you lose. The full checklist, covering redirect mapping, canonical tags, sitemaps and analytics setup, applies to every migration regardless of platform, size or technical complexity.

How long does a website migration take?

A website migration takes anywhere from four weeks to six months, depending on the size of the site and the complexity of the move. A small business site with twenty to fifty pages moving to a new platform can be completed in four to eight weeks if the team works methodically. A site with several hundred pages, multiple content types, and a domain change alongside the platform change will take considerably longer.

The most common reason migrations run over schedule is the redirect map. Building an accurate URL-by-URL redirect map for a large site takes more time than most clients and developers budget for. Rushing it is where most ranking losses originate.

The technical build of the new site is rarely the bottleneck. The SEO preparation (the crawl, the baseline data export, the redirect mapping and the pre-launch checks) is where the time goes. A migration compressed into a weekend to save time or money tends to cost far more in lost rankings than a careful migration done over several weeks would have.

How much does a website migration cost?

Website migration costs vary widely, depending on who manages the SEO elements, who builds the new site, and how large the existing site is. The technical build of a new platform is a separate cost from the SEO migration work.

For the SEO component (the audit, redirect mapping, pre-launch checks and post-launch monitoring), a small business site typically involves ten to twenty hours of specialist work. What that costs depends on the agency's rates. Larger sites with complex URL structures and domain changes require more.

Avoid treating the SEO migration work as optional or as something to add after the developer has finished. Fixing a failed migration, by recovering lost rankings, rebuilding traffic and diagnosing redirect errors after the fact, costs more in most cases than doing the migration correctly from the start. Your website migration checklist protects the investment you have already made in your rankings.

Which pages are performing well and need the most careful migration?

Your top-performing pages by organic clicks and impressions in Google Search Console are the ones needing the most careful handling in a website migration. These are the pages generating real traffic and, in most cases, real enquiries or revenue. Losing their rankings isn't a minor statistical shift; it is a direct loss of business.

Export these pages from Search Console before you touch anything on the old site. For each one, confirm a redirect is mapped to the closest equivalent page on the new site, the new page carries the same or improved title and meta description, and the canonical tag is set correctly. Then, after launch, monitor these specific pages first. If any show a significant drop in the first two weeks, treat it as urgent and investigate immediately. Pages driving the most traffic are often also the ones with the most backlinks pointing to them, so a broken redirect on a high-traffic page loses not only the traffic but also the ranking value those external links were contributing.

Everything on this blog is written to inform and educate. It is for information only. Nothing here is professional legal, financial, or technical advice. If you are making a significant business decision, speak to a qualified professional first. Zahavah Studio works hard to keep this content accurate and current, but is not liable for decisions made based on what you read here.

Leave a comment