WordPress sites accumulate search rankings the slow, honest way: years of indexed pages, backlinks, and domain trust. That's exactly what makes migrating one to Next.js nerve-wracking. A rebuild is a chance to fix everything that made the old site slow and hard to maintain, and it's also the single easiest way to torch years of SEO equity if it's done carelessly. Here's the playbook we run on every migration.
Audit before you touch anything
Before writing a line of new code, we crawl the existing site and export every indexed URL, its current ranking position, its backlink count, and its meta data. This becomes the source of truth for the entire migration. If a page doesn't show up in this audit, it doesn't get quietly dropped, it gets a deliberate decision made about it.
Build a complete redirect map, not a best-effort one
Every single URL from the audit gets mapped to its new destination, even the ugly ones, even the ones with query strings, even the ones that get consolidated into a single new page. A 301 redirect map with gaps is worse than no migration plan at all, because it looks finished right up until Google Search Console starts reporting a wave of 404s three weeks later.
Structured data has to move over exactly, not approximately
WordPress SEO plugins auto-generate a lot of schema markup that most site owners never look at directly, Organization schema, Article schema, breadcrumbs, FAQ schema. We pull the exact JSON-LD output from the old site before migration and rebuild it deliberately in the new codebase, field by field, rather than letting a new CMS regenerate something "close enough."
Rendering strategy is the part people get wrong
The temptation with a Next.js rebuild is to make everything client-side rendered because it feels modern. For content that needs to rank, that's a mistake. We use static generation for anything that doesn't change per-request, and only reach for server-side rendering or client-side data fetching where the content genuinely requires it. Google can crawl a slow, client-rendered page. It crawls a fast, statically generated one better and more often.
Ship it staged, not all at once
We move a subset of lower-traffic pages first, watch Search Console for indexing and ranking behavior over one to two weeks, then move the rest once the pattern looks healthy. A full cutover on day one removes your ability to catch a redirect mistake before it costs you rankings across the whole site.
What this actually looked like on a recent project
On one WordPress-to-Next.js migration, the client's biggest fear was losing five years of blog rankings. We migrated 340+ URLs with a complete redirect map, rebuilt every schema type the old site used, and staged the rollout over three weeks. Organic traffic dipped under 4% during the transition window and recovered within a month, standard behavior for a well-executed migration, not a red flag.
The internal linking structure has to survive the move too
WordPress themes and plugins often generate internal links automatically, related posts widgets, category archive links, breadcrumb trails, and all of that link equity disappears silently if the new site doesn't recreate an equivalent structure. We map the old site's internal linking pattern as part of the audit and rebuild it deliberately, rather than letting the new CMS's default behavior decide which pages link to which.
Image migration is where SEO quietly leaks
Alt text, file names, and image sitemaps all carry ranking signal, particularly for sites that get meaningful traffic from Google Images. A lift-and-shift image migration that just moves files without preserving this metadata gives up rankings that took years to build, for no reason other than moving quickly. We export the full image metadata set and verify it maps one-to-one in the new build.
Core Web Vitals: the upside that makes the risk worth it
The reason clients migrate off WordPress in the first place is usually performance: plugin bloat, unoptimized images, and render-blocking scripts that tank Core Web Vitals scores. A properly built Next.js site with static generation typically posts dramatically better Largest Contentful Paint and Interaction to Next Paint scores, and Google has been increasingly explicit that these metrics factor into ranking. The migration risk is real, but so is the upside once it's done correctly, sites that were stuck on page two sometimes move up simply because the technical foundation stopped working against them.
What to ask any agency before you commit to a migration
- Will you provide a complete URL-level redirect map before development starts, or only after launch?
- How do you handle schema markup that the current SEO plugin generates automatically?
- What's the rollback plan if Search Console shows a ranking drop after launch?
- Will the migration be staged, or is it a single cutover?
If an agency doesn't have a clear, specific answer to all four, that's a sign the migration plan exists mostly in someone's head rather than on paper, which is exactly how rankings get lost by accident.
If you're sitting on a WordPress site that's slow, hard to maintain, or held together by six plugins nobody remembers installing, but you're worried about losing what it's already earned in search, that's exactly the problem we solve. Take a look at our web development service or get in touch for a migration audit before you commit to anything.