Ecommerce SEO

TL;DR — Ecommerce SEO is just SEO for an online store — getting your product and category pages to show up in Google when people search to buy. There’s no special “ecommerce algorithm.” It feels harder only because stores have way more pages than a normal site, and a lot of those pages are near-identical (the same product in five colors, the same category sorted ten ways). The job is keeping that mess organized so Google ranks the pages that actually make you money.

What ecommerce SEO is

When you run a store, two pages do most of your earning in search:

• Product pages — one per item you sell.
• Category (collection) pages — the lists that group products, like “men’s running shoes.”

Ecommerce SEO is the work of getting those pages to rank for searches like “waterproof hiking boots” or “wireless earbuds under $100” — the searches where someone is ready to buy. Same Google, same rules as any other site. You still need pages that are crawlable, relevant to what people search, and trusted enough to compete.

Why stores are trickier than a blog

A blog might have 100 pages. A store with 2,000 products, each in a few colors and sizes, can quietly create hundreds of thousands of web addresses once you count every filter and sort option. Most of those are duplicates of each other. Google doesn’t have unlimited patience to crawl them all, and duplicate pages compete against your own pages. So a big part of the job is just tidying up: making sure Google focuses on the real pages, not the thousands of filtered variations.

The handful of things that matter most

• Write real descriptions. Don’t paste the manufacturer’s text that 50 other stores also use. Even a couple of original sentences per product helps.
• Put useful content on category pages. A category page that’s only a grid of products is hard for Google to rank. A short, genuinely helpful intro helps — but don’t dump a wall of keyword text at the bottom that no shopper reads.
• Handle out-of-stock items sensibly. If it’s coming back, keep the page up. If it’s gone for good, redirect it to something similar or let it 404.
• Use product structured data so you can earn the star ratings, prices, and shipping info that show up in Google’s results. Important: this makes your listing look better and get more clicks — it does not push you higher in the rankings.

The thing most people get wrong

Adding product schema does not make you rank higher. Google’s own people have said this directly. Schema earns you those nice rich snippets (stars, price, “in stock”), which can win more clicks — but only once you already rank. It’s a multiplier on visibility, not a shortcut to the top.

Want the full version — faceted navigation, crawl budget, platform-specific fixes for Shopify and the rest, and where to go next? Switch to the Advanced tab.

TL;DR — Ecommerce SEO is a scale-and-structure problem before it’s a ranking problem. A store generates near-duplicate URLs by default — variants, filters, sort parameters — so the real work is controlling a massive URL space, not coaxing any single page up the results. It runs on the same Google as every other site (no separate ranking system, no special indexing), and what makes it its own discipline is everything that scale and structure pile on: revenue riding on each page, platform-imposed URL structures, and duplication baked in. Faceted navigation is the canonical technical challenge. Product structured data earns rich results but is not a ranking factor. Core Web Vitals are a confirmed factor, but modest next to relevance and authority. Most small stores never need to think about crawl budget; large catalogs absolutely do.

A store manufactures URLs faster than Google will crawl them

The defining fact of ecommerce SEO is volume. A catalog of 10,000 products spins up hundreds of thousands of crawlable URLs the moment you add filters, sorts, and variants — most of them near-duplicates of each other. So the core problem isn’t ranking one product page; it’s keeping Google’s attention on the pages that earn money instead of the endless filtered permutations of them. Under the hood it’s the same Google as everywhere else — same signals, relevance and authority doing most of the work, no separate “ecommerce algorithm” or secret treatment for stores. What makes ecommerce its own discipline is that scale and structure turn ordinary SEO decisions into infrastructure ones.

Google does publish a dedicated ecommerce section of Search Central — one of the few topic-specific hubs they maintain — and it opens with the real problem: “A critical challenge for any ecommerce website is being discovered in Search.” Discovery, not ranking, is where stores struggle first. That framing tells you where to spend your effort.

Why ecommerce SEO is harder than general SEO

It comes down to five compounding pressures:

