The same questions keep coming up from people considering a WordPress to Next.js migration. Here are honest answers to the most common ones.
Will I lose my SEO rankings?
This is the most common concern, and it's a legitimate one.
Short answer: typically no, when the migration is executed with proper redirect mapping and hreflang preservation. Some sites see temporary fluctuation that normalizes within weeks.
The key steps are:
- 301 redirects for any URLs that change (all of these get mapped before launch)
- Meta tags, titles, and descriptions migrated exactly
- Structured data (schema markup) carried over
- Same content - your copy is migrated, not rewritten
In most cases, rankings improve after migration because Google's Core Web Vitals are a ranking factor and Next.js sites typically score 90-98 on mobile PageSpeed. Many WordPress sites score in the 40-65 range without dedicated optimization. Some clients have improved positions on competitive keywords within 60-90 days of launch; outcomes depend on prior baseline and content investment.
What happens to my WordPress content?
All of it comes with you. Blog posts, pages, images, metadata - everything gets migrated. Your content is extracted programmatically so nothing is left behind.
Images are re-optimised (converted to WebP/AVIF where supported, compressed, properly sized for each breakpoint). This alone typically reduces page weight by 40-60%.
Can I still edit the site after migration?
Yes, in two ways:
Option 1: Self-managed. If you have a developer on your team, they can edit the Next.js codebase directly. It's a standard React/TypeScript codebase - any competent developer can work with it.
Option 2: Managed editing support. Send your changes by email - "add this testimonial to the homepage", "update pricing on the services page", "create a new case study page". Common edits can move through an automated update workflow. Larger structural changes are scoped separately. This is what most clients choose because it removes WordPress admin entirely from their lives.
Managed editing support: scoped by edit volume and response expectations. Common edits can move through an automated update workflow; larger structural changes are scoped separately.
What about my contact forms and integrations?
Standard contact forms are rebuilt using a Next.js API route (a serverless function). They work exactly as before.
More complex integrations, CRM connections, booking systems, and e-commerce are scoped individually. Most common integrations (HubSpot, Mailchimp, Calendly embeds) are routine.
WooCommerce migrations are handled case-by-case and are priced separately due to complexity.
How long does it take?
Typical timeline: 7-14 days from kick-off to launch for a standard business site (up to ~50 pages, standard content types).
Larger or more complex sites take longer. Your site gets scoped specifically before any timeline is given.
Do I need to know anything about Next.js?
No. From your perspective, you have a website. You email changes, and they get made.
If you're technical and want to understand the stack, I'm happy to walk through it. But it's not a requirement.
What if I want to change the design at some point?
Design changes can be included in managed support when the scope is clear. Minor layout changes, colour updates, and adding new sections can be handled there. Large redesigns are scoped separately.
Why Next.js specifically, and not another modern framework?
Next.js is the most widely adopted React framework, with the largest community, the best Vercel deployment pipeline, and strong long-term backing from Vercel (the company). It has excellent built-in performance primitives: static generation, server-side rendering, image optimisation, and edge deployment.
Practically: more developers know it, there are more resources, and it's a low-risk, mature framework choice for a site that needs to be maintained long-term.
What does it cost?
Migration: Scoped around the number of pages, content types, SEO risk, integrations, and custom functionality required. Scope and price are agreed before implementation starts.
Managed editing support: scoped by edit volume and response expectations. Common edits can move through an automated update workflow; larger structural changes are scoped separately.
Can I see what my site would score before committing to anything?
Yes. webvise built a free tool for exactly this.
Enter your URL and email, and you'll get a WordPress Health Report that shows:
- Your current PageSpeed score (mobile and desktop)
- Security flags worth knowing about
- Projected Next.js score after migration
- Estimated monthly revenue impact of your current load time
Get your free WordPress Health Report at webvise.io/wp-health-report
It takes 60 seconds. No account. No credit card.
How do I get started?
Two options:
- Get a free health report at webvise.io/wp-health-report. See your numbers first.
- Book a free 20-minute call at webvise.io to talk through your site and whether a migration makes sense.
No pitch decks. No pressure. You'll get an honest answer if a migration isn't right for you.