The Complete SEO Migration Checklist for Website Redesigns

One missed redirect during your redesign? That’s potentially thousands in lost revenue down the drain. Website redesigns are brilliant opportunities to boost performance and refresh your look, but they’re also minefields for your search rankings. Without a structured approach to SEO migrations, you could watch years of hard-earned organic traffic disappear overnight.

Google treats your website changes exactly like a house move. Every single piece of content needs a clear forwarding address and if you miss even one step, search engines might assume your pages have vanished completely.

We’ve built this checklist to cover every single phase of an SEO-safe migration. Pre-planning, execution, post-launch monitoring. Each step protects your search visibility as your new site goes live.

Pre-Migration Planning and Audit

Everything starts before a single line of code gets written. The pre-migration phase? That’s where you establish your baseline and figure out exactly what needs protecting, because without this foundation you’re basically flying blind.

Fire up Screaming Frog or Sitebulb and crawl every single URL on your existing site. You need to know exactly what you’re working with before you change anything. Export at least 12 months of ranking data from Google Search Console too, because seasonal patterns matter more than you’d think.

Want to know the difference between migrations that go smoothly and complete disasters? Documentation. We’ve seen teams wing it and regret it every single time.

Don’t just look at traffic numbers when you’re deciding which pages matter most. That blog post pulling 10,000 visitors might generate zero revenue, while your product page with 500 monthly visits could be worth £50k annually. Build your priority list around actual business impact and you’ll make much smarter decisions about where to focus your energy during the migration.

Time to dig into what’s broken on your current site. Orphaned pages sitting there doing nothing, internal links pointing to 404s, duplicate content confusing search engines. The redesign gives you a perfect chance to clean house rather than just moving the mess to a prettier location.

Audit Area	Tools Required	Key Metrics
Content Inventory	Screaming Frog, Sitebulb	Total URLs, response codes, content types
Performance Baseline	Google Search Console	Top 500 ranking keywords, click-through rates
Backlink Analysis	Ahrefs, Majestic	Referring domains, anchor text distribution
Technical Health	PageSpeed Insights, Core Web Vitals	Loading speeds, mobile usability scores

URL Structure and Redirect Mapping

Poor URL planning kills more migrations than any other single mistake. We’ve watched sites lose months of rankings because nobody mapped where the old pages should land. Search engines get confused, users hit dead ends and your traffic vanishes.

WordPress permalink structures stay consistent most of the time, but redesigns shake everything up. You’re reorganising content, maybe switching from posts to pages, definitely changing how categories work. Document every single mapping decision because you’ll need to justify them later when something breaks.

Build your redirect matrix around these four buckets: straight swaps, pages you’re merging together, content you’re binning completely and structural changes to your URLs. WordPress migrations get messy fast when taxonomy structures shift.

Redirects aren’t something you sort out post-launch when you notice problems. Every URL choice you make during development either preserves your search equity or throws it away.

Multiple redirects are a nightmare for everyone involved. Search engines might just give up halfway through a chain of three or four redirects and your page speed takes a proper hit too. Skip the interim pages and point those old URLs straight to their final destination.

For WordPress sites on Apache, your redirect map lives in .htaccess. A clean set of 301 redirects looks like this:

# Single page redirects
Redirect 301 /old-services/web-design/ /services/web-design/
Redirect 301 /old-blog/seo-tips/ /blog/seo-best-practices/

# Pattern-based redirects for restructured sections
RedirectMatch 301 ^/insights/(.*)$ /blog/$1

# Category structure changes
RedirectMatch 301 ^/blog/category/news/(.*)$ /blog/$1

Avoid redirect chains at all costs. If /page-a/ redirects to /page-b/ and /page-b/ redirects to /page-c/, update the first rule to point directly to /page-c/ instead. Every hop in the chain leaks link equity and adds latency.

• Document every existing URL and its intended destination
• Group redirects by type: 301 permanent, 302 temporary, 410 gone
• Test redirect logic on a sample of URLs before full implementation
• Account for query parameters and trailing slash variations
• Plan redirects for images, documents and media files, not just pages

Content Preservation Strategy

Redesigns are brilliant for user experience but they can tank your search rankings if you’re not careful. Content preservation isn’t just about keeping words on the page. It’s about maintaining all those invisible signals that search engines use to rank you.

Don’t mess with title tags and meta descriptions on pages that already rank well. Sure, you can tweak them slightly, but completely rewriting these elements tells search engines you’ve fundamentally changed what the page is about (even when you haven’t).

Watch out for WordPress development projects that accidentally break your schema markup or mess up internal linking patterns when switching themes.

Got pages you’re planning to axe or heavily rework? Write them down. Sure, you can ditch those low-value pages without breaking a sweat, but anything with decent backlinks or solid rankings needs a proper think. Merging several weak pages into one powerhouse often works better than keeping them scattered.

What happens when old pages disappear but nothing new takes their place? You’ll need bridging content or tweaks to existing pages so you don’t lose the search traffic those removed pages were pulling in.

Technical SEO Considerations

WordPress migrations come with their own headaches around permalinks, plugin conflicts and server setup. Your new site’s technical backbone decides whether search engines can crawl and index everything properly.

Before you even think about moving content over, get your technical infrastructure sorted. XML sitemaps, robots.txt files, canonical tags. Technical SEO can’t be an afterthought because search engines need them working from launch day.

Permalink structures mess with everything when you change them during a migration. Custom post types and category hierarchies are all connected to how WordPress builds your URLs and links everything together internally.