1. Scale. A mid-size retailer with 10,000 SKUs across 5 colors and 4 sizes is already at 200,000+ potential URLs before faceted navigation touches them.
2. Duplicate content by default. Variants, filtered category views, sort-order parameters, session IDs, and pagination all generate near-duplicate URLs. This isn’t a bug you introduced — it’s how ecommerce platforms work. The SEO job is to manage those URLs intentionally.
3. Platform constraints. Unlike a custom build, platforms impose URL structures you can’t fully override (more on the specifics below).
4. Revenue per page. A blog post slipping a few positions is disappointing. A product or category page slipping on a purchase-intent query hits revenue directly. The stakes per page are simply higher.
5. Rich-results surface area. Ecommerce has more SERP feature opportunities than almost any vertical — product snippets, merchant listings, shopping panels, image search, Lens, the Shopping tab — but each one needs correct structured data to unlock.

Faceted navigation — the canonical ecommerce challenge

If you only fix one technical thing on a large store, fix this. Faceted navigation (filtering a category by color, size, price, brand, and so on) generates a combinatorial explosion of URLs that are mostly near-duplicates. Google’s faceted navigation guidance names the two failure modes precisely: overcrawling (filtered URLs “appear novel, causing crawlers to access many useless URLs before recognizing their lack of value”) and slower discovery (“Resources spent on faceted URLs reduce time available for discovering genuinely new content”).

If you don’t need filtered URLs indexed, Google offers a tiered defense: robots.txt blocking, URL fragments (Google “generally doesn’t support URL fragments in crawling and indexing”), rel="canonical" to the unfiltered page, and nofollow on filter links. If you do need some filtered combinations indexed (e.g. “red running shoes” has real demand), use the standard & separator, keep filter order consistent, and return a 404 when a filter combination has no results so you don’t index empty pages.

One myth to retire here: canonical tags do not “fix” faceted navigation. Canonicals are hints, not directives — Google can and does ignore them when other signals (especially internal or external links to the filtered URL) disagree. Canonicals are one layer; robots.txt is a stronger crawl-waste control when you truly never want those URLs fetched.

Crawl budget — when it actually matters

Gary Illyes has said roughly “90% of websites don’t need to think about crawl budget,” and that’s true. For a store under ~10,000 unique pages with decent URL hygiene, crawl budget is not your bottleneck — content quality and indexation are. The remaining 10% is where a lot of ecommerce lives: large catalogs, daily SKU churn, and faceted navigation generating combinatorial URLs.

You need to care when you see the symptoms: 10,000+ unique pages, pages taking weeks to get discovered, or a large “Crawled — currently not indexed” bucket in GSC. For very large sites, Google’s guidance is direct: “Eliminate duplicate content to focus crawling on unique content rather than unique URLs”, return 404/410 for permanently removed pages, and avoid long redirect chains. And a counterintuitive one — don’t use noindex to save crawl budget, because Google “will still request, but then drop the page when it sees a noindex”, wasting the very budget you were trying to protect. Block at robots.txt for true crawl-waste; reserve noindex for things you want crawled but not indexed.

Structured data: eligibility, not ranking

This is the single most over-sold idea in ecommerce SEO, so let me state it plainly. Product structured data does not make you rank better. John Mueller, April 2025: “Structured data won’t make your site rank better.” What it does do is make pages eligible for rich results — product snippets and merchant listings — which can lift CTR once you already rank. Schema is a visibility multiplier, not a ranking lever.

Practically: use Merchant Listing markup for pages where people can buy and Product Snippet markup for editorial/review pages. Merchant listings require name, image, and a nested Offer with a positive price and ISO-4217 priceCurrency; add availability, shippingDetails, hasMerchantReturnPolicy, and aggregateRating to unlock more. Use ProductGroup + Product for variants (each variant and the group need unique IDs). And pair structured data with a Google Merchant Center feed — Google recommends both, because a feed “increases confidence Google knows all of your products, since web crawling is not guaranteed to find all products on your site.”

Core Web Vitals — a real factor, in proportion

