Skip to content

Migration Guides

How to Remove WordPress Without Losing SEO

How to reduce the risk to search traffic when leaving WordPress: URL mapping, redirects, metadata parity and post-launch monitoring, based on Google's guidance.

By
Paweł Szmidt
Published
9 min read

If you want to leave WordPress but worry about losing your Google rankings, that worry is reasonable: a careless migration can lose traffic. But the avoidable causes are well documented, and most of the list below comes down to one thing: search engines arriving at URLs that no longer lead where they used to.

This article covers the work that reduces that risk when you move from WordPress to a static website (or to anything else). It complements the step-by-step guide How to Convert WordPress to a Static Website, which covers the whole project.

What causes traffic loss in migrations

The avoidable causes of lost traffic fit on a short list:

  • URLs that changed without a redirect. The old address returns a 404. Google treats it as content that no longer exists, and over time crawls it less often. URLs that were already indexed and start returning a 404 are removed from the index.[4]
  • Redirects that point to the wrong place. Sending many old URLs to the homepage is something Google explicitly advises against.[1]
  • Redirect chains. Old URL → intermediate URL → new URL. Google advises redirecting straight to the final destination.[1]
  • Lost on-page metadata. Titles, descriptions, canonical tags or hreflang that existed in an SEO plugin and weren't carried over.
  • Missing pages. URLs nobody knew about (old landing pages, paginated archives, attachment pages) that still get visits or links.
  • Broken internal links pointing to the old host or to /wp-content/ paths that no longer exist.
  • A staging site that gets indexed, or a production site that launches with noindex still switched on.

None of these is caused by being static. They're caused by losing track of URLs and metadata during the move.

First, know which kind of move you're making

Google's documentation distinguishes two cases, and it helps to know which one you're in:

  • The URLs stay the same and only the hosting changes. Google calls this a site move without URL changes. It notes that a temporary drop in crawl rate right after launch is normal, and that crawling then rises again over the following days, as long as Googlebot doesn't hit serious slowdowns or errors.[2]
  • Some URLs change. Then the guide for site moves with URL changes applies: map old URLs to new ones and redirect them. Google says to expect temporary fluctuation in rankings during such a move, and that for a medium-sized site it can take a few weeks or more for the new URLs to show up.[1]

If you keep the same domain, you don't need Search Console's Change of Address tool. Google says it's only needed when moving from one domain or subdomain to another.[1]

The practical conclusion: the more URLs you keep identical, the closer your migration is to a simple hosting change. That's why our migration process makes "keep" the default in the URL map and "redirect" the exception.

Build a complete URL inventory

You can't protect URLs you don't know about. Collect them from several sources and merge the lists:

  1. Sitemaps. WordPress's core sitemap index lives at /wp-sitemap.xml (since WordPress 5.5);[8] SEO plugins usually add their own. Check /robots.txt for Sitemap: lines.
  2. A crawl of the live site, starting at the homepage. This catches paginated archives, author and date archives, attachment pages and old pages still linked from content.
  3. Search Console. Export pages with impressions or clicks. Its Performance report has an export function.[9] This is where you find URLs that matter but that nothing links to anymore.
  4. Analytics landing pages, if you use analytics.
  5. Backlinks to deep URLs, if you have a backlink tool. Links from other sites to specific articles or images are worth protecting.

Google also suggests starting the mapping with the most important URLs: those in sitemaps, those with the most traffic and those with links, and including images, videos, JavaScript and CSS files.[1]

The result is one file. Our process keeps it as a CSV with one row per old URL:

old_url,action,new_path,reason
https://example.com/about/,keep,/about/,
https://example.com/2023/05/post-name/,keep,/2023/05/post-name/,date permalinks kept
https://example.com/category/news/page/2/,redirect,/category/news/,pagination changed
https://example.com/post-name/attachment-1/,redirect,/post-name/,attachment page
https://example.com/old-offer/,drop,,removed by the owner

That file drives everything else: routing, the redirect file and the checks before and after launch.

Keep URLs identical where you can

Most WordPress URLs can be reproduced exactly on a static site. Watch the details:

  • Trailing slashes. If /about/ was the address, /about isn't the same URL. Configure the generator to match (in Next.js: trailingSlash: true).[10]
  • Date-based permalinks. /2023/05/post-name/ can be kept as is. There's no need to "clean them up" during a migration.
  • Category and tag bases. /category/news/ stays /category/news/ unless there's a strong reason to change it.
  • Image paths. Serving images from the same /wp-content/uploads/... paths keeps image links from other sites working without any redirects.
  • Feeds. Decide what /feed/ becomes. Redirect it to the new feed if your readers use RSS.

Redirect everything that changes

For every URL that can't stay identical:

  • Use permanent redirects. Google recommends permanent server-side redirects where possible. 301 and 308 mean the page has moved permanently, and Google uses a permanent redirect as a signal that the target should be the canonical URL.[3] Temporary redirects (302, 307) don't send that signal.[3]
  • One hop only. Redirect directly to the final page.[1] Google's crawlers follow up to 10 redirect hops,[4] but staying far below that keeps things simple and fast for everyone.
  • Redirect to the closest equivalent page, not to the homepage. Consolidating several old pages into one new page is fine; sending unrelated URLs to the homepage isn't.[1]
  • Let truly removed pages return 404. Google's indexing documentation says a 404 isn't necessarily a problem if a page was removed without a replacement, and that moved pages should get a 301.[5]
  • Keep the redirects for a long time. Google says to keep them as long as possible, generally at least one year.[1]

