WordPress SEO Migration Checklist: 25 Steps to Keep Your Rankings
A step-by-step checklist for migrating your WordPress blog without losing search rankings. Covers pre-migration audit, redirect mapping, meta tag preservation, and 30-day post-launch monitoring.
Most WordPress migrations that lose rankings fail not because the new platform is worse, but because the migration skipped steps. A redirect was missing. A canonical URL pointed to the wrong page. Meta descriptions were not carried over. The sitemap was not resubmitted. Each missed step is small on its own, but together they add up to the kind of traffic drop that takes months to recover from.
This checklist covers the 25 steps that separate a clean migration from a ranking-destroying one. It applies whether you are moving from WordPress to a headless platform , a different CMS, or even just changing your WordPress host. The same SEO principles apply to every migration: preserve what Google already knows about your site, and do not give it conflicting signals about where your content lives.
How long does recovery take? A well-executed migration with proper redirects and metadata preservation typically sees rankings stabilize within 3–7 days. A poorly executed migration — missing redirects, lost meta tags, broken internal links — can take 3–6 months to recover, if it recovers at all. The difference is almost always in the preparation, not the platform.
Phase 1: Pre-migration audit (before you touch anything)
Every step in this phase creates your "before" snapshot. You cannot measure whether the migration succeeded without a baseline to compare against. Budget 2–4 hours for a typical blog with under 500 posts.
1. Export Google Search Console performance data
Go to Search Console → Performance → Search results. Export the last 16 months of data (the maximum available) as CSV. Include pages, queries, clicks, impressions, CTR, and position. This is your single most important reference document — it tells you which pages drive traffic and where they rank.
Sort by clicks descending. Your top 50 pages are migration-critical. If any of these return 404 after migration, you lose your most valuable traffic immediately.
2. Crawl the entire site
Use Screaming Frog, Sitebulb, or Ahrefs Site Audit to crawl every URL on your current site. Save the crawl — it becomes your "before" URL list for redirect mapping. Export at minimum: URL, status code, title tag, meta description, H1, canonical URL, and inbound internal link count.
Screaming Frog's free tier caps at 500 URLs per crawl. For larger sites, the paid license ($259/year) or Ahrefs Site Audit (included with Ahrefs subscriptions) handles unlimited URLs.
3. Export your XML sitemap
Download your current sitemap (usually at /sitemap.xml or /wp-sitemap.xml). If you use Yoast or Rank Math, the sitemap is at /sitemap_index.xml. This gives you a second URL inventory to cross-reference against the crawl — sometimes the sitemap includes URLs that the crawler could not reach, and vice versa.
4. Record backlinks per URL
Export your backlink data from Ahrefs, Semrush, or Moz. You need referring domains per target URL. A page with zero organic clicks but 40 referring domains is a page you redirect very carefully — those backlinks pass authority to your domain. Losing them means losing domain authority.
5. Document all meta tags and structured data
For every page template on your site, record:
6. Snapshot Core Web Vitals
Record your current Core Web Vitals from Search Console (Core Web Vitals report) or PageSpeed Insights . Test at least one URL from each page template: a post, a category page, the homepage, and any custom templates. The new platform should be equal or better. If your Largest Contentful Paint or Cumulative Layout Shift scores drop after migration, something is wrong with the new site's rendering — not the migration itself. This baseline also helps you argue the ROI of migration: if your WordPress LCP was 3.2 seconds and the new platform delivers 1.1 seconds, that is a concrete improvement to report.
7. Export existing redirects
If your WordPress site has existing redirects (from the Redirection plugin, .htaccess, or Yoast Premium), export them all. These redirects must survive the migration. If /old-post redirects to /new-post on your current site, and you migrate without that redirect, the old URL will 404 on the new site — and any external links pointing to /old-post lose their value.

