A headless CMS is a content management system that stores content, such as pages, articles, product details and images, but does not decide how it looks. Websites, apps and other channels fetch the content through an API and display it in their own way. The "head" is the front end visitors see; a headless CMS separates it from where editors work.
Traditional CMS vs headless CMS
- Traditional (coupled) CMS: editing, templates and the public website live in one system. A typical WordPress-style site works this way: editors write a page, a theme controls the layout, and the CMS builds the page.
- Headless CMS: the CMS only manages content and makes it available through an API. A separate front end, such as a website, a mobile app or a kiosk screen, requests that content and handles layout and design.
- Hybrid: some traditional CMS platforms also offer an API, and some headless products add previews or page builders, so compare features rather than labels.
How content gets from the CMS to the screen
Editors fill in structured fields rather than one large page; a product entry might have a name, description, price, images and category. The front end asks the CMS API for the entries it needs and places each field in its own design. Many sites pre-build pages and rebuild them when content changes, often triggered by a webhook from the CMS, then serve them through a CDN.
Because content is not tied to one layout, the same entry can appear on the website, in a mobile app or a progressive web app, or in another system connected through system integration.
Multilingual content
A business publishing in English, Traditional Chinese and Simplified Chinese can store each language as a version of the same entry, with its own title, text, URL slug and SEO fields. Check how a missing translation is handled, whether alt text can differ by language, and whether editors can see which languages are incomplete.
Benefits
- Design freedom. The front end is not limited by theme templates.
- One source for several channels. A website and an app can share entries, so an update is made once.
- Performance options. Pre-built, cached pages can help speed, though results depend on the front end.
- Separation. The public site does not expose the editing system, and either side can be rebuilt later.
Drawbacks
- Needs developers. Someone must build and maintain the front end; a new page type usually means development work.
- Harder preview and editing. Editors work in forms, not on the page, so seeing a draft as it will look needs a preview set up between the CMS and the front end.
- Higher build cost. Content models, the front end, previews and deployment all need to be planned and built.
- More moving parts. The CMS, front end and hosting may come from different providers, each with its own plan and limits.
When a small business should, and should not, choose one
A headless CMS often fits when content must appear in more than one channel, the site needs a design a theme cannot handle, several languages must stay in step, or the website is part of a larger web app. It also assumes ongoing development support.
It may not be worth it for a small company site that changes a few times a year, when no developer will be available after launch, or when editors want to drag and drop layouts themselves. A well-maintained traditional CMS or a hosted website builder can be simpler. See also five concepts to know before building a website.
Illustrative example: A training centre shows course details on its website and in a member app. With a headless CMS, staff change a course date once and both show it.
Checklist before choosing a headless CMS
- Which channels will use the content now and in the next few years?
- What content types do you have, and which fields does each need?
- How many languages, and who approves each one?
- Do editors need a visual preview, and how will changes be tested in a staging environment?
- Who maintains the front end after launch?
- What do the CMS plan limits cover (users, API requests, storage), and can you export your content later?
- Does it need to connect to booking, payment or CRM systems?
- Should the front end be a website, web app or mobile app? See web app vs mobile app.
See our website and web app development service or our mobile, web and WeChat app development page.
Frequently asked questions
Is a headless CMS better than WordPress?
Not in general. A traditional setup is often quicker for a simple site that editors manage alone; a headless setup gives more control over design and channels but needs development support.
Can WordPress be used as a headless CMS?
Yes. WordPress includes a REST API, so a separate front end can fetch its content, but you give up some theme features and must build that front end.
Is a headless website good for SEO?
It depends on the front end. Search engines see the pages they receive, so the front end must output proper titles, descriptions and language tags, and load quickly.
Can we move an existing website to a headless CMS?
Often, but treat it as a project: content is mapped into new fields, URLs kept or redirected, and the front end rebuilt.