Page experience, including Core Web Vitals, is a confirmed ranking factor — this isn’t a myth. But keep the magnitude honest: its impact is modest compared to relevance and authority. On a store, the highest-leverage performance work is usually LCP on product and category templates (hero images, render-blocking scripts). Fix it because it converts and because it’s a tiebreaker, not because it’ll vault a weak page past strong competitors.

Out-of-stock products

Decide by permanence, not by reflex:

• Temporarily out of stock: keep the URL live and indexable; set availability to OutOfStock in structured data; offer a back-in-stock signup. Mueller: “what works best for us is if we can keep the URL online for things that are really temporary.”
• Permanently gone, with links/traffic: 301 to the closest equivalent product or its category.
• Permanently gone, no equity: 404 or 410.
• Avoid: noindex on pages that have external backlinks (Google eventually drops the links on noindexed pages), and redirect chains into other products that may themselves get discontinued.

The governing principle, again from Mueller: “the short version is to do what works best for the user, and search engines will generally figure it out from there too.”

Category pages need content — the right kind

A category page that’s nothing but a product grid is hard to rank. Mueller’s framing: “When ecommerce category pages don’t have any other content at all beyond links to the products, it’s really hard for Google to rank those pages.” The trap is overcorrecting into footer keyword sludge — he’s also noted that “about 90-95% of extra text placed at the bottom of pages is unnecessary.” Gary Illyes lands it: if you add content, “add content that people will actually find useful,” not low-quality auto-generated blurbs. Write the short, genuinely helpful intro a shopper would read; skip the wall of text they won’t.

Platform choice matters — but nothing is un-SEO-able

Platform architecture has compounding SEO effects at scale, so platform selection is an SEO decision. But to be clear: no mainstream platform is inherently un-SEO-able — each just hands you a different starting difficulty.

• Shopify forces /collections/[name]/products/[slug], creating duplicate product URLs for every collection an item belongs to; it canonicalizes to /products/[slug] but internal links often point at the collection-scoped URL, misaligning signals. The common fix is removing the | within: collection Liquid filter from theme templates. Workable — just needs attention.
• WooCommerce / WordPress gives you full URL control and deep SEO-plugin integration; performance is the thing you have to engineer.
• BigCommerce ships stronger built-in ecommerce SEO and more URL flexibility than Shopify out of the box — a solid mid-market default.
• Magento / Adobe Commerce offers maximum flexibility but generates serious duplicate content (layered navigation, sort parameters) unless configured by someone who knows what they’re doing; it’s an enterprise tool.

Where to go next

This hub is the map. Each topic below is its own deep dive — they’re in the sidebar too.

Platform guides — the SEO realities of each stack

• Shopify SEO — the forced collection/product URL duplication, the within: collection fix, and what you genuinely can’t change.
• Magento SEO — taming layered navigation and sort parameters on Adobe Commerce so the default duplication doesn’t sink you.
• WooCommerce SEO — using WordPress’s full URL control well, plus the performance work the flexibility costs you.
• BigCommerce SEO — the stronger built-in features and where the mid-market balance pays off.

On the store itself

• Product Page SEO — unique descriptions, image SEO, variant handling, and the on-page signals that move purchase-intent queries.
• Category Page SEO — the right kind of content, internal linking down the hierarchy, and ranking commercial head terms.
• Out of Stock — the permanence-based decision tree for temporary vs. discontinued products.
• Faceted Navigation — the canonical crawl-budget challenge: when to block, when to index, and why canonicals alone don’t cut it.
• Site Architecture — the menu → category → sub-category → product linking pattern that shapes how Google understands your store.
• Ecommerce SEO Audit — the repeatable process for finding crawl waste, duplication, and indexation gaps before they cost revenue.

For the broader fundamentals these all build on, see the technical SEO work on crawl budget, canonicalization, and faceted navigation in the technical-SEO pillar — ecommerce just applies them at scale.

AI summary

A condensed take on the Advanced version:

