One language, several countries
A generic English page can serve several markets when the offer, currency, conditions and message do not differ substantially.
Guides
Multilingual SEO and GEO: how to help Google and AI understand languages, markets and content
Translating words is not enough. Every version needs a stable URL, consistent signals, genuinely localised content and a structure that lets search engines and AI systems find the right page.
Short answer
A multilingual website works when each language lives on distinct, indexable URLs, equivalences are declared with reciprocal hreflang annotations, every page keeps its own canonical and visible content genuinely answers its market. Technical SEO, accessibility, localisation and GEO must describe the same reality.
Gian Luca Partengo
Web developer since 1995 · bespoke websites · Updated
A multilingual website is not one page that changes language
It is a system of equivalent but autonomous pages, connected by technical signals and adapted to the people who need to use them.
- 01Define real languages and markets
- 02Create distinct, reachable URLs
- 03Align hreflang, canonicals and sitemaps
- 04Localise content, evidence and conversions
Language and market are not the same decision
A website can be multilingual, multi-regional or both. Confusing these levels creates the wrong URLs, prices and content.
Same language, different markets
English for the United States and the United Kingdom may require different prices, availability, vocabulary, evidence and terms: en-US and en-GB describe the market as well as the language.
Several languages, one market
A Swiss business may publish content in Italian, German and French while keeping one commercial scope.
Unavailable language
A neutral page or selector can act as x-default for people who do not match the declared variants, without imposing irreversible redirects.
First question
Do I need to speak another language, or am I genuinely offering something different in a market? The answer determines architecture, content, hreflang codes and maintenance costs.
Every language needs its own permanent URL
Google recommends distinct URLs instead of changing content only according to cookies, IP addresses or browser settings.
GLP choice
Subdirectories on the same domain when the project permits
A structure such as domain.com/ for the default language and domain.com/en/ for English concentrates management and authority without hiding variants.
Country-code domains and subdomains remain valid when corporate separation, infrastructure or geotargeting requires them. The choice follows the project, not a universal formula.
| Structure | When it makes sense | Watch out for |
|---|---|---|
| Subdirectory — /en/ | Same brand, domain and infrastructure; centralised management | Clear, economical to maintain and suitable for most GLP projects |
| Subdomain — en. | Genuinely separate teams, stacks or environments | Adds configuration, monitoring and opportunities for divergence |
| Country domain — .de | Presence and offer strongly tied to one country | Strong geographical signal, but higher costs and separate infrastructure |
| Parameter — ?lang=en | Rarely appropriate for indexable content | Google does not recommend it for geographic segmentation; it complicates links and canonicals |
Hreflang: a map of equivalences, not a ranking command
It declares which URLs are language or regional versions of the same content and helps Google offer the most appropriate one.
Technical rule
Every relationship must be complete and reciprocal
Every page lists itself and all alternatives with absolute URLs. The other versions must return the same set of relationships.
If A points to B but B does not point to A, Google may ignore the pair. A language code is required; the optional region follows the language.
Self-reference
The Italian page includes its own it variant, not only en or other languages.
Valid codes
Use supported language codes and, when needed, language-region: it, en, en-GB. A country-only code such as UK is invalid.
x-default
It identifies the fallback page for uncovered languages, often the default home page or a language selector.
One well-managed method
HTML, HTTP headers and sitemaps are equivalent methods for Google. Duplicating all three adds no benefit and increases mistakes.
Canonicals and hreflang answer different questions
A canonical chooses the principal URL among duplicates; hreflang connects language or regional variants. Treating them as synonyms can remove entire translations.
Real translation: self-canonical
A complete English page points its canonical to itself and connects to the Italian page through hreflang.
Never point everything to Italian
Canonicalising every language to the Italian URL tells systems that the other versions are not preferred.
Duplicates in one language
Near-identical regional versions in the same language may require a coherent canonical preference alongside hreflang.
Signals must agree
Redirects, canonicals, sitemaps, internal links and hreflang must not identify different or unreachable URLs.
The lang attribute serves browsers and assistive technologies
Google determines language mainly from visible content, but html lang remains essential for correct pronunciation, reading and interface behaviour.
Default language
The html element declares the main page language with an appropriate BCP 47 tag, such as it or en.
Language changes
A quotation or meaningful phrase in another language uses lang on the relevant element when the technology can identify it.
It is not hreflang
lang describes the language of a document or passage; hreflang connects alternative URLs intended for different languages or regions.
Automated and manual testing
Verify markup and test at least screen-reader and selector behaviour, because a formally correct value can still be applied to the wrong page.
Accessibility meets SEO
A correctly declared language does not replace translated content, but it makes that version more understandable to people and the technologies interpreting it.
What must be translated for a page to be genuinely equivalent
Changing the title and menu while leaving the body in Italian does not create a useful English version. Google uses visible content to recognise language.
-
01
Main content
Headings, paragraphs, tables, FAQs, calls to action, examples and microcopy must be understandable in the selected language.
-
02
Metadata and sharing
Title, description, Open Graph, breadcrumbs and entity names must describe that specific version.
-
03
Navigation and components
Menus, footers, buttons, filters, search, dialogs and panels must not create a half-translated interface.
-
04
Forms, errors and confirmations
Labels, instructions, validation, transactional emails and outcome pages belong to the journey and affect conversion.
-
05
Media and text alternatives
Informative alt text, captions, subtitles and text embedded in images must be localised or avoided when they become unmanageable.
-
06
Policies and terms
Privacy, cookies, sales, shipping and terms must genuinely represent the applicable languages, territories and processing.
Translation and localisation are not synonyms
The first changes language. The second adapts search intent, evidence, the offer and the journey to market expectations.
Demand and vocabulary
People do not always translate the same query literally. Keywords, entities, questions and terminology must be researched in the actual language and industry.
Prices and terms
Currency, taxes, shipping, availability, timing, measurements and guarantees must match what the business genuinely offers.
Local evidence
Relevant locations, contacts, case studies, reviews, certifications and partnerships help people and systems understand where the business operates.
Complete conversion
The journey does not end on the landing page: forms, checkout, support and subsequent communications must support the promise made.
The language selector must be a system of real links
People and crawlers must reach every version without depending on geolocation, cookies or fragile JavaScript.
Corresponding version
From an Italian guide the selector goes to the same guide in English, not always to the English home page.
Links with href
Alternatives use navigable links and real URLs; a script-only menu can prevent discovery and access.
User choice
A language can be suggested, but not locked automatically according to IP or Accept-Language.
Preserved context
Navigation, breadcrumbs, calls to action and internal links remain in the current language unless the user chooses otherwise.
The sitemap must list real, canonical and current pages
It supports URL discovery and can describe language alternatives, but does not guarantee indexing or ranking.
Absolute and canonical
Every loc contains the complete public URL that the site considers principal for that version.
Consistent alternatives
When hreflang is in the sitemap, every URL repeats the same complete set of variants, including itself.
Real lastmod
The date changes when content is substantially modified, not on every request or deployment.
Reachable pages
No redirects, errors, noindex or canonicals to other URLs inside the list intended for indexing.
A sitemap does not repair a website
If routing, links, canonicals or content are wrong, adding the URL to the XML file does not resolve the contradiction.
Localised structured data consistent with the page
Markup makes entities and properties more explicit, but it must describe what the user can see in the same language.
inLanguage
CreativeWork, Article and other compatible types can declare their language with a consistent BCP 47 tag.
Names and descriptions
Headline, description, breadcrumbs, FAQs and other textual values follow the published version rather than staying in the source language.
Business entity
Addresses, areas served, contacts, currency and conditions remain verifiable and do not invent a local presence that does not exist.
Parity with visible content
JSON-LD must not contain prices, reviews, questions or services that are absent from or different to the accessible page content.
Multilingual GEO: every language must deserve to be cited
A generic translation multiplies pages, not authority. Answer systems need accessible, specific and verifiable sources in the language of the question.
Discoverable and indexable
The page has a public URL, internal links, the correct status and main content available to authorised crawlers.
Open sourceUseful in its local context
It answers real questions with first-hand experience, clear definitions, limits, examples and data that do not look mass-produced.
Open sourceVerifiable and attributable
Author, organisation, sources, dates, contact details and terms let people and systems assess provenance and freshness.
Open sourceNo GEO shortcuts
Hidden text, serial pages and files marketed as magic formulas are not required. What matters is a genuinely useful version in that language, supported by technical structure and reliable signals.
Six mistakes that make a website appear multilingual when it is not
They are common because the interface can look translated while crawlers, assistive technologies and users receive contradictory signals.
One URL, language by cookie
Variants have no stable address, cannot be shared and may not be discovered or indexed separately.
Non-reciprocal hreflang
Self-reference, absolute URLs or return links are missing and the annotation may be ignored.
Every canonical points to the source
Complete translations are treated as non-preferred copies rather than autonomous pages.
Only the template is translated
Menus and footers change language while content, FAQs, errors or policies remain in the original language.
Forced redirects
IP or browser settings decide for the user and may prevent people and crawlers reaching a version.
Mass-produced translated pages
Content without review, local research or specific evidence increases volume but not its ability to rank or convert.
The GLP method for a controllable multilingual website
Language is a project module, not a switch. Scope, sources, routing, signals, content and tests are defined before publication.
-
01
Map pages and markets
Decide which pages each language needs, which markets share the offer and which require genuine variations.
-
02
Prepare translations
The client supplies complete approved content, including metadata, microcopy, forms, policies and commercial material.
-
03
Implement routing and URLs
Every version receives a stable path, explicit default language, accessible selector and predictable fallbacks.
-
04
Generate technical signals
Canonicals, hreflang, html lang, sitemaps, breadcrumbs and structured data derive from the same map.
-
05
Verify page by page
Check parity, links, status codes, redirects, metadata, forms, images, mobile layouts and the absence of untranslated keys or text.
-
06
Keep versions aligned
Every new page or substantial change requires an editorial decision across languages and genuine update dates.
| Item | Scope | Price |
|---|---|---|
| Multilingual setup | Technical configuration for Essential and Pro websites | €300 |
| Source page | Implementation of supplied versions for every page in scope | €80 per source page |
| Translations | Approved copy, policies and content are supplied by the client | Not included |
| Multilingual ecommerce | Catalogue, variants, checkout, emails, policies and markets according to the actual project | Quoted separately |
The final price depends on languages, pages, components, integrations and differences between markets. SEO and GEO improve structure and understanding but cannot guarantee rankings, traffic or AI citations.
Explore how to appear on ChatGPT and AI search and how to make a website usable by AI agents. For packages and prices, review custom website services.
Verified primary sources
The guidance separates search-engine recommendations, web standards, accessibility and structured-data properties. Recheck it whenever markets or platforms change.
-
Google Search Central — Multilingual and multi-regional websitesOpen source
Differences between language and region, distinct URLs, geotargeting, selectors and local signals.
-
Google Search Central — Localised versions and hreflangOpen source
Equivalent methods, reciprocity, self-reference, absolute URLs, codes and x-default.
-
Google Search Central — Optimising for AI featuresOpen source
SEO foundations, indexing, useful content, page experience and structured data in generative experiences.
-
Google Search Central — Sitemap overviewOpen source
URL discovery, alternate language versions and the limits of XML files.
-
Google Search Central — Build a sitemapOpen source
Absolute canonical URLs, meaningful lastmod dates and file structure.
-
W3C Internationalization — Declaring language in HTMLOpen source
The lang attribute, default language, language changes and BCP 47 tags.
-
W3C WAI — WCAG 2.2, language of partsOpen source
Programmatic identification of the language of meaningful passages and phrases.
-
Schema.org — inLanguageOpen source
Property for declaring the language of content or an action using BCP 47 tags.
-
Google Search Central — Helpful, people-first contentOpen source
Originality, first-hand experience, clear purpose and content created for people.
-
OpenAI — Crawlers and publisher controlsOpen source
Distinct roles for OAI-SearchBot, GPTBot and ChatGPT-User and management through robots.txt.
Sources checked on 28 July 2026. Specifications, AI products and crawling behaviour can evolve: always verify the applicable documentation before changing a website.
Frequently asked questions
Direct answers to the doubts that most often create fragile architectures or unrealistic expectations.
Does translating a website automatically improve SEO?
No. It opens a new search scope but requires URLs, technical signals, useful content, local demand, authority and maintenance. Done badly, it can multiply weak pages instead.
Are subdirectories, subdomains or country domains better?
It depends on brand, infrastructure and markets. For many same-domain websites, subdirectories are simplest to manage; ccTLDs and subdomains make sense when separation is real.
Does hreflang improve rankings?
It is not a magic ranking factor. It helps Google understand equivalences and offer the most appropriate language or regional version.
Should every translation canonicalise to the Italian page?
No. A complete, indexable translation normally points its canonical to itself. Equivalence with other languages is expressed through hreflang.
Does Google use html lang to understand language?
Google states that it mainly uses visible content to determine language, not lang or hreflang. html lang remains fundamental for browsers, screen readers and accessibility.
Can JavaScript change language on the same URL?
It can for a non-indexable interface, but it is not the recommended SEO solution: each version should have a distinct, reachable and shareable URL.
Do I need x-default?
It is not mandatory for every project, but it is useful for identifying a fallback page for users who do not match the specified languages or regions.
Is an unreviewed machine translation enough?
No. It can produce errors, unsuitable tone, inconsistent terminology and incorrect commercial promises. Someone familiar with the language, industry and responsibility for the text must review it.
Does multilingual GEO need special ChatGPT markup?
There is no universal markup that guarantees citations. Pages need to be public, clear, verifiable, technically accessible and useful in the language of the question.
How much does adding a language to a GLP website cost?
For Essential and Pro websites, the package starts at €300 setup plus €80 per source page. The client supplies translations; multilingual ecommerce is quoted according to its actual scope.
Who supplies the translations?
The client supplies complete approved copy. GLP implements the multilingual structure and verifies technical consistency and completeness within the agreed scope.
How do you audit an existing multilingual website?
Start with a URL-language matrix and verify status codes, redirects, canonicals, hreflang, lang, sitemaps, links, content, metadata, structured data, forms and parity across versions.
Next step
Do you want to add a language without duplicating mistakes and weak content?
Review the scope and cost of multilingual options designed to keep SEO, accessibility, GEO and real maintenance aligned.