Do translated service pages need separate URLs?
Your business has an English service page.
Now you want Georgian, German or French.
Should the translation live at a separate URL?
Or should one URL automatically change language depending on the visitor?
For a real multilingual site, Google’s current guidance is clear: it recommends different URLs for each language version.
But the business decision comes before the technical implementation.
The useful question is:
Does the translated page serve a real customer audience well enough that you can maintain it as a current version of the service?
Short answer
If you publish full language versions of a service page, separate URLs are usually the cleanest structure.
Google recommends:
- different URLs for different language versions;
hreflangannotations to connect the versions;- visible language links so users can choose;
- avoiding automatic language redirects that can prevent users or search engines from accessing all versions.
Google also says it determines page language from visible content, not from the URL or lang attribute alone.
The business still needs to decide whether the translated page is worth maintaining.
A second-language page should exist because it serves customers, not merely because “multilingual SEO” sounds useful.
Why does Google recommend separate URLs?
Because one stable URL can represent one stable language version.
For example:
/services/audit//ka/services/audit//de/services/audit/
The exact structure can vary.
Google’s multilingual-site guidance says different URLs make it easier for Google Search to discover and serve the appropriate language page.
If the same URL changes content based on browser language or cookies, Google may not discover every version reliably.
What does hreflang do?
hreflang tells Google that different URLs are language or regional alternatives of the same content.
For example:
- English;
- German;
- Georgian.
Google says alternate versions can be declared in:
- HTML;
- HTTP headers;
- sitemaps.
You do not need to use all three methods at once.
The important point is that the language versions are real URLs and are connected correctly.
Does hreflang translate the page?
No.
It only identifies relationships between alternate URLs.
The page itself must be translated.
Google says it determines language from the visible content of the page.
It does not rely on hreflang or the HTML lang attribute to decide what language the page actually contains.
Should the translated page contain only translated navigation?
No.
Google warns that translating only boilerplate, such as navigation and footer, while leaving most of the page in another language can create a poor experience.
A translated service page should translate the information the customer actually needs.
That includes, where applicable:
- service explanation;
- price;
- inclusions/exclusions;
- location;
- contact route;
- preparation;
- FAQ;
- legal/commercial notices that genuinely apply.
Do not create a “German page” where the important service description remains English.
Does every service need every language?
No.
A language page is useful when there is a real audience for that service in that language.
For example:
- one service may have strong German-speaking demand;
- another may be sold only in English;
- a local branch may serve Georgian and Russian;
- a specialist service may require one carefully maintained master language first.
Do not multiply URLs just because the site has a language selector.
The translated page creates an ongoing maintenance obligation.
What happens when the English price changes?
The translated versions need updating too.
This is where multilingual sites often become inconsistent.
For every change in:
- price;
- scope;
- availability;
- address;
- hours;
- contact route;
- FAQ;
- policy;
ask which language versions also need the update.
If the business cannot maintain the translations, publishing fewer high-quality language versions can be better than maintaining several contradictory ones.
Should the site auto-redirect visitors by language?
Be careful.
Google recommends allowing users to switch language versions and warns against automatic redirects based on assumed language.
Automatic redirects can prevent users and search engines from viewing all versions.
A better pattern is:
- detect or suggest a likely language if useful;
- show a clear language selector;
- let the user choose;
- keep every language URL directly accessible.
Should the URL contain the language?
It often helps make the structure understandable.
Examples:
/en/service//de/service//ka/service/
Google says language-specific words in URLs are fine and recommends UTF-8 encoding.
The exact path is a site-architecture choice.
The important thing is stable, separate URLs for stable language versions.
What about regional versions in the same language?
Language and region are different.
For example:
- English for the UK;
- English for the US;
- English for Georgia-based international customers.
If the content genuinely differs by region, Google supports regional hreflang variants.
Do not create regional URLs unless there is real regional content to maintain.
Can translated pages be duplicates?
Google says fully translated main content is not treated as duplicate merely because the meaning is the same in another language.
If only the template is translated while the main content remains the same language, that can create a different problem.
The value of the language version comes from the translated main content and customer usefulness.
Should every language use the same canonical URL?
Generally, each real language version should be treated as its own localized URL and linked with hreflang.
Do not point all translated pages to the English page as canonical simply because English is the master copy, unless there is a specific technical reason supported by the content setup.
Google’s localized-site guidance explains that regional/language versions should be connected with hreflang.
What should a business owner check before adding a language?
- Is there a real customer audience?
- Which services need that language?
- Who owns translation accuracy?
- Who updates prices and commercial terms?
- Are separate URLs implemented?
- Can users switch language manually?
- Is
hreflangconfigured correctly? - Does the translated page contain the full useful information?
- Can we keep both versions current?
The hard part is usually not the first translation.
It is keeping every public version accurate six months later.
Discuss a business visibility audit with Madloba Consult
FAQ
Does Google recommend separate URLs for different languages?
Yes. Google’s multilingual-site guidance recommends different URLs for each language version.
Should we use hreflang?
If you have alternate language or regional URLs, Google recommends hreflang to help Search understand which versions correspond.
Can one URL automatically change language instead?
It can technically, but Google warns that locale-adaptive pages may not be fully crawled and recommends separate locale URLs.
Should we automatically redirect visitors based on browser language?
Google advises against forcing automatic language redirects because users and search engines may be unable to access all versions. Give users visible language links.
Is translated navigation enough?
No. Google says page language is determined from visible content and warns against translating only boilerplate while leaving the main content in another language.
Does every service need every language?
No. Publish a language version when it serves a real audience and can be kept accurate.
Related links
- How to add website to Google Business Profile
- Does each business location need its own website page?
- Business audit
Ask about your own listing
If this article raised a question about your own business on Google, send it in writing through the contact page: madlobaconsult.com/contact. Describe the situation in a few sentences and we reply by email. Prices and service terms are on the pricing page.