← All notes
April 2026 Notes / 02 6 min read

Killing WordPress without killing your Google rankings.

The fear is reasonable. You've got a WordPress site that has been gathering rankings for three years. The product pages have backlinks. The fitting page sits on the first results page for "saddle fitter near me". The idea of switching the entire site to a different platform feels like asking Google to start the relationship over.

So the assumption is: stay on WordPress, or accept a six-month dip in traffic. Neither is actually true.


Google ranks URLs, not platforms. If the URL still works, the content is still on it, and the page loads at least as fast as before, the ranking carries across. Migrating off WordPress without breaking any of those three constraints is a solved problem.

The mechanism is the HTTP 301 redirect. Every existing WordPress URL gets a permanent redirect to its new equivalent. So /product-category/dressage-saddles/ on the WordPress site becomes a redirect to /saddles/dressage/ on the new site. Google reads the redirect, follows it once, and transfers the ranking signal across. The transfer typically completes inside seven to fourteen days, during which Search Console will usually show a small dip and then a recovery to or above the previous level.

The catch that catches most rebuilds is forgetting a URL. If Google has indexed /shop/wintec-500/ but the new site has no redirect for it, the URL stops working and that page's ranking is lost. The dropped pages are nearly always the long-tail product detail URLs that don't appear in the sitemap, so they're easy to miss.

The fix is mechanical. Pull the full URL list from Search Console before cutover. Cross-reference with the WordPress sitemap and the actual permalink structure. Map every entry to its new equivalent. For pages that are being retired entirely, redirect to the closest topical alternative, not the homepage. (Redirecting everything to the homepage is the single most common mistake in a botched migration.)


Page speed is the second concern. Google rewards fast pages, partly because faster pages keep more visitors on the site, and partly through Core Web Vitals as a direct ranking signal.

WordPress sites are usually slow because every visit boots PHP, runs MySQL queries, walks through plugin hooks, and renders HTML on the server before the response even leaves the building. A site rebuilt in Astro and served from the edge has none of that boot cost. The HTML for every page is built ahead of time and served as a static file from the server closest to the visitor. Click-to-visible typically drops from three or four seconds on the old WordPress site to under one hundred milliseconds on the new build. Google notices, and so do customers.


The third concern is structured data. This is the small piece of hidden information on each product page that tells Google the price, the stock state, the brand and the rating. With structured data, your saddles are eligible for Google Shopping free listings and your search results show stars and prices alongside the title. Without it, you get the plain blue link.

Most WordPress product sites need a plugin to emit structured data. Most don't have the plugin configured correctly. The Yoast SEO plugin alone doesn't do it. The Uncode theme that a lot of saddle and bike sites use doesn't do it either. A modern Astro build writes the structured data into every product page automatically, from the same content collection that powers the product listing. Eligible from launch day, with no plugin involved.


So the practical playbook for a WordPress migration is short. Pull the URL list. Add the 301 redirects. Add the structured data. Cut over the DNS during a low-traffic window. Pause Google Ads for four hours so paid clicks don't land on a half-deployed site. Monitor Search Console daily for two weeks. Rankings recover inside fourteen days, usually higher than where they started, because the site is now faster and structurally richer than it was.

The Lonsdale migration is on the public web. The Saddle Central proposal walks the same process step by step. Neither lost a ranking.

The right time to leave WordPress is not "when the rankings are no longer at stake". The right time is now, with the rankings at stake, and the right plan in hand.

Got a WordPress site you want to leave?

Start a project