Ecommerce Platform SEO
SEO for ecommerce platforms — Shopify, WooCommerce, Magento, BigCommerce, Salesforce Commerce Cloud, Shopware, OpenCart, Ecwid, Wix, Squarespace, and PrestaShop. What each platform handles for you automatically, what it locks down, and the platform-specific quirks that affect organic performance.
1 evidence signal on this page
- Related live toolFaceted Navigation Auditor
Every ecommerce platform makes SEO decisions that affect your store before you touch a single product. Shopify locks the URL structure but auto-handles canonicals and sitemaps. WooCommerce (on WordPress) gives you full control via plugins. Magento is flexible but requires developer work for most SEO configurations. BigCommerce sits between Shopify and Magento — more flexibility than Shopify, less developer overhead than Magento. None of that makes one platform inherently better for rankings: pick based on your store's product, category, variant, feed, localization, and operational requirements, then verify what the implementation actually outputs. All four add ecommerce-specific concerns: product schema, faceted navigation, duplicate URLs from variants and collections, and pagination.
Evidence for this claim Regardless of platform, Google needs crawlable product links and consistent product data. Scope: Search-engine requirements independent of platform. Confidence: high · Verified: Google Search Central: Ecommerce site structure Evidence for this claim Platform automation varies; Shopify, for example, automatically generates canonical tags and sitemap files but still exposes merchant-controlled SEO fields. Scope: Shopify-specific example, not a search-engine rule. Confidence: high · Verified: Shopify Help: SEO overviewTL;DR — Ecommerce platforms handle some SEO automatically — HTTPSHTTPS is the encrypted version of HTTP — it uses TLS to authenticate the server and protect data in transit between a browser and a website. Google announced it as a lightweight ranking signal in 2014 and today conditionally prefers HTTPS pages as canonical; Chrome marks plain HTTP pages 'Not Secure.', sitemapsA sitemap is a file that lists the pages, images, videos, and other files on your site so search engines can discover them. It helps discovery, but submitting a sitemap doesn't guarantee crawling or indexing., canonical tagsA rel=\"canonical\" annotation — in the HTML <head> or an HTTP Link header — that tells search engines which URL is the preferred version of duplicate or near-duplicate content. — but each one has quirks that can hurt you if you don’t know about them. The most common ones: duplicate URLs from products appearing in multiple collections (Shopify), thin category pages (all platforms), and faceted navigation creating millions of parameter URLs you don’t want indexedStoring a crawled page in the search index so it can appear in results. Crawled is not the same as indexed — Google selects what to keep, and indexing isn't guaranteed.. No platform here is inherently better for rankings — pick the one that matches your product, category, variant, and operational requirements, then verify what it actually outputs.
What makes ecommerce platform SEO different
A general-purpose website has pages. An ecommerce store has pages and products, categories, variants, collections, filters, and paginationPagination splits a large set of content — product listings, blog archives, search results — across multiple sequentially numbered URLs. For SEO, each paginated page should be crawlable, indexable, and self-canonical; Google no longer uses rel=prev/next, but Bing still does.. Each of these generates URLs — and not all of them should be indexed.
The platforms covered here each make different default decisions about how to handle this:
- Shopify — fixes URL structureURL structure is how the parts of a web address — scheme, domain, path, query string, and fragment — are organized and formatted. It mostly affects crawling, usability, and how engines understand a page, not rankings directly. (
/products/,/collections/), auto-canonicalizes duplicate collection-product URLs, generates a sitemapA sitemap is a file that lists the pages, images, videos, and other files on your site so search engines can discover them. It helps discovery, but submitting a sitemap doesn't guarantee crawling or indexing., limits robots.txtA plain-text file at the root of a host that tells crawlers which URLs they may and may not request. It controls crawling, not indexing — a blocked URL can still be indexed if it's linked from elsewhere. editing on standard plans - WooCommerceWooCommerce SEO is optimizing a WooCommerce store — which runs as a free plugin on WordPress, not as a standalone platform — to rank in organic search. Because you control the whole stack (templates, URLs, plugins, server), the ceiling is high and the ways to misconfigure it are many. — runs on WordPress, so you get full SEO plugin control (Yoast, Rank Math); more flexible but more to configure
- Magento (Adobe Commerce) — enterprise-grade, highly configurable, but most SEO settings require developer involvement
- BigCommerce — more flexibility than Shopify with less developer overhead than Magento; solid built-in SEO defaults
The comparison below focuses on these four, but the platform deep dives at the bottom of this page also cover Salesforce Commerce Cloud, Shopware, OpenCart, Ecwid, Wix eCommerce, Squarespace Commerce, and PrestaShop.
The ecommerce-specific SEO concerns
Regardless of platform, every ecommerce store faces these:
Product structured dataStructured data is a standardized way of labeling page content (using the schema.org vocabulary in JSON-LD, Microdata, or RDFa) so search engines can understand its meaning. It's not a direct ranking factor — its value is rich results and entity understanding. — Schema.org Product markup with price, availability,
and reviews can make a page eligible for richer Google presentations — eligible,
not guaranteed to display. Some platforms inject this automatically; others need a
plugin or theme, and you need to check the actual page output, not just the
platform’s marketing claim.
Faceted navigationFaceted navigation (faceted search, product filtering) lets visitors refine a list of products or content by attribute — price, color, size, brand, rating. The SEO problem: each filter combination can spawn a distinct crawlable URL, turning a small catalog into millions of near-duplicate pages that waste crawl budget and dilute ranking signals. — Filter parameters (?color=red&size=M) can generate
thousands of URLs with near-identical content. Most need to be either blocked from
indexation or canonicalized to the base category page.
Duplicate URLs from variants — A product with 10 size/color combinations shouldn’t have 10 indexed pages. Canonical tagsA rel=\"canonical\" annotation — in the HTML <head> or an HTTP Link header — that tells search engines which URL is the preferred version of duplicate or near-duplicate content. or parameter handling prevents this.
Out-of-stock and discontinued productsA discontinued product is an item you'll never sell again — the manufacturer stopped making it, or you dropped the line. The SEO decision is end-of-life: 301-redirect the URL to a genuinely similar replacement or the closest relevant category if it earned links or traffic, 404/410 it if it didn't, or keep it live as a Discontinued tombstone page only when it still helps users. This is distinct from a temporary out-of-stock product, which you keep live at 200. — How the platform handles missing products (404, 301 to category, keep with availability structured data) directly affects link equity and user experience.
PaginationPagination splits a large set of content — product listings, blog archives, search results — across multiple sequentially numbered URLs. For SEO, each paginated page should be crawlable, indexable, and self-canonical; Google no longer uses rel=prev/next, but Bing still does. — Category pages paginate. Page 2 of /collections/shoes/ has
thinner content than page 1. Platform-specific handling varies.
Evidence for this claim Regardless of platform, Google needs crawlable product links and consistent product data. Scope: Search-engine requirements independent of platform. Confidence: high · Verified: Google Search Central: Ecommerce site structure Evidence for this claim Platform automation varies; Shopify, for example, automatically generates canonical tags and sitemap files but still exposes merchant-controlled SEO fields. Scope: Shopify-specific example, not a search-engine rule. Confidence: high · Verified: Shopify Help: SEO overviewTL;DR — At scale, ecommerce platform SEOPlatform SEO covers the SEO considerations specific to the technology a site is built on — CMS, website builder, headless stack, or JavaScript framework. Each platform has different defaults, constraints, and required configurations that affect crawling, indexing, and ranking. comes down to: how does this platform handle URL canonicalizationHow search engines pick one canonical URL among duplicates and consolidate signals onto it. at volume, what’s the structured dataStructured data is a standardized way of labeling page content (using the schema.org vocabulary in JSON-LD, Microdata, or RDFa) so search engines can understand its meaning. It's not a direct ranking factor — its value is rich results and entity understanding. coverage (auto or manual), how controllable is robots.txtA plain-text file at the root of a host that tells crawlers which URLs they may and may not request. It controls crawling, not indexing — a blocked URL can still be indexed if it's linked from elsewhere. and the sitemapA sitemap is a file that lists the pages, images, videos, and other files on your site so search engines can discover them. It helps discovery, but submitting a sitemap doesn't guarantee crawling or indexing., and what’s the approach to faceted navigationFaceted navigation (faceted search, product filtering) lets visitors refine a list of products or content by attribute — price, color, size, brand, rating. The SEO problem: each filter combination can spawn a distinct crawlable URL, turning a small catalog into millions of near-duplicate pages that waste crawl budget and dilute ranking signals.? Shopify has the most opinionated (least flexible) defaults; WooCommerceWooCommerce SEO is optimizing a WooCommerce store — which runs as a free plugin on WordPress, not as a standalone platform — to rank in organic search. Because you control the whole stack (templates, URLs, plugins, server), the ceiling is high and the ways to misconfigure it are many. has the most control; Magento has the most power but the highest configuration cost. None of that is a ranking advantage — it’s a description of who owns the configuration work. Google evaluates the pages, links, and data your implementation actually produces, not which CMSA content management system (CMS) is software that lets users create, manage, and publish digital content — like blog posts and pages — without writing raw code. WordPress, Drupal, and Joomla are the most common open-source CMS platforms. built it.
Platform selection method
Pick a platform against your store’s actual requirements, not a feature checklist or a “best platform for SEO” ranking — no commerce platform is inherently superior for search rankings. Architecture constrains and enables what you can build; the crawlabilityCrawlability is how well search engine crawlers can discover, access, and fetch a site's pages. A crawlability issue is any technical condition — blocked access, broken links, server failures, or bloated URL inventory — that stops pages from reaching the index., structured-data accuracy, rendered output, performance, content, and ongoing operations of the specific implementation are what determine outcomes. Work through these dimensions before comparing vendors:
- Product data — how product, price, availability, and review data reaches the page, and whether it’s automatic, theme-dependent, or plugin/module-driven.
- Category and facet structure — whether the platform’s templates expose crawlable links from navigation to categories to products, and how filtered (faceted) URLs are handled.
- Variant architecture — whether the platform supports one canonical product URL per item, separate URLs per variant, or both, and what that means for your catalog.
- LocalizationLocalization is adapting content for a specific target market — not just translating the words, but adjusting currency, formats, idioms, cultural references, local search terms, and trust signals so the experience feels native. and feeds — multi-region/multi-language support and how product feeds sync to the storefront.
- Publishing and release process — who can change templates, robots.txtA plain-text file at the root of a host that tells crawlers which URLs they may and may not request. It controls crawling, not indexing — a blocked URL can still be indexed if it's linked from elsewhere., and redirectsA redirect sends browsers and crawlers from a requested URL to a different one. An HTTP redirect specifically is a 3xx status code paired with a Location header; meta refresh and JavaScript redirects achieve a similar navigation without being a 3xx response themselves. Permanent redirects (301/308) are Google's signal the target should be canonical; temporary ones (302/303/307) aren't., and how fast.
- Operational ownership — product lifecycle handling, category governance, redirects, sitemapA sitemap is a file that lists the pages, images, videos, and other files on your site so search engines can discover them. It helps discovery, but submitting a sitemap doesn't guarantee crawling or indexing. freshness, release testing, and who owns incidents when something breaks.
Control over these is distributed differently by platform — hosted platforms, plugins, themes, modules, and custom code all place the configuration knobs in different hands. More configurability generally means more implementation and maintenance ownership, not more inherent SEO capability. Any capability claim about a specific platform needs to name the vendor, edition, plan, theme, app/module, version, and date it applies to — defaults change, and a plan or app can override them.
Platform comparison
| Concern | Shopify | WooCommerce | Magento | BigCommerce |
|---|---|---|---|---|
| URL structureURL structure is how the parts of a web address — scheme, domain, path, query string, and fragment — are organized and formatted. It mostly affects crawling, usability, and how engines understand a page, not rankings directly. | Fixed (/products/, /collections/) | Configurable via WordPress | Highly configurable | Semi-flexible |
| robots.txt | Locked (standard plans) | Full control | Full control | Partial control |
| Sitemap | Auto-generated | Via plugin (Yoast/Rank Math) | Built-in + configurable | Auto-generated |
| Product schemaProduct schema (schema.org/Product) is structured data that tells search engines a page's product name, price, availability, and reviews so it can appear in Shopping-style rich results. It's separate from a Google Merchant Center feed, though Google reconciles the two. | Theme-dependent | Via plugin | Via module | Built-in (basic) |
| Faceted nav | Via URL parametersThe `?key=value` data tacked onto the end of a URL after a question mark — used for tracking, sessions, filtering, sorting, and search — and one of the biggest sources of duplicate URLs and wasted crawling in SEO., needs handling | Via plugin or custom | Built-in layered nav config | Built-in facets, configurable |
| Canonical tagsA rel=\"canonical\" annotation — in the HTML <head> or an HTTP Link header — that tells search engines which URL is the preferred version of duplicate or near-duplicate content. | Auto (collection→product URLs) | Via plugin | Built-in | Built-in |
| Redirect management | Built-in manager | Via plugin (Redirection) | Built-in + configurable | Built-in |
| Developer requirement | Low | Low-medium | High | Medium |
Platform defaults, apps, modules, and themes can all change the final Product markup. This checker reads the public raw HTML; JavaScript-only buy boxes and merchant feeds are outside its scope.
Audit a representative PDP with my free PDP SEO Checker Free
- Test at least one in-stock, out-of-stock, and variant-heavy product URL.
- Compare missing Product, price, and availability findings across templates or platforms.
- Fix the theme or schema source, then validate eligibility separately without assuming a rich result is guaranteed.
The PDP SEO Checker reports: Product schema: No Product schema found.
Variant architecture: one URL or many
Google’s product structured data documents more than one supported approach to
product variants — there’s no single required URL count. A store can put every
color/size combination on one canonical product URL and describe the variants
with ProductGroup data, or it can give each variant its own URL and link them
together as a group. Both are documented designs with different implementation
requirements (which URL gets internal linksAn internal link is a hyperlink from one page on a website to another page on the same website. Internal links help search engines discover your pages and pass ranking signals (PageRank and anchor-text context) between them., how the group is declared, what each
variant page needs). Pick the one your platform and catalog size actually support
well, and confirm the live markup matches whichever design you chose — don’t
assume the platform’s default matches what your theme or app is emitting.
The collection/product duplicate URL problem
The most common ecommerce canonical issue is a product reachable at multiple URLs:
-
Shopify:
/products/blue-shirtand/collections/summer/products/blue-shirt— Shopify auto-canonicalizes the collection URL back to/products/. This works correctly by default, but internal links should point to/products/only. -
WooCommerce: Similar with category base (e.g.
/product-category/shirts/blue-shirtvs/shop/blue-shirt). The Yoast or Rank Math plugin sets canonical tags; review your permalink structure to minimize duplicates. -
Magento: The layered navigation (filters) is the primary source of duplicate URLs. Configure canonical tags for filtered pages or block parameters in robots.txt.
-
BigCommerce: Product URLs can appear under multiple categories. BigCommerce has a “Canonical URL” setting per product that controls the preferred path.
Faceted navigation handling by platform
Start with intent, not platform mechanics: decide which filtered combinations (if any) deserve their own indexable landing page, and which are just crawl-budget inventory. Google’s guidance frames this as a choice between blocking facet URLs from crawlingCrawling is how search engines use automated bots (like Googlebot and Bingbot) to discover URLs and download pages. A page has to be crawlable to be indexed, but crawling on its own isn't a ranking factor. and optimizing the ones worth indexingStoring a crawled page in the search index so it can appear in results. Crawled is not the same as indexed — Google selects what to keep, and indexing isn't guaranteed. — the URL count can explode either way, so the strategy question comes first, then you map the chosen policy onto what the platform can implement.
- Shopify: Query parameters (
?filter.p.m.color=red) are indexed by default on some themes. Use robots metanoindexon filtered pages or add parameters to Search ConsoleGoogle's free tool for monitoring crawling, indexing, and search performance.’s URL Parameters tool. - WooCommerce: WOOCS/filter plugins generate parameter URLs. Combine
noindexon filtered pages with the Rank Math/Yoast URL parameter settings. - Magento (Adobe Commerce): Standard “Layered Navigation” generates attribute-filter URLs from catalog attributes; the catalog permissions and URL rewrites system gives fine-grained control, and canonical tags can be configured at the category level. Adobe Commerce’s separately licensed Live Search product uses its own filtered-navigation facets, which behave differently from standard layered navigation — confirm which one is actually configured before describing the store’s facet capabilities, since it depends on edition and add-on configuration, not just “Magento” as a label.
- BigCommerce: Faceted search URLs can be canonicalized to the base category via built-in settings under Store Settings → Search.
Paste the category parameter URLs your platform actually produces. The audit classifies only the supplied list—it does not crawl the store or decide which filter combinations deserve landing pages.
Map the parameter patterns with my free Faceted Navigation Auditor Free
- Export representative filter, sort, pagination, and tracking URLs from the platform or crawl.
- Separate valuable landing-page combinations from duplicate crawl inventory.
- Apply the platform-appropriate canonical, noindex, linking, or crawl rule and verify the resulting public URLs.
The auditor classifies the example shoes URL with color blue and size 10 as containing two filter parameters.
Ecommerce platform SEOPlatform SEO covers the SEO considerations specific to the technology a site is built on — CMS, website builder, headless stack, or JavaScript framework. Each platform has different defaults, constraints, and required configurations that affect crawling, indexing, and ranking. adds a layer of complexity on top of standard technical SEOTechnical SEO is the practice of making a site easy for search engines to crawl, render, index, and (now) be eligible for AI answers. It's the foundation that lets your content and links rank — not a ranking trick of its own.: product structured dataProduct schema (schema.org/Product) is structured data that tells search engines a page's product name, price, availability, and reviews so it can appear in Shopping-style rich results. It's separate from a Google Merchant Center feed, though Google reconciles the two., faceted navigationFaceted navigation (faceted search, product filtering) lets visitors refine a list of products or content by attribute — price, color, size, brand, rating. The SEO problem: each filter combination can spawn a distinct crawlable URL, turning a small catalog into millions of near-duplicate pages that waste crawl budget and dilute ranking signals. parameter handling, duplicate URLs from product variants and collections, out-of-stock product strategy, and paginationPagination splits a large set of content — product listings, blog archives, search results — across multiple sequentially numbered URLs. For SEO, each paginated page should be crawlable, indexable, and self-canonical; Google no longer uses rel=prev/next, but Bing still does.. No commerce platform is inherently superior for rankings — pick based on your store’s product, category, variant, feed, localizationLocalization is adapting content for a specific target market — not just translating the words, but adjusting currency, formats, idioms, cultural references, local search terms, and trust signals so the experience feels native., publishing, and operational requirements, then verify what the specific implementation (theme, app, module, plan, version) actually outputs, since defaults change and configuration can override them.
Shopify: Fixed URL structureURL structure is how the parts of a web address — scheme, domain, path, query string, and fragment — are organized and formatted. It mostly affects crawling, usability, and how engines understand a page, not rankings directly. (/products/, /collections/, /pages/, /blogs/). Auto-generates sitemapA sitemap is a file that lists the pages, images, videos, and other files on your site so search engines can discover them. It helps discovery, but submitting a sitemap doesn't guarantee crawling or indexing. and canonical tagsA rel=\"canonical\" annotation — in the HTML <head> or an HTTP Link header — that tells search engines which URL is the preferred version of duplicate or near-duplicate content.. The collection-product duplicate URL issue (a product accessible at both /products/slug and /collections/name/products/slug) is handled automatically via canonicalizationHow search engines pick one canonical URL among duplicates and consolidate signals onto it.. robots.txtA plain-text file at the root of a host that tells crawlers which URLs they may and may not request. It controls crawling, not indexing — a blocked URL can still be indexed if it's linked from elsewhere. is locked on standard plans; Shopify Plus allows customization. Product schemaProduct schema (schema.org/Product) is structured data that tells search engines a page's product name, price, availability, and reviews so it can appear in Shopping-style rich results. It's separate from a Google Merchant Center feed, though Google reconciles the two. is theme-dependent.
WooCommerce: WordPress-based, giving full SEO plugin control. Yoast SEO or Rank Math handle metadata, sitemapsA sitemap is a file that lists the pages, images, videos, and other files on your site so search engines can discover them. It helps discovery, but submitting a sitemap doesn't guarantee crawling or indexing., canonical tags, redirectsA redirect sends browsers and crawlers from a requested URL to a different one. An HTTP redirect specifically is a 3xx status code paired with a Location header; meta refresh and JavaScript redirects achieve a similar navigation without being a 3xx response themselves. Permanent redirects (301/308) are Google's signal the target should be canonical; temporary ones (302/303/307) aren't., and schema. Most flexible of the four; most configuration required. Product URL structureURL structure is how the parts of a web address — scheme, domain, path, query string, and fragment — are organized and formatted. It mostly affects crawling, usability, and how engines understand a page, not rankings directly. depends on WordPress permalink settings.
Magento (Adobe Commerce): Enterprise-grade flexibility. Built-in URL rewrites, canonical tags, and layered navigation configuration. Most SEO settings require developer or admin panel work. Strong at scale but high setup overhead.
BigCommerce: Sits between Shopify (ease) and Magento (power). Built-in SEO defaults are solid — auto sitemap, canonical tags, redirect manager, basic structured dataStructured data is a standardized way of labeling page content (using the schema.org vocabulary in JSON-LD, Microdata, or RDFa) so search engines can understand its meaning. It's not a direct ranking factor — its value is rich results and entity understanding.. Some flexibility on URL structure. Faceted search settings configurable in Store Settings.
Common to all platforms: product structured data (auto or via plugin/theme; eligible for rich resultsRich results (formerly 'rich snippets') are enhanced search listings — stars, images, prices, breadcrumbs, video thumbnails, and more — that Google and Bing build from structured data. They're a display feature, not a ranking factor, and eligibility never guarantees they'll show., not guaranteed to display), canonical handling for filter/variant URLs, sitemap coverage of products and categories, and redirect management for discontinued productsA discontinued product is an item you'll never sell again — the manufacturer stopped making it, or you dropped the line. The SEO decision is end-of-life: 301-redirect the URL to a genuinely similar replacement or the closest relevant category if it earned links or traffic, 404/410 it if it didn't, or keep it live as a Discontinued tombstone page only when it still helps users. This is distinct from a temporary out-of-stock product, which you keep live at 200.. Variant architecture has more than one documented design — one canonical product URL with ProductGroup data, or separate URLs per variant linked as a group — so match the design to the platform and catalog rather than assuming one URL count is correct. Faceted navigationFaceted navigation (faceted search, product filtering) lets visitors refine a list of products or content by attribute — price, color, size, brand, rating. The SEO problem: each filter combination can spawn a distinct crawlable URL, turning a small catalog into millions of near-duplicate pages that waste crawl budget and dilute ranking signals. strategy should start from whether a given filter combination deserves independent search visibility, then map that decision onto the platform’s mechanics; on Adobe Commerce, standard layered navigation and the separately licensed Live Search facets behave differently, so a facet capability claim needs to name which one is configured.
Ecommerce platform SEO audit checklist
All platforms
- Verify XML sitemapAn XML sitemap is a UTF-8 file listing the canonical URLs on your site (with optional lastmod) so search engines can discover and prioritize them. It's a discovery and diagnostic aid, not a guarantee of indexing — and Google ignores its priority and changefreq tags. includes all products and categories; excludes filtered/parameter URLs
- Confirm canonical tagsA rel=\"canonical\" annotation — in the HTML <head> or an HTTP Link header — that tells search engines which URL is the preferred version of duplicate or near-duplicate content. are present on every product and category page
- Check that faceted navigationFaceted navigation (faceted search, product filtering) lets visitors refine a list of products or content by attribute — price, color, size, brand, rating. The SEO problem: each filter combination can spawn a distinct crawlable URL, turning a small catalog into millions of near-duplicate pages that waste crawl budget and dilute ranking signals. URLs are blocked, noindexed, or canonicalized
- Verify product structured dataProduct schema (schema.org/Product) is structured data that tells search engines a page's product name, price, availability, and reviews so it can appear in Shopping-style rich results. It's separate from a Google Merchant Center feed, though Google reconciles the two. (Schema.orgSchema markup is code that uses the schema.org vocabulary to label what your content means so search engines can understand it and show rich results. It's most often written in JSON-LD, and it's not a direct ranking factor. Product) includes price, availability, reviews
- Set up redirectA redirect sends browsers and crawlers from a requested URL to a different one. An HTTP redirect specifically is a 3xx status code paired with a Location header; meta refresh and JavaScript redirects achieve a similar navigation without being a 3xx response themselves. Permanent redirects (301/308) are Google's signal the target should be canonical; temporary ones (302/303/307) aren't. for any product URL that changes (discontinuation, slug change)
- Review paginationPagination splits a large set of content — product listings, blog archives, search results — across multiple sequentially numbered URLs. For SEO, each paginated page should be crawlable, indexable, and self-canonical; Google no longer uses rel=prev/next, but Bing still does. — are page 2+ pages indexable and unique enough to justify it?
- Check out-of-stock product handling — 404, keep + update, or redirect?
Shopify-specific
- Keep internal product links pointing to
/products/not/collections/.../products/ - Review theme for product schemaProduct schema (schema.org/Product) is structured data that tells search engines a page's product name, price, availability, and reviews so it can appear in Shopping-style rich results. It's separate from a Google Merchant Center feed, though Google reconciles the two. injection — test with Rich ResultsRich results (formerly 'rich snippets') are enhanced search listings — stars, images, prices, breadcrumbs, video thumbnails, and more — that Google and Bing build from structured data. They're a display feature, not a ranking factor, and eligibility never guarantees they'll show. Test
- Use Shopify’s redirect manager for any URL changes
- On Shopify Plus: customize robots.txtA plain-text file at the root of a host that tells crawlers which URLs they may and may not request. It controls crawling, not indexing — a blocked URL can still be indexed if it's linked from elsewhere. to block thin URLs
WooCommerce-specific
- Install one SEO plugin (Yoast or Rank Math) — not both
- Set WooCommerce product permalink structure
- Configure the plugin’s product schema settings
- Handle WooCommerce archive pages (shop, product-category) — noindexNoindex is a directive that tells search engines to keep a page out of their index, so it won't appear in search results. It works only on pages a crawler can actually fetch — a page blocked in robots.txt can never be noindexed. thin ones
Magento-specific
- Configure canonical tagsA rel=\"canonical\" annotation — in the HTML <head> or an HTTP Link header — that tells search engines which URL is the preferred version of duplicate or near-duplicate content. for layered navigation URLs
- Review URL rewrite rules — remove unnecessary duplicates
- Configure robots.txtA plain-text file at the root of a host that tells crawlers which URLs they may and may not request. It controls crawling, not indexing — a blocked URL can still be indexed if it's linked from elsewhere. to block parameter URLs you don’t want crawled
- Enable Magento’s built-in HTML sitemapA sitemap is a file that lists the pages, images, videos, and other files on your site so search engines can discover them. It helps discovery, but submitting a sitemap doesn't guarantee crawling or indexing. + XML sitemapAn XML sitemap is a UTF-8 file listing the canonical URLs on your site (with optional lastmod) so search engines can discover and prioritize them. It's a discovery and diagnostic aid, not a guarantee of indexing — and Google ignores its priority and changefreq tags.
BigCommerce-specific
- Set canonical URL per product in product settings
- Review faceted search settings (Store Settings → Search)
- Verify sitemap submission in Search ConsoleGoogle's free tool for monitoring crawling, indexing, and search performance.
- Use BigCommerce’s built-in redirect manager for URL changes
Patrick's relevant free tools
- Google Index Checker — Check one URL’s observable indexability blockers, or reconcile sitemap, crawl, and supplied Search Console evidence across a URL set before verifying Google’s actual state in URL Inspection.
- Canonicalization Checker — Audit HTML and HTTP canonical signals, test the canonical target, and identify observable conflicts that can cause Google to choose a different URL.
- SEO Incident Simulator — Practice thirty deterministic technical SEO incident investigations — indexability, crawl controls, redirects, sitemaps, markup, caching, DNS, bot verification, rendering, hreflang, and faceted navigation — with clearly labeled fixture evidence and Find → Fix → Verify handoffs.
Tools for testing an ecommerce platform
- Faceted Navigation Auditor — inspect whether filter combinations create crawlable or indexable URL inventory.
- PDP SEO Checker — review product-page metadata, structured dataStructured data is a standardized way of labeling page content (using the schema.org vocabulary in JSON-LD, Microdata, or RDFa) so search engines can understand its meaning. It's not a direct ranking factor — its value is rich results and entity understanding., canonicals, and content signals using the platform’s real output.
- Sitemap Validator — verify that published product and category URLs appear once and point at canonical, successful destinations.
- Redirect Chain Mapper — test product retirement, category changes, and migrations for chains or irrelevant destinations.
Platform deep dives
- Shopify SEOShopify SEO is the practice of optimizing a Shopify store to rank in organic search. Shopify handles a lot for you automatically — canonical tags, an XML sitemap, SSL, a fast CDN — but it also imposes a fixed URL structure (/products/, /collections/, /pages/, /blogs/) and creates a duplicate URL for every product reachable through a collection, which the platform canonicalizes for you.
- WooCommerce SEOWooCommerce SEO is optimizing a WooCommerce store — which runs as a free plugin on WordPress, not as a standalone platform — to rank in organic search. Because you control the whole stack (templates, URLs, plugins, server), the ceiling is high and the ways to misconfigure it are many.
- Magento SEOMagento SEO is optimizing a store built on Magento — now Adobe Commerce (paid) or Magento Open Source (free), both running the Magento 2 codebase — to rank in organic search. The defining challenge is layered navigation (faceted filtering), which can spawn huge numbers of duplicate parameter URLs.
- BigCommerce SEOBigCommerce SEO is the technical, on-page, and content work you do on a store built on BigCommerce — a hosted SaaS ecommerce platform that ships with more native SEO controls than most of its rivals (editable robots.txt, custom URL structures, auto sitemaps, and automatic 301s), while still leaving faceted navigation, multi-storefront hreflang, and review schema for you to handle.
- Salesforce Commerce Cloud SEOSalesforce Commerce Cloud SEO is the technical, on-page, and international work you do on a storefront built on Salesforce B2C Commerce (formerly Demandware, commonly SFCC) — an enterprise SaaS platform that ships strong native SEO building blocks (Business-Manager-editable robots.txt, scheduled auto-generated sitemaps, rule-based meta tags, canonical-by-design master/variation products) but leaves hreflang, faceted-navigation URLs, schema, and PWA Kit crawlability to deliberate, platform-literate configuration.
- Shopware SEOShopware SEO is the technical, on-page, and international work you do on a store built on Shopware 6 — a German-built, open-source-core ecommerce platform (Symfony/PHP + Vue.js storefront) that ships a large amount of native SEO out of the box (Twig-templated SEO URLs, canonical handling, XML sitemaps, hreflang via its Sales Channel/Domain model, and — in recent versions — native robots.txt and JSON-LD structured data), while still leaving bulk meta management, variant-canonical edge cases, cross-sales-channel hreflang, and headless (Composable Frontends) rendering to you.
- OpenCart SEOOpenCart SEO is the technical and configuration work needed to make a store built on OpenCart — a free, open-source, self-hosted PHP ecommerce platform — visible in search. Unlike SaaS platforms, OpenCart ships with SEO mostly turned off: friendly URLs, sitemaps, and structured data all require you to flip switches, rename a file, install extensions, or fill in fields the platform leaves empty by default.
- Ecwid SEOEcwid SEO is the technical, on-page, and content work you do on a store built with Ecwid (now Ecwid by Lightspeed) — an embeddable ecommerce widget that drops into an existing website. Because Ecwid is a JavaScript storefront by default rather than a hosted site, its SEO behavior (URL format, crawlable static HTML, auto sitemap and robots.txt) is scoped to a handful of integrations (Instant Site, the WordPress plugin, and the Wix app) and left to you everywhere else.
- Wix eCommerce SEOWix eCommerce SEO is the technical, on-page, and content work you do on a store built on Wix Stores — the commerce layer that sits on top of general Wix SEO, adding a /product-page/ URL prefix, auto-generated Product JSON-LD, a dedicated store-products-sitemap.xml, and platform limits around bulk editing, product variants, and per-language currency that general Wix advice doesn't cover.
- Squarespace Commerce SEOSquarespace Commerce SEO is the work of optimizing a Squarespace-hosted online store — product pages, category/store pages, variants, sold-out handling, and commerce structured data — for organic search. It sits on top of general Squarespace site SEO and adds its own mechanics: per-product SEO fields, auto-generated Product schema, category pages that can't take custom SEO settings, a single-URL variant model that sidesteps variant-URL duplication, version-dependent product-count limits, and a US-only, physical-goods-only Google Merchant Center integration.
- PrestaShop SEOPrestaShop SEO is the technical, on-page, and module-level work you do on a store built on PrestaShop — an open-source (PHP/MySQL) ecommerce platform that hands you strong native meta-tag and friendly-URL controls plus configurable canonical redirects, but leaves hreflang, comprehensive schema, faceted-navigation canonicals, and an auto-refreshing multilingual sitemap to third-party modules. (lives in the Ecommerce Platforms cluster)
Related reading
- Ecommerce SEOEcommerce 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.
- Faceted Navigation SEOFaceted navigation (faceted search, product filtering) lets visitors refine a list of products or content by attribute — price, color, size, brand, rating. The SEO problem: each filter combination can spawn a distinct crawlable URL, turning a small catalog into millions of near-duplicate pages that waste crawl budget and dilute ranking signals.
- Product Page SEOProduct page SEO is the practice of optimizing an individual product detail page (PDP) so it ranks in organic search and earns rich results. It blends unique product copy, structured data, variant canonicalization, image SEO, and customer reviews — but the structured data earns rich results and eligibility for free product listings, it doesn't make the page rank.
Mistakes stores actually make on these platforms
Linking internally to the collection-prefixed product URL on Shopify
Internal linksAn internal link is a hyperlink from one page on a website to another page on the same website. Internal links help search engines discover your pages and pass ranking signals (PageRank and anchor-text context) between them., nav menus, and related-product blocks that point to
/collections/summer/products/blue-shirt instead of /products/blue-shirt.
Why it’s wrong — Shopify auto-canonicalizes the collection-prefixed URL back to the plain product URL, so it usually doesn’t create indexedStoring a crawled page in the search index so it can appear in results. Crawled is not the same as indexed — Google selects what to keep, and indexing isn't guaranteed. duplicates. But every internal linkAn internal link is a hyperlink from one page on a website to another page on the same website. Internal links help search engines discover your pages and pass ranking signals (PageRank and anchor-text context) between them. built the long way still spends crawl budgetThe number of URLs an engine will crawl in a timeframe. and link equityPageRank is Google's original recursive link-graph algorithm: a page's score depends on the scores of the pages linking to it, and in the published model each page's score is split across its outbound links (the simplified version: links are weighted votes). Google says it's evolved since launch but still part of its core ranking systems. on a URL that immediately redirectsA redirect sends browsers and crawlers from a requested URL to a different one. An HTTP redirect specifically is a 3xx status code paired with a Location header; meta refresh and JavaScript redirects achieve a similar navigation without being a 3xx response themselves. Permanent redirects (301/308) are Google's signal the target should be canonical; temporary ones (302/303/307) aren't. its signal elsewhere instead of pointing straight at the canonical page.
What to do instead — Build theme links from the product handle directly
(/products/{{ product.handle }}), not from the collection context, so internal
links go straight to the canonical URLHow search engines pick one canonical URL among duplicates and consolidate signals onto it..
Running two SEO plugins at once on WooCommerce
Installing both Yoast SEO and Rank Math (or another pair) because “more coverage is better.”
Why it’s wrong — Both plugins generate their own sitemapA sitemap is a file that lists the pages, images, videos, and other files on your site so search engines can discover them. It helps discovery, but submitting a sitemap doesn't guarantee crawling or indexing., canonical tagsA rel=\"canonical\" annotation — in the HTML <head> or an HTTP Link header — that tells search engines which URL is the preferred version of duplicate or near-duplicate content., and meta output. When two plugins both try to own the same field, you get conflicting canonicals or duplicate sitemapA sitemap is a file that lists the pages, images, videos, and other files on your site so search engines can discover them. It helps discovery, but submitting a sitemap doesn't guarantee crawling or indexing. files — exactly the kind of self-inflicted duplicate-content problem ecommerce SEOEcommerce 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. is supposed to prevent.
What to do instead — Pick one plugin, deactivate the other completely, and verify in page source that only one canonical tagA rel=\"canonical\" annotation — in the HTML <head> or an HTTP Link header — that tells search engines which URL is the preferred version of duplicate or near-duplicate content. and one meta descriptionThe meta description is an HTML head tag — `<meta name=\"description\" content=\"…\">` — that suggests a short summary of the page for the search snippet. It's not a Google ranking factor, and Google rewrites it the majority of the time, but a good one can still lift click-through. are being output.
Leaving faceted navigation fully crawlable and indexable
Shipping filter combinations (?color=red&size=M) with no noindex, no
canonicalizationHow search engines pick one canonical URL among duplicates and consolidate signals onto it., and no robots.txtA plain-text file at the root of a host that tells crawlers which URLs they may and may not request. It controls crawling, not indexing — a blocked URL can still be indexed if it's linked from elsewhere. handling — on any of the four platforms.
Why it’s wrong — A store with even a modest number of filter attributes can generate thousands of near-duplicate parameter URLs. CrawlersA crawler — also called a spider or bot — is an automated program that fetches web pages, extracts their links, and queues new URLs to visit. Search engines use crawlers to discover and download content for their index. spend budget on them instead of your actual products and categories, and it’s the single most common ecommerce indexingStoring a crawled page in the search index so it can appear in results. Crawled is not the same as indexed — Google selects what to keep, and indexing isn't guaranteed. problem across every platform in this comparison.
What to do instead — Canonicalize filtered URLs to the base category page (or
noindex them if they need to stay crawlable for ads/UX), and confirm which
parameters Search ConsoleGoogle's free tool for monitoring crawling, indexing, and search performance. is actually seeing before you decide what to block.
Discontinuing a product without a redirect plan
Deleting a product and letting its URL 404 because “it’s out of stock now.”
Why it’s wrong — Any inbound links or ranking history that URL accumulated just evaporate. A hard 404 on a page that used to rank sends both users and link equity nowhere.
What to do instead — Decide per product whether to keep the page live with “out of stock” structured dataStructured data is a standardized way of labeling page content (using the schema.org vocabulary in JSON-LD, Microdata, or RDFa) so search engines can understand its meaning. It's not a direct ranking factor — its value is rich results and entity understanding. (if it’ll return), 301 it to the closest replacement or parent category (if it won’t), or only 404 it once nothing points to it anymore.
Assuming product schema is automatic
Treating Schema.org Product markup as a given because “the platform handles
that.”
Why it’s wrong — Coverage varies a lot by platform: it’s theme-dependent on Shopify, requires a plugin on WooCommerce, needs a module on Magento, and is only basic by default on BigCommerce. Assuming it’s there and moving on is how price and availability data goes missing from rich resultsRich results (formerly 'rich snippets') are enhanced search listings — stars, images, prices, breadcrumbs, video thumbnails, and more — that Google and Bing build from structured data. They're a display feature, not a ranking factor, and eligibility never guarantees they'll show. without anyone noticing.
What to do instead — Check actual product pages with the Rich Results Test rather than trusting platform marketing copy, and fix gaps at the theme/plugin level rather than page by page.
Leaving Magento’s layered navigation unconfigured
Turning on layered (faceted) navigation for attributes like color, size, and brand without setting canonical or indexing rules for the URLs it generates.
Why it’s wrong — Layered navigation is the single largest source of duplicate URLs on Magento specifically, because filter combinations multiply fast. Left unconfigured, it can produce far more crawlable URLs than the store actually has products.
What to do instead — Configure canonical tags at the category level and block the parameter combinations you don’t want crawled, before the catalog grows large enough for it to become a crawl-budget problem.
Build-time retrieval analysis plus live signals for this exact article. The automatic chunk report includes a deterministic readiness score and is ready without a model download.
Search Console
sampleGA4 traffic (28d)
sampleCloudflare traffic (7d)
sampledCrUX field data (28d, phone)
sampleGoogle NLP entities
localChangelog
Updated Jul 26, 2026.
Editorial summary and recorded change details.Summary
Removed the retired duplicate-content checker from the platform-testing toolkit.
Change details
-
The remaining recommendations cover facets, PDP output, sitemaps, and redirects.
Full comparison unavailable — no prior snapshot was archived for this revision.
Updated Jul 18, 2026.
Editorial summary and recorded change details.Summary
Replaced the implied platform-ranking framing with a requirements-and-ownership selection method, and generalized the variant-URL and faceted-navigation guidance to match Google's documented range of supported approaches instead of one prescribed pattern.
Change details
-
Added a platform selection method that evaluates product, category, variant, feed, localization, publishing, and operational requirements instead of ranking platforms.
-
Documented that Google's Product structured data supports both one-canonical-URL and separate-variant-URL architectures via ProductGroup, rather than treating one URL count as correct.
-
Distinguished Adobe Commerce's standard layered navigation from its separately licensed Live Search facets, since a facet capability claim depends on which is configured.
-
Added an explicit no-inherent-ranking-advantage statement: platform architecture constrains and enables an implementation, but crawlability, structured data accuracy, performance, content, links, and ongoing operations are what determine outcomes.
Full comparison unavailable — no prior snapshot was archived for this revision.