Technical SEO Checklist for E‑commerce Sites: The Complete Guide

This technical SEO checklist for e-commerce is written for store owners, marketing managers and developers running online shops in Oman, the UAE and the wider GCC, whether the store is built on Shopify, WooCommerce, Magento or a custom Next.js front end. It covers the foundations search engines need before product copy, blog content or link building can pay off.

Online stores are harder to keep technically clean than brochure sites. Thousands of product URLs, filters, out-of-stock items, bilingual versions and frequent app or theme changes all create problems that pile up quietly. Work through the sections in order, because a crawling problem makes every later fix less valuable.

Crawlability and indexing: make sure Google can reach the right pages

Start in Google Search Console. The Page indexing report shows which URLs are indexed and why others are excluded. Statuses such as Crawled but not indexed, Discovered but not indexed, and Duplicate without user-selected canonical each point to a different underlying issue, so read them before changing anything.

• Check robots.txt is not blocking collection, category or product folders, or the CSS and JavaScript files needed to render pages.
• Search the templates for leftover noindex tags, especially after a redesign, migration or staging-to-live launch.
• Make sure the XML sitemap lists only canonical URLs that return a 200 status, and submit it in Search Console.
• Keep cart, checkout, account and internal search result pages out of the index; they add crawl load and no search value.
• Return a proper 404 or 410 for products that are permanently gone, or redirect them to the closest relevant product or category.

Rendering: check JavaScript-heavy and headless stores

If your store is a client-side rendered React app with no server-side rendering or pre-rendering, search engines may struggle to index it properly. Google can render JavaScript, but it happens in a later step and is less predictable, and many other crawlers, including some AI search tools, do not execute JavaScript at all.

For headless builds, use server-side rendering or static generation, which frameworks such as Next.js support well. Product names, prices, descriptions and internal links should appear in the initial HTML response. Test with the URL Inspection tool in Search Console, compare the rendered HTML with what you see in the browser, and confirm that navigation links are real anchor links with an href, not click handlers.

Site architecture, URL structure and internal linking

A shallow, logical hierarchy helps both crawlers and shoppers: home, category, subcategory, product. Keep URLs lowercase, readable and hyphenated, and avoid session IDs or random strings. Most importantly, decide on one URL per product. Shopify, for example, can expose the same product under a collection path and a plain product path, so internal links should consistently point to the canonical version.

Faceted navigation and filters

Filters for size, colour, brand and price can generate a near-endless number of URL combinations. Decide which filtered views have genuine search demand, such as a specific colour of abaya or a brand plus category, and turn those into indexable landing pages with their own titles and copy. Leave the remaining combinations canonicalised to the parent category or out of the crawl path. Avoid blocking a URL in robots.txt while also relying on its canonical tag, because Google cannot read a canonical on a page it is not allowed to crawl.

Pagination and breadcrumbs

Google no longer uses rel prev and next as an indexing signal, so each paginated category page should be crawlable and carry its own self-referencing canonical rather than pointing to page one. Breadcrumbs add useful internal links back up the hierarchy and give you a clean source for breadcrumb structured data.

Canonical tags and duplicate content control

Duplicate content on stores rarely comes from copying. It comes from variant and sort parameters, UTM tracking links, http and https or www and non-www versions, trailing slash inconsistencies, and the same product sitting in several collections. Manufacturer descriptions reused across your site, Amazon and Noon listings and other retailers add another layer of near-duplication.

• Every indexable page should carry one self-referencing canonical tag with an absolute URL.
• Canonicals must point to a live, indexable page, never to a redirect, a 404 or a noindexed URL.
• Canonical URLs, sitemap URLs and internal links should all agree with each other.
• Check that apps or plugins are not injecting a second, conflicting canonical tag.
• Rewrite manufacturer descriptions for your highest-value products so your site offers something the marketplaces do not.

For variants, one product URL with a variant selector is usually the right approach. Separate variant URLs only make sense when a variant has its own search demand, for example a distinct model or material that people search by name.

Core Web Vitals and page speed for online stores

