PublishedVerifiedEvery 6 weeksSources4 namedAuthored bySquareRank Team
E-commerce SEO · Duplicate Content · § 2.7.4
Duplicate Product Content on Squarespace
Squarespace Commerce produces near-duplicate content in three predictable places1: variant URLs (?variant=X share the base product URL), sort-order and filter URLs on category pages (?sort=newest, ?category=A), and the cross-site duplication that happens when product descriptions are copied verbatim from manufacturer feeds. The first two are handled correctly by Squarespace's default canonical behaviour in 2026; the third is owner-implemented and produces most of the audit findings.
This page covers the three duplication patterns, the View Source audit, and the canonical-tag override for the rare template where defaults fail. Pair this with the product description leaf for the rewrite framework that resolves the manufacturer-feed pattern.
§01The three patterns
The three duplication patterns Squarespace Commerce produces
Pattern one is variant URLs — a product with multiple sizes or colours shares a single product URL with query-string variants. Pattern two is sort and filter URLs on category pages — sorting by 'newest' or filtering by sub-category produces a new URL with the same content reordered. Pattern three is cross-site manufacturer-feed duplication — product descriptions copied verbatim from manufacturer feeds appear identically on many stores. The first two are technical patterns handled by canonical tags; the third is an editorial pattern handled by rewriting copy.
Google's canonical-tag documentation1 describes all three as standard e-commerce SEO concerns. Duplicate content does not produce a manual-action penalty2 in 2026 — Google has been clear about that since 2014 — but it does dilute ranking signals when not canonicalised, because Google has to pick a single URL to attribute backlinks and engagement signals to. The canonical tag tells Google which URL to consolidate the signals into.
What Squarespace handles vs what you handle
Default
Squarespace canonical handling for variant URLs and sort-order URLs — usually correct out of the box.
Squarespace Commerce products with multiple variants (sizes, colours, configurations) share a single base URL. The variant selection updates the page state via JavaScript and adds a ?variant=X query string to the URL. Google reads both the bare URL and the variant URL as the same page (because the rendered HTML is similar) and the canonical tag points at the bare URL, consolidating ranking signals into the canonical product page rather than dispersing across variants.
The default canonical behaviour is correct for almost every store. The exception: stores that want each variant to rank separately (e.g. a stationery store where each colour of notebook is a meaningfully different product). For those stores, the workaround is to create separate Squarespace products for each variant rather than using the variant system — which is exactly what stores selling materially different items already do.
§03Sort and filter
Sort and filter query strings on category pages
Category pages on Squarespace Commerce accept sort and filter query strings — ?sort=newest, ?sort=price-asc, ?category=accessories — which reorder the product grid without changing the content. The canonical tag on these query-string variants points at the bare category URL, consolidating signals into the canonical category page. Google reads the canonical and treats the sort/filter URLs as views of the same page.
The behaviour is consistent across 7.1 templates as of 2026. Earlier Squarespace versions occasionally rendered self-referencing canonicals (the canonical on /shop/category/juicers?sort=newest pointed at itself rather than at /shop/category/juicers), which produced minor signal dispersion. The fix on legacy templates is to add an explicit canonical via page-level Code Injection pointing at the bare category URL.
§04Manufacturer feeds
Cross-site manufacturer-feed duplication
The most-common duplicate-content pattern on Squarespace Commerce stores is cross-site duplication — product descriptions copied verbatim from manufacturer feeds appear identically on every store carrying that product. Google's helpful-content classifier has been good at detecting this pattern since 2022, and stores that ship manufacturer feeds verbatim across many products consistently underperform stores that rewrite descriptions in their own voice. The fix is editorial, not technical: rewrite each product description with 200-400 words of original content.
The pattern is more common than store owners realise. A boutique reselling a popular brand often imports the brand's product catalogue with descriptions intact; an Amazon-affiliate-adjacent store copies Amazon's description; a dropshipper carries the supplier's description across every product. In all three cases, the same exact 100-300 words appears on dozens or hundreds of other stores, and Google has to pick one to attribute the rank to — and the chosen winner is almost never the smallest store in the duplication set.
The rewrite framework — 250 words of original content per product, with your sourcing, fit notes, sensory descriptors, and comparison context — is covered in the product description leaf. This is the single change with the largest impact on a duplicate-content audit; everything else on this page is technical sanity-checking by comparison.
§05Audit
Auditing the canonical tag with View Source
The audit is a 90-second pass per store. Open a representative product variant URL in the browser, View Source, search for 'canonical', verify the value. Open a representative category page with a sort applied, View Source, search for 'canonical', verify the value. Open Search Console, run URL Inspection on the canonical URL, verify that Google's chosen canonical matches. If all three match, the technical canonical layer is correct and the audit moves on to the editorial layer (the manufacturer-feed rewrite).
The Search Console verification is the part that often surfaces conflicts. Google occasionally chooses a different canonical than the one declared on the page — usually because backlinks or internal links point at a slightly different URL pattern (with or without trailing slash, with or without HTTPS, with or without www). The conflict shows up in Search Console's URL Inspection as 'Google selected a different canonical than user'. The fix is to either accept Google's choice (if the chosen canonical is reasonable) or to add explicit canonical tags and adjust internal links to consistently point at the declared canonical.
HTMLExplicit canonical override via Squarespace page-level Code Injection
