EMPIREYO
← Insights
Web developmentupdated 12 November 202614 min read

Headless CMS: why we choose Directus

Your website and your content are not the same thing. A headless CMS keeps the two apart. That has advantages, but it does not suit every site.

In short

A headless CMS is an editing environment without a website of its own: you manage the content there, and a separate website fetches it. That keeps the site light and lets the same content appear in more places. We suggest Directus when there is a lot of content that changes often. For a small site that rarely changes, it is usually too much.

On many websites, the editing side and the site itself are one system. That works, until the content also needs to appear somewhere else, the site needs to be faster, or you want to rebuild the front end without migrating everything. That is where a headless CMS comes in.

This article explains what that is, how it differs from WordPress, what it means for how easily you are found in search, when we suggest Directus and when something simpler fits better. With an example from our own work.

What is a headless CMS?

A traditional CMS glues content and design together: think of a theme that decides how your pages look. A headless CMS keeps the two apart. The content lives in the CMS, and a separate website (the front end) decides how it looks. The content travels through a fixed connection, an API, to your website, an app or another channel.

“Headless” literally means without a head: the editing side has no front end of its own. An example. You enter a vacancy once, with fields for title, location, hours and description. The website shows it on the vacancies page, an app shows it in a list, and a staff portal shows only the internal vacancies. Three places, one entry.

How is it different from WordPress?

A classic CMS such as WordPress is website and editing environment in one. Directus only does the editing side: it puts a clear editing environment on top of a database, and the website fetches the content from there through an API. A third option is a site without an editing environment, where the developer changes the text.

WordPressHeadless CMS, such as DirectusSite without an editing environment
Where does the content live?In WordPress itself, together with the theme and the pluginsIn its own database with an editing environment on topIn the files of the site
Who makes the pages?WordPress, with a themeA separate website, for example in Astro or NuxtThe whole site is built in advance
Edit text yourself?YesYes, with permissions per role and per fieldNo, the developer does that
Same content in more places?Possible, but it is not designed for thatYes, through the APINo
SuitsAnyone who wants to manage a lot themselves in a familiar systemA lot of content that changes often, or content for several channelsA small site that rarely changes

There is also a middle ground: an editing environment that stores the text in the site's own files, without a database of its own. We used that for TaalPro; more on that in the box further down. How we weigh WordPress against a custom build is set out in WordPress or custom.

Why does headless make a site faster?

The speed does not come from the CMS, but from the website that shows the content. Because that website does not have to carry an editing system, it can stay light. We build that front end in Astro or Nuxt. A site in Astro goes online as ready-made pages; an application in Nuxt builds the page on the server, so the visitor gets a finished page straight away instead of an empty screen that still has to fill up.

The separation brings three more things:

  • Flexibility: the same content on several channels, without duplicate work.
  • A front end you can replace: you redesign and rebuild the website while the content stays where it is.
  • Less exposed: the editing environment does not have to sit at the same address as your website, and the website itself has no login screen for visitors.

For how fast the sites we built load on a phone, see why every second of load time counts.

What does headless mean for your search visibility?

Headless in itself does not make your site easier or harder to find. What counts is what a visitor and a search engine receive when they open a page. Google writes that it is still a good idea to build pages on the server or in advance: it makes your site faster for users and for the programs search engines use to crawl it, and not all bots can run JavaScript.

Google runs JavaScript itself, but sometimes only later. Other bots do not always do so, and on a site that builds everything in the browser they see an empty page. That is why we build the pages in advance (Astro) or on the server (Nuxt). What else to sort out on a headless site:

  • A title and description per item. Give every type of content in the CMS fields for the page title and for the description in search results, so the editor fills them in.
  • Structured data. The website automatically turns the fields in the CMS into the description for search engines in the code, for example for an article, a vacancy or a question and answer. Structured data is part of our work on technical SEO.
  • Web addresses that stay the same. If you move from an old site, make a list of old and new addresses, so visitors and search engines land on the right page.
  • A sitemap that keeps up. Every new page from the CMS automatically goes into the list of addresses for search engines (the sitemap).

What is Directus?

Directus puts an editing environment on top of an ordinary database. According to the Directus page on GitHub, it works with the well-known SQL databases, such as PostgreSQL and MySQL, and creates the connection itself (a REST and a GraphQL API) that your website uses to fetch the content.

That makes a practical difference. The website can stay light and fast, because it does not carry an editing system. You can rebuild the website later without moving your content. And the same content can appear on your website, in an app or in a portal at the same time.

What do you see as an editor?

No code and no page builder, but an overview per type of content: a list of vacancies, a list of locations, a list of articles. Open one and you see a form with exactly the fields that belong to that type, such as title, location, photo and text. You can add a status field, such as draft or published, so that something only appears on the site when it is ready. The website decides how the page looks; you take care of the content. That keeps the pages in the same layout, even when several people fill in text. Note: on a site built in Astro, a change only appears after the site has been rebuilt.

Why do we suggest Directus?

Directus can run on your own server. Your data then sits in a database you manage yourself, and you are not tied to one supplier for storage. Permissions go down to the individual field, so an editor sees what they need and nothing more. It is as pleasant for the developer (a clean connection) as for the editor (a clear editing environment).

Mind the licence. Since version 12 (May 2026), Directus has had a new licence, the Monospace Sustainable Core License; before that it was the Business Source License. The source code is public on GitHub. According to Directus, organisations below a limit in annual revenue and number of employees use the full platform without software costs. Above that limit there is a free basic version with restrictions, and a paid licence for more users or extra features. The pricing page was changed on 2 November 2026 and is not clear on every point. Read the terms before you choose.

