Ecommerce websites present a unique set of technical SEO challenges that content sites simply do not face. Product catalogues with thousands of SKUs, faceted navigation generating millions of URL combinations, duplicate content across product variants, and the constant tension between site speed and rich product pages — these are problems that require deliberate, informed solutions.

Getting technical SEO right on an ecommerce site is not optional. It is the difference between search engines efficiently crawling and indexing your most valuable pages, and them wasting crawl budget on filtered junk pages while your money-making product and category pages languish undiscovered.

This guide covers the technical foundations that matter most for ecommerce, prioritised by impact.

Site Architecture: Get This Wrong and Everything Else Suffers

Your site architecture determines how link equity flows through your site, how easily search engines discover your pages, and how intuitive your site is for users. For ecommerce, this is the single most important technical decision you will make.

The Ideal Ecommerce Hierarchy

The cleanest ecommerce architecture follows a shallow hierarchy:

Homepage → Category → Subcategory → Product

Every product page should be reachable within three clicks from the homepage. Every category page should be reachable within two. This is not just good for users — it ensures search engines can discover your full catalogue efficiently.

URL Structure

URLs should reflect your hierarchy clearly:

/mens/trainers/nike-air-max-90-black
/womens/dresses/midi-wrap-dress-navy

Avoid deep nesting, arbitrary ID numbers, and session parameters in URLs. Keep URLs readable, descriptive, and consistent. If your platform generates URLs like /product.php?id=4582&cat=12&variant=blue, you have work to do.

Internal Linking Strategy

Category pages should link to their child products. Products should link back to their parent category. Related products and “customers also bought” sections create lateral links that distribute authority and help search engines understand relationships between pages.

The most common mistake we see on ecommerce sites is orphaned product pages — products that exist in the database but have no internal links pointing to them. If search engines cannot find a page through your internal link structure, it effectively does not exist.

Core Web Vitals: Speed Is Revenue

Google’s Core Web Vitals — Largest Contentful Paint (LCP), Interaction to Next Paint (INP), and Cumulative Layout Shift (CLS) — are ranking factors. But beyond rankings, site speed directly impacts conversion rates. Research consistently shows that every additional second of load time reduces conversions by 7–12% on ecommerce sites.

Largest Contentful Paint (LCP)

LCP measures how quickly the main content of a page becomes visible. For ecommerce, this is typically the hero product image or the main category banner. Target: under 2.5 seconds.

Common ecommerce LCP killers:

  • Unoptimised product images. Serve images in WebP format, use responsive srcset attributes, and implement lazy loading for below-the-fold images. Your hero image should be eagerly loaded with a fetchpriority="high" attribute.
  • Render-blocking JavaScript. Third-party scripts for analytics, chat widgets, personalisation engines, and A/B testing tools often block rendering. Audit your script loading and defer everything that is not critical for initial page render.
  • Slow server response times. If your TTFB (Time to First Byte) exceeds 600ms, no amount of front-end optimisation will fix your LCP. Investigate your hosting, database queries, and server-side caching.

Interaction to Next Paint (INP)

INP measures responsiveness — how quickly your site responds to user interactions like clicks and taps. For ecommerce, this matters on product listing pages where users filter, sort, and paginate, and on product pages where they select variants and add to cart. Target: under 200ms.

Fix INP issues by:

  • Minimising main thread JavaScript execution
  • Breaking long tasks into smaller chunks
  • Using web workers for heavy computation
  • Reducing the impact of third-party scripts

Cumulative Layout Shift (CLS)

CLS measures visual stability. On ecommerce sites, layout shifts typically occur when images load without defined dimensions, when ads or promotional banners inject into the page, or when fonts swap. Target: under 0.1.

Always set explicit width and height attributes on images, reserve space for dynamic content, and use font-display: swap with appropriately sized fallback fonts.

Faceted Navigation: The Crawl Budget Killer

Faceted navigation — filters for size, colour, price, brand, material, and other attributes — is essential for ecommerce usability. It is also the single largest source of crawl waste and duplicate content on most ecommerce sites.

A modest product catalogue with 10 filter categories and 5 options each can generate millions of unique URL combinations. If search engines attempt to crawl all of these, your crawl budget is consumed by low-value filtered pages while your important category and product pages receive less attention.

The Solution: Controlled Indexation

Not all faceted URLs deserve to be indexed. Your approach should be:

  1. Index valuable faceted pages that target real search queries. If people search for “black leather boots size 6,” and you have a filtered URL that serves exactly that, index it.
  2. Canonicalise low-value combinations back to the parent category page. A filter for “price: £50–£100” is useful for users but does not represent a meaningful search query.
  3. Use noindex on multi-filter combinations. When users apply three or more filters simultaneously, the resulting page is almost never worth indexing.
  4. Block crawling of parameter-heavy URLs in robots.txt or using the URL Parameters tool in Google Search Console. This preserves crawl budget for your valuable pages.

Implementation Approach

The cleanest implementation uses a combination of:

  • Canonical tags pointing filtered pages to the most relevant indexable version
  • noindex, follow on filter combinations you want crawled (for link discovery) but not indexed
  • Robots.txt disallow rules for filter patterns that generate infinite crawl traps
  • Clean, static URLs for the faceted pages you do want indexed (e.g., /mens/trainers/black/ rather than /mens/trainers/?colour=black)

Canonical Tags: Preventing Duplicate Content

