If Arabic searchers in Doha keep landing on your English pages — or an Arabic version has quietly vanished from Google — the cause is usually not your content. It is your annotations contradicting each other: codes copied from a UAE template, return links never added, an Arabic page whose canonical points at its English twin. This guide works the Qatar case: which codes to use, what .qa settles, the failure modes in order, and how to validate the cluster now Search Console no longer reports hreflang errors.
The short answer: the correct Qatar setup in one annotation set
For a bilingual site serving Qatar, both versions of each page carry the same complete annotation set in their head. With example URLs, it looks like this:
<link rel="alternate" hreflang="en-QA" href="https://example.com/en/" />
<link rel="alternate" hreflang="ar-QA" href="https://example.com/ar/" />
<link rel="alternate" hreflang="x-default" href="https://example.com/en/" />Three rules make that set work, all from Google's localised-versions documentation (checked October 2026). Every version lists itself and all the others, so the set is identical on both pages. Every URL is fully qualified, including the https. And each page canonicalises to itself, never to its twin. Break any rule and Google may ignore the annotations, fold the versions, or serve the wrong one. Hreflang only swaps versions — it is not a ranking factor.
ar/en or ar-QA/en-QA? The decision rule for a Qatar site
The codes follow the targeting, not the template. Google builds the value from an ISO 639-1 language code plus an optional ISO 3166-1 Alpha 2 region code: ar-QA is Arabic targeted at Qatar, en-QA likewise for English (checked October 2026).
Use the Qatar codes when pages genuinely target Qatar — Qatari services, pricing, address and phone number, content for Doha readers — as most bilingual Qatar business sites do. Use plain ar and en when one version honestly serves every speaker of that language wherever they are. A borrowed code never works: ar-AE on a Doha site tells Google your pages target the Emirates, whatever the content says.
If you later publish separate versions for other countries, the codes stop being optional — they distinguish your Qatar Arabic page from a Saudi one. Content inside the versions is separate, covered by our guide to SEO for bilingual Arabic-English websites, and the Arabic version must be a real right-to-left page — our Arabic RTL website checklist covers that layer.
What .qa already tells Google — and what it cannot do
Google treats a country-code domain as a strong signal that a site is explicitly intended for that country (checked October 2026), and .qa is Qatar's: the Communications Regulatory Authority's domain FAQs confirm .qa carries no registration requirement, while .com.qa requires a valid Qatar trade licence or a trademark registered in Qatar (checked October 2026).
But the domain answers only the country question, nothing about language — and a Qatar site has two. It cannot tell Google which paired page an Arabic searcher should get, repair a broken cluster, or keep an Arabic page indexed if its canonical points at the English version. On a .com the set carries even more weight, as the domain gives no country signal at all. Targeting other countries is a separate project, covered by our guide to cross-border SEO from Qatar.
The five Qatar failure modes, in the order they actually occur
- Copied UAE codes. Built from a UAE template, every page announces ar-AE and en-AE: a perfect cluster aimed at the wrong country.
- Missing return links. The English page lists its Arabic alternate; the Arabic page never lists back. Google's rule is blunt: if two pages do not both point to each other, the tags are ignored.
- No self-reference. A page's set omits the page itself — common when a template outputs only "the other language". Each version must list itself too.
- Alternates that redirect or fail. An annotation points at an old URL that now redirects, or a page that errors. Alternates must be live, fully-qualified URLs, not redirects.
- A partial or split cluster. Tags exist on some templates but not others, or the HTML and sitemap sets disagree, so Google trusts neither story.
Canonicals: the fault that removes Arabic pages from the index entirely
The most damaging Qatar fault is not a hreflang error at all. It is an Arabic page whose canonical points to the English version — a setting some themes and plugins apply on English-first builds. A canonical tells Google which URL is the original, the rest duplicates. Point Arabic at English and Google folds the translation away, indexing the English page instead.
Google's guidance supports the opposite setup: localised versions count as duplicates only when the main content remains untranslated (checked October 2026). A genuinely translated Arabic page is a duplicate of nothing. So every version canonicalises to itself, and hreflang connects two self-standing pages. If Arabic pages keep disappearing, check canonicals before touching a single hreflang tag. Wider build context: our Qatar web development guide.
Return links, self-references and x-default, done completely
Treat the cluster as a contract: page A names page B as its Arabic alternate; page B must name page A as its English alternate, and both must name themselves. Sets are identical on every version — build them once in the template or sitemap, never by hand, because hand-built sets drift.
The x-default entry is the fallback Google recommends for searchers whose language matches none of your listed versions, especially on selector pages. Point it at your selector page if you have one; if not, at the version an unmatched visitor is best served by — usually the English version, as in the set above. Do not pair it with automatic redirects: Google warns these can stop users and search engines ever seeing all versions of your site.
HTML tags or sitemap hreflang? Choosing for your site's size
Google treats the three methods — HTML tags, HTTP headers and sitemap — as equivalent, advising the most convenient one rather than several. For most Qatar business sites, HTML tags in the template are right: visible in the source and easy to inspect.
Choose sitemap annotations when the site is large or changes often — thousands of URLs, frequent new pages. Each entry lists every alternate including itself, and Google notes those child entries do not count towards the sitemap's URL limit (checked October 2026); one file is also easier to regenerate and re-validate than tags across templates. Use exactly one method — our multilingual website architecture guide covers the wider structure.
Validating without Search Console's report: crawl, inspect, re-check on a schedule
There is no report to check any more. Google deprecated the International Targeting report in August 2022 and removed it that September. Validation is now your own three-pass routine.
First, crawl the whole site with a tool that extracts hreflang, checking mechanically: every pair reciprocal, every set self-referencing, every code valid, every alternate live with a canonical matching the annotated URL. Second, inspect sample pages per template in URL Inspection and confirm Google's chosen canonical is the page itself, not its twin. Third, re-run the crawl on a schedule — after every template change, migration or new language launch, and at a fixed interval between — keeping dated results.
Checking the Doha SERP: which version Google serves, query by query
Annotations are promises; the results page is the evidence. List the queries that matter — your main services in Arabic and English — search them as a Doha user would, and record which version Google serves for each. An Arabic query returning your English page means the swap fails for that query; an English query returning the Arabic page is the same failure reversed.
Run it per query, not once for the site, because clusters break page by page. Log the date and result; repeat after every fix and validation. Over a few cycles, the log exposes the templates that quietly lose their clusters.
FAQ
Should my Qatar site use ar and en, or ar-QA and en-QA?
Use ar-QA and en-QA when pages genuinely target Qatar — Qatari services, pricing, contact details, content for Doha readers — as most bilingual Qatar business sites do. Use plain ar and en only when one version honestly serves every speaker of that language anywhere. Never keep codes copied from another country, such as ar-AE.
Does hreflang improve my rankings in Qatar?
No. Hreflang does not lift a page higher and is not a ranking factor. It tells Google which language and regional version to show a searcher, so the right version appears. It cannot make a page rank where its content has not earned a place.
Why has my Arabic page disappeared from Google?
The most common cause on Qatar sites is a canonical pointing the Arabic page at its English version, telling Google the Arabic page is a duplicate and inviting it to index the English page instead. Check that first, then confirm the Arabic page is indexable, in your sitemap, and named by its English twin.
What should x-default point to on a Qatar bilingual site?
Point it at a language selector page if your site has one. If not, point it at the version a visitor whose language matches neither English nor Arabic is best served by — for most Qatar firms the English version, usually the English home page or English version of the same page.
How do I check hreflang now that Search Console no longer reports errors?
Run your own validation. Crawl the site with a tool that extracts hreflang: check every pair links back, every set includes the page itself, codes are valid, and every alternate is live and self-canonical. Then inspect sample pages in URL Inspection, and repeat after template changes.
Arabic and English versions fighting each other? Get the Qatar cluster audited
If Arabic searchers land on English pages, or one language has fallen out of the index, the fault is in the cluster — codes, canonicals, return links — and one audit finds it. Where the cause sits in the build — a theme or plugin forcing the wrong canonical — the fix is a rebuild of that layer. Start with our page for Qatar businesses, bring your annotation set and the misbehaving pages, and we will map which signals contradict each other.