• Same algorithm, harder context. Ecommerce SEO is regular SEO applied to a store — no separate ranking system, no special indexing. The difficulty comes from scale and structure, not a different rulebook.
• Five compounding pressures: catalog scale, duplicate content by default (variants/filters/sort params), platform-imposed URLs, revenue per page, and a large rich-results surface area.
• Faceted navigation is THE technical challenge. It causes overcrawling and slower discovery; defend with robots.txt, canonicals, nofollow, and 404s on empty filter combos. Canonical tags are hints, not a fix.
• Structured data ≠ ranking. Mueller: “Structured data won’t make your site rank better.” It earns rich-result eligibility and CTR. Pair Product/Merchant Listing markup with a Merchant Center feed (Google recommends both).
• Core Web Vitals are a real but modest factor — relevance and authority dominate.
• Crawl budget: ~90% of sites can ignore it; large catalogs with faceted nav cannot. Don’t use noindex to save budget — block at robots.txt.
• Out of stock: keep temporary pages live (set OutOfStock); 301 discontinued-with-equity; 404/410 the rest.
• Category pages need useful content, not footer keyword sludge.
• Platform choice matters but nothing is un-SEO-able — Shopify, WooCommerce, BigCommerce, and Magento each hand you a different starting difficulty.

Official documentation

Primary-source documentation from the search engines.

Google — the ecommerce hub

• Ecommerce best practices (overview) — Google’s dedicated ecommerce section and its eight sub-topics.
• Share your product data with Google — structured data vs. Merchant Center feed, and why you want both.
• Include structured data relevant to ecommerce — which schema types matter for stores.
• Ecommerce URL structure best practices — minimizing duplicate URLs and handling variant parameters.
• Help Google understand your site structure — the menu → category → product internal-linking pattern.
• Pagination and incremental page loading — pagination vs. load-more vs. infinite scroll for crawlers.
• Write high-quality reviews — what Google wants from on-site reviews and editorial content.

Google — structured data & crawling

• Intro to Product structured data — product snippets vs. merchant listings.
• Merchant listing structured data — required and recommended properties.
• Product variant structured data — ProductGroup + Product for variations.
• Managing crawling of faceted navigation URLs — the canonical reference for the biggest ecommerce crawl problem.
• Optimize your crawl budget — for catalogs at 10k+/1M+ scale.

Bing / Microsoft

• Bing Webmaster Tools — markup validation and crawl info; supports JSON-LD and other formats.
• JSON-LD support in Bing Webmaster Tools — Bing’s structured-data support; Microsoft Merchant Center can import Google feeds.

Quotes from the source

On-the-record statements from Google. Each deep link jumps to the quoted passage on the source page where one is available.

The core myth — structured data is not a ranking factor

• “Structured data won’t make your site rank better. It’s used for displaying the search features listed in developers.google.com/search/docs/…” — John Mueller, Google, Bluesky, April 2025.

  Relayed via Search Engine Journal’s reporting; the original is a Bluesky post.

  Read the coverage

Discovery is the first ecommerce challenge

• “A critical challenge for any ecommerce website is being discovered in Search.” — Google Search Central docs. Jump to quote

URL structure — minimize duplicates

• “Minimize the number of alternative URLs that return the same content.” — Google Search Central docs. Jump to quote

Site structure — navigation shapes understanding

• “navigation structures on your site (such as menus and cross page links) can impact Google’s understanding of your site structure.” — Google Search Central docs. Jump to quote

Structured data on product pages

• “can help Google understand your page better and display it as a rich result.” — Google Search Central docs (on why structured data is recommended, though not mandatory).

  Sourced from Google’s “Share your product data” page; structured data is described as helpful for understanding and rich results, not as a ranking boost.

Merchant Center vs. crawling

• Uploading feed files increases confidence Google knows all your products, “since web crawling is not guaranteed to find all products on your site.” — Google Search Central docs.

  Paraphrased from Google’s “Share your product data” guidance; quoted clause is verbatim.

Faceted navigation — why it hurts crawling

• Faceted URLs “appear novel, causing crawlers to access many useless URLs before recognizing their lack of value.” — Google Crawling Infrastructure docs. Source

Crawl budget — don’t noindex to save it

