A migration that loses traffic has often gone wrong weeks before launch, when nobody wrote down which URLs existed. My rule for every move: each old URL either lands somewhere sensible, or it's a deliberate 404. Content migrations have been part of my WordPress work through theme rebuilds and platform moves, and in November 2026 I moved this site off WordPress and onto Next.js. Where I can, the examples below come from that move.
This is the order I work in.
Why rankings drop after a move
Google ranks individual URLs, and each one builds up history: links from other sites, what Google has learned about the page, how people use it. Rankings fall when that history is lost. The usual causes:
- URLs change with no redirect, so old links and search results land on a 404.
- Everything changes at once: new URLs, new titles, new content and a new design. Google has to re-evaluate the whole site, and you can't tell which change caused a problem.
- Staging settings go live: a "noindex" tag, WordPress's "Discourage search engines" box, or a robots.txt that blocks everything.
- Lazy redirects: sending every old page to the home page. Google's own guidance warns that redirecting many old URLs to one irrelevant page "might be treated as a soft 404".
Before the move
1. List every URL that exists today
You can't redirect what you don't know about. Combine four sources, because each one misses things:
- The current XML sitemap.
- Search Console → Indexing → Pages: export both the indexed and the not-indexed lists.
- Search Console → Links → Top linked pages: the URLs other sites link to. These matter most, because those links are what you're protecting.
- A crawl of the live site with any SEO crawler, to catch pages that are linked but missing from the sitemap.
Don't forget the URLs WordPress makes on its own: category and tag archives, author pages, /feed/, paginated archives (/page/2/), and on older sites, attachment pages (new installs stopped creating them in WordPress 6.4).
2. Write down a baseline
Export the last three months from Search Console → Performance: top queries, top pages, clicks and impressions. Note how many pages are indexed. Without a baseline, you can't tell a normal post-move wobble from a real problem.
3. Map every old URL to a new one
A spreadsheet with three columns is enough: old URL, new URL, and what happens (301, unchanged, or a deliberate 404 or 410). Map page to matching page wherever possible. If a page has no direct equivalent, send it to the closest relevant page. If something is truly gone and has no replacement, let it 404 on purpose, rather than redirecting it somewhere unrelated.
4. Change one big thing at a time
If you're moving platforms, keep the titles, headings and body content of your important pages the same for the move itself. Redesign and rewrite afterwards, once the new URLs have settled. If rankings move, you'll know why.
5. Build on staging, blocked from search
Keep the staging site out of Google (WordPress's "Discourage search engines" setting, or password protection), and write down exactly how to undo it. Forgetting to undo it on launch day is an easy mistake, and it can keep the whole new site out of Google.
Moving the content
For WordPress to WordPress moves, use the built-in exporter, a migration plugin, or WP-CLI. Whichever you use, compare the counts before and after: posts, pages, media files, users, comments. A number that doesn't match tells you something was left behind.
If the domain changes, update the old domain inside the database with WP-CLI rather than a raw SQL find-and-replace. WordPress stores some settings as serialized PHP, which a plain text replacement can corrupt, and WP-CLI handles it safely. Do a dry run first:
wp search-replace 'https://old.example.com' 'https://new.example.com' --skip-columns=guid --dry-run
Remove --dry-run once the report looks right. The guid column is skipped on purpose: WordPress uses it as a permanent ID for each post, and feed readers rely on it not changing.
If you can keep the same permalink structure (Settings → Permalinks), do. Every URL that doesn't change is a redirect you don't need.
Redirects
Use permanent redirects (301 or 308), one hop each, from each old page to its matching new page. Google can follow a chain of several redirects, but recommends avoiding chains.
On WordPress, the Redirection plugin manages them from the dashboard. At the server level:
# Apache: .htaccess
Redirect 301 /old-page/ https://example.com/new-page/
# Nginx: inside your server block
location = /old-page/ {
return 301 https://example.com/new-page/;
}
When this site moved from WordPress to Next.js, the old WordPress URLs that had no direct replacement went into one list in the codebase, each pointing at the closest new page:
// an excerpt of this site's redirects (config/edge.mjs), sent as 301s
export const legacyRedirects = [
{ source: "/website-design", destination: "/services" },
{ source: "/appointment", destination: "/contact" },
{ source: "/shop/:path*", destination: "/services" },
{ source: "/feed/:path*", destination: "/rss.xml" },
];
Keep redirects in place for a long time. Google's site-move guide says "generally at least 1 year", so it can transfer signals, including links from other sites, to the new URLs.
Launch day
- Unblock search engines. Untick "Discourage search engines" (Settings → Reading), remove any noindex tags, and check robots.txt. If robots.txt blocks an old URL, Google can't crawl it, so it never sees the redirect.
- Test the redirects. Check your most important old URLs one by one. Each should return a 301 and point straight at the right page:
curl -sI https://example.com/old-page/ | grep -i -E "^HTTP|^location"
- Update your own links. Internal links, menus and canonical tags should point at the new URLs directly, not rely on redirects.
- Submit the new sitemap in Search Console. If the domain changed, also use the Change of Address tool. It's only needed when moving to a new domain or subdomain.
- Request indexing for a handful of your most important pages with Search Console's URL Inspection tool.
The first few weeks
Watch Search Console → Pages → "Not found (404)". This is where the URLs you missed show up. Just before this site's switch, Search Console listed 18 pages as indexed and 25 as not indexed, and four of those were 404s: /shop/, /feed/, an old /design-system page, and /&, a malformed address Google had picked up from a broken link somewhere. Each now redirects to its closest new page (the malformed one goes to the home page), and "Validate fix" in that report asks Google to check them again.
Compare Performance against your baseline every week. Some movement is normal. Google says that for a medium-sized site "it can take a few weeks or more" for the new URLs to replace the old ones in results, and longer for big sites.
Update the links you control: your social profiles, directory listings, email signatures and any partner sites. A direct link is better than one that goes through a redirect.
Common questions
How long does it take for rankings to recover?
Google's guidance is a few weeks or more for a medium-sized site, and longer for larger ones. If clicks are still well below your baseline after a couple of months, go back to the 404 report and your redirect map: a missing or wrong redirect on a high-traffic page is the usual cause.
Should I use a 301 or a 302 redirect?
A 301 (or 308) for a permanent move. A 302 tells search engines the move is temporary, so they may keep showing the old URL.
Do I need the Change of Address tool?
Only if the domain or subdomain changes, for example example.com to example.net. Moving to a new platform, theme or URL structure on the same domain doesn't need it.
Can I just redirect everything to the home page?
No. Google may treat a pile of unrelated redirects to the home page as soft 404s, and visitors lose the page they were looking for. Redirect each page to its closest match, and let truly removed pages 404.
More on how I work
Migrations are part of my WordPress work, alongside theme builds and security hardening. See the content migration case study and the WordPress security hardening checklist. Hiring for a WordPress role? Get in touch.

Written by Devang Patel
Full-stack product engineer in Vadodara, India. I build the things I write about.