Technical SEO for eCommerce: Fix the
Issues That Limit Rankings and Revenue

You've written product descriptions. You've targeted keywords. You've published blog content. But your rankings are stuck  and your organic revenue hasn't moved.

Here's the uncomfortable truth: your content can't rank if your technical foundation is broken.

Most eCommerce store owners pour energy into the visible parts of SEO:  keywords, copy, backlinks  and completely overlook what's happening under the hood. Technical SEO determines whether Google can even find your pages, understand them, and trust them enough to rank them.

This guide breaks down every major technical SEO issue affecting eCommerce stores, what causes each problem, what it costs you if you ignore it, and exactly how to fix it.

 

What Is Technical SEO for eCommerce?

Technical SEO is the process of optimising your website's infrastructure so search engines can crawl, index, and rank your pages effectively.

For eCommerce, this covers:

• How search engine bots navigate your site

• Which pages get indexed and which get ignored

• How fast your pages load on mobile and desktop

• Whether your product data is structured in a way Google understands

• How efficiently Google's crawl budget is spent across your catalogue

Unlike content SEO (which focuses on what's on the page) or off-page SEO (backlinks and authority), technical SEO focuses on how the site is built and how it behaves.

Why eCommerce is more complex than other websites: A typical business website has 20–50 pages. A mid-sized eCommerce store can have 10,000–500,000 URLs once you account for product pages, category pages, filter combinations, pagination, and URL variants. Each of these multiplies the risk of technical problems.

 

Why Technical SEO Matters for Online Stores

Technical issues don't just affect rankings,  they directly affect revenue.

According to a 2023 study by Ahrefs, over 90% of web pages receive zero organic traffic  and a significant portion of that is due to indexation and crawlability issues, not poor content. For eCommerce, where each product page represents a revenue opportunity, this gap is costly.

Google has also confirmed that page speed is a direct ranking factor, and research from Google's own data shows that the probability of a user bouncing increases 32% when page load time goes from 1 second to 3 seconds  and by 90% when it reaches 5 seconds.

The bottom line: technical SEO isn't a background task. It's revenue infrastructure.

 

Common Technical SEO Issues in eCommerce

Before we go deep, here's a snapshot of the most frequently found issues across eCommerce sites:

• Duplicate product pages created by URL parameters (filters, colour, size, sort)

• Faceted navigation generating thousands of near-identical low-value URLs

• Crawl budget consumed by cart, wishlist, and login pages

• Missing or misconfigured canonical tags

• Thin category pages with no unique content

• No product schema or incorrect structured data markup

• Unoptimised images slowing down product and category pages

• XML sitemaps containing 404s, redirect URLs, or noindex pages

• Orphaned product pages with no internal links pointing to them

• Incorrect use of noindex/nofollow on key pages

Now let's fix each one.

 

1. Duplicate Content in eCommerce Sites

Why It Happens

Duplicate content is the most widespread and underestimated technical issue in eCommerce. It occurs when the same (or nearly identical) content appears at multiple URLs  and eCommerce platforms create these situations almost automatically.

The most common causes:

• URL parameters: /products/shoes?colour=red and /products/shoes?sort=price render the same page with different URLs

• Product variants: The same shoe available in three sizes creates three pages with 95% identical content

• Faceted navigation: Filter combinations like /dresses/red/size-12/under-$100 can generate millions of unique URLs

• Session IDs: Some platforms append session tokens to URLs, creating infinite variations

• WWW vs. non-WWW: www.yourstore.com and yourstore.com are treated as different URLs without a redirect

• HTTP vs. HTTPS: Both versions can be indexed without proper enforcement

• Trailing slashes: /products/shoes and /products/shoes/ are two different URLs to Google

Platform-specific note (Shopify): Shopify automatically creates duplicate product URLs when products are accessed via a collection — /collections/shoes/products/nike-air and /products/nike-air both exist and both contain the same content. Shopify adds a canonical tag pointing to the root /products/ URL, which handles the duplicate content penalty  but it does not fix the crawl budget waste. Googlebot still crawls both paths. 

To address this more completely, edit your Shopify theme's product card templates (e.g., product-card.liquid or product-grid-item.liquid) to ensure all internal links always point to the root /products/product-name URL instead of the collection-aware path. This prevents Googlebot from discovering and repeatedly crawling the longer duplicate URLs through your site's own internal link structure.

Platform-specific note (WooCommerce): WooCommerce creates duplicate pages for products accessible through multiple categories, plus pagination variants with identical meta titles.

What Happens If You Ignore It?

• Google splits ranking power (PageRank) between duplicate versions, weakening all of them

• The wrong version of your page may be indexed, often a parameter URL rather than your clean URL

• You compete against yourself in search results

• Crawl budget is wasted on pages that add no value

• Rankings become unstable and fluctuate without explanation

How to Fix It

Step 1 — Implement canonical tags correctly Add <link rel="canonical" href="https://yourstore.com/products/nike-air" /> to all duplicate or near-duplicate pages. This tells Google which URL is the preferred version without blocking access to the others.

Step 2 — Control URL parameters via robots.txt Use the Disallow: directive in robots.txt for parameter URLs that add no SEO value. Note: Google retired the URL Parameters tool in Google Search Console in April 2022,  it no longer exists. For parameter management today, rely on robots.txt Disallow rules, canonical tags, and where possible, use AJAX or JavaScript-based filtering so that filter selections don't generate new URLs at all (a common implementation in headless and custom-built stores).

Step 3 — Consolidate thin product variants Either:

• Use canonical tags on all variant pages pointing back to the main product

• Or noindex variant pages if they provide no unique search value

Step 4 — Enforce a single URL format Use 301 redirects to enforce HTTPS, your preferred www preference, and consistent trailing slash usage.

Step 5 — Audit with tools Run Screaming Frog or Sitebulb to identify:

• Pages with duplicate title tags

• Pages with duplicate meta descriptions

• Pages with very high content similarity scores

 

2. Indexation Problems in Large Catalogues

Why It Happens

Getting your pages indexed sounds simple but for large eCommerce catalogues, it's one of the biggest SEO bottlenecks in practice.

Google doesn't automatically index every page on your site. It chooses which pages to index based on crawlability, content quality, and crawl budget. In large stores, hundreds or thousands of product pages can end up in the "Discovered — currently not indexed" limbo in Google Search Console.

Common causes:

• Noindex tags mistakenly applied to product or category pages (often left over from a staging environment)

• Robots.txt blocking key directories (/products/, /collections/)

• Thin pages with very little unique content (common with generic product descriptions from supplier feeds)

• Pages not included in the XML sitemap, or sitemap hasn't been updated since products were added

• Orphaned pages:  products with no internal links pointing to them

• Pages that are indexed but not crawled frequently enough due to crawl budget limits

The site: search test: Type site:yourdomain.com into Google and compare the result count to your actual product count. If Google shows 800 pages and you have 5,000 products, you have a serious indexation gap.

What Happens If You Ignore It?

• Products that should rank for high-intent searches ("buy [product] Australia") simply don't appear in Google

• Revenue from long-tail, product-specific searches is permanently lost

• New product launches fail to gain organic traction before seasonal buying windows close

• You rely entirely on paid ads to surface products that could be found organically

How to Fix It

Step 1 — Audit your XML sitemap

Your sitemap should:

• Include all indexable product and category pages

• Exclude 404s, redirect URLs, and noindex pages

• Be submitted to Google Search Console

• Update automatically when new products are added (most platforms support this natively)

Step 2 — Check for accidental noindex tags

Inspect the <head> section of key pages for:

<meta name="robots" content="noindex">

 

Also check for X-Robots-Tag: noindex in HTTP response headers, which can be added by apps or server settings.

Step 3 — Fix robots.txt

Navigate to yourstore.com/robots.txt and confirm that key directories like /products/ and /collections/ (Shopify) are not accidentally blocked.

Step 4 — Build internal links to all products

Every product needs at least one internal link from an indexed page. Improve this by:

• Adding new products to relevant category pages immediately

• Featuring new arrivals on the homepage or blog posts

• Using "Related Products" sections that are crawlable (not loaded via JavaScript after page render)

Pro tip — Implement Breadcrumb Schema: Breadcrumbs are the unsung connector in eCommerce technical SEO. Implementing BreadcrumbList schema (e.g., Home > Footwear > Running Shoes > Nike Air Max 90) does two things simultaneously: it reinforces your internal linking hierarchy for Googlebot, and it makes that hierarchy visible in your search listings as clickable breadcrumb paths. This helps Google correctly map the relationship between your categories and products,  which directly supports indexation of deeper product pages. Most platforms support breadcrumbs natively; the key is ensuring the schema markup reflects your actual page hierarchy accurately.

Step 5 — Monitor in Google Search Console

Check the Coverage report weekly. Pay attention to:

• Discovered — currently not indexed (Google knows the page exists but hasn't prioritised it)

• Crawled — currently not indexed (Google crawled it but chose not to index it, usually a content quality signal)

 

3. Crawl Budget Issues for eCommerce

Why It Happens

Crawl budget is the number of pages Googlebot will crawl on your site within a given timeframe. Google allocates it based on your site's authority, server speed, and perceived importance of your pages.

The problem for eCommerce stores is that the crawl budget is finite and if Google wastes it on low-value pages, your high-value product and category pages may not get crawled (and therefore not indexed or updated) in time.

What consumes crawl budget unnecessarily:

• Faceted navigation URLs (e.g., /dresses?colour=red&size=12&brand=zara)

• Paginated pages beyond the first few (e.g., /category/page/47)

• Session IDs and tracking parameters in URLs

• Cart, checkout, login, and account pages

• Search results pages (/search?q=red+dress)

• Redirect chains (pages that redirect to pages that redirect)

• Soft 404 pages (pages that show "product not found" but return a 200 status code)

A mid-to-large eCommerce site can easily generate hundreds of thousands of these low-value URLs through faceted navigation alone. If your total URL count is 500,000 but Google only crawls 10,000 per day, your actual product pages may wait weeks to be re-crawled after an update.

What Happens If You Ignore It?

• Price changes, stock updates, and new products take weeks to be reflected in Google

• Important category and product pages are crawled infrequently, causing ranking volatility

• You lose competitive ranking ground to stores with cleaner crawl architectures

• Google's assessment of your site's quality degrades over time

How to Fix It

Step 1 — Block low-value URLs via robots.txt

Add Disallow: rules for:

/cart/

/checkout/

/account/

/login/

/search/

/wishlist/

 

Step 2 — Noindex or block faceted navigation URLs

For filter combinations that create infinite URL variants:

• Use rel="canonical" pointing back to the unfiltered category page

• Or use noindex, follow on filter pages if they have unique value but shouldn't be indexed

• Or block crawling via robots.txt if they add no SEO value at all

Step 3 — Fix redirect chains

A → B → C should become A → C directly. Every redirect in a chain wastes crawl budget. Audit redirect chains with Screaming Frog and consolidate them.

Step 4 — Fix soft 404s

Pages for out-of-stock or discontinued products that show content but return a 200 status code confuse Googlebot. Options:

• Return a 404 or 410 status if the product is permanently discontinued

• 301 redirect to a related product or category if the product has been replaced

• Keep the page live with updated messaging if the product may return (e.g., "Back soon" with related recommendations)

Pro tip — Seasonal and returning products: For products that go out of stock temporarily (e.g., seasonal ranges, limited editions that will restock), do not 404 or redirect the page. Instead, keep it live and update your Product schema to mark availability as https://schema.org/OutOfStock. This preserves any ranking you've built for that product page over time,  so when the product returns, you don't need to start building rankings from zero. Pair this with an email capture ("Notify me when back in stock") to also recover potential revenue from returning visitors.

Step 5 — Improve server response time

Googlebot crawls more pages on faster servers. Ensure your server response time (TTFB) is under 200ms. Use a CDN and server-side caching to improve this.

 

4. Page Speed Impact on SEO and Conversions

Why It Matters More Than Most Stores Realise

Page speed is one of the rare technical factors that directly affects both search rankings and revenue at the same time.

Google has used page speed as a ranking signal for desktop since 2010 and for mobile since 2018. In 2021, Core Web Vitals became a confirmed ranking factor,  a set of speed and experience metrics that Google measures for every page.

The three Core Web Vitals:

The revenue case for speed:

• Google data shows bounce probability increases 32% when load time goes from 1s to 3s, and 90% when it reaches 5s

• Walmart found that for every 1 second of improvement in page load time, conversions increased by 2%

• Amazon calculated that a 100ms delay cost them 1% in revenue

• Deloitte research found that improving mobile site speed by 0.1 seconds increased retail conversions by 8.4%

For an eCommerce store generating $50,000/month in revenue, a 2% conversion improvement from a 1-second speed gain is worth $1,000/month  or $12,000/year.

Common speed killers in eCommerce:

• Unoptimised product images (the most common cause,  images account for 75%+ of page weight on most product pages)

• Too many third-party apps and scripts (live chat, reviews widgets, tracking pixels)

• Render-blocking JavaScript that prevents the page from displaying until scripts load

• No lazy loading on images below the fold

• Missing browser and server caching

• No CDN for serving images and assets to visitors across different locations

• Unminified CSS and JavaScript files

What Happens If You Ignore It?

• Lower rankings because Google deprioritises slow pages in competitive SERPs

• Higher bounce rates because shoppers leave before your page loads

• Lower conversion rates — even shoppers who stay are less likely to buy on a slow site

• Worse mobile performance — since Google uses mobile-first indexing, a slow mobile experience affects your desktop rankings too

How to Fix It

Step 1 — Run a Core Web Vitals audit

Use these free tools:

• Google PageSpeed Insights (pagespeed.web.dev) — test individual pages

• Google Search Console → Core Web Vitals report — shows site-wide performance

• GTmetrix or WebPageTest — for detailed waterfall analysis

Step 2 — Optimise images first (biggest impact)

• Convert product images to WebP format (typically 30–50% smaller than JPEG with equivalent quality)

• Implement lazy loading for images below the fold: loading="lazy"

• Set correct width and height attributes on all images to eliminate CLS

• Use a CDN to serve images from servers close to your visitors

Step 3 — Audit and reduce third-party scripts

List every third-party script running on your store (Google Tag Manager, live chat, review widgets, heat mapping tools). For each one, ask: does this script load on every page? Can it be deferred or loaded asynchronously?

Step 4 — Enable caching

• Browser caching: set Cache-Control headers so returning visitors don't re-download assets

• Server-side caching: use a CDN like Cloudflare or a platform-level cache

Step 5 — Minimise and defer JavaScript

Move non-critical JavaScript to load after the main content renders. Use defer and async attributes appropriately.

Platform note (Shopify): Shopify's infrastructure handles much of the server-side performance, but app bloat is the primary speed killer. Audit and remove unused apps  each one typically adds scripts to every page.

 

5. Structured Data for Product Pages

What Is Structured Data and Why Does It Matter?

Structured data (also called schema markup) is code you add to your pages to help Google understand exactly what content it's looking at. For eCommerce, this means telling Google that a page is a product page  including the product's name, price, availability, reviews, and ratings.

When implemented correctly, structured data enables rich results in Google Search,  the enhanced listings that show star ratings, price, and availability directly in the search results page before a user clicks.

Example of what a product rich result includes:

• Product name and image

• Price and currency

• Availability (In Stock / Out of Stock)

• Review star rating and review count

• Shipping information (new in 2023)

• Return policy

Why rich results matter for revenue:

Rich results consistently achieve higher click-through rates than standard listings. Studies show rich snippets can improve CTR by 20–30% compared to standard listings for the same position. That means more clicks without ranking any higher.

What Happens If You Ignore It?

• Your product listings appear as plain blue links in Google while competitors show star ratings, prices, and availability

• Your click-through rate is lower even when you rank in the top 3

• You miss eligibility for Google Shopping integration and rich result placement

• Review content that your customers took the time to write provides no SEO benefit

How to Implement Product Schema

The most important schema types for eCommerce product pages:

Product Schema (required fields):

{

  "@context": "https://schema.org",

  "@type": "Product",

  "name": "Product Name",

  "image": "https://yourstore.com/images/product.jpg",

  "description": "Product description here",

  "brand": {

    "@type": "Brand",

    "name": "Brand Name"

  },

  "offers": {

    "@type": "Offer",

    "url": "https://yourstore.com/products/product-name",

    "priceCurrency": "AUD",

    "price": "49.99",

    "availability": "https://schema.org/InStock"

  },

  "aggregateRating": {

    "@type": "AggregateRating",

    "ratingValue": "4.5",

    "reviewCount": "89"

  }

}

 

Additional schema to implement:

How to validate your schema:

Use Google's Rich Results Test (search.google.com/test/rich-results) to check if your structured data is correct and eligible for rich results.

Platform shortcuts:

• Shopify: Most themes include basic Product schema by default, but it often lacks review data and return policy

• WooCommerce: Plugins like Yoast SEO or Rank Math add schema markup, but audit for accuracy

• Magento: Requires custom implementation or a dedicated schema extension

 

6. How Technical SEO Impacts Sales, Not Just Rankings

Most eCommerce businesses think of SEO as a visibility exercise,  get to page one, then revenue follows. But technical SEO has a direct and measurable impact on sales regardless of where you rank.

Here's how each technical factor connects to revenue:

Speed → Conversion Rate

As covered above, faster pages convert better. If your product pages take 5 seconds to load, you're losing potential buyers before they even see your price. Speed improvements don't require a ranking change to increase revenue.

Indexation → Revenue from Long-Tail Searches

Product-specific searches like "Nike Air Max 90 size 10 white Australia" have extremely high purchase intent. If your product pages aren't indexed, you're invisible to shoppers who are ready to buy. Each unindexed product represents a permanent revenue gap.

Structured Data → Click-Through Rate → Revenue

Higher CTR means more traffic at the same ranking position. If you're ranking #3 with a plain listing and your competitor at #4 has star ratings and pricing shown, they may be getting more clicks than you. Schema markup directly affects the revenue you extract from your current rankings.

Crawl Efficiency → Catalogue Freshness

If Google only crawls your site every few weeks due to crawl budget issues, your price changes, stock updates, and new products are stale in search. Shoppers find products that are out of stock, or miss products you've just added. Both scenarios cost revenue.

Duplicate Content → Ranking Cannibalisation

When multiple versions of the same product page compete against each other, none of them rank as well as a single, consolidated page would. Fixing this doesn't just clean up SEO,  it can directly lift your product page rankings and the organic revenue they generate.

 

Platform Limitations and How to Work Around Them

Every major eCommerce platform has known technical SEO limitations. Here's what you need to know:

The honest reality: No platform is perfectly optimised out of the box. Every store needs platform-specific technical SEO configuration on top of the default setup  and this is an area where our eCommerce development team can make a significant difference during both the build phase and ongoing optimisation.

 

eCommerce Technical SEO Audit Checklist

Use this checklist to identify and prioritise technical issues in your store. Work through each section systematically.

Crawlability & Indexation

• [ ] robots.txt is correctly configured, no key directories blocked accidentally

• [ ] XML sitemap is submitted to Google Search Console and contains no errors

• [ ] XML sitemap includes all indexable pages and excludes 404s, redirects, and noindex pages

• [ ] No important pages have accidental noindex meta tags or X-Robots headers

• [ ] Google Search Console Coverage report shows no critical errors

• [ ] site:yourdomain.com result count roughly matches your actual page count

• [ ] All important pages have at least one internal link from an indexed page

Duplicate Content

• [ ] All pages have a canonical tag pointing to the preferred URL version

• [ ] URL parameters (filters, sort, sessions) are handled via robots.txt or canonicals

• [ ] WWW and non-WWW both redirect to a single preferred version

• [ ] HTTP redirects to HTTPS for all pages

• [ ] Trailing slash usage is consistent across the site

Crawl Budget

• [ ] Cart, checkout, login, and account pages are blocked in robots.txt

• [ ] Search result pages are blocked or noindexed

• [ ] Faceted navigation URLs are controlled (canonical, noindex, or robots.txt)

• [ ] No redirect chains longer than one hop

• [ ] Soft 404 pages return correct status codes (404, 410) or are redirected

Page Speed & Core Web Vitals

• [ ] LCP is under 2.5 seconds on mobile (tested in Google PageSpeed Insights)

• [ ] CLS score is under 0.1 (images have width/height attributes set)

• [ ] INP is under 200ms

• [ ] All product images are converted to WebP format

• [ ] Lazy loading is enabled for below-the-fold images

• [ ] A CDN is configured to serve images and static assets

• [ ] Third-party scripts are audited and unnecessary ones removed

• [ ] CSS and JavaScript files are minified

Structured Data

• [ ] Product schema is implemented on all product pages

• [ ] AggregateRating schema is included where products have reviews

• [ ] BreadcrumbList schema is implemented site-wide

• [ ] Structured data passes Google's Rich Results Test

• [ ] No errors or warnings in Google Search Console's Rich Results report

URL Structure

• [ ] URLs are short, descriptive, and use hyphens (not underscores)

• [ ] URLs include target keywords without keyword stuffing

• [ ] Category and product URLs follow a logical hierarchy

Mobile & HTTPS

• [ ] Site passes Google's Mobile-Friendly Test

• [ ] HTTPS is enforced across all pages with a valid SSL certificate

• [ ] No mixed content warnings (HTTP resources on HTTPS pages)

 

Ready to Fix Your eCommerce Technical SEO?

Technical SEO issues are silent revenue killers. They don't generate error messages. They don't send you alerts. They just quietly prevent your products from being found and your revenue from growing.

The good news is that every issue covered in this guide is fixable. And fixing them creates compounding benefits: better crawl efficiency leads to faster indexation, which combined with proper structured data and speed improvements, directly increases both rankings and conversions.

If you're not sure where your store's biggest technical gaps are, the best starting point is a structured technical audit. Our team at The Development works with eCommerce businesses to identify and fix these exact issues, from platform-specific configuration to full technical overhauls.

Explore how we can help:

• eCommerce Website Development — Build or rebuild your store with technical SEO best practices from day one

• Digital Marketing Services — Full-funnel SEO strategy including technical, content, and off-page

• Custom Web Development — Custom technical fixes and platform optimisations

• Case Studies — See how we've helped eCommerce brands like EzyDog grow online

• Contact Us — Talk to our team about your store's technical SEO needs