When does Directus fit, and when not?

Directus fits when your content is more than a few pages: products, locations, vacancies, articles in several languages, or data that also ends up in an app or portal. Then it pays for that content to have its own, well-organised place.

Choose Directus if...Choose something simpler if...
You have a lot of content that changes often, such as vacancies, locations or productsYour site has ten pages that change a few times a year
Several people enter content, each with their own permissionsOne person changes a text now and then
The same content has to appear on your site, in an app or in a portalThe content only appears on your website
You want to rebuild the website later without moving the contentYou already have a system you know and that works well
You want to keep your data on your own serverYou do not want a server that needs maintaining

For a small site that rarely changes, it is often too much. Then we choose a static site without an editing environment, or a CMS you already know. And if you want to create new pages and their layout yourself, we build in WordPress, as we did for Daily Phones. In Directus you fill in content in fixed fields; the website decides how the page looks.

What should you ask your developer?

If you receive a proposal with a headless CMS, ask these questions before you sign:

  • Where does the editing environment run, and who keeps it up to date?
  • Which licence does the CMS have, and what does it cost at our size?
  • Can we export the content if we want something else later?
  • How do we see a page before it goes live?
  • Who may change what, and how do we set that up?

A good developer has a short, concrete answer to each question.

And a headless webshop?

A webshop can be headless too: a fast front end on top of a shop system, connected to your own systems. We choose that when speed and integrations matter most. If you mainly want to manage products and pages yourself, WordPress is often the more logical choice. We can advise on that after a single conversation; more on our ecommerce website page.

How do we set it up?

  1. Map the content. Which types of content there are, which fields each type has, and who may change what.
  2. Permissions per role. Directus has permissions down to the individual field, so an editor only sees what they need.
  3. Build the website. In Astro or Nuxt, fetching the content from Directus. How we build the website itself is on our web development page.
  4. Hand over. You get an admin manual to edit text and images yourself, step by step, and technical notes on hosting, domain and integrations.
  5. Keep it up to date. A CMS gets updates too. With a maintenance plan they are applied on a fixed schedule.
“Your content is not a by-product of your website, but something you take with you for years.”

What does switching involve?

If you already have a site, moving to a headless CMS is more than a new editing environment. Expect these steps:

  • Moving the content. Text, images and documents go from the old system into the fields of the new one. It is often also the moment to clear out what nobody reads any more.
  • Keeping addresses. Every old page that is found in search or that other sites link to gets a redirect to its new address.
  • Reviewing images. Photos that are too heavy or the wrong size make a new site slow as well.
  • Bringing people along. Whoever keeps the content up to date needs to know the new editing environment. A short introduction and the admin manual stop everyone from falling back on emailing the developer.

What maintenance does it need afterwards?

A headless site has two parts that need looking after: the editing environment with its database, and the website. Both get updates, and the database needs a backup that can be restored. If you host Directus yourself, you need someone to look after the server, the database and the backups. Factor that into your choice from the start, not once the site is finished.

When this does not apply

If you have a site of a handful of pages that rarely changes, a headless CMS mainly adds extra parts: a server, updates and a connection that all need maintenance. If your business runs on a WordPress site with plugins you rely on, switching is a project of its own with its own costs, and not automatically an improvement.

What we do not know: we have not measured whether a headless site ranks better in Google than the same site in WordPress; that depends on how it is built, not on the CMS. A client project with Directus is not yet on our site as a case; the example above uses Sveltia CMS. And the Directus licence terms may have changed again after 3 November 2026.

Frequently asked questions

What is a headless CMS?+
An editing environment without a website of its own. You manage the content there, and a separate website or app fetches it through an API. That way the same content appears in more places, and you can rebuild the website without moving the content.
Is a headless CMS better for SEO?+
Not by itself. What counts is that the website delivers complete pages. Google writes that it is still a good idea to build pages on the server or in advance, because not all bots run JavaScript. That is why we build pages in advance in Astro or on the server in Nuxt.
Is Directus free?+
For small organisations below a limit in revenue and staff, yes, according to Directus. Above that limit there is a free basic version with restrictions, and a paid licence for more users or extra features. The terms changed in 2026, so read them before you choose.
Can I edit my own text in a headless CMS?+
Yes. That is exactly the point: you change text, images and other content in the editing environment, without code. In Directus you set permissions down to the individual field, so each editor only sees what they need.
When is a headless CMS too much?+
For a small site that rarely changes. Then it mainly adds extra parts that need maintenance. A static site without an editing environment, or a CMS you already know, is often the better choice.

Wondering what it would mean for you? Tell us what content you have and who keeps it up to date, and we will tell you whether headless is a good fit. More about how we build is on our Astro and Nuxt pages. You work directly with Nawid, with a fixed team of five specialists.

Sources

Consulted on 3 November 2026.

NR
Nawid RasaFounder of Empireyo · in design, development & strategy since 2014

Written with the help of AI, reviewed and edited by Nawid Rasa, who is responsible for the content. Sources are listed below the article. Spotted an error? Email hi@empireyo.com.

Ready for a platform that performs?

We advise on the right architecture and build a foundation that lasts for years.

What do you have in mind?
What budget do you have in mind?
When do you want to launch?
Almost there. How do we reach you?
Request sent.

Your request has reached us. You will usually hear back within two working days. Prefer direct contact? Email hi@empireyo.com or message us on WhatsApp with the chat button at the bottom right.

Reply within two working days · No obligation · privacy