Book a call
Go back

WordPress to Next.js migration, planned to protect your organic traffic.

We move company websites off WordPress onto a fast, secure Next.js build, planned to protect your organic traffic: every URL mapped, every redirect in place and your content carried across.

From €2,9002 weeks for most company sites

A WordPress to Next.js migration rebuilds your website on Next.js and React while keeping what already works in search: every indexed URL is mapped and redirected, titles, descriptions and content move across, and structured data is added. Unlockd plans and delivers the migration founder-direct, at a fixed price.

Timeline
Most sites in 2 weeks
SEO
Every indexed URL mapped and redirected
Content
Pages, posts and media migrated
Who builds it
Temim Turkusic, the founder
Price
From €2,900, fixed after scoping
After launch
Search Console monitored, support included

Why companies leave WordPress

  1. 01

    Plugins, updates and breakages

    Dozens of plugins to patch, each update a risk, and a site that breaks when one of them changes.

  2. 02

    Speed you can't fix

    Themes and page builders that load megabytes of scripts, so mobile scores stay red whatever you try.

  3. 03

    Security exposure

    The most attacked platform on the web, with a login page and plugin vulnerabilities bots scan for every day.

  4. 04

    A template that looks like everyone

    The same theme your competitors bought, which no longer reflects the company you've become.

How the migration works

Crawl and URL map

Every indexed page, post and image is listed before anything is rebuilt, and each old URL gets its new home.

Rebuild in Next.js

A custom design and a fast Next.js build, with a CMS for your team and structured data on every page.

Content and redirects

Content moved across, permanent 301 redirects for every changed URL, titles and descriptions preserved or improved.

Launch, watch and roll back if needed

A traffic baseline before launch, sitemaps submitted, Search Console monitored after launch, crawl errors fixed as part of the project, and the old site kept ready to restore.

  1. 01Audit and crawl the current site
  2. 02Map every URL and agree the scope
  3. 03Rebuild, migrate content, test redirects
  4. 04Launch and monitor Search Console

Moved off templates and WordPress

  • ANiX Fire SolutionsFrom a generic template to a custom Next.js site: 100 for performance, best practices and SEO in Lighthouse on desktop (September 2026), and one contract won through the new site (client-reported).
  • Sotheby's MontenegroA surgical move from WordPress to Next.js: every old address mapped one by one, with the aim of keeping every Google position the old site had earned. Now live.

Journal

Read next

Frequently asked questions

Will we lose Google rankings when moving from WordPress to Next.js?

Nobody can guarantee rankings through a site move: Google recrawls the site and positions can fluctuate for a few weeks. What a careful migration controls is the risk: every indexed URL is mapped before the rebuild, changed URLs get permanent redirects that are tested before launch, relevant content and titles carry across, a traffic baseline is recorded, and Search Console is monitored after launch so any drop is traced and fixed quickly.

Can we redesign our website without losing SEO?

Yes, if the redesign is planned as a migration. Most traffic lost in a redesign comes from old addresses that stop working, so every indexed URL gets a new page or a tested 301 redirect, titles and content that already rank carry across, and Search Console is watched daily after launch. A new design on its own doesn't cost rankings; broken addresses do.

How long does a WordPress to Next.js migration take?

Most company websites take 2 weeks, including the crawl and URL map, design, build, content migration and redirect testing. Larger sites with hundreds of posts, several languages or a shop are scoped individually, and you get the launch date in writing before you commit.

Can we still edit content after leaving WordPress?

Yes. Content is managed in a headless CMS with a familiar editor, so your team keeps publishing pages and posts without a developer, and edits SEO titles and descriptions next to the content. Existing posts, images and authors are moved across, and you get a recorded walkthrough at handover.

Why migrate instead of redesigning on WordPress?

Because a new theme doesn't fix the platform: the plugin stack, the weekly updates, the speed ceiling and the security exposure all stay. A Next.js rebuild removes them, and the redesign happens in the same project, so you pay for the move once. If your WordPress site is simple and works, staying can be the right call.

All questions (14)
What does a migration cost?

Migrations start from €2,900, quoted as one fixed price after a short scoping call. The price depends on the number of pages and posts, languages, integrations such as forms, CRM or a shop, and how much design work is new. A full redesign at the same time is quoted as a website project, from €3,900.

What do we need to provide for a migration?

Admin access to WordPress (or an export), access to Search Console and analytics, your hosting and DNS details, and a list of pages that matter commercially. Search Console data shows which URLs earn impressions and links, and those are protected first.

What happens to our blog posts, images and PDFs?

They move with the site. Every post keeps its text, headings, images with alt text and internal links. Posts that keep their URL stay where they are; any that change get a 301 redirect. Old PDFs and image URLs that still get traffic or links are kept or redirected, not left to return 404.

What is a WordPress to Next.js migration?

It's moving a website off WordPress onto a Next.js front end, with content managed in a headless CMS, or in WordPress kept running headless behind the scenes. Pages are rebuilt as fast, server-rendered HTML; text, images and authors move across; and every URL that changes gets a tested 301 redirect, so visitors and Google land on the right page.

Can we keep WordPress as the CMS and only replace the front end?

Yes, that's headless WordPress: your editors keep the WordPress admin, and Next.js builds the site from WordPress's API. You still host and update WordPress behind the scenes, so part of the maintenance stays. For most company sites a headless CMS built for the job is simpler; we recommend one or the other after looking at your content and your team.

What happens to our WordPress plugins?

Every plugin is listed during the audit and replaced by what it actually did: form plugins by built-in forms, SEO plugins by metadata and sitemaps generated from content, caching plugins aren't needed at all, and page builders and sliders become components. Plugins that talk to outside services, like a CRM or newsletter tool, are rebuilt as direct integrations.

Can we see the new site before switching?

Yes. The new site runs on a private preview link while your WordPress site stays live. You review every page, try editing in the CMS and approve before anything changes. The DNS switch is planned for a quiet moment, and the old site is kept as a fallback until the new one is confirmed in Search Console.

Is Next.js better for SEO than WordPress?

Not by magic: Google ranks content, links and relevance, not frameworks. Next.js helps with the technical side: complete server-rendered HTML, fast pages on phones, no plugin bloat, and metadata, structured data and sitemaps generated from your content. A well-kept WordPress site can rank too; the difference is how much ongoing effort it takes to stay fast and clean.

What still needs maintaining after we move off WordPress?

Much less. There are no weekly core and plugin updates. What remains is a framework and dependency update a few times a year, the CMS and hosting plans, and your content. That's covered by an optional maintenance plan, or done per change at a fixed price.