On a static host, redirects live in the hosting configuration, not in the site's code. On Cloudflare Pages, a _redirects file can hold up to 2,000 static and 100 dynamic rules; larger maps need Cloudflare's Bulk Redirects.[7] A rule without a status code defaults to 302, a temporary redirect, so write 301 on every rule.[7] Note that _redirects doesn't match query strings,[7] so old /?p=123 style links need a small function if they still get traffic or links. Generate the redirect file from your URL map rather than editing it by hand.

Attachment pages and other WordPress leftovers

Attachment pages are separate URLs for individual uploaded files. WordPress 6.4 switched them off by default for new installations, while existing sites kept them,[11] so an older site may still have one for every image. These pages usually have little content of their own; redirecting each one to the post that contains the file is usually the sensible choice. Make the same explicit decision for author archives, date archives (/2024/, /2024/05/) and paginated archives (/page/2/). /wp-admin/, /wp-login.php and /xmlrpc.php can simply return 404.

Carry over on-page SEO

What search engines see is the rendered <head> of each page, so capture it from the live site, page by page, before you switch anything off:

  • <title>
  • meta description
  • canonical URL (self-referencing, on the production domain)
  • meta robots: pages that were noindex stay noindex, or are dropped deliberately
  • H1
  • hreflang, for multilingual sites. Every language version must list itself and all other versions, and if two pages don't point to each other, Google ignores the annotations.[6]
  • structured data (JSON-LD): the same types present (Article, BreadcrumbList, Organization…) and valid
  • Open Graph image, where there was one
  • image alt text

Then compare old and new automatically, for every URL you kept. Our process requires a script that checks each field and produces a report of every difference. Each difference must be either fixed or listed as an intentional change. Launch happens only when there are zero unexplained differences.

This is also the moment to resist "while we're at it" changes. Rewriting all titles, merging articles and changing URLs in the same release makes it hard to tell what caused any change in traffic afterwards. Migrate first, improve afterwards.

Launch without surprises

  • Keep staging out of the index. Use a temporary hostname with noindex for the test copy.[2]
  • Lower the DNS TTL well before the switch. Google suggests a week or more.[2]
  • Check that Search Console verification survives the move.[2] If you verified with a file or meta tag, it has to exist on the new site too.
  • Remove noindex from production and confirm robots.txt allows crawling.[2]
  • Keep the old hosting running as a fallback. Google's advice for hosting moves is to shut the old provider down once its traffic reaches zero.[2]

After launch: what to watch, and for how long

On day one:

  • Crawl the full list of old URLs against the live site: every kept URL returns 200, every redirected URL returns exactly one 301 to a page that returns 200.
  • Submit the new sitemap in Search Console.[1]
  • Inspect a few key URLs with the URL Inspection tool.[2]

Over the following weeks:

  • Watch the 404 log on your host. Any old URL that shows up there was missing from the inventory; add a redirect quickly.
  • Watch the Page indexing report. "Not found (404)" and "Page with redirect" are the statuses to review.[5] Old URLs you redirected will appear under "Page with redirect": the redirecting URL itself isn't indexed, and its target is assessed on its own.[5]
  • Compare search traffic and indexed pages week by week. Google expects traffic to the old URLs to drop while traffic to the new ones grows.[1]
  • Re-run the old-URL crawl after about a week.

Plan for several weeks of monitoring, not one afternoon. Larger sites take longer.[1]

What nobody can promise

Nobody can guarantee your rankings after a migration, and you should be wary of anyone who does. Rankings depend on many things outside the migration itself, and Google says temporary fluctuation is to be expected during a move.[1]

What a careful migration can do is remove the avoidable causes of loss: no forgotten URLs, no wrong redirects, no missing metadata, no accidental noindex. Keeping URLs and metadata identical reduces the risk; it doesn't make it zero.

Want a second pair of eyes on your URLs?

If you're thinking about leaving WordPress but worried about search traffic, start with the URL inventory. That's where most risks become visible. Request a free audit and a person will review your site, including its URL structure and redirect needs, and tell you honestly what a migration would involve. For the bigger picture of what changes when you go static, read Why static?.

Sources

Information as of 22 October 2026.

  1. Google Search Central — Site moves with URL changes, last updated 20 August 2026.
  2. Google Search Central — Site moves without URL changes, last updated 10 December 2025.
  3. Google Search Central — Redirects and Google Search, last updated 14 April 2026.
  4. Google Search Central — How HTTP status codes, and network and DNS errors affect Google Search, last updated 4 February 2026.
  5. Search Console Help — Page indexing report, accessed 22 October 2026.
  6. Google Search Central — Tell Google about localized versions of your page, last updated 21 September 2026.
  7. Cloudflare Pages — Redirects, last updated 25 August 2026.
  8. Make WordPress Core — New XML Sitemaps Functionality in WordPress 5.5, 22 July 2020.
  9. Search Console Help — Performance report (Search results), accessed 22 October 2026.
  10. Next.js — How to create a static export, last updated 9 August 2026.
  11. Make WordPress Core — Changes to attachment pages, 16 October 2023.

Thinking about moving off WordPress?

Get a free, human review of your site and an honest answer about whether static is a good fit.

Get My Free Audit