How do Squarespace product variants (size, color) affect duplicate content?

Variants live as dropdowns on a single product URL, so there is no per-variant duplicate-content problem

Each variant combination gets its own URL, so you must canonicalize them

Variants are automatically noindexed to avoid duplication

Squarespace 404s all but the first variant

What is the sharpest commerce-specific SEO limitation on Squarespace?

Category and sub-category pages cannot have custom SEO title/description settings

Product pages have no SEO title or description fields

Squarespace does not generate any product schema

Sold-out products are automatically deleted

What does Squarespace do to a product page when the item sells out?

Keeps the page live and indexed with a customizable Sold Out label

Redirects it to the category page

Automatically applies a noindex tag

Returns a 404 until the item is restocked

Which is a real requirement of Squarespace's native Google Shopping (Merchant Center) integration?

You must be located in the United States with site language set to English (United States) and sell physical products

It works for digital products and subscriptions worldwide

It includes a native Bing Shopping feed

It requires a multi-client Merchant Center account

How many products can a single Squarespace store page hold, by version?

Up to 200 on version 7.0 and up to 10,000 on version 7.1

Squarespace Commerce SEO

TL;DR — 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. is SEO for a Squarespace store specifically — your product pages, category pages, and product listings — as opposed to your general Squarespace site. Each product gets its own SEO titleThe title tag is the HTML title element in a page's head that specifies the document's title. It's the primary source for the SERP title link and a confirmed light ranking factor — but since August 2021 Google doesn't always show it verbatim. and description box, and Squarespace automatically adds the behind-the-scenes product data (price, in-stock/out-of-stock) that can earn you a richer search result. The Category-page controls and the native Google Merchant connection have platform, product, and market constraints, so check the current Squarespace requirements.

What “Squarespace Commerce SEO” means

