Skip to content
Specialised engagement

WordPress to Next.js migration.

Your WordPress site, rebuilt on Next.js, with no ranking regression and a 10x improvement in render performance. Every post, page, custom post type, taxonomy, and media item exported losslessly; the URL structure preserved or 301-mapped; the Yoast or RankMath schema replaced with a hand-built JSON-LD graph; and a content layer your editors can keep using (Sanity for rich editing, MDX for engineering teams, or a headless WordPress backend if WordPress's admin is a team-policy floor).

Timeline
6 to 12 weeks
Scope
Quote-driven
01What ships at engagement end

Concrete deliverables. 9 line items.

Every item below is a real artefact, document, or component handed over at the end of the engagement. No placeholders, no abstract milestones.

  1. 01WP-CLI or REST API content export (posts, pages, CPTs, taxonomies, media)
  2. 02Content layer migration (Sanity, MDX, or headless WordPress)
  3. 03URL inventory + 301 redirect map (every legacy permalink classified)
  4. 04Schema graph rebuild (Yoast / RankMath replaced with hand-built JSON-LD)
  5. 05Theme rebuild on Next.js with component system
  6. 06Performance pass: image optimisation, font loading, third-party script audit
  7. 07AI-crawler access policy (was usually wide-open on WP; tightens correctly)
  8. 08Cutover plan with rollback (legacy WP kept warm for 30 days)
  9. 09Editor onboarding and a written content workflow
Service questions

WordPress to Next.js migration, common questions.

Full list on the FAQ page.

Work with valUX

Start where it hurts.

If your organic traffic is sliding, start with a Pulse audit. If you want a programme rather than a one-off, ask about a retainer. Either way, every enquiry is read by a senior architect, and you hear back within one working day.