Technical SEO for Shopify Stores in the UAE: A Practical Checklist

Munavar Sahad — Sun, 15 Nov 2026 18:47:26 +0000

Shopify gives you a usable storefront quickly. It does not give you a finished technical SEO setup, especially if you sell in the UAE, publish in English and Arabic, and run a catalog with many collection and filter URLs.

I am Munavar Sahad, a Dubai-based digital marketer and eCommerce specialist. Over 7+ years I have worked across 6 brands in 5 industries, connecting Shopify development, SEO, Google Ads, CRO, and marketing automation for UAE brands. I keep the longer brief and service pages on my site. This checklist is what I use when I inspect a Shopify theme, not a promise about rankings.

1. Structured data: ship JSON-LD you can defend

Most Shopify themes output some Product JSON-LD. Many graphs are incomplete, duplicated by apps, or detached from the visible page. Inspect the live source for application/ld+json. If an app and the theme both print Product schema, keep one.

A product page should describe a Product with an Offer, and include name, image, description, sku or gtin when you have one, price, priceCurrency, and availability. For UAE stores, priceCurrency should be AED when that is the price on the page, and it should match tax-inclusive pricing if that is what you show.

Google also expects return and shipping information on many product results. If the theme does not output hasMerchantReturnPolicy and shippingDetails, add them in Liquid from the policy you already publish. Do not invent a return window in schema that the store does not offer.

A compact theme pattern:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": {{ product.title | json }},
  "description": {{ product.description | strip_html | truncate: 5000 | json }},
  "image": {{ product.featured_image | image_url: width: 1200 | prepend: "https:" | json }},
  "sku": {{ product.selected_or_first_available_variant.sku | json }},
  "brand": { "@type": "Brand", "name": {{ product.vendor | json }} },
  "offers": {
    "@type": "Offer",
    "url": {{ canonical_url | json }},
    "priceCurrency": "AED",
    "price": {{ product.selected_or_first_available_variant.price | divided_by: 100.0 | json }},
    "availability": "https://schema.org/{% if product.available %}InStock{% else %}OutOfStock{% endif %}",
    "itemCondition": "https://schema.org/NewCondition"
  }
}
</script>

Adjust the price math to your money format, and add GTIN, return, and shipping objects when the data is real.

Beyond products, I add Organization (or LocalBusiness when it fits) with the legal name, logo, URL, and sameAs links; WebSite with inLanguage; BreadcrumbList that matches the visible trail; and FAQPage only when those questions appear in the HTML. Keep the organization name and address consistent. Validate with Google's Rich Results Test, and fix any price mismatch between HTML and JSON-LD.

2. Hreflang for English and Arabic

UAE shoppers move between English and Arabic. If both languages exist, each URL needs a clear language and region signal, and the two versions must point at each other. Use en-AE and ar-AE for content written for the United Arab Emirates, and add x-default for the fallback, usually the primary English storefront. Every language version should list every other version, including itself.

Shopify Markets and Translate and Adapt can emit hreflang when markets and languages are configured correctly. Do not assume they are. View source on an English product and the Arabic equivalent and confirm the tags are present, reciprocal, and not pointing at a generic /en or /ar that 404s.

If you need to output them in the theme:

<link rel="alternate" hreflang="en-AE" href="{{ canonical_url }}" />
<link rel="alternate" hreflang="ar-AE" href="{{ alternate_ar_url }}" />
<link rel="alternate" hreflang="x-default" href="{{ canonical_url }}" />

Build alternate_ar_url from Market or locale objects, not from a brittle string replace.

Arabic pages must be real translations; if a translation is incomplete, do not advertise it with hreflang. Set dir="rtl" and lang="ar-AE" on the Arabic document. Currency, shipping copy, and policy pages should follow the language of the URL. After deploy, spot-check both languages with URL Inspection in Google Search Console.

3. Core Web Vitals on a real Shopify theme

I measure field data in Search Console and CrUX, then use PageSpeed Insights and a Shopify theme profile to find the cause. Lab scores are useful for debugging, not a substitute for field data. Google's published thresholds are the bar I work to: LCP at or under 2.5 seconds, INP at or under 200 milliseconds, and CLS at or under 0.1. A green lab score is not a ranking claim.

On Shopify, the usual LCP element is the product or hero image. Preload that image only, not every slide. Serve a correctly sized file with image_url, width, height, and a srcset. Do not lazy-load the LCP image, and do not let Liquid request a 2000px file on a phone.

