Arabic–English hreflang and canonical implementation

Publish two useful versions

Each language needs its own URL, title, and content for its audience. In an Arabic-default model, Arabic may be prefixless while English lives under /en. Avoid forced geo-redirects; geography does not always reveal the visitor’s preferred language.

Pair corresponding pages

Give each page a self-referencing canonical and reciprocal hreflang links to its true counterpart. An x-default link can point to the default version. Do not pair an English service page with an unrelated Arabic article just because the translation is missing. Both indexable versions should appear in a coherent sitemap.

Inspect rendered output

Check actual HTML and 200 responses after publication, not only source components. If one language is incomplete, do not pretend the pair is ready. Include these checks in SEO implementation. Google’s localized-version documentation explains the supported signals.