WebzstoreIf this is true
Editors like the WordPress screens and use them daily
We lean towards
Keeping WordPress as a headless CMS (a content store with no public front end)
WordPress to Astro Migration
WordPress to Astro Migration
We rebuild WordPress websites as Astro sites, and we help you decide whether WordPress stays behind the scenes as the editing screen or is retired. Astro is a framework for building websites. It is not a CMS (the screen where your team edits content), so the editing plan is part of the project from the first call.
01Choose
Choose what you want to change
Do you want to keep WordPress for editing, replace it, or rebuild the interactive features? Pick one part, several, or the whole project and the plan will adjust.
Where this startsWe want a faster Astro front end, but our team likes WordPress and we run plugins we cannot lose.
In plain terms
- Headless
- WordPress or another system stores content, while a separate front end shows it to visitors.
- API
- The doorway that lets one piece of software request content from another.
- Redirect map
- A list that sends visitors from each old address to its new one.
- Custom post type
- A content type added to WordPress, such as Events or Team members.
- CMS
- The editing screen where your team writes and updates content.
- Front end
- The part of the website that visitors see and use.
02Decide
Should WordPress stay or go?
Answer these questions about your team first. The answers point towards one route.
If this is true
Pages rely on many plugins
We lean towards
Replacing WordPress, after checking each plugin
If this is true
Content changes a few times a year
We lean towards
Content kept in files inside the Astro project
If this is true
You want fixed fields, roles and approval steps
We lean towards
A different headless CMS, compared in advance
Our Headless CMS Development service covers that comparison.
03API reach
Find out what the WordPress API can actually reach
Astro can read WordPress content through the REST API (the doorway other software uses to request your posts and pages). Standard posts and pages are available there by default. Other content needs checking:
- A custom post type (a content type such as Events or Team) appears only if it was registered with show_in_rest turned on
- Plugin-generated content, such as page-builder layouts, form entries, custom fields and SEO-plugin fields, is not confirmed to be exposed
- Shortcodes (short tags that plugins turn into features) will not run in Astro and need replacing
- Menus and media files are mapped one by one, since neither arrives as part of a post
Each plugin is checked in the audit, because each registers its data in its own way.
04Publishing
Rehearse the editing and publishing loop
Astro builds pages ahead of time by default. A new post therefore shows only after a rebuild, unless the page is set to render on demand, when a visitor asks for it. We agree which method fits each page type and who triggers it.
Then we rehearse. An editor writes a draft, publishes it and times how long the live page takes to change. We also test a custom post type, a plugin-driven page, a form and the mobile layout. If the wait is too long for your team, we change the method before launch.
05Redirects
Plan the redirects and keep WordPress healthy
Old WordPress addresses need a redirect map (a list that sends visitors from each old address to its new one). Astro lets us list these in its configuration, but a static build without an adapter (the add-on that lets Astro run on a host with server code) forwards visitors with a meta refresh and cannot send status codes. We plan permanent redirects at the hosting or adapter layer and check the real response for each old address. A page file at the same address takes precedence, so we check for clashes.
If WordPress stays headless, it must keep running, with its updates applied, behind the new site. We agree the hosting and who looks after it. Keep the redirects in place for as long as you can, and monitor search performance after launch, since nothing here promises rankings. See Headless CMS Migration if you want a different content system.
Questions about moving WordPress to Astro
Can I keep the WordPress admin screen?
Yes. WordPress can feed content to Astro as a headless CMS, if its content types are exposed to the API.
Will my plugins still work?
Not automatically. Plugins that output pages or features in WordPress do not run in Astro, so each one is kept, replaced or dropped.
Will my content change appear straight away?
It depends on the page type. Pre-built pages need a rebuild first, and on-demand pages are made at each visit.
Will the move improve my rankings?
We cannot say. Search performance may fluctuate after a move, so we monitor it and do not promise a result.
Choose your editing route before the build
Send us your site address, your plugin list and the names of the people who publish. We will assess which route fits and what must be rebuilt.
Explore the next step
- Website Migration ServicesExplore website migration services with Webzstore. Plan your content, features and launch, then discuss the project on a free 30-minute call.
- Headless CMS DevelopmentExplore headless cms development with Webzstore. Plan your existing content, features and launch, then discuss the project on a free 30-minute call.
- Headless CMS MigrationExplore headless cms migration with Webzstore. Plan your existing content, features and launch, then discuss the project on a free 30-minute call.