INP is usually app and theme JavaScript. Audit app embeds and remove anything that template does not need. Defer reviews, chat, upsells, and pixels where you can, and avoid binding heavy listeners to every product card.

CLS often comes from banners, injected widgets, fonts, or images without dimensions. Reserve space for those slots, and load fonts so Arabic and English faces do not swap late.

If you are rebuilding the theme rather than patching one, I have written up how I approach custom Shopify development in Dubai, including Liquid and CSS that stays safe to update.

4. Canonicals and duplicate collection URLs

Shopify is good at creating URLs and average at telling search engines which one is the original. Watch for the same product on /products/handle, a variant query (?variant=), and collection paths such as /collections/sale/products/handle; /collections/all overlapping with the catalog; tag URLs such as /collections/shoes/black next to filter URLs such as /collections/shoes?filter.p.m.custom.color=black; sort and pagination parameters; and HTTP/HTTPS, www and apex, or market prefixes resolving without a single canonical host.

Shopify's canonical_url object is the default I trust for most templates. Product pages should canonicalize to the product URL, not a collection-prefixed path. Variant URLs should generally canonicalize to the product URL.

For collections, index clean URLs you want in the sitemap, such as /collections/shoes. Canonicalize or noindex faceted and sort-parameter URLs back to the clean collection, unless a filtered page is a deliberate landing page with unique copy. Give paginated pages a self-referencing canonical. Shopify search (/search?q=), vendor and type collections, and leftover theme pages should usually be noindex, follow and kept out of the sitemap.

Confirm the HTML canonical, the sitemap URL, and the URL that Search Console indexes are the same. When they disagree, Google may pick a URL you do not sell from.

5. Sitemaps and Search Console indexing

Shopify serves a sitemap index at /sitemap.xml, which points to product, collection, page, and blog sitemaps. The index should list only URLs you want crawled, and those URLs should return 200 with a consistent canonical.

Open /sitemap.xml while logged out. Confirm public products, collections, and policy pages are there, and that noindex pages, search, checkout, account, and filtered duplicates are not. If you intend to index both languages, each Arabic and English URL should appear as its own entry.

In robots.txt, allow the storefront and point to the sitemap. Do not disallow /collections/ or /products/ unless you have a specific reason. In Google Search Console, add the exact host you canonicalize to, verify it, and submit the sitemap. Use the Page indexing report, especially "Crawled - currently not indexed", "Duplicate, Google chose different canonical than user", "Excluded by noindex", and "Soft 404". After a theme or market change, inspect a sample of Arabic and English URLs. Request indexing only for important new or fixed URLs, not for every SKU.

Technical SEO is not a one-time theme edit. Indexing and structured data drift as you add apps, markets, and collections. That is why I treat managed SEO for Shopify stores as an ongoing check, not a launch-day task. If you run Google Ads as well, keep the landing URL identical to the canonical URL.

6. AEO and GEO: make the store answerable

AEO (answer engine optimization) and GEO (generative engine optimization) are not a new set of meta tags. They describe whether a product, policy, or brand fact can be extracted cleanly by Google's AI features, ChatGPT, Perplexity, and similar systems.

Treat this as an extension of technical SEO. Put a direct answer near the top of important pages: a shipping page should state where you ship, how long delivery takes in the UAE, and what it costs, before the marketing copy. Keep the organization name, domain, and contact details consistent on the site, in schema, and on public profiles. Use FAQ schema only when the same text is visible. Write unique product descriptions that state materials, sizes, and care. Expose returns, payment methods (including cash on delivery if you offer it), and delivery areas in HTML, not only in a PDF or chat widget.

None of this guarantees a citation in an answer engine. It does make the store easier to quote accurately when a system decides to use it.

Wrap-up

Before you call a UAE Shopify storefront done, confirm one honest product JSON-LD graph per product URL, reciprocal en-AE and ar-AE hreflang, field Core Web Vitals fixed in the theme, canonicals that collapse duplicates, a clean sitemap in Search Console, and visible answers for shipping, returns, and brand facts.

If you want a quick first pass on a live URL, you can run my free SEO audit. It returns PageSpeed, SEO, accessibility, security, and Core Web Vitals so you can see what to fix before you touch the theme.

DEV Community: Munavar Sahad