Understanding Language Specific Routes and Page Availability

Recognizing When You Are on a Language-Specific Page

In Sherkety ERP & Website Platform, one of the easiest ways to tell which language version of a page you are viewing is to look at the browser address bar. A language-specific page usually includes a short language code in the web address, such as /en/, /fr/, or /de/. That code shows which localized version of the page is currently open.

For example:

• The main homepage may open on the default route, shown simply as /.
• A localized version of that same page may appear with a language prefix, such as /en/.
• A deeper page can also carry the same pattern, where the language code appears before the rest of the page path.

This matters because the language code in the address bar reflects the actual page route being served. It does not just mean your browser prefers that language, and it is not the same as an automatic translation tool changing text on the fly.

You can usually confirm the active language in several visible places on the page:

• Header navigation labels appear in the selected language
• Page titles and section headings match that language
• Breadcrumbs follow the same language
• The language switcher highlights or displays the current choice

If the address bar shows a language prefix but the page text does not match, treat that as a page availability or content issue rather than assuming the route is correct.

If you need a refresher on how language switching works across public and admin areas, see Using Language Switching Across Public and Admin Pages.

Moving Between Languages with the Language Switcher

When you use the language switcher in the header or main navigation of Sherkety ERP & Website Platform, you are not just changing labels on the screen. You are usually moving to a different language-specific page route. This means the page address in the browser changes along with the page content.

On a page that exists in more than one language, the switcher normally takes you to the matching version of the same page. For example:

• If you are reading a company information page in one language
• And that same page has been published in another language
• Choosing the new language opens that equivalent page under the new language path

In many cases, the page keeps the same general page identity while the language part of the address changes. That helps you stay on the same topic instead of being sent somewhere unrelated.

As you switch languages, check these signs to confirm the change worked as expected:

• The address bar updates to the new language prefix
• The page heading appears in the selected language
• The navigation menu labels change to match
• The language switcher shows the newly selected language as active

This is especially useful when browsing public pages such as:

• Company Types
• ERP System
• Accounting
• Sales & CRM
• HR
• Purchasing
• Reporting

If a translated version exists, the switcher should move you directly to that localized page instead of sending you back to the homepage.

For the broader behavior of language controls across different parts of Sherkety ERP & Website Platform, refer to Using Language Switching Across Public and Admin Pages.

Understanding What Happens When a Translation Is Missing

Not every page in Sherkety ERP & Website Platform must exist in every language. Page availability is handled page by page, so one section may be fully translated while another is only published in a single language.

When you choose another language for a page that does not have a matching translated version, a few outcomes are possible:

• You may stay on the current page without moving
• You may be taken to the homepage in the selected language
• The unavailable language may appear disabled or may not be offered for that page

The exact result depends on how that page has been made available, but the main point is that missing translations do not always behave the same way as a normal page switch.

To tell the difference between a missing translation and a broken link, check a few visible clues:

• Does the language-specific address exist in the browser bar?
• Do the header navigation labels still load correctly in the selected language?
• Does the page open a valid public page, even if it is not the exact page you expected?
• Does the switcher return you to a broader page, such as a localized homepage or section landing page?

A broken link often leads to a page that clearly fails to load correctly. A missing translation, by contrast, usually still keeps you inside a working part of the website but may redirect you to a page that is available in that language.

This is common with content such as:

• A service page available in multiple languages
• A campaign page available in only one language
• A company type detail page translated for some languages but not all

Checking Whether a Page Exists in Each Language

If you want to confirm whether a page is available in more than one language, the quickest method is to compare what happens when you open the same page under different language routes in Sherkety ERP & Website Platform.

As a visitor, you can check page availability in practical ways:

• Use the language switcher and see whether it opens the same page in another language
• Look at the address bar and compare the page path under different language prefixes
• Confirm whether the destination page fully loads with the expected heading, navigation labels, and page content
• Check whether the page returns you to a broader section instead of the exact page you started from

For example, a page about ERP System may exist in several languages, while a more specific campaign or promotional page may only exist in one.

If you work with content, page availability should be checked more deliberately. Content editors should confirm that the translated page entry has been created and published for each language they expect visitors to use. It is not enough for the source page to exist in one language if the matching version has not been published in another.

Administrators can validate route behavior by opening the same page path under several language prefixes and checking the result:

• Does the page open normally?
• Does it redirect to a localized homepage or section page?
• Does the language switcher still show that language as available?
• Do breadcrumbs and page titles match the selected route language?

