Updated
Guide · Care
Headless or traditional WordPress
Headless sounds modern, but it's often sold as the answer to problems the client doesn't have. In this article, we explain what headless WordPress means, when it's the right choice and when traditional WordPress is better, cheaper and easier to maintain.
Updated
Our rule for choosing technology is fitness for purpose, not novelty.
What headless means
In a traditional WordPress site, content management and the front end are one whole. You enter content in WordPress, and WordPress also shows it to visitors through the theme. Headless architecture separates the two. WordPress acts as a content store and serves the content through an API. The front end is built separately, for example with React or Angular. The same content can then appear on the website, in a mobile app and even on an information screen at your premises.
The back end doesn't have to be WordPress. Contentful or a custom-built system can also act as the content store. Even so, we usually recommend WordPress. Content producers already know it, they edit content in the familiar block editor, and users, roles and publishing workflows are ready to use. Maintenance and security updates for the back end work the same way as on an ordinary WordPress site. So the complexity of a headless build stays on the front-end side.
Portals, apps and content for many channels
- The same content in many channels. When a website, an app and other channels use the same content, one content store with several front ends is clearer than copying content around.
- Large portals. News portals, member portals and learning platforms with lots of information and interactivity benefit when content management and the front end develop separately.
- Custom applications. Intranets, customer portals and staff tools whose front end has to work like an app can't be built with a traditional theme.
In these cases, headless brings flexibility and scalability that the traditional structure can't. We describe the architecture and its use cases on our Headless architecture page.
An ordinary company website doesn't benefit from headless
We don't recommend headless architecture for ordinary websites. The reasons are practical:
- Maintenance costs more. You have a front end, a back end and APIs to maintain, each with its own updates.
- You need skills in several technologies. Front-end development and API management are different from WordPress development. That shows in the number of people needed and in the price.
- Development takes longer. If the schedule is tight, traditional WordPress gets you to launch faster.
- Editing content is more work. In the WordPress block editor, a marketer sees what the page will look like. In a headless build, previewing and putting pages together often needs separate tools or a developer.
If the site's job is to present your company, generate leads and be easy for marketing to update, traditional WordPress does it better and for less.
Four questions before you decide
Ask yourselves
- How many channels will the same content go to over the next three years?
- Does the front end need logins, roles and content tailored to each user?
- Who updates the content, and do they need to see the result without a developer?
- Is there budget to maintain two systems after launch?
If the answer to the first is “one” and to the third “marketing”, choose traditional WordPress. If the first two are “many” and “yes”, it's worth working out what headless would cost.
Frequently asked questions
Is a headless site faster?
It can be, because the front end is built for exactly that purpose. But a well-built traditional WordPress site is fast enough for almost any company website. Speed alone is not a reason to maintain two systems.
Can we move from traditional WordPress to headless later?
Yes. The content stays in WordPress and the front end is rebuilt on top of the API. That's why WordPress is a safe back end even when the need for several channels only comes up later.
What does headless WordPress cost?
More than a comparable traditional build, because the build is larger and there are more systems. We agree a fixed price before we start, as with any other website or online service.
Summary
Headless is a tool for portals, apps and content in many channels. For an ordinary company website, it's an extra system to maintain. If you're not sure which side your project falls on, ask us. We'll tell you when the answer is traditional WordPress, too.
Related
Whole guideFAQ
Can I cancel the Care agreement?
Yes. The Care (Huolenpito) agreement can be terminated monthly. We want to earn your trust with results, and we do not tie you in with long contracts. If the service stops being useful to you, you can end it at the close of any month.
FAQ
Does a website need a privacy policy?
Yes. The EU's GDPR obliges every site that processes personal data, which in practice means almost all of them. We help you put a privacy policy and a cookie banner in place as part of the project.
FAQ
How are cookies and GDPR handled?
We install a cookie consent tool on the site. It asks the visitor for consent before analytics and marketing cookies are activated, so nothing is switched on before the visitor has chosen. The tool complies with GDPR requirements.
Want help with your decision?
Tell us your situation. We will get back to you by the next working day at the latest.