Multilingual GEO: hreflang pitfalls that kill non-English citations

Global merchants invest in translation, then wonder why German AI sessions cite competitors. The culprit is rarely "Google hates us"—it is broken locale graphs and hollow localization.

Pitfall 1 — Parameter locales

?lang=de URLs without stable paths break crawler caches and hreflang reciprocity. Prefer /de-de/product-slug patterns.

Pitfall 2 — English schema on localized pages

JSON-LD inLanguage still "en" while HTML is German. Retrieval matching deprioritizes the page for de queries.

Pitfall 3 — Shared titles across languages

Same English H1 on all locales collapses entity resolution; models pick one URL arbitrarily.

Pitfall 4 — UI translation only

German page shows EUR prices but FAQ answers still describe US return windows.

Pitfall 5 — Missing x-default

Forces systems to guess fallback—often wrong market PDP.

Remediation sprint

Audit 100 URLs per market. Fix reciprocity. Localize FAQ entities. Re-test 20 prompts per locale weekly.

FAQ

Is machine translation ever OK? For draft, not production—regulatory and sizing terms need human review.

Do ccTLDs need separate Organization nodes? Usually one Organization; localize WebSite url and contactPoint.

How does Shopify Markets fit? Map each market domain or subfolder into one hreflang cluster.

Visora /audit surfaces locale–schema mismatches alongside hreflang gaps—treat as one backlog for localization engineers.

Put this into practice

Audit your PDP or category page with Visora, then fix schema and FAQ gaps that block AI citations.

Run a free GEO audit →

https://geovisora.com/en/blog/multilingual-geo-hreflang-pitfalls