hreflang on Egypt's Bilingual Websites: We Checked 207 .eg Homepages

Summary: Bilingual Arabic-English websites need three clear signals: hreflang annotations that link the two versions, a lang attribute that declares the page language, and dir="rtl" on Arabic pages. In our own check of 207 Egyptian .eg homepages on 5 November 2026, 129 sites showed bilingual signs, yet 65 of them (50.4%) had no hreflang at all, and 45 of 128 Arabic pages (35.2%) had no dir="rtl" on the html or body element. An 8-step fix list is at the end.
In Egypt, bilingual websites are the norm: government bodies, universities and companies speak to an Arabic-speaking audience and to English-speaking clients or partners at the same time. But an "English" button in the header does not tell search engines that the two pages are translations of the same content. This article shares the results of a hreflang scan we ran at Smart One Group on Egypt's most visited websites, and explains what to configure so the right version reaches the right user.
Why hreflang and language signals matter now
Google updated its official documentation on localized versions of your pages on 21 September 2026, restating the core rules: each language version must list itself and all other versions, and if two pages don't both point to each other, the tags will be ignored. On 6 October 2026 Google also announced that the Search Console performance report can now combine several countries in one filter, which makes it easier for businesses serving Egypt and the Gulf to measure each market.
One point is often misunderstood: Google says plainly that it does not use hreflang or the HTML lang attribute to detect the language of a page; it relies on algorithms that read the visible content. hreflang exists to connect translated versions so each searcher gets the URL for their language or region, while lang and dir serve browsers, screen readers, translation tools and correct right-to-left rendering.
Quick definitions: hreflang, lang and dir
- hreflang: an attribute on link elements in the page head (or in an HTTP header or the sitemap) telling search engines that the page has another language or regional version at a given URL.
- x-default: a fallback hreflang value naming the page shown when a user's language matches none of the listed versions; Google recommends it especially for language selectors and auto-redirecting pages.
- lang: an attribute on the html element declaring the default language of the page text, such as lang="ar" or lang="en".
- dir="rtl": an attribute setting right-to-left text direction; the W3C recommends placing it on the html element itself and never using CSS to apply the base direction.
In one sentence: hreflang links the versions, lang declares the language, dir sets the direction, and none of them replaces the others.
How Smart One Group ran the scan
We checked all 332 Egyptian domains in the Tranco list (list ID 262N9) of the world's most visited sites on the morning of 5 November 2026 (09:38 Cairo time), requesting each homepage over HTTPS and then with the www prefix. 289 domains responded and 261 returned a valid HTML page. We excluded 11 that redirect to another domain and 43 pages with fewer than 200 letters of text (usually built entirely in JavaScript), leaving 207 homepages for analysis.
We classed a page as "Arabic" when at least 60% of its visible letters were Arabic, and a site as "bilingual" when it had a clear language-switch link or hreflang annotations for both Arabic and English. Where hreflang existed, we fetched up to five alternate versions per site to test return links.
Results: bilingual websites in Egypt by the numbers
| Metric | Count | Share |
|---|---|---|
| Homepages showing bilingual signs | 129 of 207 | 62.3% |
| Bilingual sites with no hreflang at all | 65 of 129 | 50.4% |
| Homepages using hreflang in any form | 67 of 207 | 32.4% |
| hreflang pages that include x-default | 34 of 67 | 50.7% |
| Sites with complete return links | 54 of 60 testable | 90.0% |
| Arabic pages without dir="rtl" on html or body | 45 of 128 | 35.2% |
| Fully declared Arabic pages (Arabic lang + rtl) | 73 of 128 | 57.0% |
Half of bilingual sites have no hreflang
The headline finding is that 65 of 129 bilingual sites use no hreflang at all, leaving search engines to guess how the Arabic and English versions relate. Google may discover alternates on its own, but it says explicit annotations are usually better. The practical risk is that an Arabic searcher lands on the English page or vice versa, raising bounce rates and weakening marketing campaigns.
Region codes that don't belong to Egypt
Of the 67 pages using hreflang, 48 used the generic code ar and only 13 included ar-EG. Two Egyptian sites label their only Arabic version ar-SA (Arabic in Saudi Arabia), and two more use ar-AA, although AA is not a country code in ISO 3166-1, the standard Google requires. en-US appeared on 12 pages. Plain ar is safe for most sites; tying the Arabic version to another country sends the wrong targeting signal.
The homepage sits outside its own cluster
Of the 60 sites we could test, 54 (90.0%) had complete return links. In 4 of the remaining six, the homepage is served at the root URL while the hreflang annotations point elsewhere, such as /ar/, so the English version never links back to the URL visitors actually see. This is common when translation plugins are switched on without reviewing canonical URLs.
lang and dir on Arabic pages
Of 128 Arabic-content pages, 89 (69.5%) declared Arabic in lang, 27 (21.1%) left it missing, and 12 (9.4%) declared English despite Arabic content, a mistake that often comes from unedited ready-made templates. dir="rtl" was absent from both html and body on 45 Arabic pages, meaning direction is set only through styling, which the W3C advises against.
Differences across Egyptian zones
| Zone | Analysed | Bilingual | With Arabic + English hreflang |
|---|---|---|---|
| gov.eg | 49 | 28 | 7 (25.0%) |
| edu.eg | 70 | 45 | 20 (44.4%) |
| com.eg | 54 | 35 | 21 (60.0%) |
| .eg and other zones | 34 | 21 | 14 (66.7%) |
Government sites use hreflang least, even though most offer two versions, a clear gap for sites that investors, tourists and international students search for in English.
An 8-step fix list for bilingual websites
- One URL per language: use paths such as /ar/ and /en/ or subdomains, not cookies or browser language alone; Google recommends separate URLs for each version.
- Complete, reciprocal hreflang: on every version, list itself and every other version, using fully-qualified https URLs.
- Choose codes carefully: ar and en are enough for most sites; use ar-EG only if you have Arabic versions for different countries, and never a country code on its own.
- Add x-default for the language selector or the version you want shown when no other version fits.
- Unify the homepage: make the URL visitors reach the same one listed in hreflang and canonical, and avoid duplicates at the root and /ar/.
- Don't auto-redirect by language: Googlebot usually crawls from the USA and sends no Accept-Language header, so it may never see the Arabic version. Suggest a switch and let the user choose.
- Declare lang and dir on the html element: lang="ar" dir="rtl" for Arabic and lang="en" for English, and check templates that default to lang="en".
- Translate the main content, not just the menu: Google treats localized versions as duplicates if the main content stays untranslated.
For more on how Google handles multilingual sites, see its guide to managing multi-regional and multilingual sites, and for direction see the W3C guidance on the dir attribute. If you are working on visibility in AI results, also read our article on the official sites section in AI Mode and our piece on universal acceptance for Arabic email and .مصر domains.
Frequently asked questions
What is hreflang and why does a bilingual website need it?
hreflang is an attribute that tells search engines a page has a version in another language at a specific URL. A bilingual site needs it so Google shows the Arabic page to Arabic searchers and the English page to English searchers instead of guessing.
Does Google use the lang attribute to detect page language?
No. Google states that it uses neither hreflang nor lang to detect a page's language; it analyses the visible content. lang still matters for screen readers, browsers and translation tools, so don't leave it empty.
Should I use ar or ar-EG in hreflang?
If you have a single Arabic version, ar is enough. Use ar-EG when you have different Arabic versions for different countries, and avoid codes for countries you don't target, such as ar-SA on an Egyptian site.
What happens if hreflang links are not reciprocal?
Google says that if two pages don't both point to each other, the tags will be ignored. The English version must reference the Arabic one and vice versa, and each page must also reference itself.
Is automatic redirection by visitor language a good idea?
Google recommends avoiding it, because its crawler sends no language preference and may not reach every version. A better approach is a visible suggestion to switch language with a clear link, leaving the choice to the visitor.
How can I quickly check my site's setup?
View the page source and search for hreflang, lang and dir, then open the other version and confirm it points back to the first. In Search Console you can track performance per country and combine several countries in one filter.
At Smart One Group we build bilingual websites with correct hreflang, lang and dir from day one, and review existing sites as part of our digital marketing services. If you'd like a review of your site, get in touch.