Phase 2: Build the redirect map
The redirect map is the single most important artifact in any migration. It maps every old URL to its new destination. Missing redirects are the #1 cause of post-migration ranking drops.
8. Map every URL 1:1
Create a spreadsheet with one row per old URL. Columns: old URL, new URL, status code (301, 410, or "same"), traffic (from your Search Console export), and referring domains (from your backlink export). Every row gets exactly one new destination URL. No row is allowed to be blank.
For a blog with 200 posts and consistent permalinks, this spreadsheet is straightforward — most rows are "same" because the slug does not change. For sites with complex URL structures (year/month/post-name, category/post-name, or custom post types with prefixes), the mapping requires more attention. Automate what you can with formulas or a script, then manually verify the top-50 pages by traffic.
9. Keep URLs identical where possible
The safest URL is one that does not change. If your WordPress permalink structure is /%postname%/ and your new platform serves the same slug at the same path, no redirect is needed. No redirect means no risk. Keep every URL you can.
10. Decide: keep, merge, or retire each URL
For each URL in your map, classify it based on traffic and backlinks:
Traffic | Backlinks | Action | Redirect? |
|---|---|---|---|
Has clicks | Has referring domains | Keep — high priority URL | 301 if URL changes |
Has clicks | No backlinks | Keep — valuable for traffic | 301 if URL changes |
No clicks | Has referring domains | Keep or merge — the backlinks have value | 301 to closest equivalent |
No clicks | No backlinks | Retire — return 410 (Gone) or merge | Optional: 301 to relevant parent |
11. Use permanent redirects (301, not 302)
A 301 redirect tells Google the move is permanent and the target should be canonical. A 302 tells Google the move is temporary and the old URL should stay in the index. Migrations are permanent moves — always use 301. Google passes 95–99 % of link equity through a 301 redirect.
12. Eliminate redirect chains
If /a/ already redirects to /b/ on your current site, and /b/ moves to /c/ on the new site, rewrite /a/ to point directly to /c/. Every hop in a redirect chain adds latency and risks losing link equity. Google follows up to 10 redirects, but every hop is unnecessary risk.
13. Never redirect to the homepage in bulk
Google's site move documentation explicitly warns: redirecting many old URLs to a single irrelevant destination "might be treated as a soft 404 error." Soft 404s pass no link equity. Every URL gets a redirect to its closest equivalent — not the homepage.
Phase 3: Staging site setup
14. Build on a hidden staging domain
Set up the new site on a staging subdomain (staging.yourdomain.com) with a robots.txt that blocks all crawlers and a meta robots noindex on every page. Never let Google index your staging site — it creates duplicate content that competes with your live site.
15. Import content and verify parity
After importing your content (whether via REST API or one-click import ), verify these elements on every page template:
16. Carry over meta tags
For every page, verify that the new site generates:
17. Implement structured data
Verify that every page template has the correct JSON-LD structured data. At minimum: Article schema for posts (headline, datePublished, dateModified, author, image), BreadcrumbList for navigation, and Organization or WebSite for the homepage. If you had FAQ or HowTo schema on specific pages, carry it over.
18. Rebuild internal links
Internal links that point to old URLs will work through redirects, but that adds a redirect hop to every page. Update internal links to point directly to the new URLs. This is especially important for navigation menus, footer links, and in-content links between posts. On Modern Blogging, internal links are stored as Sanity document references — they resolve to the correct URL automatically, even if a slug changes.
19. Test all redirects on staging
Import your redirect map into the new platform and test every single redirect. Not a sample — every one. Use a crawler (Screaming Frog) to crawl the old URL list against the staging site and verify each returns a 301 to the correct destination. Fix any that 404, chain, or loop before going live.

Phase 4: Launch
20. Launch during a quiet period
Deploy the new site during a low-traffic window. Switch DNS, or if using Cloudflare, update the proxy target. Having the new site behind Cloudflare is ideal because DNS propagation is instant for proxied records.
21. Remove staging blocks immediately
The moment the new site is live on the real domain: remove the noindex meta tags, update robots.txt to allow crawling, and verify the sitemap is accessible at its expected URL. Every minute with noindex on the live domain is a minute Google is told to de-index your pages.
22. Submit the new sitemap
Submit the XML sitemap in both Google Search Console and Bing Webmaster Tools. If you had multiple sitemap files on the old site (posts, pages, categories), verify the new site covers all of them. Use Search Console's "Sitemaps" report to confirm submission was accepted.
Phase 5: Post-launch monitoring (30 days)
23. Daily checks (week 1)
24. Weekly checks (weeks 2–4)
25. Sign-off criteria
The migration is complete when all of the following are true:

