"Headless." The word comes up more and more in conversations about the web, dropped in by developers or agencies pitching you a redesign. Most SME owners nod politely without quite knowing what it means, and that is normal. The term is technical, the usual explanation stays abstract, and you are rarely told what your business gains from it.
This article does both: it explains simply what a headless architecture is, then shows, in concrete terms, what it changes for your online visibility, your performance and your freedom to develop your website.
The "traditional" architecture: what is being replaced
How a classic website worked (and still works)
To understand headless, you first need to understand the classic architecture: that of WordPress, Joomla, Drupal, Typo3 and most existing SME websites.
In a classic system (described as "monolithic" or "coupled"), everything comes in the same package:
- The database: stores your articles, pages, products, users
- The backend: handles the logic (PHP in the case of WordPress), retrieves the data, assembles the HTML
- The frontend: the templates, themes and styles that define the appearance
These three layers are inseparable. Changing your WordPress theme does not just change the design: it changes how content is structured, displayed and sometimes even stored. Migrating from WordPress to something else often means starting from scratch.
When a user visits your website, this is what happens:
- Their browser sends a request to your server
- The PHP server queries the MySQL database
- PHP assembles the HTML from the data and the template
- The HTML is sent to the browser
- The browser downloads additional CSS and JavaScript
- The page is displayed, often after several seconds
It is slow, fragile and coupled: content and presentation are tied to each other.
The headless body metaphor
"Headless" means without a head. The "body" is the backend (the database, the logic, the content). The "head" is the frontend: what the user sees in their browser.
In a headless architecture, the body (the CMS) and the head (the website) are two separate systems that communicate through an API. The CMS does not deal with how its content will be displayed. It makes its data available through an API (usually REST or GraphQL), and any "head" can connect to it.
This may seem more complicated, since there are two systems instead of one. In practice, this separation brings flexibility and performance that a coupled architecture cannot reach.
How a headless website works
The three components of a headless architecture
1. The headless CMS: this is where your editorial team works. The interface is modern, simple and accessible from a browser. Examples: Sanity, Contentful, Directus, Strapi, Payload CMS. You create an article and fill in the title, the text, the main image and the SEO metadata. The CMS stores all of this in a structured way and exposes an API.
2. The Next.js frontend: this is the website your users see. It connects to the CMS API, retrieves the content and generates highly optimised HTML. This process happens at build time (deployment), not on every visit. The result is stored on a global CDN.
3. The CDN (Content Delivery Network): the pre-generated HTML is distributed to servers all over the world, in Geneva, Zurich, Paris, London or New York. When a user in Zurich visits your website, they receive the HTML from a server a few milliseconds away, not from a shared server in Paris.
What this changes for the user
When a user visits a well-built headless website:
- Their browser sends a request to the nearest CDN
- The CDN responds with pre-built HTML, with no server-side processing
- The browser displays the content immediately
- JavaScript activates the interactive parts in the background
The user sees the content almost immediately. For Google, which measures LCP (Largest Contentful Paint), the gap is clear.
The SEO benefits of a headless architecture
Performance: a front-line criterion for Google in 2026
Google added Core Web Vitals to its ranking signals in 2021. Technical performance is therefore part of what Google measures, page by page, not a detail.
On a pre-generated headless Next.js website, Google's "Good" thresholds (LCP < 2.5 s, INP < 200 ms, CLS < 0.1) are easier to reach: the HTML is ready before the visit, served from a CDN, with no database to query and no PHP to run. On a coupled CMS, every plugin, every database query and every theme script adds to the loading time.
Indexing and rendering: a structural advantage
Google indexes your website by sending its crawler (Googlebot) to "read" your pages. A PHP-based WordPress site sends it HTML assembled on the fly: correct, but no more. A client-side JavaScript website (a pure SPA) sends it an empty page with a <div id="root">: Googlebot has to execute the JavaScript to see the content, which can delay indexing.
A headless Next.js website solves both problems:
Static Site Generation (SSG): all pages are pre-generated as pure HTML at build time. Googlebot arrives, finds complete HTML and indexes it immediately. No JavaScript to execute to see the content.
Server-Side Rendering (SSR): for pages whose content changes frequently, Next.js can render them on the server for each request, with real HTML in the response.
Incremental Static Regeneration (ISR): a mix of the two. Pages are pre-generated (with static speed) and regenerate automatically in the background when the content changes in the CMS. You publish an article in Sanity and it is live as pure HTML within seconds.
Structured data and rich snippets: a clean implementation
Structured data (JSON-LD) allows Google to display enhanced information in search results: review stars, product prices, expandable FAQs, business information. Your result takes up more space and invites the click.
In a headless Next.js architecture, implementing JSON-LD is simple and clean:
{
"@context": "https://schema.org",
"@type": "LocalBusiness",
"name": "Your SME",
"address": {
"@type": "PostalAddress",
"streetAddress": "Rue de Rive 10",
"addressLocality": "Genève",
"postalCode": "1204",
"addressCountry": "CH"
},
"geo": {
"@type": "GeoCoordinates",
"latitude": 46.2044,
"longitude": 6.1432
}
}
This JSON is injected directly into the <head> of each relevant page, generated dynamically from the CMS data. No plugin, no limited graphical interface, no workaround: Google receives exactly what it expects.
Multilingual sites and hreflang tags: the Swiss case
Switzerland is a multilingual market. A Geneva SME often targets French-speaking clients, but some sectors (finance, real estate, industry) also require a presence in German and English. Handling multiple languages properly for SEO is complex, and necessary to avoid duplicate content.
Hreflang tags tell Google which version of a page is intended for which language market:
<link rel="alternate" hreflang="fr-CH" href="https://example.ch/fr/article" />
<link rel="alternate" hreflang="de-CH" href="https://example.ch/de/artikel" />
<link rel="alternate" hreflang="en-CH" href="https://example.ch/en/article" />
Next.js handles internationalisation (i18n) natively through its routing system. URLs, metadata, hreflang tags and translated content are all managed consistently and automatically. The headless CMS stores the translations of each piece of content, and Next.js retrieves and displays them according to the user's locale.
On WordPress or a no-code platform, this is much harder to solve cleanly.
Flexibility and evolution: building to last
Content that feeds several channels
Reusing content is an often underrated benefit of headless. Your CMS stores structured content: no HTML, no presentation code, just raw data with its metadata.
That same content can simultaneously feed:
- Your main website
- A mobile app (React Native, Flutter)
- An internal chatbot or AI assistant
- Automatic exports to LinkedIn or your newsletter
- A partner website or a white-label version
With WordPress, your content is locked in MySQL tables and HTML generated by shortcodes. Exporting to another format requires manual work or fragile plugins. With a headless CMS and its API, a single API request is enough to retrieve the content in the format you need.
Changing the design without migrating the content
For an SME, this is probably the most practical long-term benefit. When your WordPress site ages and you want to redo it, you usually have two options:
- Change the theme, then spend weeks adapting your content to the new theme
- Start from scratch, then migrate all your content manually
With a headless architecture, the frontend and backend are decoupled. You can completely redo the look of your website (new brand identity, new animations, new navigation structure) without touching the CMS. Your content stays intact in Sanity or Contentful. Only the Next.js frontend changes.
In practice, a redesign therefore costs less than a full rebuild with content migration, since the content does not move.
Handling traffic spikes
A growing SME sees its traffic increase. A LinkedIn campaign that works, an article shared within your industry, a media partnership: traffic can surge within hours.
A WordPress site on shared hosting goes down under that load. Even with a well-configured VPS and a caching plugin, traffic spikes create bottlenecks on the database.
On a modern CDN, a headless Next.js website practically never goes down on its static pages. The HTML is served from edge servers, with no database to query and no PHP to execute. Vercel, Netlify and Cloudflare Pages adapt to the load automatically: there is nothing for you to configure, and you only pay for what you use.
The headless CMS market in 2026
The main players and how to choose
The headless CMS market has matured considerably since 2020. Here is an overview of the most widely used solutions in 2026:
For a Geneva SME, the choice depends on several factors:
Publishing volume and frequency: if you publish one article a month and rarely change your content, Markdown files versioned in Git are enough, at no cost and with maximum performance. If you publish several times a week with several authors, Sanity or Directus are better suited.
Data sovereignty: if your data must stay in Switzerland (regulated sectors, a preference driven by the Swiss FADP), Directus or Payload CMS self-hosted on an Infomaniak server is the solution. SaaS CMSs generally host in the United States or the EU.
Budget: the free Sanity plan is enough for many SMEs, as long as the editorial team and the volume of content stay modest. Check the current limits on the vendor's website before choosing.
What Swiss SMEs use in practice
The combinations most often seen in production are:
- Next.js + Sanity: a very common pairing for showcase websites and professional blogs
- Next.js + Contentful: favoured by companies with large editorial teams
- Next.js + Markdown (Git-based): for websites with stable content (showcase sites, portfolios)
- Next.js + Directus: for projects requiring sovereign data or maximum flexibility
In every case, Next.js dominates on the frontend. It supports SSG, SSR and ISR in the same project, with React 19 and Server Components, which makes it the default choice for current headless architectures.
Headless for Swiss SMEs: real-world cases
Medical or paramedical practice in Geneva
A medical practice has specific constraints: content that changes little (services, team, opening hours), but data sensitivity, Swiss FADP compliance, and the need to be easily found on Google for local searches ("general practitioner Eaux-Vives", "dentist Carouge").
Suitable architecture:
- CMS: Markdown or Payload CMS self-hosted on Infomaniak (data in Switzerland)
- Frontend: Next.js 16, static rendering (SSG)
- Hosting: Infomaniak or Vercel (zero exposed database)
- SEO: LocalBusiness + MedicalBusiness structured data, FR/DE hreflang depending on the area
Expected result: website loaded in 0.9 s, Lighthouse score 95+, immediate indexing by Googlebot, zero security maintenance.
Tradesperson or construction company in French-speaking Switzerland
A tradesperson wants to rank first on Google for their local keywords, showcase their projects and make it easy for clients to get in touch. Their website rarely changes: new photos of job sites, client testimonials.
Suitable architecture:
- CMS: Sanity (free, intuitive interface for publishing project photos)
- Frontend: Next.js 16, optimised image gallery, contact form via the Resend API
- Hosting: Vercel or Infomaniak
- SEO: schema.org HomeAndConstructionBusiness, gallery with optimised alt texts, one page per service
Expected result: each new project published in under a minute via the Sanity interface, pages indexed as pure HTML within the hour.
Geneva tech or SaaS startup
A tech startup needs a fast marketing website, a blog section for content marketing and a landing page that converts. It wants to iterate quickly: new features, A/B testing, integrations.
Suitable architecture:
- CMS: Sanity (flexible schemas, complete API)
- Frontend: Next.js 16 with React Server Components, GSAP animations
- Hosting: Vercel (edge functions for A/B testing, built-in analytics)
- SEO: dynamic sitemap, Open Graph per article, JSON-LD SoftwareApplication
Expected result: 100 articles published with no loss of performance, and the ability to change the design without touching the content.
Common misconceptions about headless
"It's too complex for an SME"
The complexity is on the developer side, not the user side. The admin interface of a CMS like Sanity is simpler than WordPress, and it is accessible from any browser, with no plugin to install. For a content editor, the difference from WordPress is either non-existent or positive.
The architectural complexity is dealt with once, during development, not every time you use it.
"It costs more"
The initial development cost is slightly higher than WordPress. But over 3 to 5 years, savings on maintenance, hosting, plugin licences and updates more than make up for the difference. The detailed figures are in the comparison table of our article on no-code.
You also need to count the cost of a slow website (lower Google rankings, lower conversion rates, a weaker brand image). It is hard to quantify, but real.
"It's only for large companies"
The biggest headless websites in the world do indeed belong to companies such as Nike, Spotify or Airbnb. But headless has become widely accessible. In 2026, Sanity offers a free plan suited to SMEs, hosting a Next.js website remains affordable (Vercel's free plan is limited to personal, non-commercial projects, so a business website goes on the paid Pro plan or with another host such as Infomaniak), and the development cost of a headless showcase website is comparable to that of a professional WordPress site.
It is no longer a question of budget, but of the developer's choice.
What INFUSE offers
INFUSE has built headless websites from the start. This is not about fashion: it is the architecture that gives the best SEO performance, the best user experience and the longest lifespan for an SME investing in its online presence.
Every project follows the same approach: Next.js 16 for the frontend, a headless CMS chosen to match the content volume and constraints (Sanity, Directus or Markdown depending on the case), hosting on global infrastructure or with Infomaniak if sovereignty is a requirement, and code delivered cleanly on Git.
For your Geneva SME, this means a website that loads in under a second, is indexed immediately by Google, can be updated by your teams without technical training, and can evolve over the next 5 years without a painful migration.
If your current website is holding you back (poor Google scores, risky updates, changes you cannot make), let's look together at what a modern architecture can do for your online visibility.
Frequently asked questions
What is a headless CMS?
It is a CMS kept separate from the website that displays the content. It stores content in a structured way and makes it available through an API (REST or GraphQL), and the website, for example built in Next.js, fetches it to generate its pages.
Is a headless CMS complicated to use day to day?
No. The complexity is on the developer side. For the person publishing, an interface like Sanity's works in a browser with no plugin, and is at least as simple as WordPress.
Can you change the design without rebuilding the whole website?
Yes. Because content and display are separate, the frontend can be completely redone without touching the content stored in the CMS. A redesign then costs less than a full rebuild with content migration.