Full URL inventory & 301 map
Every indexed URL from your sitemaps, Search Console, a full crawl and your backlinks gets mapped to its new home. Redirects live in Next.js or at the edge, and every single one is tested before launch.
Fixed-price migration · Headless WordPress or full move
WordPress to Next.js migration, without losing your rankings.
I move WordPress sites to Next.js, either keeping WordPress as your editors’ CMS or replacing it entirely. Every URL gets mapped, every redirect tested, and Core Web Vitals are green on launch day. One senior developer, a fixed price, and a straight answer if migrating isn’t worth it.
- Fixed priceagreed before kickoff
- 100% of URLsmapped & 301-tested
- 90+ Lighthousemobile, key templates
- 15+ yearsWordPress & technical SEO
Where your site ends up
Next.js
React
TypeScript
WordPress
WPGraphQL
Vercel
Cloudflare
Netlify
Node.js
Tailwind CSS
Sanity
Payload
Storyblok
01 · Honest first
Next.js is not a speed plugin. Migrate for the right reasons.
I’d rather lose a project than sell you a rebuild you don’t need. A well-built WordPress site can be fast and rank well. Migration pays off when your frontend has outgrown the theme layer, not when a cache plugin is misconfigured.
Migrate when…
- Your marketing site is turning into a product: logged-in areas, calculators, configurators, dashboards.
- Your frontend team already works in React and fights the theme every sprint.
- You need content from several sources (WordPress, a PIM, a pricing API) in one fast frontend.
- You publish in several languages or markets and the plugin stack keeps breaking.
- Security and uptime matter: you want the public site served from the edge, with WordPress hidden behind it.
Don’t migrate just because…
- PageSpeed is red. That’s usually images, scripts and hosting. Fixable in weeks, not months.
- WordPress feels old. Your editors probably like it more than you think.
- An agency told you headless is the future. It’s an architecture, not a strategy.
- You want to cut costs. Two systems usually cost more to run than one, at least in year one.
Not sure which side you’re on? Read my independent WordPress vs Next.js comparison, or fix the speed first and decide later.
02 · What you get
Everything a migration needs, not just new templates.
Most migrations go wrong in the boring parts: redirects, previews, forms, the sitemap someone forgot. Those are in the scope from day one.
SEO parity, then better
Titles, meta descriptions, canonicals, hreflang, structured data, robots rules, XML sitemaps and Open Graph rebuilt with generateMetadata and compared page by page against the old site.
Editors keep their workflow
In a headless setup WordPress stays the CMS: drafts, live preview, scheduled posts and instant publishing through on-demand revalidation. Nobody needs a developer to change a headline.
Core Web Vitals by design
Server components, next/image, self-hosted fonts and a strict script budget. Target: 90+ Lighthouse on mobile for key templates, and green field data once Chrome’s 28-day window catches up.
Content & block migration
Posts, pages, custom post types, ACF fields, taxonomies, media and Gutenberg blocks mapped to typed React components. Old shortcodes get cleaned up, not copied over.
Forms, search & integrations
Contact forms, newsletter, CRM, analytics, Consent Mode and site search rebuilt or reconnected. The plugins that used to print HTML need a new home, and they get one.
Hosting, CI/CD & monitoring
Deployed to Vercel, Cloudflare, Netlify or your own servers, with a preview environment per branch, uptime and error monitoring, and a tested rollback path.
A handover you can own
A clean TypeScript repository in your GitHub, written documentation, a recorded walkthrough for your editors and hypercare after launch. No lock-in, no black box.
03 · Three ways to get there
Pick the architecture after the audit, not before.
There is no single “WordPress to Next.js” migration. These are the three I build, and the audit tells us which one fits your team, content and budget.
Headless WordPress + Next.js
WordPress stays the CMS your team already knows. Next.js renders the public site from WPGraphQL or the REST API.
- Best when
- Your editors are happy with WordPress and the content model is solid.
- You keep
- WordPress admin, users, ACF fields, revisions
- Typical timeline
- 4–8 weeks
Full move to Next.js + a new CMS
WordPress is retired. Content moves to Sanity, Payload, Storyblok or MDX in the repository, depending on who edits and how often.
- Best when
- WordPress itself is the problem: plugin debt, security worries or a content model that no longer fits.
- You keep
- Your URLs, your rankings and your content
- Typical timeline
- 6–12 weeks
Incremental migration
The templates that matter move first (landing pages, the blog, product pages) while the rest keeps running on WordPress under the same domain.
- Best when
- You can’t freeze a large site for two months, or you want proof before committing.
- You keep
- One domain, no big-bang launch
- Typical timeline
- Phased, 2–4 weeks per phase
04 · Rankings protection
How your rankings survive the move.
A migration is the riskiest SEO event a site ever goes through. These guardrails are part of every package, not an upsell.
- Crawl and export the old site before touching anything: URLs, status codes, titles, canonicals and internal links.
- Pull every URL with impressions from Search Console, plus every page other sites link to.
- Build a one-to-one redirect map. No bulk redirects to the homepage, no chains, no loops.
- Serve rendered HTML for every indexable page. Google shouldn’t need JavaScript to see your content.
- Diff metadata, structured data and hreflang page by page against the old site.
- Keep staging out of the index, and launch production with sitemap submission and URL inspection.
- Test every redirect and status code against the full URL list on launch day, before DNS is switched.
- Monitor coverage, 404s, impressions and Core Web Vitals for 30 days, with fixes included.
$ migration-check --urls old-urls.csv --target staging1,284 URLs checked872 → 200 same path412 → 301 single hop, mapped0 redirect chains · 0 loops0 soft 404s · 0 orphaned pagestitles 100% · canonicals 100% · hreflang 100%ready for DNS switch$
05 · Process
From audit to launch in weeks, not quarters.
Every step ends with something you can see and approve. Nothing reaches production untested.
- Week 0
Migration audit
Crawl, Search Console, plugin and content-model review. You get a go / no-go, the architecture and a fixed quote.
- Week 1
Architecture & URL map
Content model, routing, redirect map, hosting plan and SEO parity checklist, signed off before the build.
- Weeks 2–5
Build on staging
Templates as React components, data layer, preview, forms and search. Weekly demos on a staging URL.
- Weeks 4–6
Content migration & QA
Scripted content import, visual QA, accessibility, Core Web Vitals and an SEO diff against the old site.
- Launch day
Switch with a safety net
Redirect test, DNS switch, sitemap submission and live checks, with a rollback path ready.
- 30 days
Hypercare
Search Console and field data watched daily for the first two weeks. Anything that drifts gets fixed.
Timeline shown for the Launch package. Larger sites take longer, and the audit gives you dated milestones.
06 · Fixed prices
Clear packages. No hourly surprises.
Prices are fixed once the audit confirms the scope. If the scope changes, we agree on it in writing before I build anything new.
Migration audit
The go / no-go decision, with numbers.
€690
fixed · 5 working days
100% credited if you migrate within 60 days
- Crawl + Search Console URL inventory
- Plugin & feature map: what moves, what’s rebuilt, what goes
- Recommended architecture and hosting
- Draft redirect map and SEO risk list
- Fixed quote and timeline for the build
Launch
Company and marketing sites.
€6,900
fixed · 4–6 weeks
- Up to 30 pages and 6 templates
- Blog with up to 500 posts
- Headless WordPress or a new CMS
- Forms, analytics & Consent Mode
- Full redirect map + launch-day test
- 30 days of hypercare
Scale
Publishers, multilingual and B2B sites.
€12,900
fixed · 6–10 weeks
- Up to 12 templates and 5,000 URLs
- Up to 3 languages with hreflang
- Live preview & on-demand revalidation
- Site search and CRM integration
- Scripted migration of ACF fields & blocks
- 45 days of hypercare
Custom
WooCommerce, web apps and large sites.
from€18,000
scoped after the audit
- Headless WooCommerce or commerce APIs
- Logged-in areas and app features
- 10,000+ URLs or several sites
- ERP, PIM or SSO integrations
- Phased, incremental migration
- Dedicated launch plan
Every package includes:TypeScript codebase in your repositoryStaging environmentSEO parity checklistDocumentationNo lock-in
Payment: 40% to start, 40% at staging sign-off, 20% after launch. Prices exclude VAT; invoiced from Spain (EU), reverse charge for EU businesses.
After launch: Care plan
€390/month
Next.js and WordPress updates, uptime and error monitoring, monthly Core Web Vitals check and 3 hours of development. Cancel any time.
Ask about the Care plan
07 · Who does the work
You talk to the developer who writes the code.
I’m Anton Smolik, a senior WordPress developer based near Barcelona. I’ve spent more than fifteen years inside WordPress: themes, plugins, WooCommerce, performance and technical SEO. Today a good part of my work happens in React and Next.js on top of it.
That’s why I can tell you honestly whether to migrate: I know exactly what WordPress can and can’t do, and what a Next.js frontend really costs to run. No account managers, no junior handover, no surprises on the invoice.
- 5.0 ★Google reviews (25)
- 15+ yrsWordPress in production
- CETEU invoicing from Spain
08 · FAQ
Questions people ask before migrating.
Still unsure whether Next.js is right for your site? Ask me directly. You’ll get an honest answer, even if it’s “don’t migrate”.
Ask a questionFor a typical company site, €6,900 fixed. Content-heavy or multilingual sites are €12,900, and WooCommerce, web apps or very large sites start at €18,000. The €690 audit fixes the exact price, and it’s fully credited if you go ahead within 60 days.
Four to six weeks for a marketing site of up to 30 pages, six to ten weeks for content-heavy or multilingual sites. The audit takes five working days and gives you dated milestones.
Not if the migration is done properly. Every URL with impressions or backlinks is mapped and redirected one-to-one, metadata and structured data are compared page by page, and Search Console is monitored after launch. Small fluctuations in the first weeks are normal; lasting drops come from missing redirects and lost content, which is exactly what this process prevents.
Yes. In a headless setup WordPress stays your CMS: same admin, same users, drafts, scheduled posts and live preview. Only the public website changes.
Not automatically. Both can serve excellent, crawlable HTML. Next.js gives you more control over rendering and performance, but it only pays off when metadata, routing, sitemaps and redirects are engineered properly, which is exactly the part you’re hiring me for.
Admin-side plugins like ACF, your SEO plugin data and user management usually keep working. Plugins that print frontend HTML, like sliders, form builders and page builders, are rebuilt as React components or replaced by an API integration. The audit lists every plugin and what happens to it.
Wherever it fits best. Vercel is the simplest option, Cloudflare and Netlify work well, and your own Node server or container is possible if you need EU-only hosting or tighter control. WordPress can stay on your current hosting, locked away from the public.
Yes, although page-builder layouts don’t export cleanly. I rebuild the designs as components and move the content into structured fields, so your editors end up with a cleaner editing experience than before.
Yes, as a Custom project. Headless WooCommerce works for the right store, but checkout, payments and stock add real complexity. Often the better answer is a faster WooCommerce, and if that’s the case, I’ll tell you.
Then you get that in writing, with the reasons and a cheaper plan to fix whatever is actually holding the site back. The report is yours either way.
Send me your URL. You’ll get a straight answer.
Tell me about your site and why you’re looking at Next.js. Within one business day you’ll get a first, honest opinion for free, and then we decide together whether the audit makes sense.
hi@antonsmolik.com · Usually replies within one business day