A site migration is one of the few moments in business where you can watch months of work disappear in a week. New design, new platform, launch day comes and goes, and then the traffic graph rolls off a cliff. The owner assumes Google is punishing them for something. It isn't. Almost every ranking loss after a migration traces back to a specific, missed step, not a mystery algorithm penalty.
That's good news, actually. If the cause is a checklist item, the fix is a checklist. Here's the one we use.
Audit Your Current Site Before You Touch Anything
Before a single new page goes live, you need a complete inventory of what the old site actually has. Not what you think it has. What it has.
Pull a full list of:
- Every indexed URL (your sitemap and a crawl of the live site, since these don't always match)
- The pages that currently rank for anything, even modest terms
- Current title tags, meta descriptions, and header structure
- Any schema markup in place (reviews, products, FAQs, local business data)
- Backlinks pointing to specific inner pages, not just the homepage
This audit is tedious. It's also the entire foundation for the redirect map in the next step. Skip it, and you're redesigning blind. If your team doesn't already track this, our SEO & Analytics work starts here for exactly this reason: you can't protect what you haven't measured.
Map Every Old URL to Its New Destination
This is the step that determines whether your migration is a non-event or a disaster. Every URL on the old site needs a 301 redirect to its closest equivalent on the new site. Not the homepage. The closest equivalent.
A few rules that matter more than people expect:
- One-to-one, not one-to-homepage. Redirecting every old URL to your new homepage tells Google the old pages no longer exist. That's a loss of the relevance signal those pages spent years building.
- Match intent, not just topic. If an old blog post ranked for a question, the new URL should answer that same question, even if the content is reorganized.
- Redirect the whole list, including old ones. Pages that stopped ranking years ago can still carry backlinks. Leave them out of the map and you leave that equity on the table.
- Avoid redirect chains. A redirects to B redirects to C slows crawling and dilutes signal. Point A straight to C.
Build this as a spreadsheet before development starts, not after. It should be a required deliverable of the rebuild, the same as the design files. This is exactly the kind of technical detail that gets rushed when a site is rebuilt in-house or handed to a general contractor without SEO in the scope. It's core to how we approach custom web development: the redirect map is part of the build plan, not an afterthought bolted on the week before launch.
Carry Over Your Metadata and Schema Markup Intact
A redesign is tempting cover for a metadata rewrite. Resist it, at least for launch day.
Your title tags and meta descriptions are doing real work right now. They're part of why pages rank where they rank and why people click them in search results. If you're rebuilding the site anyway, it's easy to let a new copywriter or a new CMS default template quietly overwrite all of it. That's how a business loses rankings on pages that had nothing wrong with them.
Before launch:
- Export every current title tag and meta description and map them to their new URLs
- Preserve heading structure (your H1s and H2s) on pages that are ranking well, even if the visual design changes
- Rebuild schema markup exactly as it was: review stars, FAQ blocks, product data, local business info
- Save metadata improvements for after launch, once rankings have stabilized, so you can tell what changed what
Think of the redesign and the SEO rewrite as two separate projects that happen to share a launch date. Do the redesign first. Optimize the copy later, with data from the new site instead of guesses.
Resubmit Your Sitemap and Watch Search Console at Launch
Launch day itself has its own checklist, and it needs to happen in order.
- Confirm the redirect map is live before you do anything else. Spot-check a sample of old URLs, especially your highest-traffic pages, to confirm each one lands on the right new page with a 301, not a 302 and not a soft 404.
- Submit the new XML sitemap in Google Search Console the same day. Don't wait for Google to find it on its own.
- Remove any noindex tags that were left over from staging. This is the single most common launch-day mistake, and it's invisible until rankings vanish a week later.
- Check robots.txt to make sure it isn't still blocking crawlers, another common staging leftover.
- Request indexing on your most important pages directly through Search Console to speed up the recrawl.
This is also the moment to run a speed check on the new build. Migrations often add weight, new frameworks, bigger images, extra scripts, and Google factors load speed into how it treats the new site. Our speed test takes a minute and tells you where the new site stands before you find out from a ranking drop instead.
What to Track in the First 30 Days After Going Live
Rankings don't move instantly. The first month after a migration is when small, fixable problems still look like small, fixable problems, before they compound into something bigger. Watch these weekly, not monthly:
- Crawl errors in Search Console. A spike in 404s means your redirect map has gaps. Fix them as they appear, not in a batch three weeks later.
- Indexed page count. If it's dropping instead of holding steady or climbing, something is blocking crawlers or returning the wrong status codes.
- Rankings for your top 20 to 30 pages, tracked by URL, not just by domain. A domain-level average can hide the fact that your three highest-value pages took a hit.
- Organic traffic by landing page, compared to the same period before launch. This tells you whether the drop, if there is one, is broad or concentrated on a few pages you can go fix directly.
- Click-through rate in Search Console. If impressions hold but clicks drop, your new title tags or descriptions may be underperforming the old ones, even if rankings are fine.
A short dip in the first week or two is normal. Google needs time to recrawl and revalidate the new URLs. What you're watching for is a dip that doesn't recover, or one concentrated on pages where you know the redirect map was thin.
Your Next Step
If you have a migration planned, build the redirect map before you touch a design file, not after. Pull the full list of current URLs, their rankings, and their backlinks this week, while the old site is still live and still measurable. That list is the thing that protects everything else. If you want a second set of eyes on it before you launch, get started and we'll walk through it with you.