Contenido que llega a todos los canales, en cualquier lugar

Crea, gestiona y distribuye contenido a nivel global con la flexibilidad del CMS Headless de Liferay.

Why Multilingual SEO Breaks at Enterprise Scale

Hreflang gets out of sync

Most CMS platforms require manual hreflang tags per page, and they drift the moment a translation is missing or a slug changes. Liferay auto-generates hreflang and only outputs alternates for languages that actually have translated content.

Translations lag behind master content

Marketers wait weeks for human translations of every update. Liferay integrates Google Cloud Translation and Amazon Translate so first drafts ship the same day, with humans reviewing in the same workflow.

Region-specific URLs are a guessing game

Should it be /de/, fr.brand.com, or brand.de? Liferay supports all three patterns: virtual hosts for region domains, friendly URLs for path-based locales, and per-site sitemap controls.

Sitemaps miss localized pages

If your sitemap does not list every locale variant, search engines do not know they exist. Liferay’s sitemap configuration covers per-locale page URLs and integrates with hreflang, and also supports XML sitemaps, which are essential for optimizing website indexing, supporting multilingual content, and enhancing SEO visibility. 

SEO and Metadata Configuration Reference

Learn how to optimize SEO and metadata to improve site visibility in search engines and ensure content is properly indexed and displayed across platforms.

Hreflang explained

What is hreflang and when do you need it?

Hreflang is an HTML attribute that identifies the language and geographic region of alternative versions of a page. It tells search engines: this page exists in English for the US, German for Germany, and French for Canada — serve the right one. Hreflang is essential for multilingual websites to ensure users and search engines see the correct language and regional version. You need hreflang as soon as you publish the same content for more than one locale.

 

A multilingual CMS should effectively manage content in different languages, supporting character sets, locale variations, and formatting to cater to diverse audiences.

 

Without hreflang, search engines guess which version to show, often returning the wrong one. With hreflang, you control international ranking signals. Liferay populates these tags automatically based on the languages your site supports — no manual tagging per page, no scripts to maintain.

 

 

3-step diagram — How Liferay handles hreflang

  What it optimizes for Where results show How to optimize
Step 1: site is configured with N languages International reach, establishing the full set of languages and regions your site will target Localized search results across every configured target market Define all target languages upfront in site settings; align language selection with your actual market priorities
Step 2: a page is translated into a subset of those Per-market relevance, ensuring search engines only serve fully translated content to the right audiences Search results in each market where a translated version of the page exists Prioritize high-traffic and high-converting pages for translation first; use Liferay's translation workflow to manage status across languages
Step 3: Liferay outputs hreflang tags for only the languages with translated content (or all languages — your choice). All without manual tagging Accurate language and region signals to search engines, without the manual tagging errors that typically occur at scale Localized SERP results matching each user's language and region, with correct page variants served per market Choose whether Liferay tags only languages with translated content or all configured languages; validate output with Google Search Console's URL inspection tool

Make every locale a first-class SEO target

Hreflang automation, per-region URL patterns, localized canonical URLs, and locale-aware sitemaps. Marketers ship in every market without filing tickets.

Auto-generated hreflang per page

Liferay populates hreflang meta data with all available site languages by default. Toggle 'Enable Only Translated Hreflangs' to limit output to languages with actual translated content. Configurable at instance, all-sites, or individual-site scope.

Canonical URLs that respect locale

Set a custom canonical URL per page and localize it for each language. Liferay's canonical URL field is fully localizable using the language flag, so translated versions point to their own canonical, not the master.

Region URLs the way you want them

Configure virtual hosts to serve region-specific domains (brand.de, fr.brand.com) or use friendly URLs for path-based locales (/de/, /fr/). Choose the URL pattern that fits your domain strategy and Liferay handles the routing.

Sitemaps that include every locale

Liferay's XML sitemap includes per-locale page URLs by default and works alongside auto-generated hreflang so search engines see the full set of language variants. Granular include/exclude controls let you scope by site, content type, or category.

Display Page Templates per locale

Display Page Templates can map SEO and Open Graph fields dynamically per locale. ${title} renders the German title for German visitors, the French title for French visitors. Robots and sitemap settings are also localizable.

The Differentiator

Hreflang automation across 50+ languages out of the box

Most enterprise CMS platforms ask you to manage hreflang manually, page by page, even when supporting various languages or more than one language. Liferay does it automatically. Configure your site’s languages once, and Liferay populates hreflang meta data on every page that needs it, making multilingual CMS management seamless for multiple languages. Centralized Language Management handles translation workflows and content versions in multiple languages within one system, enabling automatic content extraction for translation. Switch on Enable Only Translated Hreflangs and Liferay outputs alternates only for languages with actual translated content, so you never signal pages that do not yet exist. The setting is configurable at instance, all-sites, or individual-site scope, and it works across widget pages, content pages, and Display Page Templates. Combined with localizable canonical URLs, locale-aware sitemaps, and 50+ supported languages out of the box, Liferay handles international SEO at the scale enterprise teams actually operate.

50 +

Languages supported out of the box

Translation

Translate at scale without breaking SEO signals

Liferay’s translation workflow integrates machine translation technology and AI providers with human review in the same tool, improving content quality and accelerating the translation process. Translated content gets proper hreflang, localized canonicals, and locale-aware sitemap entries automatically. Utilizing a multilingual content strategy ensures your content is not only translated, but also culturally relevant for each target audience.

