Technical SEO Checklist Dubai 2026 - Audit Template

Technical SEO is the unsexy work that makes all other SEO work compound. A Dubai business with great content and weak technical SEO will be outranked by a competitor with mediocre content and clean technical foundations every time. This is the exact 80-point checklist we run on every Dubai client audit, organised in priority order so you can work top-down.

1. Crawlability and indexation

Before anything else, confirm Google can find, crawl and index your pages. If this layer is broken, nothing downstream matters.

• robots.txt allows critical sections and blocks non-essential ones (admin, checkout, search results)
• XML sitemap exists at /sitemap.xml and is submitted to Google Search Console
• Sitemap contains only canonical URLs (no parameters, no redirects, no 404s)
• Index coverage report in GSC has zero unintended exclusions
• Canonical tags on every page point to themselves or the correct canonical URL
• Hreflang tags present and reciprocal for any Arabic + English bilingual content
• No accidental noindex tags on commercial pages (this is a common silent killer)
• No accidental disallow rules blocking CSS/JS in robots.txt

2. Core Web Vitals

Core Web Vitals are a confirmed ranking factor. They measure three things: how fast the main content loads (LCP), how responsive the page is (INP, which replaced FID), and how stable the layout is (CLS). All three need to pass for the page to qualify as 'good'.

3. Mobile-first essentials

Google has been mobile-first indexing since 2019. Your mobile site is what gets ranked - your desktop site is a secondary consideration.

1. 1Responsive design (not separate m. site, not adaptive)
2. 2Viewport meta tag present and correct
3. 3Tap targets at least 48x48 px with adequate spacing
4. 4Text legible without zoom (16px minimum body text)
5. 5No horizontal scroll on standard mobile viewports (375px, 414px)
6. 6Forms work properly on mobile - input types correct, autofill enabled
7. 7Phone numbers tap-to-call via tel: links
8. 8Critical content visible above the fold on mobile

4. Schema.org structured data

Schema makes your content machine-readable for Google, AI agents and other automated systems. For Dubai businesses, five schemas are essential.

• LocalBusiness on homepage and location pages (with NAP, hours, geo, areaServed)
• Service on each service page
• FAQPage on pages with FAQ sections
• BreadcrumbList on every non-homepage page
• Article + Author on every blog post (with proper sameAs links to social profiles)
• AggregateRating where you have visible reviews

5. Hreflang for Arabic + English Dubai sites

If your Dubai site has Arabic and English versions, hreflang is non-negotiable. Without it, Google cannot tell which version to serve to which audience and both versions can compete with each other in search results, hurting both.

1. 1Each language version declares hreflang for every other language version
2. 2Hreflang tags include x-default pointing to a language selector or default version
3. 3Hreflang reciprocity - if /en/ points to /ar/, /ar/ must point back to /en/
4. 4Use proper ISO codes: en for English, ar for Arabic (or en-AE / ar-AE for UAE-specific)
5. 5Implement via HTML head, HTTP headers, or XML sitemap (pick one and be consistent)
6. 6Validate with Google Search Console International Targeting report

6. Site architecture and internal linking

Information architecture tells Google what is important and how everything relates. A flat, logical architecture compounds; a tangled architecture decays.

• Pillar pages (hubs) at the top of each topic cluster
• Cluster pages link up to the pillar with descriptive anchor text
• Maximum 3 clicks from homepage to any commercial page
• Descriptive URL structure - /macbook-repair-dubai not /service-7?id=42
• Breadcrumb navigation on every non-homepage page
• Footer links to high-priority pages
• No orphan pages (pages with no internal links pointing to them)

7. Security and accessibility

• HTTPS site-wide (no mixed content warnings)
• Modern TLS version (1.2 minimum, 1.3 preferred)
• Proper HSTS header for security signal
• Accessibility - WCAG 2.1 AA minimum, alt text on all images, proper heading hierarchy
• No intrusive interstitials on mobile (Google penalises these)

8. Tools you actually need

You do not need every SEO tool on the market. This is the minimum viable stack for technical SEO on a Dubai site.

• Google Search Console - free, foundational, non-negotiable
• Google Analytics 4 - free, for behaviour data
• Screaming Frog - desktop crawler, free up to 500 URLs
• PageSpeed Insights - free, for CWV per page
• Schema.org Validator + Google Rich Results Test - both free, both essential
• SEMrush or Ahrefs - paid, for keyword + competitor + backlink data

Common technical SEO traps in Dubai

Across hundreds of Dubai client audits we see the same technical issues repeatedly. If your site is more than two years old it almost certainly has at least three of these in play right now.

• WordPress sites with five overlapping SEO plugins fighting each other and producing duplicate schema
• Shopify sites with default canonical issues and unconfigured hreflang for UAE multi-region stores
• Custom React/Next.js sites without server-side rendering, leaving content invisible to Google's older crawlers
• Sites hosted on shared servers in India or Europe with 600-1500ms TTFB from UAE
• Sitemaps that include staging URLs, parameter URLs and 301-redirect-chained URLs
• Pages that 200 OK but display a JavaScript-rendered '404 not found' message - confusing both users and Google
• Trailing-slash inconsistency between internal links and canonical URLs
• Robots.txt blocking JS bundles needed for Google to render the page (a common React mistake)

Core Web Vitals - field data vs lab data

Two sources of Core Web Vitals data show up in your reports and they disagree more often than people realise. Lab data (from tools like Lighthouse and PageSpeed Insights) is a synthetic test - one machine simulating a load with controlled variables. Field data (from the Chrome User Experience Report, CrUX) is what real users actually experienced on real devices over the past 28 days. Google uses field data for ranking, not lab data.

This matters because a page can show 95+ in lab tests yet fail field metrics due to slower real devices, weaker network conditions or geographic latency. The reverse also happens - a page can show middling lab scores yet pass field metrics because real users hit it from optimal conditions. Always optimise against field data when both are available; use lab data only for pages too new to have collected field data yet.

How to prioritise technical SEO fixes

Not every issue deserves equal attention. Sort your audit findings into three tiers and work through them in order. Tier 1 issues block indexation or destroy ranking signals; Tier 2 reduce performance materially; Tier 3 are hygiene.

1. 1Tier 1 - fix in week 1 - blocked indexation, broken canonicals, missing hreflang on bilingual sites, schema validation errors
2. 2Tier 2 - fix in weeks 2-6 - Core Web Vitals failures, broken internal links, orphan pages, missing structured data on key templates
3. 3Tier 3 - fix on a rolling basis - image alt text improvements, breadcrumb refinements, minor schema additions, performance micro-optimisations

Frequently asked questions