WordPress to Next.js: when the switch pays off for your business

Short answer: a WordPress to Next.js migration pays off when your website has to bring in enquiries and plugin updates, slow load times and security patches keep eating your time. According to Patchstack, 11,334 new vulnerabilities were reported in the WordPress ecosystem in 2025, 91 % of them in plugins, and only about 49 % of WordPress sites pass Google’s Core Web Vitals on mobile. With a clean 301 redirect plan, you keep your rankings through the move.

WordPress still runs about 41 % of all websites (W3Techs, mid-2026). It is not going away, and for many sites it is perfectly fine. But over the last two years we have seen more and more Austrian companies arrive with the same story: a theme bought years ago, 30 plugins, a page builder nobody dares to touch, and a site that takes four seconds to load on a phone.

This guide is for owners and marketing leads who are deciding whether to rebuild on Next.js, a React framework for websites. We cover what actually changes, what it costs you in effort, how the move works without losing Google traffic, and when we would tell you to stay on WordPress. We build our own sites and our client websites on Next.js, so we are biased, and we try to be honest about it.

Why so many companies are leaving WordPress right now

The reasons are rarely ideological. They are practical, and they usually pile up over years:

• Speed: the site feels slow on a phone, and Google’s PageSpeed report is red.
• Maintenance: every month brings plugin, theme and core updates, and every update can break something.
• Security: a hacked contact form or a malware redirect once was enough to lose trust in the setup.
• Design lock-in: the page builder decides what is possible, not the brand.
• AI search: answers in ChatGPT, Google AI Overviews and Perplexity draw on pages that are clean, fast and clearly structured, and a bloated builder page is none of those.

None of these is a problem with WordPress itself. They are problems with how most WordPress sites are built and maintained in practice. A rebuild on Next.js is a chance to fix the structure, the content and the technology in one go instead of patching each layer separately.

Load time and Core Web Vitals: where WordPress costs you enquiries

Google measures real-world user experience with three Core Web Vitals: Largest Contentful Paint (LCP, main content visible in 2.5 seconds or less), Interaction to Next Paint (INP, reaction to taps in 200 ms or less) and Cumulative Layout Shift (CLS, 0.1 or less). These values come from real Chrome users, not from a lab test.

The HTTP Archive’s Core Web Vitals technology report showed a mobile pass rate of about 49 % for WordPress sites in mid-2026. That is a huge improvement on 15 % in 2020, but it still means roughly every second WordPress site fails on phones. WordPress usually does well on INP. Where it struggles is loading: slow server response, heavy themes and page builders that ship scripts for features the page never uses.

Why it matters commercially: in Deloitte’s “Milliseconds make millions” study for Google, a 0.1-second improvement in mobile speed lifted conversion rates by 8.4 % for retail and 10.1 % for travel sites. Your numbers will be different, but the direction is consistent: faster pages lose fewer visitors.

A Next.js site is not fast by magic. A badly built one can be just as slow. What Next.js gives you is control: pages are pre-rendered as finished HTML, images are resized and served in modern formats automatically, and nothing loads that the page does not need. On our own builds we set a performance budget from day one and aim for an LCP under 2.0 seconds on mobile and a Lighthouse performance score of 95+.

Plugins, updates and security

The WordPress core is well maintained. The risk sits in the ecosystem around it. Patchstack’s State of WordPress Security in 2026 report counted 11,334 new vulnerabilities in 2025, 42 % more than the year before. 91 % were in plugins, 9 % in themes, and only six in core. Even more uncomfortable: 46 % were not fixed by the time they were disclosed, and the weighted median time to the first exploitation attempt was five hours.

That is why a WordPress site needs someone who updates it every week, tests the updates and restores a backup when something breaks. Many small businesses do not have that person, so the site simply stops being updated.

A Next.js site works differently. There is no admin login on the public site, no PHP and no database the visitor can reach. Content comes from a separate editor, and the website itself is mostly pre-built pages. The attack surface is much smaller. It is not zero: dependencies still need updating and forms still need spam protection. But there is no plugin layer that grows every year.

AI-readable markup: why ChatGPT and Google prefer clean pages

More and more searches start in ChatGPT, Perplexity or Google’s AI Mode. These systems fetch pages, pull out passages and cite sources. Google says plainly that there is no special trick for its AI features: a page has to be indexed, eligible for a snippet and useful. So the basics that matter for AI are the same basics that matter for SEO, done properly.

