WordPress → Next.js · Updated
WordPress to Next.js Migration
A WordPress to Next.js migration moves your content out of the WordPress export file into a custom-coded, server-rendered site, keeps every URL that earns traffic through a one-to-one redirect map, and rebuilds the design, forms and structured data rather than converting the theme.
Who this migration is for
- Sites that have outgrown page builders and plugin stacks and now pay for it in speed, security patches and editing friction.
- Businesses that want pages machines can read as delivered, for Google and for the AI search agents.
- Teams that still want an editor: content moves into a headless CMS or typed content files, not into code.
What WordPress lets you export
Taken from the vendor’s own documentation, linked below. We do not promise an export the platform does not provide.
Documented export
- WordPress documents that the Tools Export screen produces a WXR (WordPress eXtended RSS) XML file containing "your posts, pages, custom post types, comments, custom fields, categories, tags, custom taxonomies, and users".
- With "All content" selected the export also includes terms, navigation menus and custom posts.
Not exported or stops working
- The theme, page-builder layouts and plugin configuration are not content and do not travel in the export; they are the presentation layer we rebuild.
- Media files are referenced by URL in the export. We copy the files and rewrite paths rather than relying on the old host staying up.
Source: WordPress.org, Tools Export screen. Accessed October 2026.
What we rebuild rather than import
- Design and templates. A migration is a rebuild of the presentation layer; we do not try to convert a theme or builder output into React.
- Forms, lead routing and spam protection, wired to your CRM or inbox and tested end to end.
- Structured data: one Organization node, Service and FAQ markup that mirrors the visible page, validated before launch.
- Analytics, consent and conversion events, so the first month after cutover is measurable.
Want to know what your WordPress site would keep?
The free audit inventories your URLs and traffic and tells you what a migration would have to preserve.
How rankings are preserved
WordPress-specific notes first, then the eight steps every migration follows.
- Page-builder shortcodes and block markup are stripped during content import, then each page is checked against the live version so no paragraph or heading is lost.
- WordPress tag, category, author and date archive URLs are inventoried from Search Console before cutover; archives that earned nothing are redirected to the best hub rather than recreated.
- Yoast or Rank Math titles and descriptions are exported with the content and carried over field by field.
- 1
Inventory every URL that exists and every URL that earns
Crawl the live site, pull the sitemap, and export the Search Console Pages and Performance reports. The union is the redirect map input; the Performance rows decide what must be preserved exactly.
- 2
Decide the new URL structure before building
Keep paths where they are sane. Change them only where the old structure was a liability, and record the change in a one-to-one map. No wildcard redirects to the homepage.
- 3
Carry metadata field by field
Titles, descriptions, canonicals, Open Graph and existing structured data are exported with the content and loaded into the new pages, then diffed against the live site.
- 4
Rebuild structured data from one identity
One Organization node with the real address, phone and founder; Service, Article and FAQ markup that mirrors the visible page; validated before launch.
- 5
Preserve internal links and images
In-body links are rewritten to the new paths rather than left to bounce through redirects. Images are self-hosted so nothing depends on the old platform staying up.
- 6
Test the redirect map against the inventory
Every old URL is requested and must return one 301 to a 200 page. Chains, loops and 404s fail the launch.
- 7
Cut over and submit
DNS switch, new sitemap submitted, IndexNow ping, and a full crawl of the new site within the first day.
- 8
Monitor index coverage for a month
Indexed versus submitted, crawl errors, redirect-reported URLs and the top earning queries are checked weekly. A migration is done when coverage matches or beats the old site, not when the new one is live.
Why coverage is the finish line: our index coverage research. How AI agents read the result: which AI crawlers visit your site.
Why businesses make this move
- Server-rendered HTML. Search engines and the search-type AI agents read the page as delivered, not after a browser runs scripts.
- No plugin or app layer to patch, which removes a class of security and performance regressions.
- Content modeled as data, so the same facts feed pages, schema and llms.txt without drifting apart.
How the engagement runs
| Phase | What happens |
|---|---|
| Discovery | Goals, constraints, what the current platform does well, what it blocks. Access to analytics, Search Console and the admin. |
| Inventory | URL list, content audit, export of everything the platform allows, capture of everything it does not. |
| Content model and design | Document types and fields, page templates, components. Approval before build. |
| Build | Next.js frontend, CMS setup, content load, forms, schema, analytics and consent. |
| Redirect map and QA | Old to new URL map, automated redirect test, page-by-page content diff, accessibility and performance checks. |
| Cutover | DNS switch, sitemap and IndexNow submission, first crawl, old platform kept read-only until coverage is confirmed. |
| Monitoring | Weekly index coverage, crawl errors and query checks for a month; fixes shipped as found. |
Common questions
Will I lose rankings moving from WordPress to Next.js?
Rankings follow URLs, content and links. If every earning URL keeps its path or receives a one-to-one 301, the titles, body copy and internal links are carried over, and the new pages render as HTML, there is no reason for a loss. The risk comes from dropped pages, redirect chains and changed canonicals, which is what the redirect map and the post-launch crawl exist to catch.
Can my team still edit content without WordPress?
Yes. Content moves into a headless CMS with an editor, or into typed content files for sites that change rarely. Webvello builds on Sanity for most editorial sites.
What happens to my WordPress plugins?
Each plugin is mapped to a decision: rebuild the feature in code, replace it with a service, or drop it because nobody used it. Forms, SEO metadata, redirects, analytics and caching are rebuilt natively; most of the rest turns out to be unnecessary.
Do I need to change my domain or tell Google about the move?
No, if the domain stays the same. Google treats it as a site update, not a site move, so the Change of Address tool is not used. The signals that matter are the redirects, the updated sitemap and a clean crawl after launch.
Related
- WordPress vs Next.js
- WordPress vs Next.js for SEO
- Why businesses leave WordPress
- WordPress to a headless CMS
Other migration paths
Planning a WordPress move?
Tell us the page count and what the site has to keep doing. We will come back with what can be exported, what has to be rebuilt, and a dated plan.
Book a Free Call