If you sell products on Squarespace, you’re running a store on top of a regular Squarespace site. General Squarespace SEOSquarespace SEO is the practice of optimizing a Squarespace-hosted site to rank in organic search. Squarespace handles much of the technical baseline automatically — HTTPS, CDN delivery, an XML sitemap, canonical tags, and basic metadata — but its closed SaaS architecture creates hard limits: no robots.txt editing, no sitemap customization, a fixed set of auto-generated schema you can't remove, and no code injection on individual blog posts. covers the site-wide basics — the automatic 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., 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.', 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 the big gotcha that changing a URL doesn’t create a 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 you. This guide is about the commerce parts that sit on top of that: your products, your product categories, and getting them foundA 302 (\"Found\") is a temporary redirect: it forwards users to a new URL while telling search engines the original URL should stay in the index. It's a weak canonicalization signal, not the zero-equity dead end of SEO folklore. and shown in search.

What Squarespace handles for your store automatically

Product SEO fields. Every product has its own SEO title and description box, separate from your site settings. You write these; if you skip the description, Squarespace falls back to your product description text.
Product data for search (schema). Squarespace automatically adds “structured data” to your product pages — price and whether the item is in stock — which is what can give you a nicer-looking result in Google.
Variant pages stay tidy. When a product comes in sizes or colors, Squarespace keeps them all on one product page with a dropdown. It does not create a separate web address for every size/color combination — so there’s no messy duplicate-page problem to clean up (which is a real headache on some other platforms).
Sold-out products stay up. When something sells out, Squarespace keeps the page live with a “Sold Out” label instead of deleting it. That’s actually the right move for SEO — you keep the page’s rankings for when it’s back in stock.
Google ShoppingGoogle Merchant Center (GMC) is a free platform where retailers upload and manage product data so their products can appear across Google — Shopping, organic Search product grids, Images, Lens, and AI surfaces. Since 2020 it powers free (organic) product listings, not just paid Shopping ads. (with strings attached). Squarespace can send your products to Google Shopping through a built-in Google connection — but only if you’re based in the US, your site language is English (United States), and you sell physical products.

What you still have to handle

Category pages can’t get custom SEO settings. Unlike your regular pages and your individual products, the category pages Squarespace builds from your product tags/categories don’t have their own SEO title/description boxes. This is the single biggest limitation to know about.
Write real product descriptions. Don’t paste the manufacturer’s copy. Unique, helpful descriptions are what help a product page rank.
Reviews don’t add star ratings to search. Squarespace has a customer-reviews feature, but there’s no sign it feeds the “star rating” data that shows up in Google. If you want review stars, that’s a manual, custom-code job.

The thing most people get wrong

People assume Squarespace either “has no product feed for Google” (it does — just a narrow one) or that its category pages work like Shopify’s (they don’t — no custom SEO fields). Both assumptions cost you. Know what’s automatic, what’s limited, and what’s simply not there, and you’ll spend your effort in the right places.

Want the practitioner version — the character limits, the exact schema gaps, the 200-vs-10,000 product limit, and where Squarespace beats Shopify (and where it loses)? Switch to the Advanced tab.

TL;DR — 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. is the store layer on top of the platform baseline. Products expose their own SEO titleThe title tag is the HTML title element in a page's head that specifies the document's title. It's the primary source for the SERP title link and a confirmed light ranking factor — but since August 2021 Google doesn't always show it verbatim./description (Squarespace suggests 50–300 characters, 400 max) and auto-generate 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. with price and availability. The structural win is real: variants render as dropdowns on a single product URL, so there’s no per-variant duplicate-content problem to canonicalize — unlike Shopify or Magento variant-URL sprawl. The ceilings are equally real: category/sub-category controls, generated schema fields, catalog limits, and the native Google ShoppingGoogle Merchant Center (GMC) is a free platform where retailers upload and manage product data so their products can appear across Google — Shopping, organic Search product grids, Images, Lens, and AI surfaces. Since 2020 it powers free (organic) product listings, not just paid Shopping ads. integration vary by Squarespace version and eligibility. Sold-out pages stay live and 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. — which matches current best practice.

The frame: scope this against general Squarespace SEO

Most “Squarespace 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.” content re-explains 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., 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.', and canonical tags — all of which are site-wide platform behavior that applies whether or not you sell anything. I’ve kept that in the general Squarespace SEOSquarespace SEO is the practice of optimizing a Squarespace-hosted site to rank in organic search. Squarespace handles much of the technical baseline automatically — HTTPS, CDN delivery, an XML sitemap, canonical tags, and basic metadata — but its closed SaaS architecture creates hard limits: no robots.txt editing, no sitemap customization, a fixed set of auto-generated schema you can't remove, and no code injection on individual blog posts. guide (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. lockdown, the no-auto-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.-on-URL-change gotcha, the six auto-generated schema types, AMPAMP (Accelerated Mobile Pages) is an open-source web framework Google launched in 2015 to make mobile pages load near-instantly via restricted HTML/CSS/JS and CDN caching. It was never a ranking factor and, since June 2021, is no longer required for Top Stories.’s February 2025 deprecation, Core Web VitalsGoogle's three real-user UX metrics — LCP (loading), INP (responsiveness), and CLS (visual stability) — used by Google's ranking systems, with no official weight attached, measured on field data. generalities). This guide is only the commerce-specific mechanics: product-page fields, category-page limits, variants, catalog size, sold-out handling, Product schema completeness, reviews, and the Merchant Center feed. Where a topic is site-wide, I link out instead of repeating it.

Product page SEO fields

Products get their own SEO panel, separate from the site-level SEO settings. Editing a product, you open the SEO tab (or the SEO and URL section in the newer editor) to set the SEO title and description and to customize the product’s URL slug. Squarespace’s guidance is to keep the SEO description roughly 50–300 characters, with a hard 400-character limit. If you leave it blank, the engine falls back to the product description as the meta text — so an empty SEO description isn’t “no description,” it’s “whatever’s in your product body copy, truncated.”

The practical takeaway is the same one Kristine Neil makes in her Squarespace product-page SEO writing: write unique, keyword-considered descriptions rather than pasting manufacturer copy, because that’s the content that actually earns the ranking. Fill the SEO title and description on every product that matters; don’t rely on the fallback.

Note the product URL path convention: Squarespace product detail pages live under a /store/ (or your store page’s) path segment by default — worth knowing when you’re mapping redirects or reading crawl data. And the same platform-wide gotcha from the general guide applies here with a commerce-specific trigger: renaming a product slug does not auto-create a 301. Rebrand a SKU, change its slug, and you’ve broken every inbound link and lost the page’s equity unless you add the redirect yourself in URL Mappings first. On a store, slug changes are common (seasonal renames, SKU rationalization), so this bites more often than on a static site.

Category / store page SEO — the sharpest ceiling

Here’s the limitation that competitors gloss over: category and sub-category pages generated from your product taxonomy cannot have their own custom SEO title and description. Top-level pages get an SEO panel. Individual products get an SEO panel. The category pages built from your product categories/tags do not — you can’t hand-write their meta title or description the way you can on Shopify or WooCommerce, where collection pages get full meta control.

Categories and tags are indexed — Squarespace says so directly, and they help site-search too — but “indexed” isn’t the same as “optimizable.” You can’t tune the title tagThe title tag is the HTML title element in a page's head that specifies the document's title. It's the primary source for the SERP title link and a confirmed light ranking factor — but since August 2021 Google doesn't always show it verbatim. or 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. of a category listing page. This is the single biggest category-page SEO gap versus Shopify/WooCommerce, and it’s under-documented; beyond the community-forum corroboration, Squarespace’s own title-format help doc confirms it directly: “It’s not possible to customize the title format when linking to content filtered by a category or tag.” It’s the reason practitioners reach for custom code (see below) to influence how collection pages render at all.

One more nuance from the docs: when you add a new category to an unpublished collection item, that category isn’t added or indexed until the item is published — so category pages only “exist” for search once they have live products in them.

Product variants: the single-URL model (a genuine advantage)

This is where Squarespace quietly beats most ecommerce platforms on a classic SEO problem. Product variants — size, color, material — display as dropdown selectors on a single product URL. Squarespace does not mint a separate URL per variant combination. Compare that to a Shopify or Magento setup where each variant can spawn its own crawlable URL, and you inherit a duplicate-content problem you then have to canonicalize away.

On Squarespace, that problem mostly doesn’t exist. One product, one URL, one canonical — the canonicalizationHow search engines pick one canonical URL among duplicates and consolidate signals onto it. headache that plagues variant-URL platforms simply doesn’t apply here. The limits: up to 6 options and 250 variant combinations per product, and variants can’t be added to download (digital) products.

The tradeoff is the flip side of the same coin: because there’s only one URL, there’s no built-in way to deep-link to a pre-selected variant (e.g. link an ad straight to “the blue one”). Doing that requires custom JavaScript. So Squarespace trades away variant deep-linking to buy you clean canonicalizationHow search engines pick one canonical URL among duplicates and consolidate signals onto it. — a good trade for most stores, occasionally annoying for paid campaigns pointing at a specific SKU variant.

Catalog size: the 200 vs 10,000 product limit

Store page product counts are version-dependent, and it’s an SEO/crawl-architecture issue, not just a features footnote:

Squarespace 7.1: a store page can hold up to 10,000 products (also the site-wide cap).
Squarespace 7.0: a store page is capped at 200 products (site-wide cap still 10,000).

For a large catalog on 7.0, that 200-per-page ceiling forces you to split products across multiple store pages or collections — which fragments your 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. equity and crawl paths across extra pages you didn’t want. If you’re on 7.0 with a big catalog, the store-page limit is a real reason to plan a migrationA site migration is any significant change to a website's URL structure, domain, platform, protocol, or hosting that can affect how search engines crawl, index, and rank it. The risk scales with how much you change at once. to 7.1 rather than papering over it with awkward extra collections.

Sold-out and out-of-stock products

Squarespace’s default behavior here aligns with current best practice. When a product sells out, the page stays live and indexed with a customizable “Sold Out” label; customers can’t add it to the cart, but Squarespace does not auto-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., 404, or redirect the page. Squarespace even frames displaying sold-out products as a way to advertise demand.

That’s the SEO-correct default. Google’s out-of-stock guidance is to keep the page live rather than 404 or noindex it, so you preserve its rankings and links for when the item returns — see out-of-stock productsEcommerce 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. for the platform-agnostic treatment. On Squarespace you don’t have to do anything to get this right; just resist the urge to “clean up” by deleting sold-out pages, and keep optimizing the title/meta while the item’s out. Customize the label text if “Sold Out” doesn’t fit your brand.

Product structured data: what’s automatic, what’s missing

Squarespace auto-generates 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. on commerce pages, and you can neither remove nor natively edit it. It covers the core fields — price and availability — which is enough to be eligible for basic product 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.. But measured against Google’s Product structured data spec, the auto schema has documented gaps: Google’s product-snippet requirements formally require only name plus one of offers, review, or aggregateRating — but a genuinely useful listing in practice also needs image, price, and availability, and Google recommends going further with aggregateRating/review, hasMerchantReturnPolicy, and shippingDetails. Practitioners (e.g. Collaborada’s schema write-up) flag missing fields like hasMerchantReturnPolicy; return policy and full review/rating markup aren’t in the built-in output.

Because you can’t edit the native schema, the standard practice is to supplement via Code Injection / a Code Block with your own JSON-LDJSON-LD (JavaScript Object Notation for Linked Data) is a script-based structured data format, typically paired with the schema.org vocabulary to describe page content for search engines and AI systems. Google recommends it over Microdata and RDFa because it's the easiest format to implement and maintain at scale — but all three work, and structured data isn't a ranking signal. for the missing fields — that’s normal, not a sign you did something wrong. Two cautions: don’t emit conflicting Product/Offer data that contradicts the auto schema, and keep any review/rating markup you add tied to genuine on-page reviews. (For the field-by-field detail, see product schemaMeta tags are HTML elements in a page's head that pass metadata about the page to search engines and browsers. For SEO only a few matter — the title element, the meta description, and the robots meta tag — while meta keywords and most others are ignored. and the broader structured dataMeta tags are HTML elements in a page's head that pass metadata about the page to search engines and browsers. For SEO only a few matter — the title element, the meta description, and the robots meta tag — while meta keywords and most others are ignored. treatment.)

TIP Verify Squarespace's automatic Product and Offer output

Automatic schema still depends on the catalog values and final template output. Test the public page after product, variant, price, or availability changes.

Run a focused product-page preflight with my free PDP SEO Checker Free

Test representative products, variants, and sold-out states.
Confirm Product, Offer price, and availability appear in the delivered markup.
Fix catalog or custom-template output, rerun, and validate the rendered page with Google.

Missing Squarespace Product and Offer output. — The live output is missing the automatic commerce graph the catalog is expected to supply.

Customer reviews — and the structured-data gap

Squarespace has a native customer reviews feature: customers can leave a written review (up to 1,500 characters) and a 1–5 star rating per item, with the request sent roughly 14 days after fulfillment and a 120-day review window. Useful for conversion and on-page content.

The SEO gap: the docs describe display mechanics but say nothing about structured data, and practitioner consensus is that these reviews do not automatically populate Review/AggregateRating schema. So the stars show up on your product page for shoppers, but there’s no documented path from the native reviews feature to review-rating rich results in search. If review stars in the SERP matter to you, that’s another Code-Injection JSON-LD job — again, tied to the real reviews on the page. This is a genuine gap versus platforms with native review-schema plugins.

Google Shopping: the native feed and its hard limits

This corrects a common myth. You’ll read that “Squarespace has no product feed for Google Shopping” — not true. Squarespace has a native Google Merchant CenterGoogle Merchant Center (GMC) is a free platform where retailers upload and manage product data so their products can appear across Google — Shopping, organic Search product grids, Images, Lens, and AI surfaces. Since 2020 it powers free (organic) product listings, not just paid Shopping ads. integration that pushes your catalog into Google Shopping. But it’s gated, and the gates are strict. To use it you must:

Be located in the United States and set your site language to English (United States).
Sell physical products (digital products, services, subscriptions, and memberships are excluded).
Add a shipping option in Squarespace.
Be on a qualifying plan (Core, Plus, Advanced, Commerce Basic, or Commerce Advanced).
Have a Google Merchant Center account (multi-client accounts aren’t supported), with 200 or fewer data sources linked to it.

So the myth is half-right in spirit: the feed exists, but it’s useless to international sellers, digital-product sellers, and anyone on Bing — Squarespace has no native Bing Shopping integration. Squarespace’s own auto-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. includes your product and category URLs, but there’s no separate product-feed sitemap format; the Merchant Center integration is the feed mechanism. If you’re outside the US or selling non-physical products and you need Shopping visibility, you’re building a feed by other means — the native integration won’t cover you.

Subscriptions, digital, and membership products

These are a structurally different commerce case. Subscription products (subscription boxes, recurring goods/services), digital downloads, and memberships are not eligible for the Google Shopping integration above — that feed is physical-goods-only. They also carry different transaction-fee tiers by plan (higher plans reduce or zero out fees on courses/memberships/digital products), which is why sellers pick these product types and then ask “why isn’t my course in Google Shopping?” The answer is structural, not a misconfiguration: the feed doesn’t accept them. SEO for these products leans back on the fundamentals — strong product/landing pages, real descriptions, internal links — rather than any feed-driven distribution.

The practitioner workaround: custom collection code

Because collection/category pages are so uniform and can’t take custom SEO settings, the practitioner-standard workaround is custom code to style and customize individual collection pages — Will Myers-style code snippets are the community reference point for this. I’m flagging it as a workaround, not endorsing any specific paid product: it’s how experienced Squarespace builders get around the platform’s uniform collection-page limitation when a client needs collection pages that don’t all look and behave identically. Treat it as a last resort after you’ve exhausted the native options, and remember custom code is yours to maintain across Squarespace updates.

Squarespace vs Shopify for ecommerce SEO specifically

Keep this narrow — the general platform comparison lives in the sibling articles; here it’s only the commerce-SEO differences that matter:

	Squarespace Commerce	Shopify
Variant URLs	Single URL, dropdown (no dup content)	Can generate per-variant URLs
Category page SEOCategory page SEO is the practice of optimizing an ecommerce listing page (also called a PLP or collection page) — the page that groups products under a classification like /shoes/running/ — so it ranks for broad commercial queries and routes crawlers and link equity to the products beneath it. fields	None (can’t customize)	Full custom meta on collections
Redirect on URL change	Manual (URL Mappings first)	Auto-prompted 301 on URL change
Product feed	Native GMC (US/English-US/physical only)	Broad app/feed ecosystem
Bing Shopping	No native integration	Broader app options
Product schema	Auto (price/availability), gaps	App required, more complete

Shopify’s genuine ecommerce-SEO edge is automated technical control — it prompts you to create a 301 the moment you change a URL, and it has a far broader feed/app ecosystem. Squarespace’s genuine edge is the cleaner variant-URL model (no per-variant duplicate contentThe same or very similar primary content reachable at more than one URL. There's no general duplicate content penalty — the real costs are possible signal dilution, the wrong URL getting chosen, and less-efficient crawling. to manage) and simplicity. Squarespace’s genuine weaknesses are the no-custom-category-SEO ceiling, the narrow Merchant Center feed, and the manual redirect requirement. WooCommerce, Magento, BigCommerce, and PrestaShop each land differently on these axes — but on Squarespace specifically, those four traits are what you’re actually choosing between.

AI summary

A condensed take on the Advanced version:

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. = the store layer on top of general Squarespace SEOSquarespace SEO is the practice of optimizing a Squarespace-hosted site to rank in organic search. Squarespace handles much of the technical baseline automatically — HTTPS, CDN delivery, an XML sitemap, canonical tags, and basic metadata — but its closed SaaS architecture creates hard limits: no robots.txt editing, no sitemap customization, a fixed set of auto-generated schema you can't remove, and no code injection on individual blog posts. (which covers 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., 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.', canonicals, 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. lockdown, no-auto-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. gotcha, AMPAMP (Accelerated Mobile Pages) is an open-source web framework Google launched in 2015 to make mobile pages load near-instantly via restricted HTML/CSS/JS and CDN caching. It was never a ranking factor and, since June 2021, is no longer required for Top Stories. deprecation). Link out for the baseline; this is commerce-only.
Product pages: own SEO titleThe title tag is the HTML title element in a page's head that specifies the document's title. It's the primary source for the SERP title link and a confirmed light ranking factor — but since August 2021 Google doesn't always show it verbatim./description fields; Squarespace suggests 50–300 characters, 400 max; blank description falls back to the product description. Write unique descriptions, not manufacturer copy.
Category pages: the sharpest ceiling — category/sub-category pages can’t take custom SEO title/description (unlike Shopify/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. collection pages). They’re 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., just not optimizable.
Variants: the structural win — dropdowns on one product URL, so no per-variant duplicate contentThe same or very similar primary content reachable at more than one URL. There's no general duplicate content penalty — the real costs are possible signal dilution, the wrong URL getting chosen, and less-efficient crawling. to canonicalize (vs Shopify/Magento variant-URL sprawl). Limits: 6 options / 250 combinations; no variant deep-linking without JS.
Catalog size: 200 products/store page on 7.0 vs 10,000 on 7.1 (site-wide cap 10,000). Large 7.0 catalogs fragment across pages — a reason to move to 7.1.
Sold-out products: stay live and indexed with a customizable label; no auto-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./404/redirect. Matches current out-of-stock best practice.
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.: auto-generated (price + availability), can’t remove/edit; gaps in return policy and review/rating markup — supplement via Code Injection.
Customer reviews: display 1–5 stars, 1,500-char text; don’t appear to feed AggregateRating schemaAggregateRating schema (schema.org/AggregateRating) is structured data that represents the average of many ratings or reviews of an item, usually nested inside a parent type (or standalone with itemReviewed) to power star-rating rich snippets in search results. — a real gap.
Google Shopping: native GMC feed exists (corrects the “no feed” myth) but is US-only, English-US-only, physical-goods-only, needs a shipping option, ≤200 data sources; no native Bing Shopping.
Subscriptions/digital/memberships: excluded from the Shopping feed.
vs Shopify: Shopify wins on auto-redirects + feed/app breadth; Squarespace wins on the clean variant-URL model + simplicity.

Official documentation

Primary-source docs from Squarespace and Google/Bing.

Squarespace — commerce SEO mechanics

Adding SEO descriptions — the 50–300 character guidance, 400-char limit, and the fallback-to-product-description behavior.
Adding products to your store — the SEO and URL section per product.
Adding product variants — the single-URL dropdown model, 6 options / 250 combinations, no variants on downloads.
Categories and tags — categories/tags are 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.; unpublished-item 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. behavior.
Changing title formats for SEO and browser tabs — confirms directly that you can’t customize the title format for content filtered by a category or tag.
Page limits — the 200 (7.0) vs 10,000 (7.1) store-page product limits.
Sold out products — the Sold Out label; pages stay live.
Customer reviews — 1–5 stars, 1,500-char reviews, ~14-day request, 120-day window (display only; no structured-data statement).
Displaying products in Google Shopping — the US/English-US/physical-only requirements, plan list, and 200-data-source cap.
Subscription products — the recurring-revenue product type (not Shopping-feed-eligible).
Sell on Squarespace — sellable types and the plans that unlock commerce.
Site launch checklist — pre-launch commerce items.
SEO checklist — Squarespace’s own SEO checklist (treats products like blog posts; no dedicated commerce section).

Squarespace — developer / URL convention

Retrieve a specific product (Commerce API) — confirms the /store/ product-detail URL path convention.
Retrieve all products (Commerce API).

Google / Bing

Product structured data — what a complete 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. needs (and where Squarespace’s auto schema falls short).
Merchant listing experiences / requirements — what’s required for products to surface in free listingsFree product listings (originally launched as \"Surfaces across Google\" in 2020) are unpaid, organic product placements Google generates from your Merchant Center feed or on-page Product structured data. There's no bid and no CPC — Google matches your product data to a query and decides whether and where to show it — across the Shopping tab, Google Search (Popular Products grids), Images, Lens, Maps/Business Profile, YouTube, and Gemini; AI Mode and AI Overviews aren't on Google's official surfaces list, though practitioner reporting links them to the same eligibility pool. They're enabled by default in most cases for new Merchant Center accounts./Shopping.
Canonicalization — applied here to why the single-URL variant model sidesteps the variant-canonical problem.
Sitemaps overview — Squarespace’s auto-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. includes product/category URLs.
Microsoft Merchant Center (formerly Bing Merchant CenterMicrosoft's free platform (inside Microsoft Advertising, formerly 'Bing Merchant Center') where retailers create a store and submit a product feed. One feed powers both free Product Listings on the Bing Shopping tab and paid Microsoft Shopping Campaigns — the Bing/Copilot-side twin of Google Merchant Center. As of 2026 it's also the product-data foundation Copilot draws on for AI-assisted shopping and checkout.) — noting Squarespace has no native Bing/Microsoft Shopping equivalent.

Quotes from the source

On-the-record statements from Squarespace’s own documentation. Each link deep-links to the quoted passage on the source page. Everything else in this guide is paraphrased.

Squarespace — product SEO descriptions

“Keep the text between 50-300 characters. SEO descriptions have a 400-character limit.” Jump to quote

Squarespace — product SEO and URL

“Your SEO titleThe title tag is the HTML title element in a page's head that specifies the document's title. It's the primary source for the SERP title link and a confirmed light ranking factor — but since August 2021 Google doesn't always show it verbatim. and description helps search engines connect customers with your product.” Jump to quote

Squarespace — categories and tags are 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.

“Categories and tags are also indexed by search engines.” Jump to quote

Squarespace — category/tag pages can’t take a custom title format

“It’s not possible to customize the title format when linking to content filtered by a category or tag.” Jump to quote

Squarespace — sold-out products stay up

“When a product is out of stock, customers can’t add it to their carts, and a Sold Out label will display on store pages and product details pages.” Jump to quote

Squarespace — Google ShoppingGoogle Merchant Center (GMC) is a free platform where retailers upload and manage product data so their products can appear across Google — Shopping, organic Search product grids, Images, Lens, and AI surfaces. Since 2020 it powers free (organic) product listings, not just paid Shopping ads. requirements

“Be located in the United States and set your site language to English (United States).” Jump to quote
“Have 200 or fewer separate data sources linked to your Google Merchant CenterGoogle Merchant Center (GMC) is a free platform where retailers upload and manage product data so their products can appear across Google — Shopping, organic Search product grids, Images, Lens, and AI surfaces. Since 2020 it powers free (organic) product listings, not just paid Shopping ads. account.” Jump to quote

Note: Squarespace’s support pages are served through Zendesk and can reformat punctuation over time, which occasionally breaks exact-substring text-fragment links. If a “Jump to quote” link lands at the top of the page instead of the passage, re-fetch the article and confirm the quoted text before treating the fragment as final. Practitioner claims elsewhere in this guide (Kristine Neil, Collaborada, SEOSpace) are relayed from third-party sources, not Squarespace docs, and are paraphrased rather than quoted.

Squarespace-specific commerce SEO audit checklist

Prioritized by impact — top items move the needle most on a Squarespace store.

High impact

Every important product has a written SEO titleThe title tag is the HTML title element in a page's head that specifies the document's title. It's the primary source for the SERP title link and a confirmed light ranking factor — but since August 2021 Google doesn't always show it verbatim. + description (50–300 chars, 400 max) — not the auto-fallback product-description text.
Unique product descriptions, not manufacturer copy, on your priority SKUs.
Sold-out products left live — confirm you’re not deleting/noindexing/404ing out-of-stock pages; keep their titles/meta optimized.
Product slug changes have manual 301s — any renamed SKU has a URL Mapping 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. (Squarespace won’t auto-create it).
Catalog vs version check — if you’re on 7.0 with >200 products per store page, plan for 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./extra collections or a move to 7.1.

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.

Confirm the auto 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 firing (price + availability) via Google’s 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.
Decide whether to supplement missing fields (hasMerchantReturnPolicy, review/rating) via Code Injection JSON-LDJSON-LD (JavaScript Object Notation for Linked Data) is a script-based structured data format, typically paired with the schema.org vocabulary to describe page content for search engines and AI systems. Google recommends it over Microdata and RDFa because it's the easiest format to implement and maintain at scale — but all three work, and structured data isn't a ranking signal. — tied to real on-page data.
If you want review stars in search, add AggregateRating/Review JSON-LDJSON-LD (JavaScript Object Notation for Linked Data) is a script-based structured data format, typically paired with the schema.org vocabulary to describe page content for search engines and AI systems. Google recommends it over Microdata and RDFa because it's the easiest format to implement and maintain at scale — but all three work, and structured data isn't a ranking signal. yourself (the native reviews feature doesn’t appear to emit it).

Category / collection pages

Accept that category pages have no custom SEO fields — plan on-page content (headings, intro copy) and 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. to compensate.
Confirm categories only “exist” once their collection items are published.
If collection-page uniformity is a real limitation, evaluate custom code (Will Myers-style) as a deliberate, maintained workaround.

Google ShoppingGoogle Merchant Center (GMC) is a free platform where retailers upload and manage product data so their products can appear across Google — Shopping, organic Search product grids, Images, Lens, and AI surfaces. Since 2020 it powers free (organic) product listings, not just paid Shopping ads. (physical products only)

Eligible? US-based, site language English (United States), physical products, shipping option configured, Core/Plus/Advanced/Commerce Basic/Commerce Advanced.
Merchant Center account linked (single, not multi-client), ≤200 data sources.
Non-physical products (digital/subscription/membership)? Accept they’re excluded from the feed — don’t chase Shopping for them.
Need Bing ShoppingMicrosoft's free platform (inside Microsoft Advertising, formerly 'Bing Merchant Center') where retailers create a store and submit a product feed. One feed powers both free Product Listings on the Bing Shopping tab and paid Microsoft Shopping Campaigns — the Bing/Copilot-side twin of Google Merchant Center. As of 2026 it's also the product-data foundation Copilot draws on for AI-assisted shopping and checkout.? There’s no native integration — plan a separate feed.

The baseline-plus-commerce framework

Audit a Squarespace store in two layers so the store-specific work does not get lost inside generic platform advice.

Layer 1: the Squarespace site baseline

Confirm the platform-wide controls first: the generated 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., 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.', URL Mappings, page metadata, Code Injection, and the limits around 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 schema. These behaviors are shared by ordinary pages and commerce pages, so fix them once at the site level.

Layer 2: the commerce surface

Then audit the outputs unique to selling: product SEO fields, unique product copy, category-page limitations, one-URL variants, sold-out handling, 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. gaps, native reviews, catalog-size limits, and Merchant CenterGoogle Merchant Center (GMC) is a free platform where retailers upload and manage product data so their products can appear across Google — Shopping, organic Search product grids, Images, Lens, and AI surfaces. Since 2020 it powers free (organic) product listings, not just paid Shopping ads. eligibility.

For each commerce item, classify it as:

Automatic: verify it rather than rebuilding it — one URL per product’s variants, sold-out pages staying live, and the core 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..
Editable: use the provided control — product titles/descriptions and product slugs, with a manual URL Mapping for every slug change.
A platform ceiling: design around it — no custom category metadata, no native review-rating schema, and the narrow US/English-US/physical-goods Shopping feed.

This keeps the audit honest: start with the shared baseline, add the commerce layer, and do not promise a native control where Squarespace has only a workaround.

Squarespace Commerce SEO cheat sheet

What’s automatic vs yours

Area	Squarespace does it	You do it
Product SEO titleThe title tag is the HTML title element in a page's head that specifies the document's title. It's the primary source for the SERP title link and a confirmed light ranking factor — but since August 2021 Google doesn't always show it verbatim./description	Provides the fields + fallback	Write the copy
Product URL slug	Editable per product	Add manual 301 on change
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.	Auto (price, availability)	Supplement gaps via Code Injection
Variant URLs	Single URL, dropdown	Nothing — dup content already avoided
Sold-out handling	Keeps page live + label	Keep optimizing; don’t delete
Category page SEOCategory page SEO is the practice of optimizing an ecommerce listing page (also called a PLP or collection page) — the page that groups products under a classification like /shoes/running/ — so it ranks for broad commercial queries and routes crawlers and link equity to the products beneath it.	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.	Can’t customize title/description
Review stars in SERP	Not emitted	Add JSON-LDJSON-LD (JavaScript Object Notation for Linked Data) is a script-based structured data format, typically paired with the schema.org vocabulary to describe page content for search engines and AI systems. Google recommends it over Microdata and RDFa because it's the easiest format to implement and maintain at scale — but all three work, and structured data isn't a ranking signal. yourself
Google ShoppingGoogle Merchant Center (GMC) is a free platform where retailers upload and manage product data so their products can appear across Google — Shopping, organic Search product grids, Images, Lens, and AI surfaces. Since 2020 it powers free (organic) product listings, not just paid Shopping ads. feed	Native (US/physical only)	Build your own if ineligible

Product SEO description

Target 50–300 characters, hard cap 400.
Blank = falls back to the product description.

Variants

Single product URL, dropdown selectors (no dup content).
Limits: 6 options, 250 combinations; none on digital downloads.
No variant deep-linking without custom JS.

Catalog size (store page)

7.0: up to 200 products.
7.1: up to 10,000 products.
Site-wide cap: 10,000 either way.

Google Shopping gates

US-based + English (United States) site language.
Physical products only; shipping option required.
Core / Plus / Advanced / Commerce Basic / Commerce Advanced.
≤200 data sources; no multi-client accounts; no native Bing.

Don’ts

Don’t paste manufacturer product copy.
Don’t delete/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./404 sold-out products.
Don’t rename a product slug without a URL Mapping 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..
Don’t expect custom SEO fields on category pages.
Don’t assume native reviews create rating 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..
Don’t chase Google Shopping for digital/subscription/membership products.

Squarespace Commerce SEO mistakes to avoid

Assuming Squarespace has no Google Shopping feed

Why it’s wrong: A native Merchant CenterGoogle Merchant Center (GMC) is a free platform where retailers upload and manage product data so their products can appear across Google — Shopping, organic Search product grids, Images, Lens, and AI surfaces. Since 2020 it powers free (organic) product listings, not just paid Shopping ads. integration exists, but it is tightly gated. Do this instead: check the US location, English (United States) language, physical-product, shipping, plan, and data-source requirements before choosing a separate feed solution.

Treating category pages like Shopify collections

Why it’s wrong: Squarespace category and sub-category pages do not expose custom SEO titleThe title tag is the HTML title element in a page's head that specifies the document's title. It's the primary source for the SERP title link and a confirmed light ranking factor — but since August 2021 Google doesn't always show it verbatim. or description fields. Do this instead: strengthen headings, visible introductory content, taxonomy, and 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., and use maintained custom code only when the business case justifies it.

Deleting sold-out products

Why it’s wrong: Deleting, noindexing, or 404ing a temporarily sold-out product throws away the page and its accumulated signals. Do this instead: keep the page live with the Sold Out label and update the copy until stock returns.

Renaming a product slug without URL Mapping

Why it’s wrong: Squarespace does not create the 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. automatically, so the old product URL breaks. Do this instead: add and test the permanent mapping before the slug change.

Assuming native reviews produce rating-rich results

Why it’s wrong: Squarespace documents review display but does not document native Review or AggregateRating output. Do this instead: inspect the rendered schema and supplement it only with truthful markup tied to visible reviews.

Adding a second conflicting Product object

Why it’s wrong: Custom JSON-LDJSON-LD (JavaScript Object Notation for Linked Data) is a script-based structured data format, typically paired with the schema.org vocabulary to describe page content for search engines and AI systems. Google recommends it over Microdata and RDFa because it's the easiest format to implement and maintain at scale — but all three work, and structured data isn't a ranking signal. can contradict the Product and Offer data that Squarespace already emits. Do this instead: supplement missing properties, keep values aligned with the visible page, and validate the combined output.

Common Squarespace Commerce SEO issues

Review stars do not appear in search

Symptom: Reviews and star ratings appear on the product page, but the Rich Results Test finds no Review or AggregateRating data.

Likely cause: The native customer-reviews feature displays reviews without adding the rating markup needed for search eligibility.

Fix: Add supplemental JSON-LDJSON-LD (JavaScript Object Notation for Linked Data) is a script-based structured data format, typically paired with the schema.org vocabulary to describe page content for search engines and AI systems. Google recommends it over Microdata and RDFa because it's the easiest format to implement and maintain at scale — but all three work, and structured data isn't a ranking signal. tied to genuine visible reviews, avoid conflicting with Squarespace’s existing Product data, and rerun the 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.

Google Shopping rejects or will not connect the catalog

Symptom: The native Shopping setup is unavailable or products are rejected before the feed is useful.

Likely cause: One of the eligibility gates is unmet: seller location, site language, physical product type, shipping setup, qualifying plan, Merchant CenterGoogle Merchant Center (GMC) is a free platform where retailers upload and manage product data so their products can appear across Google — Shopping, organic Search product grids, Images, Lens, and AI surfaces. Since 2020 it powers free (organic) product listings, not just paid Shopping ads. account type, or data-source count.

Fix: Check each gate against the live store and Merchant Center account. If the catalog is ineligible by design, stop debugging the Squarespace connector and use an appropriate external feed path instead.

A renamed product URL returns 404

Symptom: The new product URL works, but the old slug no longer resolves.

Likely cause: The slug changed without a corresponding URL Mapping; Squarespace does not create one automatically.

Fix: Add a permanent mapping from the exact old path to the new product path, then fetch the old URL and confirm it reaches the intended product without a chain.

A category page has generic search metadata

Symptom: A product category is 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. but its search title or description cannot be edited in the normal SEO panel.

Likely cause: Category and sub-category pages do not support custom SEO settings.

Fix: Improve the category’s visible heading, content, taxonomy, and internal links. Treat custom collection code as a maintained workaround, not a missing toggle.

Validate commerce SEO changes after publishing

Test supplemental Product or review schema

Test to run: Publish the Code Injection or Code Block change and run the product URL through Google’s 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.

Expected result: The page’s Product data remains valid, the intended supplemental properties are present, and values agree with visible price, availability, returns, and reviews.

Failure interpretation: The custom block is malformed, not renderingTurning HTML, CSS, and JavaScript into the final visual page and DOM. on the product page, or conflicts with Squarespace’s auto-generated Product or Offer data.

Monitoring window: Immediate after the published page is available.

Rollback trigger: Remove the custom block if it creates invalid, duplicate, or contradictory Product data.

Test a product-slug redirect

Test to run: After adding the URL Mapping and changing the slug, request the exact old product URL and inspect the final destination.

Expected result: The old path permanently 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. to the matching new product URL in one hop.

Failure interpretation: The mapping is missing, ordered below a conflicting rule, or points at the wrong path.

Monitoring window: Immediate; the HTTP response is authoritative as soon as the mapping is active.

Rollback trigger: Restore the original slug or mapping if the old URL 404s, loops, chains, or lands on a different product.

Patrick's relevant free tools

PDP SEO Checker — Audit raw product schema, price, availability, and visible-price consistency.

Tools for Squarespace Commerce SEO

Google Search ConsoleA free Google service that reports how a site performs in Google Search and surfaces problems with how Google crawls, indexes, and serves it. It's first-party data straight from Google — but you don't need it to appear in results. — submit the auto-generated 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., inspect product and category URLs, confirm what’s actually 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., and watch for the manual-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. breakage after slug changes.
Bing Webmaster ToolsMicrosoft's free portal for monitoring and improving how a site appears in Bing search — the peer to Google Search Console, plus IndexNow instant indexing, richer backlink data, and keyword volumes. Because Bing's index also feeds Microsoft Copilot, it doubles as a window into AI-search visibility. — second 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. submission and crawl visibility (and your only path to Bing, since there’s no native Bing ShoppingMicrosoft's free platform (inside Microsoft Advertising, formerly 'Bing Merchant Center') where retailers create a store and submit a product feed. One feed powers both free Product Listings on the Bing Shopping tab and paid Microsoft Shopping Campaigns — the Bing/Copilot-side twin of Google Merchant Center. As of 2026 it's also the product-data foundation Copilot draws on for AI-assisted shopping and checkout. feed).
Google 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 / Schema MarkupSchema 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. Validator — confirm the auto Product schema (price, availability) is valid, and test any supplemental JSON-LDJSON-LD (JavaScript Object Notation for Linked Data) is a script-based structured data format, typically paired with the schema.org vocabulary to describe page content for search engines and AI systems. Google recommends it over Microdata and RDFa because it's the easiest format to implement and maintain at scale — but all three work, and structured data isn't a ranking signal. you add via Code Injection.
Google Merchant CenterGoogle Merchant Center (GMC) is a free platform where retailers upload and manage product data so their products can appear across Google — Shopping, organic Search product grids, Images, Lens, and AI surfaces. Since 2020 it powers free (organic) product listings, not just paid Shopping ads. — where the native Squarespace integration writes; check disapprovals and the ≤200-data-source cap (US/physical-product sellers only).
Screaming Frog / Ahrefs Site Audit — crawl the store to see how category and product URLs are structured, spot thin category pages, and confirm sold-out pages are staying indexed.
Squarespace Code Injection / Code Block — where you add the JSON-LDJSON-LD (JavaScript Object Notation for Linked Data) is a script-based structured data format, typically paired with the schema.org vocabulary to describe page content for search engines and AI systems. Google recommends it over Microdata and RDFa because it's the easiest format to implement and maintain at scale — but all three work, and structured data isn't a ranking signal. Squarespace omits (return policy, review/rating) and any custom collection-page code.
PageSpeed InsightsPageSpeed Insights (PSI) is a free Google tool at pagespeed.web.dev that reports two kinds of data for a URL: real-user field data from the Chrome UX Report and a single Lighthouse lab run with the 0–100 Performance score. Only the field Core Web Vitals are what Google uses for ranking. — Core Web VitalsGoogle's three real-user UX metrics — LCP (loading), INP (responsiveness), and CLS (visual stability) — used by Google's ranking systems, with no official weight attached, measured on field data. on product/category pages (Squarespace’s code is largely fixed; see the general Squarespace SEOSquarespace SEO is the practice of optimizing a Squarespace-hosted site to rank in organic search. Squarespace handles much of the technical baseline automatically — HTTPS, CDN delivery, an XML sitemap, canonical tags, and basic metadata — but its closed SaaS architecture creates hard limits: no robots.txt editing, no sitemap customization, a fixed set of auto-generated schema you can't remove, and no code injection on individual blog posts. guide for the platform-wide performance context).

Resources worth your time

On-site, related

Squarespace SEOSquarespace SEO is the practice of optimizing a Squarespace-hosted site to rank in organic search. Squarespace handles much of the technical baseline automatically — HTTPS, CDN delivery, an XML sitemap, canonical tags, and basic metadata — but its closed SaaS architecture creates hard limits: no robots.txt editing, no sitemap customization, a fixed set of auto-generated schema you can't remove, and no code injection on individual blog posts. — the platform-wide baseline (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., 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. lockdown, the no-auto-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. gotcha, the six auto schema typesSchema 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., AMPAMP (Accelerated Mobile Pages) is an open-source web framework Google launched in 2015 to make mobile pages load near-instantly via restricted HTML/CSS/JS and CDN caching. It was never a ranking factor and, since June 2021, is no longer required for Top Stories. deprecation). Read it first; this guide is the commerce layer on top.
CanonicalizationHow search engines pick one canonical URL among duplicates and consolidate signals onto it. — the mechanics behind why Squarespace’s single-URL variant model sidesteps the variant-canonical problem.
Faceted navigationEcommerce 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. and out-of-stock product handling — the platform-agnostic ecommerce-SEO context.

Squarespace official

Displaying products in Google Shopping — the Merchant CenterGoogle Merchant Center (GMC) is a free platform where retailers upload and manage product data so their products can appear across Google — Shopping, organic Search product grids, Images, Lens, and AI surfaces. Since 2020 it powers free (organic) product listings, not just paid Shopping ads. integration requirements.
Adding product variants and Sold out products.

Google official

Product structured data — the yardstick for what the auto schema is missing.
Merchant listing requirements.

From around the industry

Kristine Neil — Squarespace product page SEO tips — practitioner guidance on unique product descriptions and Squarespace’s image recommendations.
Kristine Neil — Product categories & tags in Squarespace — category/tag strategy corroborating the docs.
SEOSpace — Squarespace eCommerce SEO: Complete 2025 Guide — keyword/pillar strategy and the Will Myers custom-code workaround for collection pages.
SEOSpace — Is Squarespace Good or Bad for SEO? — the honest schema-editability and page-speed critique.
Collaborada — Squarespace schema guide — Product-schema field gaps (e.g. missing hasMerchantReturnPolicy).
Ottawa SEO — Squarespace vs Shopify SEO and hiagency — Squarespace vs Shopify SEO — the redirect-automation and feed-ecosystem contrast, applied here to product URL changes.
Squarespace community forum — SEO settings for sub-category pages — community corroboration of the category-page no-custom-SEO ceiling (practitioner-tier, not official docs).

Test yourself: Squarespace Commerce SEO

Five quick questions on optimizing a Squarespace store. Pick an answer for each, then check.

Squarespace Commerce SEO

Squarespace 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.

Squarespace Commerce SEO

Squarespace Commerce SEO is the commerce-specific slice of Squarespace SEOSquarespace SEO is the practice of optimizing a Squarespace-hosted site to rank in organic search. Squarespace handles much of the technical baseline automatically — HTTPS, CDN delivery, an XML sitemap, canonical tags, and basic metadata — but its closed SaaS architecture creates hard limits: no robots.txt editing, no sitemap customization, a fixed set of auto-generated schema you can't remove, and no code injection on individual blog posts.. General Squarespace SEOSquarespace SEO is the practice of optimizing a Squarespace-hosted site to rank in organic search. Squarespace handles much of the technical baseline automatically — HTTPS, CDN delivery, an XML sitemap, canonical tags, and basic metadata — but its closed SaaS architecture creates hard limits: no robots.txt editing, no sitemap customization, a fixed set of auto-generated schema you can't remove, and no code injection on individual blog posts. covers the platform baseline that applies to any Squarespace site — 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.' on a CDN, an auto-generated sitemap.xml, 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. on every page, per-page SEO fields, robots.txt that you can’t edit, and the gotcha that changing a URL doesn’t auto-create a 301. Squarespace Commerce SEO is what you layer on top once that site is an actual store.

The commerce layer has its own mechanics. Individual products get their own SEO titleThe title tag is the HTML title element in a page's head that specifies the document's title. It's the primary source for the SERP title link and a confirmed light ranking factor — but since August 2021 Google doesn't always show it verbatim. and description fields, distinct from the site-level ones. Squarespace auto-generates 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. (price and availability) that you can’t remove or edit natively. Product variants live as dropdown selectors on a single product URL, so — unlike Shopify or Magento setups that mint a separate URL per color/size — there’s no per-variant duplicate-content problem to canonicalize. And the platform ships a native Google Merchant CenterGoogle Merchant Center (GMC) is a free platform where retailers upload and manage product data so their products can appear across Google — Shopping, organic Search product grids, Images, Lens, and AI surfaces. Since 2020 it powers free (organic) product listings, not just paid Shopping ads. integration that pushes physical products into Google Shopping.

What Squarespace Commerce does not give you is where the SEO work concentrates: category and sub-category pages generated from your product taxonomy can’t have custom SEO titles/descriptions the way individual products and top-level pages can; the auto 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. has documented gaps (return policy, review/rating markup); customer reviews don’t appear to feed AggregateRating schemaAggregateRating schema (schema.org/AggregateRating) is structured data that represents the average of many ratings or reviews of an item, usually nested inside a parent type (or standalone with itemReviewed) to power star-rating rich snippets in search results.; the Merchant Center feed is US-only, English-US-only, physical-goods-only; and version 7.0 caps a store page at 200 products versus 10,000 on 7.1. Those are the levers — and the ceilings — that make Squarespace Commerce SEO its own topic.

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.

How this article chunks build baseline · local controls

A structure-aware retrieval preview using the shared Chunk Tester engine. The default lens is shown immediately; switch scopes to see what happens when every authored lens is treated as one source document.

Target size 300 tokens Overlap 15% Retrieval query

60readiness score / 100

12chunks

~395median tokens

83%standalone

8flagged chunks

Advanced lens only — the version readers see when this page opens.

Baseline generated at build time with a 300-token target and 15% overlap. Controls re-run the same deterministic engine in this browser.

Matching retrieval chunks

Ranked lexically for the page title, Trends, and Ngram terms. Enter a short query to test a different retrieval intent.

chunk 1 ~367 tok Default visible lens

Squarespace Commerce SEO **TL;DR —** Squarespace Commerce SEO is the store layer on top of the platform baseline. Products expose their own SEO title/description (Squarespace suggests 50–300 characters, 400 max) and auto…

chunk 3 ~379 tok Product page SEO fields

The practical takeaway is the same one Kristine Neil makes in her Squarespace product-page SEO writing: write **unique, keyword-considered descriptions** rather than pasting manufacturer copy, because that's the content …

chunk 5 ~385 tok Product variants: the single-URL model (a genuine advantage)

This is where Squarespace quietly beats most ecommerce platforms on a classic SEO problem. Product variants — size, color, material — display as **dropdown selectors on a single product URL**. Squarespace does *not* mint…

chunk 11 ~468 tok Subscriptions, digital, and membership products

These are a structurally different commerce case. Subscription products (subscription boxes, recurring goods/services), digital downloads, and memberships are **not eligible for the Google Shopping integration** above — …

chunk 2 ~405 tok The frame: scope this against general Squarespace SEO

Most "Squarespace ecommerce SEO" content re-explains sitemaps, HTTPS, and canonical tags — all of which are site-wide platform behavior that applies whether or not you sell anything. I've kept that in the general Squares…

Flagged retrieval chunks

chunk 2 ~405 tok The frame: scope this against general Squarespace SEO

~405 tokens — over 1.3× the 300-token target; a retriever may truncate it.

Most "Squarespace ecommerce SEO" content re-explains sitemaps, HTTPS, and canonical tags — all of which are site-wide platform behavior that applies whether or not you sell anything. I've kept that in the general Squares…

chunk 4 ~465 tok Category / store page SEO — the sharpest ceiling

~465 tokens — over 1.3× the 300-token target; a retriever may truncate it.

Here's the limitation that competitors gloss over: **category and sub-category pages generated from your product taxonomy cannot have their own custom SEO title and description.** Top-level pages get an SEO panel. Indivi…

chunk 7 ~440 tok Sold-out and out-of-stock products

~440 tokens — over 1.3× the 300-token target; a retriever may truncate it.

Squarespace's default behavior here aligns with current best practice. When a product sells out, the page **stays live and indexed** with a customizable "Sold Out" label; customers can't add it to the cart, but Squarespa…

chunk 8 ~413 tok Product structured data: what's automatic, what's missing

~413 tokens — over 1.3× the 300-token target; a retriever may truncate it.
Opens with "because" — refers back to text that may be in another chunk, so it doesn't stand alone.

Squarespace auto-generates **Product schema** on commerce pages, and you can neither remove nor natively edit it. It covers the core fields — **price and availability** — which is enough to be eligible for basic product …

chunk 9 ~360 tok Customer reviews — and the structured-data gap

A list is split across a chunk boundary — half its rows land in a different chunk.

Squarespace has a native **customer reviews** feature: customers can leave a written review (up to 1,500 characters) and a 1–5 star rating per item, with the request sent roughly 14 days after fulfillment and a 120-day r…

Showing 5 of 8 flagged chunks.

Methodology and limits

The readiness score starts with the percentage of standalone chunks and subtracts up to 35 points for the share carrying structural warnings. Structure-aware Markdown blocks use the selected 100–800-token target and 0–40% overlap. Tokens are estimated at roughly four English characters each. “Standalone” means a chunk has heading context and does not open with a context-dependent continuation.

Matching uses the shared lexical BM25 and term-cosine ranker. It is not an embedding or a replica of Google, an answer engine, or any vendor retriever. These chunk controls keep the article text in this browser and make no network request. The build-time baseline remains the reproducible report for this page.

Test your own content in Chunk Tester →

79readiness score / 100

32chunks

~334median tokens

94%standalone

14flagged chunks

All 14 authored lenses in this article source, with lens boundaries retained as headings.

Baseline generated at build time with a 300-token target and 15% overlap. Controls re-run the same deterministic engine in this browser.

Matching retrieval chunks

Ranked lexically for the page title, Trends, and Ngram terms. Enter a short query to test a different retrieval intent.

chunk 15 ~326 tok Squarespace vs Shopify for ecommerce SEO specifically

chunk 32 ~361 tok Resources worth your time

**Squarespace official** • Displaying products in Google Shopping — the Merchant Center integration requirements. • Adding product variants and Sold out products. **Google official** • Product structured data — the yards…

chunk 31 ~339 tok Tools for Squarespace Commerce SEO

• **Google Merchant Center** — where the native Squarespace integration writes; check disapprovals and the ≤200-data-source cap (US/physical-product sellers only). • **Screaming Frog / Ahrefs Site Audit** — crawl the sto…

chunk 4 ~496 tok The thing most people get wrong

People assume Squarespace either "has no product feed for Google" (it does — just a narrow one) or that its category pages work like Shopify's (they don't — no custom SEO fields). Both assumptions cost you. Know what's a…

chunk 8 ~385 tok Product variants: the single-URL model (a genuine advantage)

This is where Squarespace quietly beats most ecommerce platforms on a classic SEO problem. Product variants — size, color, material — display as **dropdown selectors on a single product URL**. Squarespace does *not* mint…

Flagged retrieval chunks

chunk 4 ~496 tok The thing most people get wrong

~496 tokens — over 1.3× the 300-token target; a retriever may truncate it.

People assume Squarespace either "has no product feed for Google" (it does — just a narrow one) or that its category pages work like Shopify's (they don't — no custom SEO fields). Both assumptions cost you. Know what's a…

chunk 5 ~405 tok The frame: scope this against general Squarespace SEO

~405 tokens — over 1.3× the 300-token target; a retriever may truncate it.

Most "Squarespace ecommerce SEO" content re-explains sitemaps, HTTPS, and canonical tags — all of which are site-wide platform behavior that applies whether or not you sell anything. I've kept that in the general Squares…

chunk 7 ~465 tok Category / store page SEO — the sharpest ceiling

~465 tokens — over 1.3× the 300-token target; a retriever may truncate it.

Here's the limitation that competitors gloss over: **category and sub-category pages generated from your product taxonomy cannot have their own custom SEO title and description.** Top-level pages get an SEO panel. Indivi…

chunk 10 ~440 tok Sold-out and out-of-stock products

~440 tokens — over 1.3× the 300-token target; a retriever may truncate it.

Squarespace's default behavior here aligns with current best practice. When a product sells out, the page **stays live and indexed** with a customizable "Sold Out" label; customers can't add it to the cart, but Squarespa…

chunk 11 ~413 tok Product structured data: what's automatic, what's missing

~413 tokens — over 1.3× the 300-token target; a retriever may truncate it.
Opens with "because" — refers back to text that may be in another chunk, so it doesn't stand alone.

Squarespace auto-generates **Product schema** on commerce pages, and you can neither remove nor natively edit it. It covers the core fields — **price and availability** — which is enough to be eligible for basic product …

Showing 5 of 14 flagged chunks.

Methodology and limits

The readiness score starts with the percentage of standalone chunks and subtracts up to 35 points for the share carrying structural warnings. Structure-aware Markdown blocks use the selected 100–800-token target and 0–40% overlap. Tokens are estimated at roughly four English characters each. “Standalone” means a chunk has heading context and does not open with a context-dependent continuation.

Matching uses the shared lexical BM25 and term-cosine ranker. It is not an embedding or a replica of Google, an answer engine, or any vendor retriever. These chunk controls keep the article text in this browser and make no network request. The build-time baseline remains the reproducible report for this page.

Test your own content in Chunk Tester →

Search Console

Loading…

GA4 traffic (28d)

Loading…

Cloudflare traffic (7d)

Loading…

CrUX field data (28d, phone)

Loading…

Google NLP entities

Loading…

Changelog

Updated Jul 18, 2026.

Editorial summary and recorded change details.

Summary

Verified this article's central claims directly against Squarespace's own current support docs (this topic's structured research packet was templated boilerplate and unusable for fact-checking, per owner flag). Every checked claim — the category/tag page no-custom-SEO ceiling, the single-URL variant model, the 200-vs-10,000 product limits, sold-out handling, Google Shopping's US/English-US/physical-only gates, and the reviews-don't-feed-AggregateRating gap — held up as current (Squarespace's own Google Shopping doc was last updated 2026-07-09, days before this pass). Strengthened the category-page sourcing with a direct official quote and tightened the Google Product-schema required-vs-recommended framing.

Change details

Added a direct Squarespace support-doc quote ('It's not possible to customize the title format when linking to content filtered by a category or tag') to the category-page SEO section and the Quotes/Official Docs lenses, upgrading that claim from forum-only corroboration to first-party confirmation.
Rewrote the Product structured-data section's framing of Google's spec to distinguish formally REQUIRED product-snippet properties (name plus one of offers/review/aggregateRating) from RECOMMENDED ones (aggregateRating, review, hasMerchantReturnPolicy, shippingDetails), rather than treating name/image/price/availability and the rest as one undifferentiated list.

Full comparison unavailable — no prior snapshot was archived for this revision.

Squarespace Commerce SEO

What “Squarespace Commerce SEO” means

What Squarespace handles for your store automatically

What you still have to handle

The thing most people get wrong

The frame: scope this against general Squarespace SEO

Product page SEO fields

Category / store page SEO — the sharpest ceiling

Product variants: the single-URL model (a genuine advantage)

Catalog size: the 200 vs 10,000 product limit

Sold-out and out-of-stock products

Product structured data: what’s automatic, what’s missing

Customer reviews — and the structured-data gap

Google Shopping: the native feed and its hard limits

Subscriptions, digital, and membership products

The practitioner workaround: custom collection code

Squarespace vs Shopify for ecommerce SEO specifically

AI summary

Official documentation

Quotes from the source

Squarespace-specific commerce SEO audit checklist

The baseline-plus-commerce framework

Layer 1: the Squarespace site baseline

Layer 2: the commerce surface

Squarespace Commerce SEO cheat sheet

Squarespace Commerce SEO mistakes to avoid

Assuming Squarespace has no Google Shopping feed

Treating category pages like Shopify collections

Deleting sold-out products

Renaming a product slug without URL Mapping

Assuming native reviews produce rating-rich results

Adding a second conflicting Product object

Common Squarespace Commerce SEO issues

Review stars do not appear in search

Google Shopping rejects or will not connect the catalog

A renamed product URL returns 404

A category page has generic search metadata

Validate commerce SEO changes after publishing

Test supplemental Product or review schema

Test a product-slug redirect

Patrick's relevant free tools

Tools for Squarespace Commerce SEO

Resources worth your time

Test yourself: Squarespace Commerce SEO

Squarespace Commerce SEO

Squarespace Commerce SEO

How this article chunks build baseline · local controls

Matching retrieval chunks

Flagged retrieval chunks

Matching retrieval chunks

Flagged retrieval chunks

Google Trends Squarespace · Ecommerce SEO

Books Ngram squarespace commerce seo · squarespace store seo

Changelog

Updated Jul 18, 2026.

Summary

Change details

People also ask