Your robots.txt file needs updating as part of the migration. Make sure it references your new sitemap location and doesn’t accidentally block crawlers from your new URL structure:

User-agent: *
Disallow: /wp-admin/
Allow: /wp-admin/admin-ajax.php

Sitemap: https://yourdomain.co.uk/sitemap_index.xml

Check your canonical tags too. WordPress themes sometimes hardcode canonical URLs or generate them incorrectly after a URL structure change. Every page should have a self-referencing canonical pointing to its own URL, not to the old structure or a duplicate version.

Technical problems will tank your rankings no matter how brilliant your content is. Search engines factor site health into their algorithms from the start, and a migration that introduces crawl errors or broken canonical tags can undo months of SEO work in a matter of days.

Don’t test your shiny new theme with three blog posts and call it done. Your plugins and theme choices directly impact loading speeds and Core Web Vitals aren’t just nice-to-haves anymore (they’re proper ranking factors). Load up realistic content volumes and see what happens under pressure.

Mobile performance and accessibility aren’t separate concerns you can tackle later. Accessibility improvements boost both user experience and search rankings and if you’re in public sector or healthcare, compliance isn’t negotiable anyway.

Staging Environment Setup and Testing

Migration mistakes get caught and fixed in your staging environment before they wreck your live search performance. Think of it as a parallel universe where you can break things without consequences.

Match your staging setup to production exactly. Same server specs, same PHP version, same database config. We’ve seen too many launches go sideways because staging ran PHP 8.1 while production was stuck on 7.4.

Run through every redirect with both automated tools and manual checks, but don’t treat them all equally. Your main product page redirect failing? That’s a disaster. Some obscure blog post from 2019 not working? Annoying, but not business-critical.

Does your XML sitemap still generate properly? Can search engines read your robots.txt file? Theme swaps and plugin updates love breaking these files, so double-check everything works as expected.

Before you go live, get your staging site through proper accessibility testing. We’re talking screen reader compatibility, keyboard navigation that functions correctly and colour contrast that meets standards. Sort these out now because trust us, dealing with accessibility complaints after launch is a nightmare you don’t want.

• Configure staging with production-equivalent server settings
• Test top 50 redirect mappings manually, plus automated testing for the remainder
• Validate XML sitemap generation and submission processes
• Check Google Search Console integration and data flow
• Audit Core Web Vitals performance under realistic conditions
• Test form submissions, search functions and user account systems

Launch Day Execution

Launch day is when all your planning either pays off or falls apart spectacularly.

Pick your launch window carefully. Most B2B sites can handle weekend launches since traffic drops off, but don’t assume that works for everyone. Public sector sites often see completely different usage patterns, so dig into your actual data first.

When you’re setting up redirects, start with your most important pages and work logically through the list. Skip the plugins and JavaScript workarounds if you can. Server-level redirects respond faster and search engines prefer them, which means fewer headaches all round.

Get those updated XML sitemaps into Google Search Console the moment your site goes live. Search engines won’t magically know about your new URL structure and the indexing reports will show you exactly what’s going wrong if crawlers hit problems. Google’s own sitemap documentation is worth reading before you start.

Hunt down hardcoded internal links pointing to your old URLs because they’re everywhere. Content, widgets, theme files. WordPress loves absolute URLs that completely ignore your redirect setup and create pointless redirect chains. If you have WP-CLI access, a search-replace dry run catches these before they cause problems:

wp search-replace 'https://oldsite.co.uk' 'https://newsite.co.uk' --dry-run --all-tables

Run this with the --dry-run flag first to see what would change, then remove the flag to apply. This catches URLs buried in serialised data that a simple database find-and-replace would break.

Double-check every single tracking code and analytics setup works properly after migration. We’ve seen too many launches where conversion tracking just stops working, which means you’re flying blind trying to measure what went right or wrong.

Post-Migration Monitoring and Optimisation

What happens in those first few weeks after launch? That’s when you’ll know if this whole thing worked or not, because search engines take their time processing changes and early warning signs tell you exactly where to focus your efforts.

Watch your numbers like a hawk for four weeks minimum once you’ve gone live. Organic traffic, keyword positions for your money terms and crawl errors from Google Search Console are your main indicators. Any sudden nosedive means you need to act fast.

Those redirect logs tell a story you need to hear. When server logs and analytics show heavy redirect activity, it’s usually because people (and bots) are still hitting your old URLs. Could be your internal links aren’t properly updated, or maybe external sites haven’t caught up with your new structure yet.

New pages should start appearing in Google Search Console within days, though bigger sites can take weeks to get fully processed. Still showing indexing issues after that? You’ve got technical problems somewhere.

Expect your rankings to wobble a bit after a major site change, but anything significant that lasts beyond two weeks is trouble.

Launch day went smoothly? Great, but that’s not how we measure migration success. The real test happens over the following months when you see whether search performance held steady or improved. This checklist gives you the roadmap, though it’s your ongoing attention to the details that makes or breaks the whole thing.

Worth dropping a line to those high-value sites linking to you about updating their URLs. Redirects do most of the heavy lifting for link equity, but getting direct links to your new structure beats relying on redirects forever. Target the big players first (industry publications, key partners, authoritative directories) since they carry the most weight.

SEO migrations test both your technical ability and your strategic thinking. WordPress gives you a head start with its SEO-friendly setup, but that only works if you’ve configured everything properly. Each migration you tackle teaches you something new and that knowledge becomes your safety net for keeping organic traffic intact next time around.