Arabic and English SEO: hreflang, translation and user choice

Decide what each language audience needs

Arabic and English visitors may need the same core service information, but language is more than word substitution. Terminology, direction, typography, forms, dates, numbers, currency and call-to-action wording should be reviewed by people who understand the customer and subject matter.

Translate high-value pages first: key services, contact, policies, core product or category pages and the support material customers use before enquiring. Do not create a full alternate section filled with unreviewed machine text solely to capture a language query; thin or inaccurate pages damage trust.

• Prioritise customer-critical pages
• Use qualified human review
• Test RTL layouts, forms and navigation

Next decision: Ecommerce product-page SEO: make product choices clear. If you want this applied to a live site, see the SEO audit scope.

Give language versions stable URLs

Use separate URLs for distinct language versions, such as /ar/ and /en/, and make each version accessible through normal links. Avoid automatic redirects based only on assumed language or location; a traveller, bilingual user or Googlebot may need to choose another version.

Show a visible language switcher that goes to the equivalent page when possible. Do not send every Arabic page to the Arabic homepage. Keep the selection persistent only where that improves the experience, while preserving a direct route to every language URL.

• Use one consistent URL pattern
• Link equivalent pages directly
• Let users override automatic suggestions

Implement hreflang as an accurate map

Hreflang annotations tell Google which URLs are language or region alternatives. Each page should reference itself and its counterparts, using fully qualified URLs; the relationships should be reciprocal. Use language codes that match the content, and add a default version only when it genuinely serves users not matched by another choice.

Do not point Arabic and English pages at each other when their content is not equivalent. A shorter Arabic landing page and a detailed English guide may deserve separate treatment until both versions can be maintained. Hreflang does not translate pages or guarantee that Google will show a particular version.

• Map equivalent page pairs
• Include self-referencing annotations
• Validate return links after publishing

Measure language experience separately

Track search performance by URL folder, language queries and device, then pair that with conversions or enquiries. A gap may indicate translation quality, insufficient local detail, a broken alternate link or simply different demand. Look at the page a user actually lands on, not an aggregated site average.

Maintain both versions when services, hours and policies change. A stale language page is not solved by an hreflang tag. Build translation review into the publishing workflow and mark owners clearly, especially for regulated terms, pricing and service availability.

• Segment reporting by language URLs
• Update both versions together
• Review terminology with subject experts