The real cost of getting hreflang wrong
I've watched this mistake cost real money. A Kuwait e-commerce business spent two years building an English site, then added Arabic pages, same products, same layout, nearly identical content just translated. Search rankings tanked. Not because the Arabic was bad, but because Google saw two copies of every page competing against each other. The site lost roughly 40% of English traffic and never gained equivalent Arabic traffic because Google didn't trust either version enough to rank them well.
That's what happens when hreflang is missing or misconfigured.
Here's the thing: your multilingual site isn't actually multiple sites to Google, not unless you explicitly tell it which page belongs to which audience. Hreflang is how you have that conversation. It's a single HTML tag that solves one of the most underrated problems in international SEO.
What hreflang actually does
Let me be direct about what hreflang is NOT. It's not a redirect. It's not a way to block one language version or boost another. It's metadata, information you embed in your page's HTML head section that tells Google: "This page is for English speakers in any region. The Arabic equivalent is over here. The version for English speakers in the UAE is over there."
Google uses this information to:
- Serve the right language version to the right user (someone searching from Kuwait in Arabic gets the Arabic page)
- Consolidate your authority across versions (instead of splitting ranking power between EN and AR copies, each version gets full credit for what it ranks for)
- Avoid penalizing you for duplicate content (because you've officially told Google they're not duplicates, they're translations)
The tag itself is simple:
<link rel="alternate" hreflang="ar" href="https://yoursite.com/ar/page/" />
<link rel="alternate" hreflang="en" href="https://yoursite.com/en/page/" />
<link rel="alternate" hreflang="x-default" href="https://yoursite.com/page/" />
You place one line for each language version of the page, plus one "x-default" tag that points to whichever version should show to users whose language you can't determine.
Where most businesses in Kuwait get this wrong
The mistakes I see fall into a few clear buckets, and each one costs traffic.
Mistake 1: Incomplete hreflang. You've added the English tag but forgotten Arabic, or vice versa. Now Google sees one language properly defined and the other as orphaned duplicate content. Result: the untagged version doesn't rank.
Mistake 2: Wrong language code. Using "ar-AE" when you meant "ar" for all Arabic speakers. Language codes are specific (ar = all Arabic, ar-AE = Arabic as spoken in UAE, ar-KW = Arabic in Kuwait). If your content is meant for Gulf Arabic speakers generally, use "ar". If it's specifically for Kuwait, use "ar-KW". Most content platforms let you choose, but I've seen developers hardcode "en-US" on a global site, which tells Google "this is only for America", and now you're not showing in UK, Canada, or UAE searches.
Mistake 3: Self-referential tags missing. Each language version of a page needs to reference itself. The English page should say "I'm the English version, and here's the Arabic version." The Arabic page should say the opposite. Miss one direction and the relationship breaks.
Mistake 4: Hreflang on pages that don't need it. If you only have one language on a page, don't add hreflang. It creates noise and can confuse crawlers. I'd only add it if you actually have 2+ language versions of that content.
In my experience leading projects across Kuwait and the Gulf, the worst problem is inconsistency. One template adds hreflang correctly. Another doesn't. Some pages have it, others don't. Google's crawler then makes guesses instead of following your explicit instructions, and guesses are wrong more often than not.
Expert Insight: The Consolidation Effect
When hreflang is set up correctly, something magical happens: Google treats your English and Arabic versions as one coherent entity, not competitors. If your English page earns 50 backlinks and your Arabic version earns 20, Google understands they're the same asset in different languages. That matters for authority signals. Without hreflang, those backlinks scatter across duplicate URLs and dilute each other's power. I've seen correctly implemented hreflang recover 25-35% lost traffic within 3 months just by consolidating authority this way. It's one of the highest-ROI SEO fixes when you're starting from a broken multilingual setup.
How to actually implement hreflang
There are three ways to add hreflang: in the HTML head, in HTTP headers, or in your sitemap. For most businesses, the HTML head method is simplest.
If you're using a modern CMS (WordPress, Webflow, Shopify, Laravel), check if it has a built-in hreflang setting. WordPress WPML plugin, Shopify's built-in language setup, and Webflow's locale settings all handle hreflang automatically if you configure them correctly. If you're building custom, you need to add it manually in your template.
Here's the step-by-step:
- Decide your URL structure. Are you using subfolders (/en/, /ar/) or subdomains (en.site.com, ar.site.com) or country-code domains (site.ae, site.kw)? Hreflang works with all three, but you need to be consistent. Subfolders are easiest for most businesses.
- Create the hreflang tags. For every language version of every page, write one tag pointing to that version. Include all language versions on each page.
- Add self-reference. Each page must include a tag pointing to itself. Your English page needs <link rel="alternate" hreflang="en" href="[its own URL]" />.
- Add the x-default tag. This tells Google which version to show if the user's language can't be determined. Usually your English version.
- Test it. Use Google's URL Inspection Tool to verify the tags are being read correctly.
- Monitor in GSC. Log into Google Search Console, go to Settings > International Targeting, and confirm Google has recognized your hreflang structure.
For a typical site with English and Arabic versions, here's what your head tags look like on the English version of /blog/seo-tips/:
<link rel="alternate" hreflang="en" href="https://site.com/blog/seo-tips/" />
<link rel="alternate" hreflang="ar" href="https://site.com/ar/blog/دليل-سيو/" />
<link rel="alternate" hreflang="x-default" href="https://site.com/blog/seo-tips/" />
And on the Arabic version, you swap them:
<link rel="alternate" hreflang="ar" href="https://site.com/ar/blog/دليل-سيو/" />
<link rel="alternate" hreflang="en" href="https://site.com/blog/seo-tips/" />
<link rel="alternate" hreflang="x-default" href="https://site.com/blog/seo-tips/" />
One honest caveat: regional variants
If you serve English speakers in the UAE, Kuwait, and the UK with genuinely different content, different pricing, different shipping, different product recommendations, then you need more granular hreflang. You'd use hreflang="en-KW", hreflang="en-AE", hreflang="en-GB" instead of just hreflang="en". But here's what I'd tell you: most businesses don't have truly different content per region. They have the same content with minor tweaks. In that case, using just "en" is simpler and works better. Only go regional if you actually need to.
Validating your implementation
After you've added hreflang, you need to verify Google is reading it. There are a few ways:
Google Search Console: The most authoritative source. Go to Settings > International Targeting. If Google found your hreflang, it'll show you a summary. It'll also flag errors, mismatched URLs, broken tags, missing self-references. Fix anything it highlights immediately.
Google's URL Inspection Tool: Paste any page URL from your site. Scroll down to the "Linked resources" section and look for hreflang. If it's there, Google is reading it. If it's not, check your HTML source, the tag might not be in the head section, or there might be a syntax error.
Manual HTML check: Right-click any page, select "View Page Source," and search for "hreflang". If you see your tags there and they point to real URLs, you're probably fine. But Google might still see something different due to JavaScript rendering, which is why GSC is the final authority.
Why GSC Matters More Than You'd Think
I've worked with sites that had perfect hreflang in the code but Google was reading it incorrectly because of how the site was rendering JavaScript. GSC showed "Hreflang doesn't have a matching return link" on half the pages. Took two weeks of debugging to realize the issue wasn't the tags, it was redirect chains in the site architecture. This is why validating in GSC isn't optional. It's your reality check. The code can be perfect and Google can still misinterpret it. GSC tells you what Google actually sees, not what you intended.
When NOT to use hreflang (and what to use instead)
Hreflang is not one-size-fits-all. If your situation is one of these, you might not need it or might need a different approach:
You have one language and serve multiple countries: If you're English-only but serve USA, UK, and Canada with different pricing, use hreflang with country codes (hreflang="en-US", hreflang="en-GB", etc.). But honestly, if content is identical, you probably don't need hreflang at all, just use geotargeting in GSC.
You have completely separate sites: site-en.com and site-ar.com. These aren't linked hreflang; they're separate entities. Use canonical tags instead to tell Google they're related. Or better yet, move to one domain with language subfolders, it's simpler and cleaner for SEO.
You have user-selectable language switchers but not all content is translated: Only add hreflang for pages that actually have both versions. Don't add it to pages that are only in English.
The bigger picture: why this matters for Gulf businesses
When a client comes to us asking about international SEO, the first thing I ask them is "Who do you actually want to reach?" Because that answer determines everything. A software company in Kuwait serving both English-speaking expats and Arabic-speaking locals needs hreflang to reach both without cannibalizing their own rankings. A real estate site in Dubai serving investors from multiple countries needs it to differentiate content by language and location. A product company shipping across the Gulf needs it to manage content for different markets.
But here's what I've noticed: most businesses think they don't need this level of precision. They'll build one version, maybe translate it half-heartedly, and assume one version will rank well enough. And sometimes it does, until a competitor shows up with proper international SEO setup and takes market share in the Arabic search results.
Hreflang isn't glamorous. It won't double your traffic overnight. But it's foundational. It's the difference between leaving money on the table and capturing demand across all your language audiences simultaneously.
Tools to help with hreflang audits
Screaming Frog is the gold standard for crawling your site and checking hreflang implementation at scale. Run a crawl and filter for hreflang errors, it'll catch missing tags, broken URLs, and mismatched language codes across your entire site in minutes. Google Search Console is free and mandatory, it's your direct line to how Google is interpreting your setup. DeepCrawl and Botify are enterprise-grade but overkill unless you're managing thousands of pages.
