Every few weeks a founder asks me the same question: "Should we build this on Next.js or WordPress?" The honest answer is that it depends on who will touch the site after launch, not on which technology is newer. Here is the exact conversation I have with clients, and the rule of thumb I use.
Start with who edits the site
The stack question is really a workflow question.
| If this is true | Lean towards |
|---|---|
| Marketing team publishes landing pages and blog posts every week | WordPress |
| Content changes rarely, design and interactions are the product | Next.js |
| Team edits content daily but the frontend must be fully custom | Headless (WordPress backend, Next.js frontend) |
| You sell products and need checkout, taxes and shipping today | WooCommerce |
If nobody on the team will log in and edit pages, a CMS is overhead. If three people will, a CMS is the whole point.
What Next.js gives you
- 1
Speed by default
Server rendering, image optimisation and code splitting are built in, so a Next.js site is usually green on Core Web Vitals before any tuning.
- 2
Total control of the frontend
Design systems, animations and custom components are first-class. No theme is fighting you.
- 3
Cheap, simple hosting
Vercel or Cloudflare handle deploys, previews and a global CDN for a few dollars a month.
- 4
A developer in the loop
Copy and layout changes go through code and a deploy. Fine for some teams, a bottleneck for others.
Related guide: Is Tailwind CSS a good choice for a marketing website?
What WordPress gives you
- Editing without a developer. Your team can ship a landing page on a Tuesday afternoon.
- A plugin for almost everything, from forms and CRM sync to multilingual sites and WooCommerce.
- Predictable hosting and talent. Any agency can take it over later.
- A speed tax you have to manage. Caching, image formats and plugin discipline are non-negotiable, otherwise mobile scores sink.
The plugin rule
I cap client sites at a dozen active plugins. Every plugin above that number is a future performance ticket.
Related guide: Headless WooCommerce with Next.js: cost and is it worth it?
When headless is worth it
Headless means WordPress stays as the editing backend and a Next.js app renders the pages through the REST API or WPGraphQL. You get the editor experience and the fast, custom frontend. The price is integration: previews, redirects, forms and SEO metadata all need wiring up, which adds a week or more to a build.
I recommend it when both of these are true: the content team is active, and the frontend genuinely needs to be custom. If only one is true, pick the single stack.
Related guide: WordPress to Next.js migration cost: what you pay for
The SEO question, answered honestly
Google does not rank a stack. It ranks fast pages with clear structure, real content and good links. I have ranked WordPress sites at number one and Next.js sites at number one. The differences:
- Next.js makes speed and structured data easy to get right in code.
- WordPress makes publishing easy, which matters more for content-led SEO.
Whichever you choose, the checklist is the same: server-rendered HTML, green Core Web Vitals on mobile, one H1 per page, schema markup, a generated sitemap and canonical URLs.
Related guide: How much does a headless WordPress site cost?
My rule of thumb
If you remember one thing: choose for the team you have, not the team you imagine. A WordPress site a marketing team actually updates beats a Next.js site that goes stale because every edit needs a developer. And a Next.js site that loads in under a second beats a plugin-heavy WordPress site every time.
Not sure which one you are? Send me two lines about the project and who will maintain it, and I will tell you which way I would go. For a quick first opinion, the free Tech Stack Advisor recommends a stack with reasons and trade-offs.
