One company, many languages — hreflang, translated names, and schema that does not invent a second organization.
Your English site says "Northstar Analytics." The French site says "Northstar Analytique" in the H1, "Northstar Analytics SAS" in the footer, and Organization schema with a different url that looks like a second company. Assistants do not know whether to merge or split you — so they hesitate, or cite the clearer English competitor.
Multilingual sites need one company entity expressed carefully across languages: hreflang, translated marketing copy, and schema that does not invent sibling organizations by accident.
The core rule
One Organization (or LocalBusiness) identity globally, with language-specific pages that point at each other. Translate descriptions and articles. Do not freely translate the legal or brand name in schema unless that localized legal name is real and you intentionally model it.
| Field | Keep identical across languages | Localize |
|---|---|---|
| Brand / product trademark | Usually yes | Only if you legally market a different mark |
Organization url | Prefer primary canonical site or locale-specific site URL with clear sameAs | Locale homepages linked via hreflang |
sameAs profiles | Same LinkedIn/Crunchbase where accurate | Local directory profiles if NAP matches |
| About / product copy | — | Yes |
| Currency and pricing | — | Yes, with clarity |
| Article body | — | Yes |
| Logo | Same mark when possible | Localized wordmarks only if real |
hreflang without entity chaos
Implement hreflang so each language/region URL declares its alternates and a self-reference. Mistakes that hurt AEO and SEO alike:
- Pointing hreflang at soft 404s or login walls.
- Mixing
en-USandeninconsistently. - Forgetting
x-default. - Annotating machine-translated trash as a peer of your carefully edited English — quality gaps become trust gaps.
Canonical tags should point to the appropriate locale URL, not always to English, unless you intentionally consolidate. Entity consistency is about names and organization identity, not forcing every language onto one URL. For canonical edge cases, see canonical tags and the one-URL problem.
Schema patterns that stay sane
Preferred: On each locale homepage, Organization markup with:
name: official brand string you want resolved globally (plusalternateNamefor true local variants).url: that locale’s homepage or the global primary URL — pick a policy and stick to it.sameAs: shared global profiles; add locale profiles only when they represent the same org.inLanguageon WebSite / WebPage where appropriate.
Avoid: Creating a new Organization @id per language that disagrees on legal name, logo, and founding date. That looks like five companies.
If you operate distinct legal entities per country, model that honestly (parent/subsidiary) instead of pretending they are one blob — related to multi-brand entity separation.
Hypothetical: say Northstar Analytics markets as "Northstar Analytics" in EN and DE, but French corporate filings use "Northstar Analytics SAS." Put the trademark string in name, and the legal local name in a clearly labeled About section or as legalName if you use it — do not let the H1 invent a second product brand.
Step-by-step weekend pass
- List every domain and subdomain that represents the company (
example.com,example.fr,fr.example.com). - Write down the single brand string you want assistants to say aloud.
- Audit H1, title, logo alt, and schema
nameon each homepage. - Add
alternateNameonly for real variants people search. - Fix hreflang pairs; validate no locale points to a blocked URL.
- Align
sameAslists; remove dead profile links. - Check that AI crawlers are not blocked only on some locales.
- Translate the About page properly — machine-only About pages with broken entity names are worse than a thin English About with hreflang.
- Spot-check assistants in two languages: "What is [Brand]?" and note if they invent a local subsidiary.
- Re-scan each locale homepage after fixes so access and clarity checks are not English-only.
Content and NAP
For local service businesses with multilingual sites, NAP consistency still applies — same phone format policy, same address spelling across directories. See NAP consistency and the local playbook in AEO for local service businesses.
Ecommerce catalogs should keep SKU identity stable across languages even when titles translate — assistants that mix locales otherwise invent availability. Pair with the ecommerce AEO checklist.
Crawler and WAF gotchas by locale
Teams often allow GPTBot on the main domain and forget the .de mirror behind a stricter WAF. Answer crawlers then see an incomplete brand. Apply the same robots and allowlist policy on every public locale, then verify with a fetch — not only with a Googlebot test.
Mistakes
- Auto-translating brand names inside JSON-LD every deploy.
- Different Twitter/X or LinkedIn company pages per language that describe unrelated products under similar names.
- Blocking GPTBot on
/fr/because of an old WAF rule. - Publishing hreflang to URLs that require cookies before HTML.
- Translating review schema text while leaving star counts that belonged to another locale’s product set.
Honest ceiling
You cannot make every language model equally fluent in your secondary markets. Similarweb / TechCrunch (June 2025) data on AI referrals (about 1.13B to top sites in the measured month) is dominated by large platforms and likely skewed toward major languages. Do the consistency work so that when retrieval happens in French or German, you still look like one company.
BrandKnown Agency ($49/mo) supports multiple saved brands and rescans — useful when each locale needs its own readiness pass. The score remains a website checklist, not a promise of citations in every language.