Migrating from WordPress Without Losing SEO: Step-by-Step Guide

You have decided to move a site that has run on WordPress for years to a faster, more secure or more flexible platform. The new design is ready and the team is keen to launch. The problem that shows up most often in these projects is a sharp drop in organic traffic a few weeks after go-live, and the cause is nearly always the same: old URLs were not properly connected to new ones, or content and metadata were lost along the way. Protecting SEO during a WordPress migration comes down to a clear plan and doing things in the right order. This guide walks through those steps.

Why sites lose traffic during a migration

Over the years Google has learned your URLs and attached links and user signals to them. When those addresses change on the new site and are not redirected, all of that history runs into 404 errors. Visitors following old bookmarks and external links hit dead pages too.

Other common causes include page titles and descriptions not being carried over, broken internal links, trimmed content, a staging noindex tag that makes it to production, and a new site that is slower than the old one. All of them can be prevented with planning.

1. Record where you are now

Before migrating, take a complete snapshot of the current site. It is the foundation of your redirect map and the baseline you will compare against after launch.

• Crawl the whole site with an SEO crawler and export URLs, titles, descriptions, H1s and status codes.
• Download twelve months of page-level clicks and impressions from Google Search Console.
• List the top organic landing pages in GA4.
• Identify pages with external backlinks using a backlink tool.
• Back up the XML sitemap, robots.txt and structured data.
• Note current rankings for your key search terms.

2. Do not forget WordPress-specific URLs

WordPress generates many URLs without you noticing, and some of them may be indexed or have earned links. When building your inventory, look beyond posts and pages:

• Category and tag archives (/category/…, /tag/…).
• Author pages (/author/…) and date archives.
• Pagination URLs (/page/2/).
• Attachment pages and images or PDFs under /wp-content/uploads/.
• Short links such as ?p=123 and feed URLs (/feed/).
• If you run WooCommerce, product, product category and shop pages.

3. Build the redirect map

A redirect map is a table that pairs every old URL with the most relevant URL on the new site. It is the heart of the migration and needs the most effort.

The ground rules: use 301 redirects for permanent moves. Send each old page to the closest equivalent new page; redirecting everything to the homepage is often treated by Google as a soft 404 and throws away that page’s value. Avoid chains: rather than A to B to C, point A straight at C. Pages with no real equivalent, no traffic and no links can return 404 or 410.

Keeping the URL structure unchanged is the safest route. If you have to change it, for example moving from dated post URLs to clean slugs, combine pattern-based rules with one-to-one redirects and test every rule.

4. Move content and metadata in full

A redesign often comes with the urge to shorten copy or merge pages. Make that decision deliberately; cutting a well-ranking page in half puts its rankings at risk.

Export the SEO titles and meta descriptions set in plugins such as Yoast or Rank Math and import them into the new system. Add image alt text, H1 and subheading structure, canonical tags, structured data (Organization, Article, Product, FAQ and so on) and, on multilingual sites, hreflang to the list. Finally, update internal links in your content to point to the new URLs; even when redirects work, direct links are cleaner.

5. Test on staging

Run the new site on a staging environment before launch, and protect it with a password; noindex alone is not enough because links can leak. Use a crawler to bulk-test the redirect map on staging: every old URL should reach the right target in a single 301 hop.

Check page speed, mobile layout, forms and tracking (GA4, Google Tag Manager, ad pixels) at this stage too.

6. Launch-day checklist

If you can, launch on your lowest-traffic day and make sure the team is available throughout.

• Confirm that the staging noindex and password protection are gone on the live site.
• Check that robots.txt is not blocking important sections.
• Re-crawl the redirects on the live site.
• Submit the new XML sitemap in Search Console.
• Make sure HTTP, HTTPS, www and non-www all resolve to a single version.
• Confirm GA4 and Search Console are still receiving data.
• If the domain changed too, use the Change of Address tool in Search Console.

7. The weeks after launch

Some ranking fluctuation after a migration is normal while Google recrawls and understands the new structure. What matters is that the dip does not turn into a lasting decline.

In the first weeks, check the page indexing report and 404 errors in Search Console daily and add any missed URLs to the redirect map. Compare rankings and organic traffic for your top pages with the pre-migration baseline. Contact sites whose important links still point to old URLs and ask them to update. Google’s site move documentation recommends keeping redirects in place for as long as possible, generally at least one year; in practice, leaving them permanently is the safest choice.

Do you have to leave WordPress completely?

In some projects a headless setup makes more sense than leaving WordPress entirely. The content team keeps the WordPress dashboard they know, while the front end visitors see is rebuilt on a modern, fast stack. Keeping URLs and content structure largely intact lowers the risk. At Norcored we plan the redirect map and SEO checks from day one on both full migrations and headless WordPress projects, and we can run a pre-migration review of your site if that would help.

FAQ

How long does a traffic dip last after migration?

With a well-planned migration, short-term fluctuation is normal and usually settles as Google recrawls the site. A long-lasting drop usually points to missing redirects, lost content or a technical block.

Can I redirect all old pages to the homepage?

It is not recommended. Google often treats mass redirects like this as soft 404s and the page’s accumulated value is not passed on. Redirect each page to its closest equivalent.

Can I migrate without changing the URL structure?

Often, yes. If the new platform supports flexible routing, keeping your existing URLs exactly as they are is the lowest-risk way to migrate.