• “Don’t use noindex, as Google will still request, but then drop the page when it sees a noindex meta tag or header in the HTTP response, wasting crawling time.” — Google Search Central docs. Jump to quote

Out-of-stock products

• “what works best for us is if we can keep the URL online for things that are really temporary, in the sense that if the URL remains indexable and with structured data you tell us this product is currently not available.” — John Mueller, Google SEO Office Hours. Relayed via Search Engine Journal’s reporting of Office Hours. Read the coverage

Category page content

• “When ecommerce category pages don’t have any other content at all beyond links to the products, it’s really hard for Google to rank those pages.” — John Mueller, Google.

  Relayed via iLoveSEO’s reporting of Mueller’s Office Hours remarks.

  Read the coverage
• On adding category-page content, “add content that people will actually find useful” — and not “low-quality, auto-generated blurbs of text.” — Gary Illyes, Google.

  Relayed via Search Engine Roundtable’s reporting of Office Hours.

  Read the coverage

Ecommerce SEO foundations checklist

A first-pass audit for any store, in roughly the order I’d work it:

• Indexation is clean — site: and GSC show your real product/category pages indexed, not filter/sort variations or session-ID URLs.
• Faceted navigation is controlled — filtered URLs you don’t want indexed are blocked (robots.txt) or canonicalized; empty filter combinations return 404; you’re not relying on canonicals alone.
• Variants are consolidated — one canonical per product (or a deliberate ProductGroup setup), not a thin indexable URL per color/size.
• URLs are descriptive and stable — words not IDs, no tracking/session parameters in internal links, consistent across links/sitemaps/canonicals.
• Internal linking flows down the hierarchy — menu → category → sub-category → product, with real <a href> links (not JS-only nav).
• Product descriptions are unique — not verbatim manufacturer copy.
• Category pages have useful (not boilerplate) content.
• Out-of-stock policy is set — keep temporary, redirect/404 permanent.
• Structured data is valid — Merchant Listing on buyable pages, with a nested Offer, positive price, and currency; variants use ProductGroup.
• Merchant Center feed exists alongside the on-page structured data.
• Core Web Vitals pass on the product and category templates (LCP first).
• Crawl budget reviewed only if you qualify — 10k+ pages, heavy facets, or a large “Crawled — currently not indexed” bucket in GSC.
• Pagination is crawlable — <a href> page links; not infinite scroll with no fallback; first page not used as the canonical for the series.

The mental models

1. Same algorithm, different surface area. There is no ecommerce algorithm. Every ranking signal is the general one. So when a page underperforms, don’t reach for “ecommerce tricks” — diagnose it like any page (crawled? indexed? relevant? authoritative?) and check the ecommerce-specific failure layer underneath it.

2. The duplication-first lens. On a store, assume duplication is the default state and your job is consolidation. Before optimizing anything, ask: how many URLs return roughly this content, and which single one do I want to be the canonical? Variants, filters, sort params, and pagination are the usual suspects.

3. Schema is a multiplier, not a lever. Structured data multiplies the visibility of a page that already ranks (rich results → CTR). It does not move the ranking itself. Budget it as a CTR/eligibility investment, never as a ranking strategy.

4. The crawl-budget gate. Most stores never pass through it. Only spend time here if you clear the bar: ~10k+ unique pages, faceted explosion, fast inventory churn, or pages that take weeks to index. Below the bar, fix content and indexation instead.

5. The out-of-stock decision tree. Branch on permanence, then on equity: temporary → keep live + OutOfStock; permanent + has links/traffic → 301 to the nearest relevant page; permanent + no equity → 404/410. Never noindex a page that has external backlinks.

Ecommerce SEO — cheat sheet

Structured data: what each type is for

Merchant Listing required vs. recommended

• Required: name, image, offers → nested Offer with price > 0 and ISO-4217 priceCurrency.
• Recommended: description, brand.name, sku, gtin, availability, itemCondition, shippingDetails, hasMerchantReturnPolicy, aggregateRating, review.

Faceted navigation — pick your control