Core Web Vitals are three field metrics measured from real Chrome users. Largest Contentful Paint measures loading, and Google treats 2.5 seconds or less as good. Interaction to Next Paint, which replaced First Input Delay in March 2024, measures how quickly the page responds to taps and clicks, with 200 milliseconds or less rated good. Cumulative Layout Shift measures visual stability, with 0.1 or less rated good. The Core Web Vitals report in Search Console shows field data; Lighthouse and PageSpeed Insights lab scores are useful for debugging but are not the same thing.

Common causes on e‑commerce sites

• Oversized hero and product images, not served in modern formats such as WebP or AVIF, or the main image lazy-loaded when it should load first.
• Too many third-party scripts: review widgets, live chat, WhatsApp buttons, heatmaps and several ad pixels competing for the main thread, which hurts INP.
• Layout shifts from late-loading promo bars, cookie banners, web fonts and images without set width and height.
• Slow server response or hosting far from GCC shoppers, without a CDN that has edge locations in or near the Middle East.

Test on a mid-range Android phone over a mobile data connection, not only on a fast office laptop, since a large share of GCC shopping happens on mobile.

Structured data for products, reviews and breadcrumbs

Structured data helps search engines understand product pages and can make them eligible for richer results. Use Product markup with an Offer that includes price, priceCurrency in OMR, AED or SAR as appropriate, and availability. Add aggregateRating and Review only when those reviews are genuinely visible on the page. Add BreadcrumbList on category and product pages, and Organization markup on the homepage. Shipping and return policy details can also be marked up, which supports merchant listing features.

Validate with the Rich Results Test and monitor the enhancement reports in Search Console. Keep structured data in sync with the visible page: a price or stock status in the markup that differs from what shoppers see can cause warnings and disapprovals in Google Merchant Center. Note that FAQ rich results are now shown mainly for well-known authoritative sites, so do not expect them on store pages.

Hreflang and bilingual Arabic and English e‑commerce stores

Many GCC stores run Arabic and English versions, and some also have separate country versions for Oman, the UAE or Saudi Arabia. Hreflang annotations tell Google which version to show to which audience and prevent the language versions from competing with each other.

• Use language codes such as ar and en if one version serves the whole region, or language-region codes such as ar-OM, en-OM, ar-AE and en-AE if prices, delivery or stock differ by country.
• Each page must list itself and all its alternates, and every alternate must link back; one-way hreflang is ignored.
• Add an x-default entry for the version shown to users who match none of your targets.
• Point hreflang only at canonical, indexable URLs that return a 200 status.
• Set the correct lang and dir attributes on Arabic pages so right-to-left layout and language are declared in the code.

Avoid automatically redirecting visitors by IP address or browser language. Googlebot mostly crawls from the United States and may never see your Arabic or country-specific pages if they are hidden behind redirects. A visible language and country switcher is safer for both users and crawlers.

Technical SEO checklist for e‑commerce: step-by-step action plan

1. Verify the domain in Google Search Console and Bing Webmaster Tools, and submit a clean XML sitemap.
2. Crawl the full site and export indexability, status codes, canonicals and duplicate titles.
3. Fix robots.txt rules, stray noindex tags and broken internal links, and redirect retired products sensibly.
4. Confirm key content renders in the initial HTML, especially on headless or React builds.
5. Choose one canonical URL per product and align canonicals, sitemaps and internal links.
6. Decide which filter combinations deserve indexable landing pages and contain the rest.
7. Review Core Web Vitals field data, then tackle images, third-party scripts and layout shifts.
8. Add and validate Product, Offer, BreadcrumbList and Organization structured data.
9. Implement reciprocal hreflang for Arabic, English and any country versions, with an x-default.
10. Re-crawl monthly and after every theme, app or platform change, and log what changed.

How EcomConvey can help with technical SEO

EcomConvey's SEO and web development teams work on the technical side of online stores for brands in Oman and the UAE. That includes technical audits, Shopify and Next.js development, Core Web Vitals work, structured data and bilingual Arabic and English setups.

If you would like a second pair of eyes on your store, we can review your Search Console data and crawl results with you and outline the fixes we would prioritise and why.

Frequently asked questions

Want expert help with this? Explore our SEO Services service or book a free consultation with the EcomConvey team. Related reading: How Long Does SEO Take to Work? A Realistic, Honest Answer.