Here a clean rebuild helps in a very concrete way:

• Complete HTML on first load. Next.js renders pages on the server, so crawlers that do not run JavaScript still see all the text. An analysis by Vercel and MERJ in December 2024 found that the crawlers behind ChatGPT and Claude do not execute JavaScript.
• Semantic structure. One H1, logical H2s, real lists and tables instead of nested builder containers. Models extract clean passages more reliably.
• Structured data built in. Organisation, service, FAQ and article schema are part of the components, so every new page ships with them automatically.
• Crawler control. robots.txt, sitemap and llms.txt are generated from the same content as the pages, so they never go stale.

To be fair: WordPress also renders HTML on the server, and a carefully built WordPress site can do all of this. The difference is that with Next.js it is the default, not something you add plugin by plugin. If AI visibility is your main goal, read our guide on how to get cited by ChatGPT or run the free GEO report.

Editing without WordPress: how our editor works

The most common worry we hear: “Can we still change texts ourselves?” Yes. Every site we build comes with our own editor (app.404media.at). It is made for exactly one job: changing the content of your website, without touching code.

Your team opens the page, clicks the text or image it wants to change, edits it right there with a live preview, and publishes. Because the design is fixed and only the content is editable, nobody can accidentally break the layout, which is the main difference to a page builder.

• Everything on the page: every text, image and button is editable, as are pages and collections such as projects or team members.
• Live preview: you see the change on the real page before it goes online.
• Language switch: German and English versions of the same content are one entry with a language toggle, not two copies to keep in sync.
• No plugins: nothing to install, nothing to update, no plugin that breaks after an update.
• Training: we train your team on request, usually in one short session.

What you give up: the WordPress plugin directory. A new feature, such as a booking form or a filter, is built rather than installed. For most company websites that is a benefit, because every feature is made for your site and does not drag 200 KB of extra script along.

Hosting in the EU and running costs

WordPress needs a PHP server, a database, backups, caching and a security plugin, and all of it has to be maintained. A Next.js site is mostly static files plus a few server functions. We host on Vercel with servers in the EU region (Frankfurt), which keeps load times short for visitors in Austria and Germany and keeps data processing in the EU.

In terms of budget, the move shifts costs. The one-off build of a custom Next.js site costs more than installing a theme, and less than people expect compared to a properly designed WordPress site. Ongoing effort drops, because the weekly update-and-test cycle disappears. For an honest comparison of prices in Austria, see our article on website costs. And funding may cover part of it: we check for free which funding fits you, see our website funding page.

WordPress vs. Next.js at a glance

How the move works without losing rankings

Most of the risk in a migration is not the technology. It is URLs that disappear. Google recommends keeping redirects for as long as possible, generally at least a year, so it can transfer all signals from old to new URLs. This is the sequence we use:

1. Crawl the old site. Every URL, title, description, H1, image and internal link, plus the pages that bring traffic according to Search Console and analytics.
2. Decide per page. Keep, merge or drop. Pages with traffic or backlinks are never simply deleted.
3. Build the redirect map. Every old URL gets exactly one new target via 301. No chains, no blanket redirects to the home page.
4. Carry over the content. Texts, metadata and structured data move into the editor, improved where they were thin.
5. Test on staging. Every redirect is checked automatically before launch, as are canonicals, hreflang and the sitemap.
6. Launch and monitor. Submit the new sitemap in Search Console, watch crawl errors and rankings for the first weeks, fix 404s immediately.

A short dip in the first weeks is normal while Google recrawls. With a complete redirect map it usually recovers quickly. The full checklist is in our guide to a website relaunch without losing SEO.

When WordPress is still the better choice

We do not rebuild every site, and you should not either. WordPress remains a good choice if:

• your site is mainly a blog with many authors who publish daily and know WordPress well,
• you rely on a specific plugin with no reasonable alternative, for example a membership system your business runs on,
• your current site is fast, secure, maintained and brings in enquiries, so a rebuild would solve a problem you do not have,
• your budget only allows a theme, and that is honestly enough for now.

And if you mainly sell products online, the better move is often neither: a store on Shopify is usually faster to run than a custom shop. We cover that on our e-commerce page.

Written byChristoph SpeiserProject lead & sales

Meet the team →