Comparisons

Next.js vs WordPress for a marketing site

WordPress suits a marketing site that a non-technical team edits every week and extends with plugins; Next.js suits one that needs custom design, speed and control at code level, with a developer looking after it. We build in Next.js, and we say so when WordPress or Webflow would serve a client better.

The two are different kinds of thing. WordPress is a content management system: PHP and a database, an editor in the browser, themes for the look and a large catalogue of plugins for features. Next.js is a React framework: a developer writes the pages in code, and content comes from files in the repository or from a headless CMS connected to it.

That difference decides who can change what. On WordPress an editor can add a page, change a menu or install a form plugin without a developer, which is its main strength. On Next.js the editor changes content in whatever CMS the site is given, and anything about layout or features is a code change. That suits a team with a developer, and frustrates one without.

The second difference is upkeep. A WordPress site runs on a server that executes PHP on request, and its core, theme and plugins all need updating; each plugin is code from a different author with access to the whole site. A Next.js marketing site is often built ahead of time into static pages, so there is less running on the server to patch, but its dependencies still need updating and someone has to know how.

Speed is possible on both and guaranteed on neither. A light WordPress theme with caching can be fast; a Next.js site loaded with scripts can be slow. What Next.js gives is control: every script on the page is one somebody chose to add. We measure the result, not the framework.

Side by side

AspectNext.jsWordPress
What it isA React framework; pages are codeA content management system; pages are records in a database
LanguageTypeScript or JavaScript, on Node.jsPHP, with MySQL or MariaDB
Who edits contentEditors in a headless CMS, or developers in filesEditors in the built-in admin
Adding a featureWritten in code or added as a package by a developerUsually a plugin, installed from the admin
HostingStatic hosting or a Node platform such as VercelAny host that runs PHP and a database
UpkeepDependency updates in the code, by a developerCore, theme and plugin updates, often from the admin
Design freedomAnything the developer buildsWhat the theme allows, unless it is custom-built
Best fitCustom sites, apps and sites that share code with a productContent-heavy sites run by a non-technical team

When to choose Next.js

  • The site is closer to a product than a brochure: logins, search, a configurator, data from your own systems.
  • The design is custom and has to stay exact, and you want control over every script on the page.
  • You have, or will pay for, a developer who maintains the code after launch.

When to choose WordPress

  • A non-technical team publishes often and needs to add pages and features without asking a developer.
  • The features you need exist as well-maintained plugins, and the budget favours configuring over building.
  • You have a host or agency that keeps WordPress core, theme and plugins updated.

An example from our own sites

All our own sites are built in code. Envision Deco runs on Next.js 14, with its idea pages kept as typed data and its guides in MDX. The BrandableWorks portfolio is a Next.js static export, and each brand package it sells comes with a ready-to-launch Next.js site. Videojam, our own platform, is a Next.js build with a Studio CMS we wrote for it, with an audit log and 30-day undo, which is the part WordPress would have given us out of the box and we chose to build. audacian.eu itself is a React site prerendered page by page at build time. We do not run a WordPress site of our own, which is why this page makes no claim about WordPress performance from our data.

Questions

Is Next.js better for SEO than WordPress?
Neither is better by itself. Both can serve crawlable HTML, clean URLs and structured data. What matters is how the site is built and maintained.
Can a Next.js site be edited without a developer?
Its content can, through a headless CMS connected to it. Changes to layout and features still need a developer.
Do you build WordPress sites?
No. We build in Next.js and TypeScript, occasionally in Webflow for a quick marketing site, and we say so when another tool would serve a client better.

Tell us what you're launching.

Book a 20-minute intro call, or email a few lines about what you're launching. We'll reply with a rough plan and a price range, whether or not we end up working together.