Guide · 6 chapters
WordPress to Next.js without losing SEO
Redirect maps, content migration, hreflang, and the post-launch monitoring that catches misses.
Chapter 01
The redirect map is the project
A WordPress-to-Next.js replatform is mostly a content migration plus a redirect map. The content part is mechanical. The redirect map is the part that decides whether your traffic survives the cutover.
Chapter 02
Categories to check first
Some URL patterns are higher risk than others. We sort the existing site's URLs into categories and review the redirect rule for each.
- Permalink structure changes — explicit rules, not regex.
- Category and tag pages — accumulate internal link equity.
- Pagination URLs — even if canonicalized away.
- Author, archive, and search pages — easy to forget; often have backlinks.
- Trailing-slash inconsistencies — /about and /about/ differ to Google.
Chapter 03
Cutover day
Set up daily Search Console crawl-error monitoring. Keep the old WordPress install running on a subdomain for two weeks as a fallback. Watch the 404 logs in real-time for the first 48 hours.
Chapter 04
Hreflang for multi-language sites
Hreflang is one of those things that's easy to get 80% right and almost impossible to get 100% right without tooling. We generate the hreflang tags from the CMS at build time, validate every page, and re-validate weekly via a scheduled crawl.
Chapter 05
What to expect post-launch
Expect a short traffic dip while Google recrawls the new URLs. Agree the recovery window before cutover, and track it daily in Search Console. A dip that deepens instead of closing means the redirect map needs another pass.
Chapter 06
Killing WordPress
Two weeks post-launch with no critical 404 hits and stable Search Console crawl coverage, you can sunset the WordPress install. Archive a final database backup. Document the redirect map as a permanent artifact.
More guides
Multi-tenant SaaS, end to end
Postgres RLS, RBAC, metered billing, and a SOC 2-ready audit trail — wired in before the first tenant signs.
Building production AI agents
Tool use against real APIs, eval harnesses, observability, and the kill-switches you'll want.
Core Web Vitals — the playbook we run
LCP, INP, CLS — how we diagnose, fix, and lock in. With the GitHub Action we use to enforce.
Run this with your team
Book the workshop version.
A half-day workshop with your team — same content, your codebase. We tailor the chapters to where your team is today.