Translate via Google or Amazon

Connect Google Cloud Translation or Amazon Translate to translate content immediately across your site, enabling rapid updates and efficient multilingual content management. First drafts ship the same day; teams refine in the same editor where translations land. Reduces translation backlog without skipping editorial review.

Configure 50+ site languages

Site Localization settings let you configure support for different languages, including the English language, by enabling any combination of 50+ supported languages per site, setting a default locale, and toggling which languages are publicly visible. Modifying localizable site fields works the same way: pick the language, enter the value, save.

Export and import translations in bulk

Export translations as XLIFF for translation memory tools, human translators, or integration with translation management systems (TMS) to handle bulk translation workflows efficiently. Useful when working with external translation agencies or compliance-driven workflows that require audit trails.

Every multilingual SEO feature in one CMS

Auto hreflang

Hreflang meta data generated automatically per page.

Translated-only mode

Output hreflang only for languages with actual translated content.

50+ languages

Out-of-the-box support for 50+ languages with no add-on licensing.

AI translation

Translate via Google Cloud or Amazon Translate inside the CMS.

Localized canonicals

Set per-locale canonical URLs from Page Settings UI.

Region URLs

Virtual hosts, subdomains, or path-based locale URLs supported.

Localized sitemaps

XML sitemap includes per-locale page URLs alongside hreflang.

Field-level translation

Translate individual fields rather than re-translating whole pages.

Servicios financieros

Un banco suizo utiliza la tecnología API Headless para impulsar su intranet

La nueva intranet de BancaStato mejora la productividad de los empleados con un acceso rápido a la información, los documentos y las aplicaciones cotidianas.

60,000 +

años de experiencia

50 %

agencias

20 %

mes para la puesta en marcha

Complementary multilingual capabilities

Technical SEO

Sitemaps, redirects, canonical URLs, and 404 tracking that work per locale.

AI & answer-engine SEO

Make localized content AEO-ready so AI engines cite the right language.

SEO audit

Audit each locale separately for SEO and accessibility issues, including monitoring search performance and search visibility to ensure optimal reach across regional search engines.

Personalization

Personalize content for your target audience by region, language, or audience segment to engage diverse, multicultural groups.

Headless content delivery

Deliver localized structured content to any frontend via APIs.

Site localization

Configure default locales, enabled languages, and field-level translation per site.

Preguntas frecuentes

Un CMS tradicional (como WordPress o Drupal) es "monolítico", lo que significa que la gestión y la entrega de contenidos están estrechamente vinculadas. Un CMS tradicional se crea principalmente para publicar en un sitio web utilizando temas y plantillas predefinidos.

 

Un CMS headless separa la gestión de contenidos de la presentación, gestionando solo los contenidos para que el front-end se pueda crear con cualquier marco. Esto te permite gestionar los contenidos en un solo lugar y publicarlos en sitios web, aplicaciones y otros canales.

 

  • Entrega omnicanal. Gestiona una vez y publica en cualquier lugar: sitios web, aplicaciones móviles, dispositivos inteligentes y mucho más.
  • Libertad para los desarrolladores. Los desarrolladores pueden utilizar cualquier marco o herramienta, lo que acelera los ciclos y agiliza los flujos de trabajo.
  • Arquitectura preparada para el futuro. A medida que surgen nuevas tecnologías y canales, el contenido estructurado está listo para ser entregado.
  • Mayor seguridad. El back-end está separado del front-end, lo que reduce la exposición a los ataques.
  • Mejor rendimiento. La separación del contenido de la capa de presentación da como resultado tiempos de carga de página más rápidos y una mejor experiencia de usuario

 

Liferay combina la entrega headless con una amplia experiencia de creación. Los profesionales del marketing y los creadores de contenido pueden: 

 

  • Utilizar estructuras de contenido predefinidas.
  • Colaborar entre equipos y regiones.
  • Utilizar la IA para la creación y traducción de contenidos.
  • Aplicar herramientas de gobernanza para mantener la coherencia y el cumplimiento.

Liferay es una buena opción si tu organización necesita:

 

  • Publicar contenidos en múltiples canales y regiones.
  • Dar a los desarrolladores más flexibilidad y agilidad.
  • Optimizar los flujos de trabajo de contenido y mejorar la colaboración entre equipos.
  • Mantener una gobernanza, coherencia y cumplimiento sólidos.
Sí. Incluso con una configuración headless, Liferay te permite obtener una vista previa de cómo se verá el contenido en diferentes canales antes de que se publique. El módulo Sites proporciona vistas previas visuales y las API permiten a los desarrolladores probar el contenido en diferentes dispositivos y canales.
Sí. Incluso con una configuración headless, Liferay te permite obtener una vista previa de cómo se verá el contenido en diferentes canales antes de que se publique. El módulo Sites proporciona vistas previas visuales y las API permiten a los desarrolladores probar el contenido en diferentes dispositivos y canales.
Sí. Incluso con una configuración headless, Liferay te permite obtener una vista previa de cómo se verá el contenido en diferentes canales antes de que se publique. El módulo Sites proporciona vistas previas visuales y las API permiten a los desarrolladores probar el contenido en diferentes dispositivos y canales.

Recursos adicionales

Lleve su contenido a todas partes, más rápido con Liferay CMS.