Common Hreflang Mistakes on Multilingual Car Rental Sites
July 17, 2026
Broken hreflang doesn’t throw an error or drop a site from the index — it just makes Google show the wrong language version to the wrong audience, and most car rental owners only find out when they notice a Spanish-speaking tourist landing on the English version of a page. An international car rental business almost always runs in at least two or three languages, and it’s exactly at the seams between those language versions that mistakes appear — ones that stay invisible without a specific check.
This article covers five specific mistakes and how to find them on your own site, not a general “what is hreflang” explainer.
Mistake 1: hreflang tags aren’t reciprocal
Every language version of a page needs to link to every other version, including itself, and all versions need to link back to each other the same way. If the English page links to the Russian version but the Russian version doesn’t link back to the English one, Google treats the markup as unreliable and may simply ignore it entirely for that group of pages. This is the single most common technical reason hreflang “doesn’t work” even when the tags look correct on any one page by itself.
Mistake 2: the hreflang URL doesn’t match the real canonical
An hreflang link needs to point to the target page’s canonical URL, not a redirect or a version with different parameters. If the Spanish page physically lives at /es/blog/... but the hreflang tag on other language versions points to /es/blog/.../index.html or a no-trailing-slash URL that redirects to the canonical address, Google isn’t obligated to follow that redirect when processing hreflang, and the link between versions breaks.
Mistake 3: no x-default tag
The x-default tag tells Google which version to show a visitor whose language doesn’t match any of the listed alternates — without it, part of your international traffic gets a random language version instead of a sensible default. On the CapDrew site, every group of language versions explicitly includes an x-default pointing to the English version of the page — it’s one line in the template, but without it, visitors whose browser is set to a language the site doesn’t have see an unpredictable result.
Mistake 4: the content’s lang doesn’t match the URL’s language
If a page physically lives under /ru/ and its hreflang is tagged ru, but the content itself isn’t actually translated or the lang in its frontmatter is still en, that mismatch confuses both search engines and AI crawlers, which rely on the declared language when deciding who to show the page to. The markup needs to reflect the content’s actual language, not just where the file happens to sit.
Mistake 5: hreflang isn’t applied consistently across every page
A common situation: hreflang is set up correctly on the core money pages but forgotten on blog posts, or added later for some articles and not others. Every new page that has language versions needs the full set of hreflang tags the moment it’s published — if this is added manually per article, the markup drifts out of sync with the site’s actual state over time, and some pages fall out of the cluster.
How to check your own site quickly
Open the page source of any language version and confirm the <head> has one hreflang tag per language on the site plus x-default, that every URL in those tags points to a real canonical address with no redirects, and that the same set of tags, mirrored, sits on every linked language version too. A mismatch on any of these is a signal to fix it before investing further in SEO for car rental.
How this is built on the CapDrew site
On every page of this site — including this article — hreflang is generated automatically from a single source: the list of languages and the current path get passed into a shared template that builds peer links to every version plus x-default, with nothing filled in by hand on each page. That automated approach, rather than manually tagging each publication, is what rules out mistakes 1, 2, and 5 above by construction.
How this fits the bigger picture
Technical SEO like hreflang doesn’t replace substantive content — it determines whether that content ever reaches the right audience in the right language at all. Full picture of SEO for car rental, including geo-page structure and AI search citability, in SEO for car rental: ranking and AI citation and in how to attract customers to a car rental business.
FAQ
Can broken hreflang hurt a site’s search rankings? Not directly — it isn’t a ranking penalty, but incorrect markup can cause the wrong language version to rank for a given query, which in practice looks like lost traffic in the language that should have shown up.
Do I need hreflang if my site is only in one language? No — hreflang only matters once the same page exists in multiple languages or for multiple regions; a single-language site just needs a canonical tag.
How often should hreflang be checked? After any structural change — adding a new language, changing the URL structure, migrating CMS — and periodically, about once a quarter, alongside a general technical SEO check.
Can hreflang be used instead of a separate canonical tag on each language version? No — they’re different tags doing different jobs: canonical says which URL is authoritative for that specific page, and hreflang links language versions to each other; a multilingual site needs both at the same time.
Want your car rental site’s hreflang checked? Book a 15-minute call — we’ll look at the current markup and what’s keeping the right audience from landing on the right language version.