Services

SEO Recovery After a WordPress to Next.js Migration

You are in the right place when you migrated from WordPress to Next.js and then lost traffic, rankings, or indexed coverage because the new technical SEO layer no longer matches the old estate.

Recover lost visibility after a WordPress‑to‑Next.js migration by tracing the technical gaps in redirects, canonicals, sitemaps, and rendering.

Typical symptoms

  • Traffic, rankings, or indexed URLs dropped after a WordPress to Next.js migration.
  • Old WordPress URLs are not mapping cleanly into the new platform.
  • Metadata, canonicals, or sitemaps no longer match what search engines expect.

Likely causes

  • Redirect coverage is incomplete or implemented inconsistently.
  • Metadata parity between WordPress and Next.js was not preserved.
  • Rendered links, canonicals, or crawl paths changed during the migration.

What I look at first

  • Quick check: compare a handful of high‑value legacy WordPress URLs against the live redirects, canonicals, and rendered metadata now in production.
  • Internal links and navigation paths that changed with the new build.
  • Which important commercial pages lost visibility first.

How I help fix this

  • Trace the visibility loss back to specific rendering, redirect, and discovery issues.
  • Define the highest‑priority fixes before broader cleanup starts.
  • Support rollout and monitoring of the recovery work.

When to bring me in

  • Bring me in as soon as the post‑launch drop is visible rather than after weeks of partial fixes.
  • Bring me in when the migration shipped but nobody has a route‑by‑route view of what broke.

Related technical articles

  • 301 vs. 307 redirects

    11 July 2019

    301 and 307 redirects do different jobs. This guide explains when each one fits, what they tell browsers, and where SEO enters the picture.

  • Automatically generate `urllist.txt` from `sitemap.xml`

    06 January 2020

    Using PHP it is quick and easy to automatically generate your urllist.txt sitemap from your sitemap.xml file (for example, using gatsby-plugin-sitemap).

  • Optimising HTML markup for SEO

    03 February 2017

    Optimising HTML improves SEO, accessibility, and user experience. Here, I explore semantic HTML, clean code, alt text, and other best practices.

Related services

  2. Capability

    Technical SEO for JavaScript Applications

    Bring in engineering‑led SEO help when Google is not indexing important JavaScript pages because rendering, crawlability, metadata, or migration changes are getting in the way.

  3. Adjacent scenario

    Traffic Drop After a Redesign or Replatform

    Use redesign recovery and technical SEO recovery work to isolate what changed in URLs, templates, rendering, or crawl signals before the organic traffic drop compounds.

  4. Adjacent scenario

    JavaScript SEO Rendering and Indexing Fix

    Diagnose why Google is not indexing important JavaScript pages before incomplete HTML, unstable metadata, or routing changes keep them out of search.

Questions teams usually ask

Is this different from a general SEO audit?
Yes. This page is for post-migration recovery where the old WordPress estate and the new Next.js estate need to be compared route by route, template by template, until the technical cause of the visibility loss is clear.
Can you help if the migration is already live?
Yes. Most recovery work starts after launch, once the drop in rankings, traffic, or indexed URLs is visible enough to prioritise.

Tell me what needs fixing

Send me the affected page or route, point me at the code if that helps, and tell me what you expected to happen versus what is happening now. If this connects to a Next.js migration, technical SEO drop, performance issue, launch, or platform move, include that context too. I'll come back with the clearest next step.

Send the details
Skip past clients

Previous Clients