Legacy Knowledge Base
Published Sep. 10, 2025

How to Optimize Language Selection for SEO

Written By

Daniel Martinez Cisneros

How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How To articles!

While we make every effort to ensure this Knowledge Base is accurate, it may not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with any feedback or concerns.

Legacy Article

You are viewing an article from our legacy "FastTrack" publication program, made available for informational purposes. Articles in this program were published without a requirement for independent editing or verification and are provided"as is" without guarantee.

Before using any information from this article, independently verify its suitability for your situation and project.

Issue

  • The language selector in Liferay DXP uses the /c/portal/update_language URL, which calls the UpdateLanguageAction.java action. This action sets the selected language and redirects the user to the translated page with a 302 response. This extra HTTP request adds overhead and might impact SEO.
  • Is there a way to configure the language selector to bypass this redirect and link directly to the translated page URL?

Environment

  • Liferay DXP 2024.Q1 (Quarterly Release)

Resolution

Create a custom Application Display Template (ADT) to generate language links that point directly to the final friendly URL for each language. This method avoids the extra redirect through UpdateLanguageAction. Here's an example:

<div>
<a href="/en/test-page">English</a>
<a href="/es/pagina-de-prueba">Español</a>
<a href="/fr/page-de-test">Français</a>
</div>

Within your custom ADT, ensure the appropriate friendly URLs are generated dynamically for each supported language. This direct linking approach improves SEO by reducing redirects and HTTP requests.

 

Did this article resolve your issue ?

Legacy Knowledge Base