What to do if traffic drops after migration
Even with a thorough checklist, some migrations see a temporary traffic dip. Here is a decision tree for diagnosing and fixing the most common causes:
Symptom | Likely cause | Fix |
|---|---|---|
All pages dropped at once | Sitewide noindex still in place, or robots.txt blocking crawlers | Check robots.txt and meta robots on the live site immediately |
Specific pages 404 | Missing redirects for those URLs | Add 301 redirects from the redirect map; resubmit sitemap |
Rankings dropped but pages are indexed | Meta tags changed (title, description), or internal link structure differs | Compare meta tags against the pre-migration baseline; fix discrepancies |
Rich results disappeared | Structured data missing on the new site | Add JSON-LD Article schema; validate with Rich Results Test |
Traffic down only on mobile | Mobile rendering issue on the new site (font size, tap targets, viewport) | Test with PageSpeed Insights mobile mode; fix responsive issues |
Slow recovery (2+ weeks) | Redirect chains, canonical conflicts, or competing old URLs still in index | Crawl for chains; check canonical consistency; request removal of old URLs |
Image traffic gone | Old image URLs return 404, images not re-indexed at new URLs | Add redirects from old /wp-content/uploads/ paths to new image URLs |
If traffic has not recovered within 30 days despite addressing all the above, the issue is likely content-related rather than migration-related. Google may be reassessing the content quality independent of the platform change. Use the SEO scorer to audit each affected page and address any optimization opportunities.
DNS and SSL: the invisible migration risks
Two technical details cause more migration issues than they should:
DNS propagation
When you change your domain's DNS records to point to the new platform, the change propagates globally over 1–48 hours. During this time, some visitors see the old site and others see the new site. Cloudflare-proxied domains avoid this problem entirely — when the domain is already proxied through Cloudflare, changing the origin server takes effect immediately because Cloudflare resolves the domain, not the visitor's DNS resolver.
SSL certificate timing
The new platform needs to provision an SSL certificate for your domain before it can serve HTTPS traffic. If DNS points to the new server before SSL is ready, visitors get a certificate error. Most platforms (including Modern Blogging and Cloudflare-based hosts) provision SSL automatically within seconds of the DNS change, but verify HTTPS works before announcing the migration.
Mixed content is the other SSL risk: if your post content references images or scripts via http:// (not https://), browsers will block them or show warnings. Search your post content for "http://" and update all references to "https://" or protocol-relative URLs (//) during migration.
The complete checklist (copy this)
Here is the full 25-step checklist in a format you can copy into your project management tool:
# | Step | Phase | Done? |
|---|---|---|---|
1 | Export Search Console data (16 months) | Pre-migration | ☐ |
2 | Crawl entire site, save URL inventory | Pre-migration | ☐ |
3 | Export XML sitemap | Pre-migration | ☐ |
4 | Export backlinks per URL | Pre-migration | ☐ |
5 | Document meta tags and structured data | Pre-migration | ☐ |
6 | Record Core Web Vitals baseline | Pre-migration | ☐ |
7 | Export existing redirect rules | Pre-migration | ☐ |
8 | Build 1:1 URL map (every old URL → new URL) | Redirect map | ☐ |
9 | Keep URLs identical wherever possible | Redirect map | ☐ |
10 | Classify each URL: keep, merge, or retire | Redirect map | ☐ |
11 | Use 301 permanent redirects only | Redirect map | ☐ |
12 | Eliminate all redirect chains | Redirect map | ☐ |
13 | No bulk homepage redirects | Redirect map | ☐ |
14 | Build on hidden staging domain (noindex) | Staging | ☐ |
15 | Verify content parity on all templates | Staging | ☐ |
16 | Carry over all meta tags | Staging | ☐ |
17 | Implement structured data (JSON-LD) | Staging | ☐ |
18 | Update internal links to new URLs | Staging | ☐ |
19 | Test every redirect on staging | Staging | ☐ |
20 | Launch during low-traffic window | Launch | ☐ |
21 | Remove noindex and update robots.txt | Launch | ☐ |
22 | Submit sitemap to GSC and Bing | Launch | ☐ |
23 | Daily 404 and crawl checks (week 1) | Monitoring | ☐ |
24 | Weekly traffic and ranking comparison | Monitoring | ☐ |
25 | Sign-off: zero new 404s, traffic within 5 % | Monitoring | ☐ |
The trailing slash problem (and how to fix it)
One of the most overlooked migration issues is trailing slash inconsistency. WordPress often serves pages both with and without trailing slashes (e.g., /my-post and /my-post/ resolve to the same content). Your new platform may enforce one format. If the canonical URL says /my-post/ but your sitemap lists /my-post and your redirects point to /my-post, Google sees three conflicting signals.
Before launch, decide on a trailing-slash policy and enforce it everywhere:
This sounds minor, but canonical confusion is one of the most common reasons Google takes longer to consolidate URLs after a migration. Getting it right from launch day saves weeks of indexing delay.
Image migration: the step most guides skip
Images have their own SEO value. Google Image Search drives meaningful traffic for many blogs, and images contribute to Core Web Vitals scores (they are often the Largest Contentful Paint element). A migration that handles text content perfectly but breaks images still loses traffic.
What to preserve
Image redirect strategy
If your WordPress images were at /wp-content/uploads/2024/08/image.jpg and your new platform hosts them at cdn.example.com/images/image.webp, you have two choices: redirect old image URLs to new ones (preserves image search equity), or accept that old image URLs will 404 (faster to implement, but loses image search traffic). For blogs where image search is significant, add the redirects.
The five mistakes that cause the most traffic loss
After auditing dozens of WordPress migrations, the same five mistakes account for the majority of ranking drops:
Platform-specific migration notes
WordPress to Modern Blogging
The automated import handles Steps 14–18 automatically: content import, image re-hosting, URL slug preservation, and meta tag generation. You still need to do the pre-migration audit (Steps 1–7), build the redirect map (Steps 8–13), and monitor post-launch (Steps 23–25). The built-in SEO scorer helps with Step 24 by flagging optimization opportunities on imported posts.
WordPress to WordPress (host change)
Host migrations are simpler because URLs, themes, and plugins stay the same. Your main risks are: database export/import errors (verify post count matches before and after), DNS propagation delays (use Cloudflare for instant switching), and SSL certificate provisioning (verify HTTPS works before switching DNS). One common trap is migrating with a different PHP version — the new host may run a newer PHP that breaks an older plugin, changing how certain pages render. Test the full site on the new host before switching DNS.
WordPress to headless CMS (generic)
Generic headless CMS migration adds the frontend development step, which is where most timelines expand from 1 week to 4–8 weeks. The SEO checklist is identical — the extra time is in building the frontend, not in the SEO work. See our complete WordPress to headless migration guide for the technical steps.
Recommended tools for migration SEO
Tool | What it does | Free tier? |
|---|---|---|
Google Search Console | Performance data, indexing status, 404 monitoring, sitemap submission | Yes — free |
Screaming Frog SEO Spider | Crawls URLs, checks redirects, exports meta data | Yes — 500 URL limit |
Ahrefs | Backlink data per URL, site audit, rank tracking | No — starts at $99/mo |
Google Rich Results Test | Validates structured data on any page | Yes — free |
PageSpeed Insights | Core Web Vitals measurement | Yes — free |
Modern Blogging SEO Scorer | Per-post SEO analysis (15 signals), improvement suggestions | Yes — included free |

The bottom line
WordPress SEO migration success is 80 % preparation and 20 % execution. If you do the pre-migration audit (Steps 1–7) and build a complete redirect map (Steps 8–13), the actual migration and monitoring are straightforward. If you skip the preparation, no amount of post-launch firefighting can fully recover what you lose.
The checklist above works for any WordPress migration — to another host, another CMS, or a headless blog platform . Modern Blogging automates the import and takes care of hosting, CDN, SSL, SEO metadata, and image optimization, but the redirect map and monitoring steps are still your responsibility. Start your free migration and use this checklist to protect every ranking you have earned.
If you want to understand the technical details of moving content out of WordPress, our WordPress to headless migration guide covers the REST API export, content model mapping, and both the manual and automated import paths.
Need help with your migration? The Modern Blogging importer connects to your WordPress REST API and transfers everything in 60 seconds. Try it free — no credit card required.