Ecommerce sites generate duplicate content in ways that content sites rarely encounter:

  • Product variants (same product in different colours or sizes) often create separate URLs with nearly identical content
  • Sorting and pagination create multiple URLs for the same content in different orders
  • Cross-category listing means the same product appears under multiple category paths
  • HTTP/HTTPS and www/non-www variations double every page if not properly redirected

Canonical Tag Best Practices

Every page on your site should have a self-referencing canonical tag unless it is a duplicate that should point to a canonical source. Be explicit — do not rely on search engines to figure out which version is canonical.

For product variants, decide whether each variant deserves its own page (if the variants have meaningfully different search intent) or whether they should all canonical to the parent product page (if the differences are minor).

For pagination, use rel="canonical" pointing to the first page of the series, and ensure your paginated pages are accessible through internal links so search engines can discover all products.

Structured Data: Rich Results for Products

Structured data markup helps search engines understand your product pages and can qualify you for rich results — enhanced search listings showing price, availability, reviews, and images directly in search results.

Essential Ecommerce Schema Types

Product schema is non-negotiable. Every product page should include:

{
  "@type": "Product",
  "name": "Product Name",
  "image": "https://example.com/image.webp",
  "description": "Product description",
  "brand": { "@type": "Brand", "name": "Brand Name" },
  "offers": {
    "@type": "Offer",
    "price": "99.99",
    "priceCurrency": "GBP",
    "availability": "https://schema.org/InStock",
    "url": "https://example.com/product"
  }
}

AggregateRating if you have reviews. Only include this if you have genuine reviews — fabricating review markup violates Google’s guidelines and risks a manual action.

BreadcrumbList to reinforce your site hierarchy in search results and help search engines understand your category structure.

FAQPage on category pages if you include FAQ sections. This can earn additional SERP real estate through FAQ rich results.

Validation

Use Google’s Rich Results Test and Schema Markup Validator to check your implementation. Errors in structured data can prevent rich results from appearing and, in extreme cases, result in manual penalties.

CDN and Caching: Global Performance

Ecommerce sites serve users across multiple regions and load heavy assets — product images, videos, JavaScript bundles. A Content Delivery Network is essential for consistent global performance.

CDN Configuration for Ecommerce

  • Cache static assets aggressively. Product images, CSS, JavaScript, and fonts should be served from CDN edge nodes with long cache TTLs (at least 30 days).
  • Use cache-busting for deployments. Include content hashes in filenames so updated assets bypass existing caches automatically.
  • Configure stale-while-revalidate. This serves cached content to users while fetching fresh content in the background, eliminating cache miss latency.
  • Set up image transformation at the edge. Modern CDNs can resize, compress, and format-convert images on the fly, serving optimally sized WebP images without maintaining multiple versions.

Server-Side Caching

Beyond CDN, implement server-side caching for dynamic pages:

  • Full-page caching for category and product pages (with cache invalidation when products update)
  • Database query caching for frequently accessed product data
  • Object caching for session-independent computed data like navigation menus and filter counts

Mobile-First Indexing: Your Mobile Site Is Your Site

Google uses the mobile version of your site for indexing and ranking. For ecommerce, this means your mobile experience is not a secondary concern — it is the primary one.

Common Mobile Ecommerce Failures

  • Hidden content on mobile. If product descriptions, specifications, or reviews are collapsed behind tabs or accordions on mobile, ensure the content is still present in the HTML. Content hidden with CSS display: none may be devalued.
  • Slow mobile load times. Mobile users are typically on slower connections. Aggressive optimisation — smaller images, fewer scripts, reduced DOM complexity — is essential.
  • Unusable navigation on mobile. If your category structure requires three taps through tiny menus to reach a product, both users and search engines struggle.
  • Missing structured data on mobile. Ensure your schema markup is present in the mobile version, not just desktop.

Mobile Performance Checklist

  • Touch targets are at least 48×48 pixels
  • Text is readable without zooming (minimum 16px body text)
  • No horizontal scrolling required
  • Forms are optimised for mobile input (appropriate input types, autofill attributes)
  • Images are responsive and serve appropriate sizes for mobile viewports
  • Critical CSS is inlined, non-critical CSS is deferred

XML Sitemaps for Large Catalogues

For ecommerce sites with thousands of products, your XML sitemap strategy matters. Search engines use sitemaps as a discovery mechanism, and a well-structured sitemap helps them find and prioritise your most important pages.

Sitemap Best Practices

  • Split sitemaps by type. Separate sitemaps for products, categories, and informational content. This makes it easier to monitor indexation by page type.
  • Only include indexable pages. Do not include noindexed pages, redirected URLs, or paginated filter pages in your sitemaps.
  • Update lastmod dates accurately. Only change the lastmod date when page content genuinely changes. Search engines learn to trust (or ignore) your lastmod signals based on accuracy.
  • Keep individual sitemaps under 50,000 URLs. Use a sitemap index file to organise multiple sitemaps for large catalogues.
  • Submit sitemaps through Google Search Console and reference them in your robots.txt file.

Bringing It All Together

Technical SEO for ecommerce is not a one-off project. It is an ongoing discipline that requires attention as your catalogue grows, your platform evolves, and search engine requirements change. The priorities outlined here — architecture, performance, faceted navigation, canonicalisation, structured data, CDN configuration, mobile optimisation, and sitemap management — form the foundation that everything else builds upon.

If your ecommerce site has technical debt that is suppressing organic performance, addressing these fundamentals will unlock visibility that no amount of content or link building can achieve on a broken foundation.

Ready to audit and improve the technical SEO on your ecommerce site? Book a discovery call to discuss your technical SEO priorities with our team.