Why your Arabic pages are not being found: five technical mistakes
A bilingual site is two sites that happen to share a server. The English half usually gets the attention during the build, and the Arabic half inherits whatever was left. Search engines and AI answer engines notice the difference, and the Arabic pages quietly stop being found.
The short answer
Most Arabic pages that do not appear in search are not being penalised. They are being misread. The page says it is English, the language versions do not point at each other properly, links reach it through redirects, and the Arabic text is a thinner copy of the English. Each of these is small and fixable in an afternoon. Together they make the Arabic side look like an afterthought, because technically it is one.
Why it happens on so many sites
None of these faults comes from carelessness about Arabic. They come from how bilingual sites are built. The English version is designed, reviewed and tested page by page. The Arabic version is usually produced afterwards, often by a plugin or a translation step, and checked by looking at it in a browser. A page can look perfect in a browser and still carry every fault on this list, because none of them is visible on screen.
They are also invisible in the tools most owners look at. A site audit that crawls from the English home page will report the Arabic side as healthy if the links work, even when every one of them passes through a redirect. The only reliable way to find them is to look at the Arabic pages the way a crawler does: the source, the headers and the sitemap.
Mistake one: the page tells the browser the wrong language
Open an Arabic page, view the source, and look at the first line. If it reads <html lang="en">, the page is announcing itself as English. It is one of the most common faults we find on bilingual sites built with JavaScript frameworks, where the Arabic route reuses the English layout and nobody changes the root element.
Google says it detects a page’s language from the text itself rather than from this attribute, so the fault rarely costs rankings directly. It costs almost everything else. Screen readers pronounce Arabic with English rules, browsers offer to translate a page that is already in the reader’s language, and the right-to-left direction ends up applied by CSS instead of by the markup. The W3C’s guidance on structural markup and right-to-left text is direct about the last point: put dir="rtl" on the html element, and do not use CSS to set the base direction, because the direction is part of the meaning of the text.
The fix is one line per template: lang="ar" dir="rtl" on every Arabic page, generated by whatever decides which language is showing.
Mistake two: language versions that do not point at each other
The hreflang tags in a page’s head tell search engines which pages are translations of each other. The rule people miss is that the relationship has to be complete in both directions. Google’s documentation on localised versions says each version must list itself as well as every other version, and that when one page points to another without a link back, the annotations may be ignored.
In practice the failure looks like this: the English page lists the Arabic one, the Arabic page lists only itself, or lists a URL that has since changed. Search engines then treat the pair as unrelated pages, and the Arabic one competes with the English one instead of serving Arabic searchers.
Check any page by viewing its source and counting the hreflang lines. A two-language site should show the same set on both versions, each pointing at a live URL, plus an x-default if you use one.
Mistake three: internal links that pass through redirects
Arabic URLs change more than English ones. A site launches with Latin slugs on the Arabic side, such as /ar/about-ar/, and later moves to proper Arabic ones. The old addresses are redirected, correctly, so nothing looks broken.
But the links inside the Arabic pages still point at the old addresses. Every internal link now costs a redirect hop, crawlers spend their time following them, and the sitemap and the links disagree about where the page lives. We found twenty such links across fourteen pages on our own site after a rename, all technically working and all worth fixing.
After any change to Arabic URLs, search the content for the old paths and rewrite them to the final address. Redirects are for visitors arriving from outside, not for your own links.
Mistake four: the Arabic page says less
Translation compresses. When an English article is turned into Arabic, the argument usually survives and the examples, the exceptions and the worked figures quietly fall out. The result is an Arabic page with roughly half the substance of its English twin.
| Check | What to look for |
|---|---|
| Length | Arabic runs denser than English, but under about 60% of the English length usually means content was dropped |
| Examples | Every worked example in the English version has an Arabic equivalent |
| Figures | Prices, dates and quantities match exactly |
| FAQ | The same questions exist, answered in full |
| Meta | Title and description written in Arabic, not left in English |
A thin Arabic page is not a duplicate problem. It is a quality problem: when an AI answer engine or a search engine chooses which page to cite for an Arabic question, it picks the page that actually answers it. That is the same reason we argued for depth in getting cited in Arabic AI answers.
Mistake five: the sitemap stopped telling the truth
A sitemap lists each page with the date it last changed. Search engines use that date to decide what to recrawl. If the dates stop moving, updated pages look unchanged, and new Arabic pages can sit undiscovered.
This happens more often than it should. Caching in an SEO plugin, a sitemap generated once at launch, or a separate sitemap for one language that nobody regenerates. On one install we found three of a site’s sitemaps frozen for a week while the pages underneath were being rewritten.
Read the dates, not just the list. Open the sitemap after you edit a page and confirm that page’s date moved. If it did not, the sitemap is not doing its job, however complete it looks.
A fifteen-minute check you can run today
Pick your three most important Arabic pages and, for each one:
- View the source and confirm
lang="ar"anddir="rtl"on the html element. - Count the hreflang lines and open each URL they list.
- Click three internal links and watch the address bar for a redirect.
- Compare the Arabic word count and examples with the English version.
- Find the page in the sitemap and check its date.
If all five pass on three pages, the site is probably sound. If one fails, it has usually failed across the whole template, which is good news: one fix repairs every page.
Where this fits
These are the first things we check on any bilingual site, before any content work, because good Arabic writing on a page that announces itself as English starts at a disadvantage. It is part of our search visibility work and of every site we build. Send us one Arabic page and we will tell you which of the five it has.
Frequently asked questions
Does the lang attribute affect my Google ranking?
Not directly. Google says it detects language from the text. The attribute matters for screen readers, browser translation and correct right-to-left rendering, which affect how people experience the page.
Should Arabic URLs use Arabic or Latin characters?
Either works if it is consistent. Arabic slugs read naturally in results and when shared. What matters most is choosing once and not changing them later, because every change leaves old links behind.
Do I need x-default?
It helps when you have a language chooser or a default version for visitors whose language you do not serve. A simple two-language site can work without it, provided the two versions reference each other correctly.
Is machine translation acceptable for the Arabic side?
As a first draft, yes. Published without review, it tends to produce exactly the thin, slightly wrong page described above. Someone who writes Arabic well should read it against the English before it goes live.
[…] Ask the designer to show you an Arabic page they built, on a phone. If the Arabic looks like an afterthought there, it will look like one on your site too. We listed the common technical faults in why your Arabic pages are not being found. […]