Preserving SEO authority during a WordPress to Next.js migration

Right now I'm in the middle of moving a large financial review platform off WordPress and onto Next.js. The tempting part of a rebuild like this is to start with the frontend — new components, new design system, new stack. The risky part is that a large site like this has years of indexed pages, backlinks, and search rankings that a careless relaunch can quietly erase.

So the migration started somewhere less exciting than a component library: a full export of every indexed URL, its redirect chain, and its current ranking signals. Only after that map existed did the actual rebuild begin — and the rule was simple: the new templates had to reproduce the same information architecture crawlers already trusted, not a reimagined one.

#Non-negotiables for the rest of this migration

A few things I'm treating as fixed through the rest of this migration:

• Every legacy URL either resolves directly or 301s to its clear successor — no orphaned paths.
• Metadata (title, description, canonical) migrates before the visual redesign does.
• Structured data that existed on the old templates gets reproduced on the new ones, not "improved" mid-migration.
• Performance wins (which Next.js makes easy) ship as a bonus on top of parity, never as a reason to skip parity.

#Why impatience is the real risk

The unglamorous truth is that most SEO lost during a replatform isn't lost to bad content — it's lost to impatience. I'll post real before/after numbers here once this one ships.

Questions readers ask

Do 301 redirects fully preserve search rankings?+

Mostly, not fully — Google treats a 301 as a strong signal to consolidate ranking to the new URL, but some equity loss is normal even when done correctly. The redirect map matters more than the redirect mechanism: vague many-to-one redirects (everything to the homepage) lose far more authority than precise one-to-one mappings.

How long does re-indexing take after a replatform?+

For a site this size, expect a partial recovery within 1-2 weeks and full stabilization over 4-8 weeks, assuming redirects and metadata shipped correctly on day one. Submitting the new sitemap and using URL inspection on the highest-traffic pages speeds up the recrawl of what matters most.

What's the single biggest mistake in an SEO-sensitive migration?+

Redesigning the information architecture at the same time as the platform. Changing URL structure, navigation, and visual design all at once makes it impossible to isolate what caused a ranking drop if one happens. Parity first, redesign second.