Technical SEO for Arabic Websites: Core Web Vitals, RTL Markup, and Bilingual Indexing

Technical SEO for Arabic websites is not simply 'standard technical SEO applied to an Arabic site'. The combination of RTL layout requirements, bilingual content management, Arabic-specific font loading challenges, and the performance characteristics of MENA mobile networks creates a distinct set of technical issues that do not appear in English-language SEO guides. Brands operating bilingual EN/AR websites in Jordan and the broader MENA region routinely have indexing problems, duplicate content signals, and Core Web Vitals failures that trace back to technical decisions made during site development — not to content or link quality.

hreflang implementation for bilingual MENA websites

hreflang tags tell search engines which version of a page to show users based on their language and country settings. For a bilingual EN/AR website serving Jordan, the implementation should specify: `` and `` with an `x-default` fallback pointing to the preferred default. Common errors in MENA implementations: using `ar` for Arabic without country specification when targeting a specific Arab country (use `ar-JO` for Jordan, `ar-SA` for Saudi Arabia, `ar-AE` for UAE); inconsistent hreflang across paginated content; and missing return links (each page in the hreflang set must link to all other language versions, including itself). An incomplete hreflang set signals confusion to Google and can cause the wrong language version to rank in the wrong market.

RTL markup: HTML and CSS technical requirements

RTL layout is implemented via `dir='rtl'` on the `` element for Arabic pages, with CSS logical properties (margin-inline-start, padding-inline-end) replacing physical properties (margin-left, padding-right) for elements that need to mirror between LTR and RTL. Common technical errors that affect both UX and crawlability: applying RTL only at the component level (not the document level), which causes search engine rendering to see mixed directionality; using absolute positioning for layout elements that need to mirror (absolutely positioned elements do not inherit RTL direction); and embedding English text within Arabic pages without proper `dir='ltr'` inline tags on those elements, which causes bidirectional text rendering issues. Google's rendering engine sees these rendering failures — pages that look broken in a headless browser tend to receive lower crawl priority over time.

Arabic font loading and Core Web Vitals

Arabic web fonts are significantly larger than Latin fonts because of the contextual letter-form system (each Arabic letter has 4 forms depending on position). A typical Arabic web font in WOFF2 format runs 80–150 KB compared to 20–40 KB for an equivalent Latin font. On MENA mobile networks where 4G connection quality varies significantly by location, this font loading gap directly impacts Largest Contentful Paint (LCP) — the Core Web Vitals metric that measures when the page's main content appears. The technical remedies: font subsetting (load only the Unicode ranges actually used on the page); `font-display: swap` to prevent render-blocking while the Arabic font loads; and preloading critical Arabic fonts in the `` with ``. Sites running both Urbanist (EN) and Tajawal (AR) without these optimisations routinely fail LCP on mobile — which directly affects search ranking in Google's mobile-first index.

Structured data for Arabic content

Schema.org structured data markup should be implemented in the language of the page — Arabic structured data for Arabic pages, English for English pages. Common errors: using English-language structured data on Arabic pages (this creates a mismatch between page language and markup language that search engines flag); missing structured data on the Arabic version of a page that has structured data on the English version; and using organisation schema with English-only name properties on pages targeting Arabic speakers. For local businesses in Jordan, `LocalBusiness` schema with Arabic-language `name` and `description` properties, combined with `addressLocality` set to the correct Arabic city name, improves local search visibility for Arabic-language searches.

The bilingual technical audit

As the SEO Agency in Amman Jordan, our technical audit for bilingual MENA websites covers: hreflang implementation and return link completeness; RTL rendering verification using headless Chrome screenshots; Arabic font loading analysis in PageSpeed Insights and Lighthouse; Core Web Vitals by language version (Arabic and English pages should be audited separately — they often have different scores because of font loading and content length differences); structured data completeness and language matching; and crawl budget analysis for sites with large bilingual content volumes where duplicate content signals across language versions are consuming indexation budget.