Out-of-stock

Fast facts

• Structured data: rich-result eligibility, not a ranking factor.
• Core Web Vitals: confirmed factor, modest vs. relevance/authority.
• Crawl budget: ~90% of sites can ignore it.
• Canonical tags: hints, not directives — don’t rely on them alone for facets.

Ecommerce SEO mistakes that waste the most effort

Treat structured data as a ranking tactic

Product markup makes an eligible page understandable for rich results; it does not make the page rank. Fix crawlability, indexability, relevance, and authority before expecting schema to change organic positions.

Use noindex to save crawl budget

Google must fetch a page to see noindex, so the crawl still happens. Use noindex for index control and a deliberate crawl-prevention strategy for URL spaces that should not be fetched.

Expect canonical tags to solve faceted navigation by themselves

Canonicals are hints and require the variants to be crawled. Remove crawlable paths to useless states and use narrow robots.txt rules where real crawl waste exists.

Build every platform default as if it were correct

Shopify, WooCommerce, BigCommerce, and Magento make different tradeoffs around variants, parameters, and internal links. Audit the generated HTML and URL behavior instead of trusting the platform label.

Redirect every discontinued product to the homepage

An irrelevant redirect can be treated as a soft 404. Send a retired product to a genuinely similar replacement or relevant category, or return 404/410 when no useful target exists.

Tools for an ecommerce SEO operating system

• Faceted Navigation Auditor — classify real filter, sort, pagination, and tracking URLs before deciding what to index, canonicalize, block, or return as 404.
• Schema Markup Validator — check product, offer, variant, breadcrumb, and organization markup in JSON-LD or full HTML.
• Rich-Result Eligibility Checker — see which Google product rich-result requirements the current markup meets and which required properties are missing.
• Google Search Console Page Indexing — segment product, category, facet, pagination, and variant URLs to find index bloat or discovery gaps.
• Google Search Console Crawl Stats — watch request trends and response behavior on stores large enough for crawl budget to matter.
• Google Merchant Center — pair feeds with structured data and investigate product availability or data-quality mismatches.
• Ahrefs Site Audit or Screaming Frog — crawl templates at scale for canonical conflicts, redirect chains, orphan products, duplicate pages, and crawl depth.
• Google Rich Results Test and URL Inspection — validate deployed markup and inspect Google’s rendering, indexing, and selected canonical for representative URLs.

Ecommerce SEO health metrics

Index coverage by page class

Metric: indexed, duplicate, crawled-not-indexed, and soft-404 URLs split into products, categories, facets, variants, pagination, and retired products. What it tells you: whether the right inventory is discoverable while duplicate URL classes stay contained. How to pull it: classify Search Console Page Indexing exports with catalog and crawl data. Benchmark / realistic range: compare actual counts with the approved URL inventory for each class; one sitewide index-rate target would hide intentional exclusions. Cadence: monthly and after platform releases.

Non-canonical crawl share

Metric: share of verified Googlebot requests spent on duplicate facet, sort, tracking, and consolidated variant URLs. What it tells you: whether scale and URL generation are diverting crawl from products and categories. How to pull it: segment server logs by known URL patterns and compare with Crawl Stats. Benchmark / realistic range: establish a baseline by template and aim for a sustained reduction in intentionally suppressed classes; small stores may not need to optimize this at all. Cadence: weekly during remediation, then monthly on large catalogs.

Core Web Vitals pass rate by template

Metric: share of product and category URL groups with good field CWV status. What it tells you: whether shoppers and search engines receive healthy page experience on revenue-driving templates. How to pull it: use Search Console Core Web Vitals or CrUX, separated by template and device. Benchmark / realistic range: use Google’s current good/needs-improvement/poor classifications and the site’s own trend; do not replace field data with a lab-only score. Cadence: monthly because field data uses a rolling window, plus lab checks on releases.

Organic landing-page value

