WordPress migration to Next.js or AstroMove off WordPress.
Next.js or Astro with a headless CMS, or WordPress kept as one. Posts, permalinks, and SEO stay intact.
- Free assessment, fixed price in writing
- Redirect map before any code
- Search Console checks at launch, day 30, and day 60
How do you migrate from WordPress without losing SEO?
Keep the permalinks and carry over everything your SEO plugin stored. Keep WordPress headless and no URL has to change at all.
- /pricing-guide/1,320
- /2024/05/launch-week/690
- /category/news/260
- /author/ana/60
- /launch-week/attachment/hero/10
● Top 3 URLs bring 97% of clicks. They’re protected first.
Illustrative example
Every indexed URL from Search Console, the sitemap, and a full crawl, ranked by clicks and backlinks. Posts, pages, custom post types, and media are read through the WordPress REST API.
Posts and pages keep their permalinks. Category, tag, author, date, and attachment URLs each get a decision: keep, redirect, or retire. Rules from plugins like Redirection are carried over and flattened.
Titles, descriptions, canonicals, and schema from Yoast or Rank Math, exported per post and compared page by page against the live site on staging.
On launch day we test every redirect and submit the new sitemap. Then we check Search Console for 404s and lost queries at launch, day 30, and day 60.
Flexible. Until plugins pile up.
Four problems that grow with every year a site runs.
- 01
Every feature is another plugin
SEO, forms, caching, sliders, security. Each one adds updates to apply, conflicts to debug, and code you didn’t write.
- 02
Updates and security never stop
Core, theme, and plugin updates are a standing job. Skip them and the site becomes a target.
- 03
Speed depends on the theme
Heavy themes and page builders load scripts on every page, and caching plugins can only hide so much.
- 04
Content is tied to the page builder
Shortcodes and builder layouts mix content with design, so redesigns and reuse turn into copy-paste work.
Three years on WordPress.
What WordPress costs over three years vs. a stack you own. Change any number.
Staying on WordPress costs you
22.9× more€5,245a year
- Every month
- €437
- Over three years
- €15,736
The €15,736 is your break-even budget: the most a migration could cost and still pay for itself in three years. Every month you wait adds another €437.
| Year | WordPress | Own stack | Difference |
|---|---|---|---|
| 1 | €5,220 | €240 | €4,980 |
| 2 | €5,481 | €240 | €5,241 |
| 3 | €5,755 | €240 | €5,515 |
| 3 years | €16,456 | €720 | €15,736 |
Starting values are rough examples, not quotes. Use your invoices. Migration cost isn’t included.
Every feature gets a new home.
What your WordPress setup becomes in the new stack.
- Posts & pagesTyped CMS collections with drafts, versions, and live preview
- Custom post types & ACFTyped collections with relations and validated fields
- Gutenberg / page buildersReusable page blocks editors can arrange
- Yoast / Rank MathPer-page metadata, canonicals, Open Graph, JSON-LD in code
- Form pluginsForm handling connected to your CRM (HubSpot, Salesforce…)
- WPML / Polylangi18n routing with localized fields and hreflang
- Caching & security pluginsStatic pages on a CDN, with nothing to patch
- WordPress hostingVercel, Cloudflare, Netlify, or EU / self-hosted
WooCommerce, memberships, and LMS plugins are scoped individually. Prefer WordPress as the CMS? It can run headless behind the new frontend.
SEO preserved.
Nobody can promise rankings. We guarantee the process: Search Console checks at launch, day 30, and day 60, and any redirect or indexing issue from the move fixed within the project price.
- Crawl of every indexed URL, cross-checked with Search Console and analytics
- 1:1 URL parity where possible; reviewed 301 map where not
- Titles, descriptions, canonicals, and Open Graph carried over
- Structured data preserved or improved
- XML sitemap and robots.txt regenerated
- Image alt text and file paths migrated
- Pre-launch crawl on staging to catch broken links and redirect chains
- Search Console checks for indexing, 404s, and lost queries at launch, day 30, and day 60
Six steps.
WordPress stays live until the new site is ready.
Audit
Every URL, collection, and integration, mapped.
When to stay.
If most of these apply, we'll say so and help you get more out of WordPress instead.
Moving likely pays off.
Nothing here keeps you put. A migration is worth scoping.
Tick what applies to you.
Staying still has a cost.
AI agents now draft, translate, and update content. A headless CMS gives them structured content and an API to work with, and your team approves every change.
- Content as data, not pages
- API access for agents
- Drafts and review built in
- Any channel, any language
- Drafting…
Draft 3 posts from the product changelog
Blog
- Queued
Translate the pricing page to German
Pages · de
- Queued
Rewrite 12 weak meta descriptions
SEO
- Queued
Add the new integration to the docs
Docs
Every change lands as a draft. Your team decides what gets published.
WordPress migration guides.
What we've learned moving sites off WordPress.
Platforms2 min read
Headless WordPress or a new headless CMS?
You can keep WordPress as the CMS behind a modern frontend, or move content out entirely. How to decide, and what each path costs you.
Read →SEO2 min read
The website migration SEO checklist we use
Before, during, and after launch. The checks that protect rankings when you move from Webflow, Wix, Framer, or WordPress to a new stack.
Read →SEO2 min read
How to build a 301 redirect map for a site migration
The redirect map is where migrations win or lose search traffic. A step-by-step method, with the most common mistakes.
Read →
WordPress questions.
Anything else, ask on the call.
Can we keep WordPress as our CMS?
Yes. WordPress can run headless: editors keep the admin they know, and a Next.js or Astro frontend reads content through its API. We compare it with a dedicated headless CMS in the assessment.
What happens to our plugins?
We list every active plugin in the assessment. Most are replaced by a few lines of code or one integration, and some turn out not to be needed at all.
Will our URLs change?
Not unless you want them to. Permalinks are mapped 1:1, and any change gets a reviewed 301 redirect.
What about shortcodes and page-builder layouts?
They’re converted into structured blocks in the new CMS, so content is no longer tied to a builder or theme.
Next.js or Astro?
Astro suits content-heavy marketing sites that should ship little JavaScript. Next.js fits when the site sits close to your product, with login, dynamic pricing, or app features. We recommend one in the assessment and explain why.
What would it take?
URLs, CMS, integrations, and risks, ending in a fixed scope and timeline.