How to Migrate WordPress to Next.js Without Losing SEO

Three Reasons People Leave WordPress. Only One Is About Speed.

Before getting into the how, it is worth being clear on why. Businesses migrate WordPress to Next.js for one of three reasons. Understanding which one applies to you affects how you approach the migration.

• ✓
  Still slow after real effort: some WordPress sites stay slow no matter what you do, because the theme, the plugins, the database, the hosting or outside scripts are the limit. Measure representative pages before deciding that a rebuild is necessary.
• ✓
  Search and page-experience risk: poor Core Web Vitals can weaken the user experience and contribute to search-performance problems, but they are only part of Google's broader ranking systems. Base the decision on lab tests, field data, crawl health, content quality, and conversion evidence rather than a blanket WordPress failure statistic.
• ✓
  Cost and maintenance burden: compare the current spend on hosting, premium plugins, security, updates, and developer support with the proposed WordPress migration cost. Commercial Next.js hosting on Vercel Pro starts at $20 per month plus usage. Vercel Hobby is for personal, non-commercial use, so it is not a valid business-hosting cost assumption.

If any of these sound familiar, a migration may be worth scoping. If your WordPress site is reliable, traffic is growing, conversions are healthy, and maintenance is manageable, there may be no urgent reason to rebuild it. A fit audit should compare repair, optimization, and migration before recommending a platform change.

"Businesses migrate WordPress to Next.js for one of three reasons, and speed is only one of them.

First Decide Whether WordPress Stays: Headless or Full Migration

Every other decision on this page depends on this one, and it is the step most guides skip. There are two destinations, not one. Headless keeps WordPress running as the content backend and replaces only the front end with Next.js, so editors keep working in wp-admin exactly as they do today. Full migration takes the content out of WordPress altogether, into Markdown/MDX files in the repository or into a separate headless CMS, and WordPress is switched off at the end.

Choose by who edits the site and how often, not by which stack sounds more modern:

• ✓
  Choose HEADLESS when non-technical people publish regularly, when editorial workflow, roles, scheduling or preview matter, or when existing plugins own real functionality you are not ready to rebuild. Next.js reads the content over the WordPress REST API at /wp-json/wp/v2/, or over GraphQL if you install the WPGraphQL plugin.
• ✓
  Choose FULL MIGRATION when the site is a marketing or documentation site that changes rarely, when developers are the people who edit it, or when you want the WordPress hosting, updates and plugin-security surface gone permanently. Content lands as MDX in the repo, or in a CMS such as Sanity or Payload.
• ✓
  Count the ongoing bill before choosing. Headless keeps you paying for WordPress hosting and maintenance on top of the new front end, so it is two systems to run, not one. Full migration removes that line but moves editing further from non-technical staff.
• ✓
  Decide this before the URL audit below, because it changes what you have to export and what you can leave in place.

Neither is the advanced option. A five-person marketing team publishing twice a week is usually worse off on MDX, and a documentation site with two developer maintainers is usually worse off paying to keep WordPress alive behind it. The one combination that reliably disappoints is choosing headless to avoid a content migration and then discovering the plugins you kept WordPress for are the same plugins slowing the site down.

The Pre-Migration Audit That Protects High-Value URLs

Do not start building until you have worked through this checklist. If you skip the baseline, the list of URLs, or the map of what connects to what, you are far more likely to break something at launch and lose search traffic you did not need to lose.

• ✓
  Crawl your full site with Screaming Frog (free up to 500 URLs) and export every URL, title tag, meta description, H1, and status code
• ✓
  Export your Google Search Console data: top 50 pages by clicks, top 50 by impressions. These are the pages you cannot afford to break
• ✓
  Screenshot your current PageSpeed score on mobile for every key page. This is your baseline to beat
• ✓
  Document every third-party integration: forms, chat, analytics, pixels, booking tools. Each one needs a Next.js equivalent
• ✓
  List every plugin and its function. Each will need a native replacement in Next.js
• ✓
  Set up Google Search Console for your domain if not already done. You will need it immediately after launch

A small business site might take half a day to inventory. A large publisher or shop takes much longer. What you end up with should be one file, kept under version control, that says: here are the URLs, here is the content, here is what connects to what, here are the numbers we started from, here is who owns each part, and here is how we will sign it off.

The 8 Steps We Run Every Time

async redirects() {
  return [
    {
      source: '/old-wordpress-slug',
      destination: '/new-nextjs-path',
      permanent: true, // 301
    },
  ]
}

export const metadata = {
  title: "Your Page Title",
  description: "Your meta description",
  alternates: { canonical: "https://yoursite.com/page" },
  openGraph: { title, description, type: "website" },
}

What to Expect After the Migration: The Real Timeline

A WordPress to Next.js migration is not an instant ranking boost. This sequence describes what the team should verify after cutover; it is an operating plan, not a promise about when Google will recrawl the site or how rankings will move.

DIY Migration vs Professional Migration: The Honest Comparison

This guide gives you the full process. But it is worth being direct about what DIY migration actually involves if you are not an experienced Next.js developer.

The decision comes down to technical capacity, migration risk, and what the website supports. For a revenue-generating site, compare the quoted migration cost with maintenance spend, conversion friction, downtime exposure, and the internal time required for DIY delivery. A professional migration can reduce execution risk, but it cannot promise payback or rankings. If you are a developer who wants to learn Next.js through a real project, DIY is a legitimate path. Just budget time for crawl QA, accessibility, analytics, consent, security, and rollback testing as well as the build. For the measurement process, read our guide to a 90+ PageSpeed score.

Either way, read our post on WordPress vs Next.js before committing: it covers the full comparison of what you gain and what you trade off. And see our guide to fixing a slow WordPress site if you want to understand exactly where the WordPress speed ceiling is before deciding whether a migration is necessary. This is also the exact move we made for our own site, and we documented why we moved off WordPress ourselves with the before and after numbers.

Key Takeaways

1. Every old URL needs a deliberate disposition: Keep stable URLs unchanged where possible, map changed URLs to relevant successors with permanent redirects, and document intentional 404 or 410 retirements. Validate each decision before launch.
2. Timeline follows the work, not a template: how many pages there are, how much content needs tidying, what has to be reconnected, how long approvals take, how many URLs are awkward exceptions, and how much testing you do.
3. No agency can guarantee rankings: Expect possible ranking volatility, preserve technical signals carefully, and use Google Search Console monitoring against a dated baseline. Better Core Web Vitals support page experience, but do not cause a guaranteed position gain.
4. The audit before you start is what makes testing possible: every URL listed, the landing pages that matter most identified, canonical tags recorded, the sitemap captured, integrations mapped, analytics noted, and agreement on what counts as done.
5. Plan a controlled cutover and rollback: Keep WordPress available until the Next.js release is accepted, lower DNS TTL when appropriate, verify production immediately, and define how to reverse the cutover if a critical check fails.