Metric: clicks, impressions, conversions, and revenue from canonical product and category landing pages. What it tells you: whether technical cleanliness supports pages that actually produce commercial value. How to pull it: join Search Console URL data with analytics and commerce reporting. Benchmark / realistic range: compare page classes and seasonal prior periods; margins, catalog churn, and demand make a universal revenue target dishonest. Cadence: weekly operationally and monthly for strategy.

Resources worth your time

My related writing

• Enterprise SEO — large-scale SEO including the crawl-budget, duplication-at-scale, and faceted-navigation problems that define big ecommerce.
• The Beginner’s Guide to Technical SEO — the technical foundation everything on a store is built on.
• Internal Links for SEO — directly relevant to internal linking across thousands of product and category pages.
• Search Engine Land author archive — my technical-SEO writing, much of which touches ecommerce challenges.

From others

• Ecommerce SEO: A Beginner’s Guide — Chris Haines’s Ahrefs guide (not mine, but a solid step-by-step).
• Backlinko’s Ecommerce SEO guide — data-heavy and widely cited.
• Resolving Shopify duplicate content (Amsive) — the collection/product URL fix in detail.
• r/TechSEO — where crawl/index/faceted-nav debugging actually happens.
• Search Engine Land Ecommerce SEO Guide — SEL’s reference guide covering the discipline end to end.
• Shopify’s Ecommerce SEO Guide — useful for understanding Shopify-native constraints and built-in SEO features from the platform itself.
• Shopify SEO challenges: platform architecture limitations and workarounds (NotProvided.eu) — deep technical look at the collection/product URL duplication issue and what you can and can’t fix.

Stats worth citing

• ~90% of sites don’t need to think about crawl budget — Gary Illyes, Google. The flip side: large ecommerce catalogs with faceted navigation are squarely in the 10% that do. Context
• Catalog math compounds fast — 10,000 SKUs × 5 colors × 4 sizes = 200,000+ potential URLs before any faceted navigation is applied. Scale, not difficulty of any single page, is the core ecommerce SEO problem.
• Internal links rank above sitemaps for discovery — Google has described XML sitemaps as the second most important way it finds URLs, with internal links first. On a store, your navigation and category structure are doing more discovery work than your sitemap.

  Relayed from Google rep commentary; treat as directional guidance rather than a published metric.

Ecommerce SEO

Ecommerce SEO is the practice of optimizing an online store so its product and category pages rank in organic search and attract purchase-intent visitors. It uses the same Google algorithm as any other site, but compounds the usual SEO work with commerce-specific challenges like faceted navigation, product variants, and platform-imposed URLs.

Related: Crawl Budget, Faceted Navigation, Canonicalization, Product Schema

Ecommerce SEO

Ecommerce SEO is the practice of optimizing an online store so that its product and category pages rank in organic search and attract visitors with purchase intent. It is not a separate algorithm or ranking system — the same Google algorithm applies to a store that applies to a blog. What makes it its own discipline is everything that surrounds that algorithm at commerce scale.

Ecommerce sites generate enormous, dynamic URL spaces: a catalog of a few thousand SKUs, multiplied by colors, sizes, sort orders, and filters, can balloon into hundreds of thousands of crawlable URLs — most of them near-duplicates. So the core work is consolidation: managing faceted navigation, canonicalizing product variants, controlling crawl budget on large catalogs, and shaping site architecture and internal links so the commercially important pages get crawled, indexed, and ranked.

On-page, ecommerce SEO covers product-page and category-page optimization, unique product descriptions, out-of-stock handling, and structured data. Product and Merchant Listing structured data make pages eligible for rich results, but — per Google’s John Mueller — structured data does not make a site rank better; it is a visibility and CTR multiplier, not a ranking shortcut. Core Web Vitals are a confirmed ranking factor, though their impact is modest next to relevance and authority.

Platform choice (Shopify, WooCommerce, Magento/Adobe Commerce, BigCommerce) shapes the starting difficulty — each imposes different URL and duplication defaults — but no mainstream platform is inherently un-SEO-able. The discipline ties all of this back to one thing a blog rarely has to: revenue per page.

Related: Crawl Budget, Faceted Navigation, Canonicalization, Product Schema

Changelog