WordPress to Astro migration, with every permalink redirected
We pull your posts, pages and custom post types out of WordPress, keep them as files with a schema, and map every permalink to its new address with a permanent redirect. No plugin stack and no WordPress to update afterwards. You see the plan before we start.We move your posts, pages and custom post types out of WordPress into Astro, and redirect every old permalink.
- Every WordPress URL mapped
- Plugins matched or retired
- Fixed scope
- WordPress contentPosts, pages and custom post types out through the REST API and the export file
REST + XML - Content files in GitCategories, tags, authors and SEO fields kept, checked against a schema
content collections - Astro pagesA static page for each item, with images processed by Astro
build - Redirect mapYour permalink structure answered with permanent redirects
301
- A small custom piece
- A form endpoint
- Not needed any more
Teams we've worked with
Six things we plan for
Getting content out of WordPress is easy. Getting all of it, with the right URLs, takes more care.
Redirects that are only a meta refresh
In Astro's static output, redirects become HTML files with a meta refresh tag. Google prefers permanent server-side redirects, so we serve the 301s from the host and test each one.
Only the first page of posts comes out
WordPress returns 10 items per request unless you ask for the next page. We page through all of them and check the count against your dashboard.
Custom post types and fields are missing
Types beyond posts and pages have to be exposed to the REST API before Astro can read them. We expose them, or use the export file, so nothing your plugins stored is left behind.
Drafts and private posts mixed in
The posts endpoint returns published items by default, with drafts, pending and private as separate statuses. We choose what moves, and you sign it off.
Permalinks that don't match
A WordPress site can use plain /?p=123 links, day and name, post name or a custom structure, and categories sit under /category/ by default. We read yours and build the redirect map from it.
Forms that need a server
A plugin form won't come across. In Astro, form actions need pages rendered on demand, so we send forms to a small endpoint instead, with spam checks, and on to your CRM.
A site with nothing to update every week
Your content as files, your URLs kept, and no plugin stack.
All your content moved
Posts, pages and custom post types pulled from WordPress, with categories, tags and authors, and checked against the live pages.
Content as files with a schema
Astro content collections hold Markdown, MDX or JSON files, checked against a schema, so missing fields fail the build.
Static pages from your data
Astro builds a page for each item with getStaticPaths, so a static site needs no WordPress running to serve them.
A redirect map
Every WordPress URL mapped to its new page and served as a permanent redirect.
Images optimised
Images moved into the project so Astro can resize them and set width and height. Files in public/ aren't processed.
SEO fields carried over
Titles and descriptions from your SEO plugin, page by page, plus a sitemap built with the site and sent to Google on launch day.
Forms and tracking
Rebuilt to post to your CRM, with a test enquiry and a check on GA4, Google Ads and Meta.
An editor your team can use
Keystatic edits saved as commits, as on our own site. A new section type needs a developer.
What we connect the Astro site to
The new site replaces a lot of plugins. These are the tools that take over, and what passes along each wire.
Once WordPress is gone, so are its form and analytics plugins. We rebuild the tracking and the form hand-off beside the new site.
Who this is for
For you if
- Your WordPress site has become slow or fragile and you're tired of plugin updates.
- You need something WordPress makes awkward: pages built from data, forms into your own systems, or content in Git.
- You want the people moving you to have moved their own site.
Not for you if
- Your team wants to redesign pages visually. That's Webflow, and we'll say so.
- You want to stay on WordPress. We only move sites off it.
- You run a WooCommerce shop. That's Shopify.
What changes when you move
WordPress builds pages when someone visits. Astro builds them once, ahead of time.
| What matters |  Astro and KeystaticOur pick | WordPress |
|---|---|---|
| Where content lives | Files in your repo: Markdown, MDX or JSON with a schema. | A database behind WordPress, readable through the REST API at /wp-json/wp/v2/. |
| Reading content out | Not needed once moved. | REST API without authentication by default, 10 items per request by default. |
| Page addresses | Routes from your files, plus the redirects you define. | A permalink structure you choose; default plain /?p=123. |
| Forms | Astro Actions need on-demand rendering. | Usually a forms plugin. |
| Images | Optimised if kept in the project. | Depends on your theme and plugins. |
| Editing | Fields and blocks in Keystatic. | The WordPress admin. |
Sources: Astro, WordPress and Pacing pages, checked 16 October 2026. We don't quote prices: check their pricing pages.
What happens after you get in touch
Short call
You tell us how many posts, custom post types and plugins you have, and what you want the new site to do.
Export and plugin list
We pull everything through the REST API and the export file, and list every plugin and what it was quietly doing.
Write the plan
You get the permalink map, which plugins are retired or rebuilt, who looks after hosting and a timeline in writing, before we start.
Build and compare
We build the Astro site and check each page against the live WordPress one, with redirects tested before launch.
Launch and watch
The 301s go live, Google gets the new sitemap, and we read Search Console and your leads every day for two weeks.
Work we can show you
We rebuilt our own site in Astro in October 2026 and checked every live URL against the new build before we switched over. The destination, the redirects and the checks are the same ones we'd use on yours.
372
addresses on our old site checked against the new build
113
redirects from old addresses to their new pages
Pacing's own move from Webflow to Astro, live 13 October 2026, not a WordPress move.
Questions people ask before booking
Straight answers, so you know what to expect.
Still have a question?
Book a callWhy move a WordPress site to Astro?
We move your content into files on the new site, so there is no WordPress and no plugin stack to keep updated. If your team wants a visual editor, we'll say so on the first call.
Will we lose our Google rankings?
We can't promise that, and nobody honest can. Google says to expect temporary fluctuation during a move. We map every WordPress URL to its new page with a permanent redirect and check Search Console daily for two weeks.
Do we keep WordPress running as the CMS?
No. We move your content into files in the new site, so there's no WordPress to keep updated.
Why Astro rather than Webflow?
If your team edits pages every week and wants a visual editor, Webflow. If the site needs custom logic, pages built from data or content in Git, Astro. We'll say which fits yours on the first call.
Where does the sitemap come from?
Astro's sitemap integration, which writes sitemap-index.xml on every build once the site's address is set in the config. We read it for stray old addresses and send it to Google on launch day.
Will our blog URLs stay the same?
Where we can, yes. Where they must change, we redirect each old URL to its new one and test it.
How long does it take?
A WordPress to Astro migration used to take months. Now it can take weeks, or even days. The biggest factor is how quickly your team can review the work and give feedback. You'll see the timeline in the written plan before we start.
Tell us about your WordPress site.
How many posts and custom post types, which plugins matter, and what the site should do next.
- You'll talk to Ben or Cam, the people who do the work.
- We'll reply within one working day.
Get a WordPress to Astro plan
Send us your WordPress site's address and we'll tell you on the call what we'd check first.
Every WordPress URL mapped · Plugins matched or retired · Fixed scope