# How do I migrate my WordPress site without losing SEO? > Migrate without losing SEO by preserving two things: your URLs and your content. Inventory every URL the live site exposes, keep the same paths wherever possible, carry titles, descriptions and schema across unchanged, and set a single-hop 301 for every address that has to change. Do the inventory before you build the new site, not after, because every later step depends on it. WPBuildAI scans the live site and produces the URL inventory, redirect map and metadata export the migration runs on, so nothing ranked is left behind. Source: https://wpbuildai.com/migrate-wordpress-without-losing-seo/ By lawrence-arya ยท 2026-06-28 --- You migrate a WordPress site without losing SEO by preserving two things: your URLs and your content. Everything else in a migration is detail in service of that. Rankings attach to specific addresses and to the content on them, so if both survive the move intact, the rankings survive too. The single most important rule is to inventory every URL the live site exposes before you build anything new, because every later step, the redirects, the metadata, the verification, depends on knowing exactly what exists. WPBuildAI scans the live site and produces the URL inventory, redirect map, and metadata export the migration runs on, so nothing that ranks is left behind by accident. ## Why migrations lose SEO, and why they do not have to Migrations lose rankings for mechanical reasons, not mysterious ones. URLs change and are not redirected, so ranked pages become 404s. Metadata is rebuilt from scratch, so on-page signals reset. Internal links are not recreated, so the structure flattens. Pages are quietly left behind, so content thins. None of these is caused by the new platform being worse: Backlinko's review of [11.8 million search results](https://backlinko.com/search-engine-ranking) found rankings track content, links, and authority, not the CMS. That is the good news, because it means an SEO-safe migration is a process you can follow, not luck. Get the URLs and content across faithfully and the platform underneath is free to change. ## The one principle: preserve URLs and content Hold onto one idea and the checklist writes itself: keep the URLs and keep the content. Keeping URLs means using the same paths on the new site wherever you can, so most pages do not move at all and need no redirect. Keeping content means carrying the page bodies, media, headings, and metadata across without thinning them. Where a URL genuinely must change, a single-hop 301 preserves its equity. This matters more than it looks because of how traffic concentrates. The Ahrefs [search traffic study](https://ahrefs.com/blog/search-traffic-study/) found a small share of pages earns most organic visits, so the goal is not just to redirect everything, it is to be certain the high-value URLs are handled exactly right. ## The 10-step SEO-safe migration checklist 1. **Inventory every URL** from the sitemap, internal links, and Search Console. 2. **Export the content and media** in a format the new platform imports, with alt text intact. 3. **Export the metadata:** titles, descriptions, canonicals, and schema. 4. **Design the new URLs** to match the old paths wherever possible. 5. **Build the redirect map:** every changed URL to its exact new counterpart, single hop. 6. **Rebuild on staging** with content, metadata, and internal links recreated. 7. **Keep staging noindex** so it is not indexed before launch. 8. **Verify parity on staging:** URLs, titles, H1s, canonicals, redirects. 9. **Launch, remove the staging noindex,** apply redirects, and resubmit the sitemap. 10. **Monitor Search Console** for 404s and indexed-page counts, and fix gaps fast. The order is the method. Steps 1 to 3 are the inventory, and they come first because steps 4 onward are impossible without them. ## Building the URL inventory The inventory is the foundation, and it is bigger than most owners expect. A site exposes more URLs than appear in its menu: paginated archives, category and tag pages, author pages, attachment pages, old campaign URLs, and PDFs. Combine three sources to catch them all, a full crawl, the XML sitemap, and Search Console's record of URLs that actually receive clicks, because each source sees URLs the others miss. The technique for pulling a complete list is covered in [finding and extracting all URLs on a website](/find-extract-all-urls-website-301-redirects/). The URLs that earn traffic but hide outside the menu are exactly the ones a rushed migration drops, so the inventory is where rankings are saved or lost. ## The redirect map The redirect map pairs every old URL with its exact new address, and its quality decides whether equity transfers. Google's [site move guidance](https://developers.google.com/search/docs/crawling-indexing/site-move-with-url-changes) describes this map as the heart of a safe move. Two rules keep it clean: each redirect is a single hop, landing directly on the destination rather than on another redirect, and each points to the true counterpart, not a generic page, because a bulk redirect to the homepage reads as a soft 404. Use permanent 301s, per Google's [redirects guidance](https://developers.google.com/search/docs/crawling-indexing/301-redirects), and for larger sites build the map systematically rather than by hand, as in [mapping 301 redirects in bulk](/how-do-i-map-301-redirects-for-e-commerce-site-bulk/). ## Metadata and content parity Parity means the new pages carry the same ranking signals as the old ones. Titles, meta descriptions, canonical tags, and structured data are inputs you tuned over time, and a fresh build starts with none of them. So export them with the content and map them field by field into the new system, the discipline covered in [exporting Yoast SEO data](/export-yoast-seo-data-leaving-wordpress/). Content parity is the matching half: every page, section, image, and caption that existed should exist after the move, not a simplified subset. Thinner pages rank worse and missing pages rank not at all, so parity is checked page by page against the inventory, not assumed from a glance at the new design. ## What to check on staging before launch Staging is your last chance to catch problems while they are cheap. Confirm the new URLs match the intended paths, the titles and H1s carry across, the canonicals point at the right addresses, and the redirects resolve in a single hop using a tool that reports the chain, as in [checking that 301 redirects work correctly](/check-if-301-redirects-are-working-correctly/). Crucially, confirm staging itself is noindex so search engines have not indexed your work-in-progress, and make a note to remove that noindex at launch. A staging review that takes an afternoon prevents the launch-day mistakes that take weeks to recover from. ## What to monitor after launch Launch is the start of a short settling period, not the finish line. After you go live, remove the staging noindex, apply the redirects, and resubmit the sitemap, then watch two numbers in Search Console: the 404 count and the number of indexed pages. If 404s appear, they point to URLs your inventory missed, and you redirect them as they surface. If indexed pages recover toward the old total over the following weeks, the transfer held. Some ranking wobble during the recrawl is normal; a sustained climb in 404s with falling impressions is the signal that a batch of URLs is missing a redirect and needs attention now. ## A worked example A 250-page WordPress site moved hosts and platforms. The team inventoried first and found 250 pages plus 90 archive, tag, and old campaign URLs, around 30 of which still earned traffic. They exported content, media, and metadata, designed the new site to reuse the old paths so most URLs did not move, and built a redirect map for the 60 that did. On staging they verified titles, canonicals, and single-hop redirects, with noindex on. At launch they removed noindex, applied the redirects, and resubmitted the sitemap. A dozen 404s surfaced over the next week from URLs the crawl had missed, were redirected within a day, and rankings held with only brief movement. The migration was uneventful because the inventory was complete before the build began. ## Common mistakes - Building the new site first and inventorying URLs last, so redirects are an afterthought. - Redirecting old URLs to the homepage instead of their true counterparts. - Rebuilding pages without their titles, descriptions, and schema. - Launching with the staging noindex still applied, which deindexes the live site. - Treating launch as the end and not monitoring Search Console for the weeks that follow. ## Key points to remember To migrate WordPress without losing SEO, preserve the URLs and the content, and do the inventory before you build. Keep the same paths where you can, carry the metadata and internal links across, and set a single-hop 301 for every URL that changes. Verify parity and redirects on staging with noindex on, launch, resubmit the sitemap, and watch Search Console for 404s and indexed pages. The platform does not rank, so a complete, verified transfer keeps your rankings whatever you move to. WPBuildAI scans the live site and produces the inventory, redirect map, and metadata export, so the migration runs on facts rather than hope. Send your site URL for a free migration assessment. Not affiliated with WordPress, Lovable, Webflow, Shopify, Wix, or Squarespace.