Elnahrawy logo
العربية
Back to all articles
Technical SEO May 11, 2026 10 min read

Technical SEO Checklist for UAE Businesses (2026)

A complete 2026 technical SEO checklist for UAE businesses — crawlability, hreflang for Arabic/English, Core Web Vitals targets, LocalBusiness schema, and mobile-first essentials.

Technical SEO audit checklist on a laptop in a Dubai office

Why a UAE-specific technical SEO checklist?

Generic checklists miss the things that actually break UAE sites: bad hreflang between Arabic and English mirrors, CDN edge nodes far from Dubai, RTL layouts that ship the wrong fonts, and LocalBusiness schema that doesn't include the proper UAE address fields. This checklist is what I run on every UAE engagement before touching content or links.

1. Crawlability & indexation

  • robots.txt allows Googlebot, Googlebot-Image, Googlebot-Mobile, and Bingbot.
  • No accidental noindex on production templates (check Arabic mirror separately).
  • XML sitemap lists EN and AR URLs with correct <xhtml:link rel="alternate" hreflang> entries.
  • Sitemap submitted to GSC for both https://example.com and (if used) https://example.com/ar.
  • Canonical tags are self-referential per language — Arabic page canonicals to itself, not to the English URL.
  • No infinite faceted-navigation crawl traps (filter URLs blocked or canonicalized).
  • Pagination uses real links, not JS-only onClick handlers.

2. hreflang for Arabic + English

The single most common UAE technical bug. Get it right:

  • Every EN page links to its AR twin: <link rel="alternate" hreflang="ar" href="...">.
  • Every AR page links back to EN: <link rel="alternate" hreflang="en" href="...">.
  • x-default points to the English version (or a language selector).
  • hreflang URLs are absolute, use HTTPS, and match the canonical exactly (trailing slash matters).
  • Validated in GSC's "International Targeting" report and a tool like Merkle's hreflang tester.

3. Core Web Vitals targets for the UAE market

UAE users are mostly on fast 4G/5G with newer devices, but your CDN matters:

  • LCP < 2.5s at the 75th percentile on mobile.
  • INP < 200ms — audit third-party scripts (chat widgets, ad pixels).
  • CLS < 0.1 — reserve dimensions for images, ads, and Arabic web fonts.
  • CDN has an edge node in Dubai or Fujairah (Cloudflare, Akamai, AWS CloudFront all do).
  • Hero image preloaded with fetchpriority="high" and served as AVIF/WebP.
  • Arabic web fonts subset and self-hosted with font-display: swap.

4. LocalBusiness schema for UAE

  • @type: LocalBusiness (or a specific subtype like Dentist, RealEstateAgent).
  • address includes addressLocality (Dubai), addressRegion (Dubai/Abu Dhabi/Sharjah/etc.), addressCountry: "AE", postalCode if available.
  • telephone in international format (+971...).
  • areaServed lists the emirates you serve.
  • openingHoursSpecification reflects UAE working week (Mon–Fri or Sun–Thu depending on sector).
  • sameAs links to verified Google Business Profile, LinkedIn, Instagram.
  • Validated in Google's Rich Results Test — no errors, no warnings.

5. Mobile-first indexing (95%+ UAE traffic is mobile)

  • Mobile and desktop content are identical (no hidden mobile-only or desktop-only content).
  • Tap targets ≥ 48px, font size ≥ 16px to avoid iOS auto-zoom.
  • Viewport meta: <meta name="viewport" content="width=device-width, initial-scale=1">.
  • No intrusive interstitials on mobile landing pages.
  • Click-to-call tel: links and click-to-WhatsApp wa.me links present on mobile.

6. Arabic content technical tips (RTL, fonts, encoding)

  • <html lang="ar" dir="rtl"> on every Arabic page (not on EN pages).
  • CSS uses logical properties (margin-inline-start instead of margin-left) so layouts mirror cleanly.
  • Arabic font (e.g. IBM Plex Sans Arabic, Cairo, Tajawal) is subset and preloaded.
  • UTF-8 charset declared in <head> — no Windows-1256 anywhere.
  • Numbers in product/price contexts use Arabic-Indic digits (٠١٢٣) only when audience expects them; otherwise stick to Latin digits for SKU/price clarity.
  • No mixed LTR/RTL inside the same paragraph without proper Unicode bidi controls.
  • Schema inLanguage: "ar" on Arabic pages, "en" on English pages.

7. Internal linking & site architecture

  • Every important page is reachable in ≤ 3 clicks from the homepage.
  • Internal links use descriptive anchor text in the page's language.
  • Cross-language switcher links every EN page to its AR twin and vice versa.
  • Breadcrumbs implemented in the UI and as BreadcrumbList schema.

Where to go next

Run through this checklist, fix the red items, then re-audit. If you'd rather have a senior consultant run it for you, the entry points are Technical SEO services and the Core Web Vitals optimization service.

FAQ

Do I need separate sites for Arabic and English in the UAE?

No. Subfolders (example.com/ar) on a single domain are easier to manage, consolidate authority, and work perfectly with hreflang. Separate ccTLDs are overkill for most UAE businesses.

How often should I re-audit a UAE site technically?

Full audit annually, or after any major release (CMS migration, redesign, replatform). Lightweight checks (CWV, GSC errors, broken links) every month.

Can I rank in the UAE without Arabic content?

For some B2B and expat-targeted niches, yes. For local consumer search, you're capping yourself at maybe 40–50% of the addressable demand. Arabic content is the highest-leverage move most UAE sites can make.

By Mohamed Elnahrawy

SEO Engineer & Growth Consultant

Related articles