hreflang for bilingual Saudi sites: done once, done right

hreflang tells a search engine that two pages are the same content in different languages, so it can show the right one to the right person instead of picking between them. On a bilingual site it is the difference between two pages that support each other and two pages that compete.

It has to be reciprocal

If your English page points at the Arabic one, the Arabic one must point back — and both must also point at themselves. A one-sided declaration is ignored. Not warned about, not reported: ignored. This is the single most common way the tag ends up doing nothing.

Name the region when the region matters

For a Saudi audience, ar-SA is more useful than a bare ar. Arabic is spoken across many markets, and the region code is how you say this version is for Saudi Arabia specifically. Pair it with x-default pointing at whichever version a visitor outside both should land on.

Canonical and hreflang must agree

Every page should carry a canonical pointing at itself. If the Arabic page's canonical points at the English URL, you have told the search engine the Arabic page is a duplicate that should not be indexed — while simultaneously telling it the two are language alternates. The contradiction resolves against you.

How to check it actually works

• View source on both pages and confirm all three tags appear on each.
• Confirm each URL is absolute, not relative.
• Confirm the sitemap declares the same pairs the pages do.
• Read the International Targeting report in Search Console after a few weeks.