What Is Hreflang and Why Multilingual Stores Need It
Hreflang is an HTML attribute that tells search engines which language and region a page is written for, and which alternative versions exist in other languages or regions. Without it, Google cannot reliably decide which language version of your store to show a visitor, and your translated pages may end up competing against each other in search results instead of complementing them.
What Hreflang Actually Does
Hreflang signals the relationship between pages that cover the same content in different languages or for different regional audiences. Each signal is a small tag that says: “this page is in German for Germany, and these other URLs cover the same content in French, Spanish and English.” Search engines read those tags and route each user to the version most likely to match their language and location.
Without these tags, Google is guessing. It might index your German product page but show it to French visitors. Or it might treat your English and Australian English pages as duplicate content and suppress one. Neither outcome is good for traffic or conversions.
The attribute lives in one of three places: the <head> section of each page, the HTTP response headers, or the XML sitemap. For most WooCommerce stores, the head tag approach is the most practical and easiest to audit.
How a Hreflang Tag Is Built
Each tag follows the same pattern: a language code, optionally combined with a region code, pointing to the full absolute URL of the equivalent page. The language codes follow the ISO 639-1 standard (en, de, fr, nl) and the region codes follow ISO 3166-1 alpha-2 (GB, DE, FR, US).
| Attribute value | What it means | When to use it |
|---|---|---|
| en | English, any region | One English version, no regional split needed |
| en-GB | English for the United Kingdom | Separate UK version with local spelling or pricing |
| en-US | English for the United States | Separate US version with different currency or content |
| de | German, any region | One German version serving DE, AT, CH |
| x-default | Fallback for unmatched regions | Always include; usually points to the main language version |
Every page in the set must reference all the others, including itself. If the German page does not point back to the English page, and the English page does not point back to the German page, the signal is broken and search engines may ignore the entire set.
The Most Common Hreflang Mistakes in WooCommerce Stores
These errors appear repeatedly in stores that added multilingual support as an afterthought rather than building it in from the start.
- Missing the self-referencing tag. Every page must include a hreflang tag pointing to itself. If the French page only lists the other languages and forgets itself, the signal is incomplete.
- Using relative URLs instead of absolute URLs. Hreflang requires full URLs including the protocol (https://). A relative path like /fr/produit/ will not work.
- Omitting x-default. This fallback tells Google where to send visitors whose language does not match any of your versions. Without it, those visitors may land on the wrong page or see no result at all.
- Tags pointing to pages that return a 301 redirect or a 404 error. Every URL in a hreflang tag must resolve correctly. Stale redirects from old URL structures break the signal silently.
- Inconsistent tags across the page set. If the English page says the Spanish version is at /es/product-a/ but the Spanish page says its canonical is /es/producto-a/, the two signals contradict each other.
- Not updating hreflang after adding a new language. When you launch a new language version, every existing page in the set must be updated to include the new URL. This is easy to miss at scale.
Hreflang and WooCommerce: What to Check Before Going Live
Multilingual WooCommerce stores generate a large number of translated URLs — product pages, category pages, cart, checkout, account pages and static content pages all need correct tags. A product catalogue with several hundred items in five languages means thousands of hreflang relationships to maintain correctly.
The right approach is to let the multilingual plugin handle tag generation automatically, then verify the output on a sample of pages before launch. As explained in detail in our guide on building a multilingual WooCommerce store, the plugin choice and configuration matter because incorrect setup can silently generate broken tags at scale.
Use Google Search Console’s International Targeting report and a hreflang validator tool to check your tags after launch. Search Console will flag pages where it found conflicting or incomplete hreflang signals. Fix those before the crawl settles, because incorrect tags can persist in Google’s index for weeks.
What Hreflang Does Not Do
Hreflang is a signal, not a command. Google treats it as a strong hint but can override it. If your German page actually contains mostly English content, hreflang alone will not make Google rank it for German searches — the content itself must match the language declared in the tag.
Hreflang also does not solve duplicate content between language versions that are too similar. If your French and Belgian French pages are nearly identical, you may still need to decide whether to combine them or differentiate the content enough to justify separate URLs. A lawyer or SEO specialist should confirm whether regional splits are worth the maintenance cost for your specific situation.
It also has nothing to do with currency display, payment methods, or which shipping zones appear at checkout. Those are handled separately in WooCommerce through geolocated pricing and shipping zone configuration.
How We Run This in Our Own Projects
GiantParts.eu sells tested used OEM car electronics across ten languages. Every product page, category page and static content page carries a full set of hreflang tags covering all ten language versions plus x-default. The tags are generated automatically by the multilingual layer and validated on a schedule so that any broken URL — from a product that is delisted, for example — is caught before it corrupts the signal for the entire product set. The store also has structured data and technical SEO built in from the start, which means hreflang works as part of a complete signal set rather than in isolation.
The supremecommerce.eu site itself runs in six languages and follows the same pattern: every page references all six versions, the x-default points to the primary language, and the XML sitemap includes the hreflang annotations as a secondary layer of confirmation for crawlers.
FAQ
Does hreflang affect my search rankings directly?
Hreflang does not boost rankings for a single page. What it does is ensure the right language version ranks for the right audience, which improves click-through rates and reduces bounce rates from visitors who land on a page in the wrong language. Those engagement signals do influence rankings over time.
Do I need hreflang if my store only has one language but ships to multiple countries?
If the content is genuinely identical across countries and you are not splitting into separate URLs per country, you usually do not need hreflang. If you do have separate URLs — for example, different pricing pages per country — then x-default and country-region tags become relevant even with a single language.
Can I add hreflang to a WooCommerce store after it is already live?
Yes, and it is worth doing even if the store has been running without it for some time. The main risk is introducing incorrect tags by updating only some pages and not others. A systematic approach — update all pages in one pass, validate with Search Console, then monitor — avoids creating contradictions in the tag set.
How long does it take Google to process new hreflang tags?
Google needs to crawl every URL referenced in the tag set before it can process the relationships. For a large store this can take several weeks after the tags are added. Submitting an updated XML sitemap that includes hreflang annotations speeds up the process by giving the crawler a complete map to follow.
Where to Go Next
If you are building or fixing a multilingual store and want hreflang set up correctly from the start alongside live shipping rates, structured data and translated checkout, the studio can scope and build the full setup. See the Inside Our Projects page for live examples of how multilingual stores are structured, then request a project quote — the studio replies within 24–48 hours.
