Translation sounds simple enough. Take your English content, convert it into another language, publish it, job done. Lovely. Kettle on. Sadly, multilingual website management has a habit of turning into a digital sock drawer if it is not planned properly. You start with one language variation, then suddenly someone asks whether the French campaign page should use the same hero image, whether the German team page needs a different legal disclaimer, and why the Spanish homepage is still showing last year’s Christmas banner in March.
The good news is that Umbraco is very well suited to multilingual content management when it is set up with care. The even better news is that most translation headaches can be avoided before anyone opens the CMS. This guide explains how to manage content translation in Umbraco in a practical, editor-friendly way, covering structure, workflows, SEO, localisation, and governance.
If you are planning a new multilingual build or trying to untangle an existing one, our Umbraco multilingual website services explain how Gecko helps organisations create multilingual Umbraco platforms that are easier to manage, scale and support.
Start with your content model, not the translation
The biggest mistake is treating translation as something you bolt on at the end. That is a bit like building a house and then remembering you wanted plumbing. You can do it, but everyone involved will be a little damp and cross.
In Umbraco, your content model should be designed with language variation in mind from the start. That means deciding which properties should vary by culture and which should stay shared. A page title, summary, body copy and SEO meta description will usually need to vary by language.
This matters because over-localisation creates needless editor work, while under-localisation creates a poor user experience. A university might translate course descriptions but keep application deadlines aligned globally. A healthcare organisation may need translated patient-facing copy but centralised regulatory wording. A tourism brand may want localised calls to action depending on audience and market.
Umbraco gives you flexibility, but flexibility needs decisions. Before content is translated, agree what should be translated, what should remain shared, and what each language team is allowed to adapt. This includes Content Nodes, Multi-Value Property Editors, Site information, Current page settings and any content duplication rules that could affect how translations are created or maintained.
Choose the right multilingual structure
Umbraco gives you a few ways to organise multilingual content. The most common approach is to use variants, where one content node can have different language versions. This keeps the content tree tidy and helps editors see related translations in one place.
Another option is to create separate site trees for each language or region. This can be useful when markets have very different content, navigation, products or legal requirements. The trade-off is that it can become harder to maintain consistency. You get more flexibility, but also more moving parts. And more moving parts are where the swearing usually begins.
For many organisations, language variants are the most manageable route. They allow content editors to switch between language versions, compare status, and keep translated content connected to the source page. Separate trees may still be better for complex regional sites where language is only one part of localisation. For example, an English UK site and an English US site may need different spelling, pricing, legal pages, product availability and conversion journeys.
The right structure depends on how closely aligned your language versions need to be. If most pages are equivalent across languages, variants usually make sense. If each region behaves like its own website, separate trees may be cleaner. You should also define the root site, Default Language, target languages, and Backoffice Language before editors sign in and start creating content.
Create a clear source language workflow
Before you translate anything, agree which language acts as the source. Usually, this will be English for UK organisations, but not always. The source language should be treated as the master content version from which translation begins. That does not mean every local market is less important. It simply gives your team a clear starting point.
A strong source workflow reduces confusion. Editors should know when content is draft, approved, ready for translation, translated, reviewed and published. Without this, you get the classic “which version did you translate?” problem. It is not glamorous, but it is one of the most common causes of duplicated work. Translating an old draft is the content equivalent of painting a room just before someone knocks the wall down.
In Umbraco, you can support this through permissions, notifications, content states and agreed editorial processes. For larger teams, it may also be worth integrating translation management tools or external workflows, especially if professional translators, regional reviewers or legal approvers need to be involved.
A Translation Manager can help here by turning messy manual steps into clearer translation tasks. Tools such as Jumoo Translation Manager, Trados Connectors, LanguageWire TMS, or other translation management system integrations can support project management, language mappings, content transfer, and job progress tracking.
Be honest about machine translation
Machine translation can be useful. There, we said it. It can speed up first drafts, help editors understand content quickly, and support large-scale translation projects where budget or timing is tight.
But it should not be treated as a magic button that turns your website into a polished multilingual masterpiece. That button does not exist. If it did, every agency would be using it while eating biscuits in a hammock.
The best approach is usually a blended one. Use machine translation where it genuinely helps, then bring in human review for accuracy, tone, cultural relevance and sector-specific terminology. This is especially important for legal, healthcare, financial, education, government and technical content.
If your organisation is considering the Google Translate API or another automated translation service, be clear about where it fits. It may help with draft translation, but it should not replace review by native speakers or subject specialists. For video or training content, AI-powered dubbing may also sit alongside written translation, but it still needs the same quality control. Robots are useful. They are not famous for nuance.
If your organisation has brand terminology, product names, accessibility phrases or regulated wording, create a glossary and style guide for translators. This helps keep translations consistent and prevents every language version from developing its own little personality. Charming in a dog. Less charming in a corporate website.
Think beyond words: localisation matters
Translation changes language. Localisation adapts the whole experience. That includes dates, currencies, measurements, address formats, imagery, legal notices, forms, calls to action and even content hierarchy.
A phrase that works beautifully in one market may feel odd, overly casual or completely irrelevant in another. Likewise, an image, testimonial or campaign message may not carry the same meaning across different audiences.
Umbraco gives you the flexibility to manage these differences, but your team needs to decide where localisation is allowed and where consistency is required. Should each market choose its own homepage hero? Can regional editors change navigation labels? Are contact forms routed to local teams? Do cookie notices, privacy content or accessibility statements need different wording by country?
This is where a solid multilingual strategy earns its keep. It stops translation being treated as a page-by-page admin task and turns it into a coherent publishing model. That is the difference between “we have some translated pages” and “we have a proper multilingual digital experience”. Our multilingual Umbraco CMS support is designed to help teams make those decisions before the CMS becomes an editorial obstacle course.
For multilanguage websites, you should also plan for region-based differences, localized slugs, Language Switching Navigation and any static strings. These small details often shape how polished multilingual sites feel to users.
Protect multilingual SEO from the start
Multilingual SEO is one of those areas where small mistakes can have surprisingly large consequences. Search engines need to understand which language and regional audience each page is intended for. Users need to land on the right version. Editors need to manage metadata without needing a degree in technical wizardry.
Your Umbraco setup should support translated page titles, meta descriptions, URLs and navigation labels. You should also consider the hreflang attribute, language-specific XML sitemaps, the canonical tag, and redirect behaviour. These are not decorative extras. They help prevent duplicated content issues and improve the chances of users finding the right page in the right language.
Do not simply translate keywords word for word. Search behaviour varies by language and region. The phrase that performs well in English may not match how people search in German, French, Spanish or Welsh. Local keyword research should guide important pages, especially commercial landing pages, service pages and high-intent content.
A practical tip: build SEO fields into your multilingual editing workflow, not as an afterthought. If a translator only receives the body copy, the metadata often gets forgotten or rushed. That is how you end up with beautifully translated content hiding behind an English meta title. Not ideal. Not fatal. Definitely avoidable.
Make life easier for editors
A multilingual CMS only works if editors can actually use it without needing a lie down afterwards. Umbraco is flexible, but flexibility needs guardrails.
Give editors clear labels, helpful descriptions, sensible validation and content templates that explain what should be translated and what should stay shared. If a property is shared across all languages, make that obvious. If a field should be translated, tell editors what good looks like.
Permissions are important too. Not every editor needs access to every language. Regional teams may only need their own culture variant, while central teams may need oversight across all languages. Clear permissions reduce accidental edits, protect approved content and help everyone feel less like they are tiptoeing through a digital minefield.
You should also plan for missing translations. Should the user see the source language? Should the page be hidden from that language’s navigation? Should there be a fallback message? Should the CMS prevent publishing until all required variants are complete?
There is no universal answer. For legal or compliance-heavy content, showing an untranslated fallback may be risky. For blog content, it might be acceptable. For e-commerce, fallback behaviour could affect trust and conversion. Decide the rules early, document them, and configure Umbraco accordingly.
Keep governance boringly brilliant
Governance is not the sparkliest word in the digital dictionary, but it is what keeps multilingual websites from slowly collapsing into weirdness. You need ownership, review cycles, publishing rules and a process for updating translations when the source content changes.
One of the trickiest questions is what happens after the English page is edited. Does Umbraco notify translation owners? Does the existing translation remain published? Is it marked as needing review? Does the page show a warning in the backoffice? These details matter because multilingual content is never truly finished. It needs maintenance, especially across service pages, policy content, product information and campaign pages.
Create a simple governance model that covers who owns each language, who approves changes, how often content is reviewed, how urgent updates are handled, and how retired content is removed. Keep it practical. A 46-page governance document that nobody reads is just a very formal doorstop.
Frequently Asked Questions About Managing Translation in Umbraco
Yes. Umbraco supports multilingual content through language variants, culture settings and flexible content structures. The important bit is configuring it properly for your editorial workflow, not just switching on languages and hoping for the best.
Language variants are often best when the same content exists across different languages. Separate trees can work better when each region has substantially different content, navigation or business rules.
Yes, with the right integration or workflow, but human review is strongly recommended for important content. Machine translation can speed things up, but it should not be your only quality control.
Set a source language, define review workflows, use notifications where appropriate, and create ownership for each language. The boring answer is process. The useful answer is process supported by a CMS that makes it hard to miss important updates.
You need translated metadata, localised URLs where appropriate, hreflang, sitemaps, sensible canonical rules and local keyword research. SEO should be part of the translation workflow, not a frantic Friday afternoon add-on.
Final thought: translation is a system, not a task
The real secret to managing content translation in Umbraco is to stop thinking of translation as something that happens after the “real” content work is finished. It is part of the content strategy, technical architecture, editorial workflow, SEO setup and long-term governance of your site.
Done well, Umbraco gives teams a powerful, flexible way to manage multilingual content without turning the backoffice into a puzzle box. Done badly, it becomes a place where old translations lurk in corners, editors lose confidence, and nobody is quite sure which version of a page is telling the truth.
So, plan the structure. Make smart decisions about variants and shared content. Give editors clear workflows. Treat SEO properly. Review content regularly. And, most importantly, build the system around the humans who have to use it every week.
If you are planning a multilingual build, reviewing your current Umbraco setup, or quietly suspecting your translation workflow is held together with hope and biscuits, take a look at how we approach building multilingual websites in Umbraco. And when you are ready for a candid chat about what is working, what is wobbly and what needs fixing, get in touch with us today.