How to translate SEO titles and meta descriptions in Umbraco

Your French service page is ready, but its search title and description are still in English. Translating the body copy is only part of creating a complete experience: the search and social text should speak to the same audience. Omni brings that work into the normal Umbraco translation workflow.

Which SEO fields should you translate?

Start with the fields your templates actually render. Property aliases vary between sites, and a document's name is not necessarily its SEO title.

Google recommends titles in the same language as the page's main content. It can use a meta description for a search snippet, although the displayed title and snippet may also be drawn from other page content. See Google's guidance on title links and meta descriptions and snippets.

Translate standard Umbraco SEO properties

If your site uses text boxes or text areas for SEO copy, Omni can translate those supported editors alongside other page properties. Enable culture variation for the relevant document type and fields so each language has its own values. For an existing site, follow the multilingual conversion guide before changing the content model.

1. Save the source-language title and description in Umbraco.
2. Open the page's Translate tab and choose the source language, target language and AI profile.
3. Preview the report and select the SEO properties you want to translate. You can leave the body copy out when only metadata needs attention.
4. Start the translation and inspect the property results.
5. Check the target-language draft and preview the rendered page before publishing manually.

Existing target values are skipped by default. If you want to replace metadata already written in the target language, choose the appropriate overwrite option when your permissions allow it. See the page translation instructions for the full workflow.

Umbraco backoffice

Enlarge ↗

×

Preview a page's supported properties and choose which values to include in the translation.

Using SeoVisualizer or MetaMomentum?

Omni includes support for selected community SEO editors, so you can translate their known text fields without asking the AI to rewrite the whole stored JSON value.

• SeoVisualizer: translates populated SEO titles and descriptions while preserving indexing and title-suffix settings.
• MetaMomentum: translates supported search titles and descriptions and explicitly overridden social titles and descriptions, while preserving media identifiers, indexing settings and fallback behaviour.

These integrations recognise supported stored formats when the editors are already installed; Omni does not install the community packages. Check supported editors and compatibility details for your setup. For a site-specific SEO editor, use configuration mappings for compatible text values or a code adapter for structured data.

Keep brand names and terminology consistent

Add glossary rules for product names that should stay unchanged and terms that have an approved translation. This helps titles, descriptions and body copy use consistent language across a section. A modern efficient model is a practical starting point for these short text fields; see choosing an AI provider and model.

For example, a fictional software company could preserve Acme Cloud while translating the surrounding copy:

This is an illustrative translation, rather than a captured Omni result. The aim is natural language that retains the source meaning and brand. Translation gives you localised copy; local keyword research can then refine it for the phrases your audience searches for.

Umbraco backoffice

Enlarge ↗

×

Use glossary rules to preserve brand terms and apply preferred translations across jobs.

Read the glossary and translation management documentation to configure rules for your languages.

Translate SEO metadata across a whole section

For a product catalogue or service section, use Page and descendants to preview multiple pages and refine the included pages and properties. Select the supported SEO properties you need, then run one monitored section job. This saves opening and translating every page individually. See page and section translation.

Afterwards, use Translation Coverage and Source Changes to help find content gaps and changes that need attention. Inspect the SEO property results as well as overall page status when checking that the metadata work is complete.

Check the rendered metadata before publishing

• The target culture renders its own title and description, rather than falling back unintentionally to the source language.
• The copy describes the page accurately and uses the intended regional language.
• Brand names and any title suffix appear as intended.
• Titles and descriptions are concise; check your editor's preview rather than imposing one character limit on every language.
• Social text and images use the intended overrides or fallbacks.

A light editorial check is usually appropriate for everyday SEO copy. Use specialist review for legal, medical or regulated claims. For language URLs, canonicals, hreflang and sitemaps, follow the multilingual SEO guide.

Common questions

Can I translate SEO fields without translating the whole page?

Yes. Omni lets you select supported properties in the preview, so you can run a translation for just the SEO fields.

Will Omni write missing descriptions from scratch?

This workflow translates saved source text. Write the source description first, then translate it into your target languages.

Can translating metadata improve search performance?

Yes, it can help. Localised titles can make your pages more relevant to searches in the target language, while clear descriptions can encourage readers to click through. Combined with useful translated content and sound technical SEO, this supports stronger visibility and opportunities for better rankings, although no ranking improvement is guaranteed. Omni makes it practical to translate these fields consistently across your site, helping each language reach its intended audience.