Typical patterns include:

• A product or service page published in two languages
• A company type detail page published in all supported languages
• A landing page published in only one locale

Explaining Localized Routes to Visitors and Internal Teams

When visitors or coworkers ask why a page address changes after switching languages, keep the explanation simple and tied to what they can see in Sherkety ERP & Website Platform.

Useful wording for help text or support replies includes:

• “The language code in the page address shows which language version of the page is open.”
• “If you switch languages, the website tries to open the matching page in that language.”
• “If that page is not available in the selected language, you may be taken to another available page, such as the homepage.”

This kind of wording is clear because it connects the language switcher, the address bar, and the page the visitor actually lands on.

When sharing pages in emails, campaigns, or service messages, always copy the link from the language version you want people to open. That helps visitors land directly on the intended localized content instead of starting on the default route and switching manually.

This is especially important for links to pages such as:

• Company Types
• ERP System
• Accounting
• Sales & CRM
• HR
• Purchasing
• Reporting

For internal teams, keep three things aligned:

• The language names shown in the switcher
• The language prefixes used in page addresses
• The published page availability for each language

If those do not match, the switcher can suggest a language that does not actually have a usable version of the current page. That creates confusion for visitors and makes shared links less reliable.

Fixing Common Problems with Localized URLs and Page Availability

Most language route problems in Sherkety ERP & Website Platform can be understood by checking the page address, the language switcher, and whether the page actually exists in the selected language.

If the language switcher opens the homepage instead of the matching page, the most likely reason is that the destination page has not been translated and published in that language. The homepage may still exist for that language even when the current page does not.

If the URL shows a language prefix but the page content is still in another language, check whether a true localized version of that page has been created. A language-specific route should lead to content that matches the selected language, including headings, navigation, and page text.

If a language option is missing or should not be selectable, review whether that language is actually available for the current page. A page can exist in one language without existing in another, even when the rest of the site supports both.

If shared links send people to the wrong language, compare the copied link in the browser address bar before sending it. Make sure it includes the intended language prefix rather than the default route.

Use this quick troubleshooting approach:

• Check the address bar for the language prefix
• Use the language switcher again from the current page
• Confirm whether the destination page is the same page or a fallback page
• Look for translated page titles, breadcrumbs, and navigation labels
• If you manage content, verify that the page is published in that language

These checks usually reveal whether the issue is a missing translation, an incorrect shared link, or a page that is available only in certain languages.

Overview

Language-specific routes in Sherkety ERP & Website Platform help visitors open the correct version of a page based on the language shown in the page address. The clearest sign is the language code in the browser URL, such as /en/, /fr/, or /de/. When that code changes, the page route changes too.

The main ideas to remember are:

• A default route may appear without a language prefix
• A localized route includes a visible language segment in the address
• The language switcher usually moves you between matching page versions
• A page may be available in one language but not another
• Missing translations can lead to a fallback page instead of the exact page you expected

You can usually confirm the active route language by checking:

• The browser address bar
• The selected value in the language switcher
• Translated navigation labels
• The page title and breadcrumbs

This topic is especially important when browsing public sections like Company Types, ERP System, Accounting, Sales & CRM, HR, Purchasing, and Reporting, because visitors often move between languages while staying on the same subject.

If you are helping others, the simplest explanation is that the language code in the URL shows which localized page version is open. If the same page has been published in another language, switching languages opens that version. If not, Sherkety ERP & Website Platform may keep you on the current page, send you to a broader localized page, or hide that language choice for the current route.

Prerequisites

Before using the guidance in this page, you should already be comfortable with the basic language controls in Sherkety ERP & Website Platform and know where to find the language switcher on public pages.

You will get the most value from this guide if you can already do the following:

• Identify the language switcher in the site header or navigation
• Change from one visible language to another while browsing
• Recognize common public sections such as Company Types, ERP System, and the ERP app pages
• Check the browser address bar after switching languages

If you have not covered that yet, start with:

• Switching Languages While Browsing the Platform
• Browsing Localized Pages and Language Specific Routes
• Using Language Switching Across Public and Admin Pages

For content editors and administrators, it also helps to have access to the admin area pages used to manage public content, since page availability depends on whether a translated page has been created and published. You do not need advanced setup knowledge for this guide, but you should understand which public pages your team expects to offer in each language.

The next document in this section is Browsing Multilingual Content Consistently Across Sections, which focuses on keeping the browsing experience consistent as visitors move between different parts of the website.