Playbook Mar 19, 2026 15 min Sam Okafor

Migrating from Next.js Pages Router without losing rankings

Migrations are where rankings go to die. The good news: with a disciplined redirect map and a careful canonical strategy, you can move stacks without losing the traffic you spent years earning.

#Build the redirect map first

Before you touch a line of code, export every indexed URL. Map each one to its new home with a 301. Anything that can't be mapped gets a deliberate decision — never a 404.

#Canonicals during the cutover

Run both stacks in parallel behind a feature flag. Set canonical tags to the new URLs from day one, even before traffic shifts. Google will start consolidating signals before launch.

#Protect your crawl budget

→Submit a fresh sitemap the day of cutover.
→Watch Search Console crawl stats hourly for the first 48 hours.
→Block parameterised duplicates aggressively in robots.txt.

#The first two weeks post-launch

Expect a 5–15% dip in week one. If you're still down at week three, you have a real problem — start with redirect chains and rendered HTML diffs.