Migrating WordPress to Astro on Cloudflare without losing URLs or rankings

Not if every old address is carried over or redirected and the content stays equivalent. Rankings usually drop in a migration because URLs were lost, and that is the avoidable part. We cannot promise where Google will place you, but we can promise no lost addresses, and we check it.

The process is the same every time: archive the old sitemap, map every old URL to a new page, redirect every address that changes or disappears, and compare the old list against the new site after launch.

We write a permanent (301) redirect for every old address that does not exist on the new site. A 301 tells Google and visitors that the page has moved for good, so links and ranking signals follow it to the new page.

1. Archive the old site's sitemap while the old site still answers, so there is a fixed record of every address.
2. Map each old address to its new page, or to the closest relevant page when it no longer exists.
3. Redirect each one with a 301. Tag and category archives usually point to the blog index; one-off pages are redirected individually.
4. After launch, compare the archived list against the live site. Any address that returns a 404 gets a redirect before we call the job done.

This site is the example. Glivera Team ran on WordPress and now runs on Astro and Cloudflare, and the old WordPress addresses still redirect to the right pages.

For speed, fewer things to maintain, and low running cost. An Astro site is built ahead of time and served from Cloudflare's network, instead of being assembled by a database on every visit. There are no plugins to keep updating and no server software to patch.

The trade-off is real: the editing experience changes, and anything that depended on a WordPress plugin has to be replaced on purpose. We go through both before you commit.

Yes. The content moves into a CMS, we use Sanity, where your team edits text, images, links, menus and contact details by clicking, not by touching code. Nothing that is content or data is hard-wired into the pages.

We set it up so publishing a change rebuilds the site and puts it live. Editors work in a friendly structure organised by page, so nobody has to type a URL or know a slug.

Yes, if you want it to. We measure the live site's spacing, fonts and colours and rebuild by those numbers, then compare old and new side by side on desktop and mobile until no visible difference is left.

A redesign is a separate decision. We keep the two apart on purpose, because changing the design and the platform at once makes it hard to tell what moved your rankings.

Forms are reconnected to your CRM or inbox, and each plugin is replaced case by case: SEO fields become CMS fields, and contact forms post straight into your tools. We list every plugin on your site at the start and tell you what replaces it.

A full online shop with a large catalogue is a different project, and we scope it separately. If a WordPress setup is the right home for your shop, we say so.

We crawl every internal link on the new site, compare the archived old sitemap against it, and compare content page by page with the old site. Dead links and missing pages get fixed before we call the migration finished.

On a recent rebuild of three public sites for a European online-prescription business, this process ended with 0 dead links across 4,772 checked and zero lost web addresses.

glivera-team.com was a WordPress site. It now runs on Astro and Cloudflare, with the old WordPress addresses redirected and all content editable in a CMS. For an online-prescription business we rebuilt and relaunched three public sites with 0 dead links across 4,772 checked and zero lost web addresses.

Read the full case study →

Clutch Top Company 2023 · Upwork Top Rated, $500K+ delivered · Fortune 500 work delivered under NDA. We do not demo. We deploy, with tests, monitoring, and documentation, the same way we have shipped 200+ times.