I looked into headless WordPress seriously. Next.js on the frontend, WordPress as a headless CMS through the REST API, all the modern architecture benefits. The more I researched, the more I realized it makes no sense for the kind of work I do.<\/p>\n
Headless WordPress has real advantages in the right context. Faster frontend performance, tighter control over the markup, and the ability to use modern JavaScript frameworks for the presentation layer. These benefits are real \u2014 for specific projects with the budget and infrastructure to support them. But the right projects are not the ones I build, and the trade-offs are not worth it for the Algerian market I serve.<\/p>\n
My clients are on shared hosting. The economics of the Algerian market do not support VPS or dedicated server costs for a small business website. Shared hosting at 500 to 1,000 DA per month is what clients will pay and what makes sense for their budget. That hosting runs Apache or LiteSpeed with PHP and MySQL \u2014 exactly what a standard WordPress installation needs. It does not run a Node.js process for a Next.js frontend.<\/p>\n
To run headless WordPress, I would need at minimum a VPS capable of running both the WordPress backend and a Node.js server for the Next.js frontend. Alternatively, I would need two separate hosting services \u2014 one for the WordPress database and admin, another for the JavaScript frontend. Both options multiply the monthly hosting cost by five to ten times. For a client paying 30,000 to 60,000 DA for a full site build, adding a 5,000 DA monthly hosting bill is not feasible. The math simply does not work.<\/p>\n
WordPress plugins power most of the functionality my clients need. WooCommerce for online stores. Jetpack for security and performance. Contact form builders. SEO management tools. These plugins generate their output through WordPress’s standard template rendering system. The admin interfaces, the shortcodes, the template hooks \u2014 all of them expect the standard WordPress frontend pipeline to be running.<\/p>\n
In a headless setup, the plugin output does not automatically appear on the frontend. The WooCommerce cart, checkout, and product pages \u2014 all the e-commerce functionality \u2014 needs to be rebuilt on the JavaScript side. The contact form markup needs custom implementation. The SEO meta tags need to be extracted through the REST API and injected into the Next.js head. Every plugin that the client relies on becomes an integration project.<\/p>\n
Some plugins offer REST API endpoints. Many do not. The ones that do often expose partial functionality, missing critical features that the standard template system provides without effort. I would spend more time building custom integrations between plugins and the headless frontend than I currently spend building the entire site on a standard WordPress stack. That development time has to be billed to the client, which makes an already expensive project prohibitively costly. The value proposition collapses before the first line of code is written.<\/p>\n
Search engine optimization is critical for my clients. A local business website that does not rank on Google for relevant searches is a wasted investment. Standard WordPress handles SEO well \u2014 the server renders the full HTML response on every request, search engines crawl the content easily, and plugins like Yoast or Rank Math handle the meta tags and structured data without any additional configuration.<\/p>\n
Headless WordPress requires a server-side rendering setup for the frontend. Without SSR, the search engine bot receives an empty HTML shell with JavaScript tags and cannot index the actual content. Setting up SSR with Next.js adds a significant layer of complexity beyond the standard WordPress setup. Deploying it requires a Node.js-capable server or a serverless platform that costs more than shared hosting. Monitoring the deployment means understanding both the WordPress backend infrastructure and the Next.js frontend deployment \u2014 two separate systems with separate failure modes. Every maintenance task is doubled. Every deployment concern is doubled. The complexity grows faster than the benefit.<\/p>\n
I can think of specific scenarios where headless WordPress would be worth the overhead. A content-heavy site with a dedicated development team managing both the backend and the frontend separately. A project where the frontend needs to be a mobile app or a React-based single page application. A client with a large budget who needs custom frontend interactions that WordPress templates and page builders simply cannot deliver. These projects exist, but they are not the majority of web development work, and they are certainly not the projects I typically work on as a solo developer in the Algerian market.<\/p>\n
For the standard small business website \u2014 a clinic wanting online booking, a restaurant needing a menu and contact page, a hardware store requiring e-commerce, a service provider asking for a professional portfolio \u2014 standard WordPress with a well-coded theme delivers everything the client needs at a fraction of the cost, time, and complexity. The headless approach solves problems that these clients do not have and introduces problems they never asked for.<\/p>\n
Headless WordPress is a solution looking for a problem in most cases. It is an interesting architectural choice for specific situations, but the developer content ecosystem promotes it as the default modern approach, which it is not for the majority of real-world projects. For solo developers working in price-sensitive markets with shared hosting budgets and plugin-dependent client requirements, standard WordPress is the correct choice every time.<\/p>\n
The architecture that ships the site fastest, costs the least to maintain, and requires the fewest specialized services is the architecture that wins in a market where budget and timeline are the primary constraints. I am glad I studied headless WordPress \u2014 understanding the trade-offs helped me make an informed decision rather than following a trend. My conclusion is that it is the wrong tool for my clients. I use standard WordPress because it solves their actual problems without creating new ones that they would have to pay me to solve again.<\/p>\n","protected":false},"excerpt":{"rendered":"
The ‘Headless WordPress’ movement has matured into the definitive architectural choice for the high-end industrial web. By decoupling the Word…<\/p>\n","protected":false},"author":1,"featured_media":851,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"rank_math_title":"","rank_math_description":"I studied headless WordPress + Next.js. It needs a VPS, breaks plugin output, and complicates SEO. For shared hosting clients, standard WordPress wins.","rank_math_focus_keyword":"Why I don't use headless WordPress for client sites","rank_math_canonical_url":"","footnotes":""},"categories":[3],"tags":[14,8],"class_list":["post-241","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-web-design","tag-performance","tag-wordpress"],"blocksy_meta":[],"_links":{"self":[{"href":"https:\/\/nassimstudio.com\/blog\/wp-json\/wp\/v2\/posts\/241","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/nassimstudio.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/nassimstudio.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/nassimstudio.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/nassimstudio.com\/blog\/wp-json\/wp\/v2\/comments?post=241"}],"version-history":[{"count":7,"href":"https:\/\/nassimstudio.com\/blog\/wp-json\/wp\/v2\/posts\/241\/revisions"}],"predecessor-version":[{"id":1477,"href":"https:\/\/nassimstudio.com\/blog\/wp-json\/wp\/v2\/posts\/241\/revisions\/1477"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/nassimstudio.com\/blog\/wp-json\/wp\/v2\/media\/851"}],"wp:attachment":[{"href":"https:\/\/nassimstudio.com\/blog\/wp-json\/wp\/v2\/media?parent=241"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/nassimstudio.com\/blog\/wp-json\/wp\/v2\/categories?post=241"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/nassimstudio.com\/blog\/wp-json\/wp\/v2\/tags?post=241"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}