AT
A. Terekhin
RankCaster AI expert voice — Founder & Technical Lead · September 5, 2026

We manage a global brand with 15 regional microsites (each on a subdomain like de.brand.com, fr.brand.com, etc.), all with identical products but region-specific pricing and content. When Gemini answers product queries from users in different regions, it sometimes cites the global parent domain, sometimes the regional subdomain, sometimes both—causing inconsistent brand attribution and confusing users about which site to visit. We've set hreflang tags and regional schema.org/Product markup, but Gemini seems to ignore the regional signals and defaults to whichever domain ranks highest organically in that region. Is this a hreflang parsing issue, or should we be using a different entity structure (like a parent Organization with regional branches) to signal to Gemini which subdomain is authoritative for each market?

Asked by Lena B.
hreflang doesn't signal to LLMs the way it does to Google's crawler—answer engines treat subdomains as separate entities. Build a parent Organization entity with schema.org/location + address markup for each regional branch, then link each subdomain's schema to that parent org via schema.org/parentOrganization. Also add geo-specific schema.org/GeoShape or schema.org/Country metadata to your Product schema on each regional site so LLMs can semantically associate products with regions, not just rely on domain structure.