Three brands. Four countries. One website, copied four times, because that was the quickest way to get started.
This is a familiar scenario for companies entering new markets. A new country means a new copy of the website and a new account in the CMS dashboard, whilst a new brand means yet another separate system to keep track of.
The problem doesn’t arise straight away, but it becomes apparent as soon as the first change to the product range needs to be rolled out in four places at once: in Polish, German, French and English.
The hidden cost of copying content across brands and countries
Copying a webpage seems like the quickest way to get started. You duplicate it for a new country, change the language, and you’re done.
The problem arises, however, with the first update. A new section, offer or price has to be pasted in separately on each copy. With three brands and four countries, that’s already over a dozen places to edit manually each time.
This is exactly where errors arise. Someone will update the French site, forget about the German one, and as a result, the language versions start to take on a life of their own. The team’s time is spent repeating the same task, rather than on content and strategy.
A separate CMS for each brand or country - a simple decision that becomes more expensive over time
There is usually just one source of the problem: a separate CMS installation for each brand and market. A new brand, a new market, yet another separate installation. With just two such deployments, it isn’t a problem: each team has its own login and templates, and nobody gets in anyone else’s way.
However, each subsequent implementation increases the total maintenance cost more than the previous ones. Each one has to be updated, secured and manually enhanced with features that have appeared in a different version. Your IT team isn’t developing the product; it’s simply maintaining several parallel environments, often running on different versions of the same technology.
Separate systems also mean separate, independent decisions. The team in Germany changes the colour of a button, the team in France adds a section, whilst the Polish version sticks with the old layout. Each of these decisions makes sense on its own, but taken together, they result in a brand that looks and sounds slightly different in every country.
An inconsistent brand is not just a matter of aesthetics, but above all a matter of customer trust.
A classic CMS vs a headless multilingual CMS - the difference only becomes apparent at scale
A classic CMS, such as WordPress, links content to a specific page and template. The database, control panel and website design form a single, integrated system. Consequently, a new brand or a new market means starting from scratch.
A multilingual headless CMS works differently - the content is separated from the page’s layout. The repository of texts, images and data is stored in one place and is delivered to any number of pages via an API.
That’s what multisite is all about: a single installation supporting multiple brands and markets at once, rather than a separate copy for each one. Any change to a shared element, for example a new product image or a redesigned section of the website, is immediately reflected across all language versions. The text itself still needs to be translated, but there’s no need to manually copy and paste it into successive copies of the page.
It is the foundation that makes it easier to manage multiple brands and markets from a single location.
One content repository, multiple brands and countries - how does this work in practice
Separating content from presentation is just the starting point. It gets more interesting when you see how it works in practice, in a specific system such as Sanity or Payload.
Global components and regional exceptions within a single system
In such a system, most of the content is shared. The website structure, components and product catalogue originate from a single source and are deployed to all markets simultaneously.
Local variations apply only to individual fields, not the entire content structure. Prices in local currency, legal information required in a given country, or seasonal promotions specific to a single market: these are fields you can overwrite without affecting the rest of the content.
Sanity and Payload - the systems we work with most frequently, support this directly. They allow you to specify, right at the content model level, which fields are global and which are local.
A translation workflow without the chaos
Without a properly configured CMS, translating new content looks like this: export to a spreadsheet, email to the translator, import back in, and manually check that nothing has gone wrong.
A headless multilingual CMS manages this process in one place. New text is immediately visible as a missing translation in the other languages. The translator works within the same system, on the same content, without having to copy it to external files.
Roles and permissions - who edits what, in which country
The team in Germany should not be able to change the homepage in Poland, and the marketing team should not be able to modify the website’s code.
This system allows for a clear separation: who can view which content, who can edit it, and who merely approves it before publication. Global brand elements remain under the control of a single team, whilst local content remains under the control of the teams on the ground.
AI agents connected to the CMS via MCP
Modern CMS systems, such as Sanity, provide MCP servers. Thanks to this standard, the AI agent operates directly on the content within the system, rather than via manual clicks in the control panel.
In practice, this means that dozens or even hundreds of pieces of content - articles, product descriptions, website sections - can be updated all at once, without having to click on each one individually. Translating all of this into a new language would take a team a great deal of time if done manually, but an agent connected via MCP can complete the task in a matter of hours.
This does not replace human oversight. Your team still checks and approves translations before publication. The starting point does change though: instead of a blank page, they receive a ready-made version for verification.
For a company entering a new market, this is the difference between weeks of preparation and a launch within the same month.
What this means for your business - faster entry into a new market, a consistent brand across the board
A multilingual headless CMS changes the starting point for each new brand and market. Instead of spending weeks copying and adapting the website, your team starts with a ready-made content structure that simply needs to be translated and localised.
Your brand maintains a consistent look across all countries, as each version draws from the same content source, rather than from separate, independently developed copies. Your IT team maintains a single system rather than several running in parallel, and entering a new market no longer means starting a new project from scratch.
This is an architectural decision, not a cosmetic change to the CMS dashboard. Make the shift before the number of brands and countries grows to the point where rewriting the entire content structure costs more than building it right from the start.
