Guide Squarespace Commerce SEO

TL;DR — Squarespace Commerce SEO is SEO pour a Squarespace store specifically — votre product pages, category pages, and product listings — as opposed to votre general Squarespace site. Chaque product obtient its propre SEO title and description box, and Squarespace automatically adds the behind-the-scenes product données (price, in-stock/out-of-stock) que peut earn vous a richer résultat de recherche. The Category-page contrôle and the native Google Merchant connection have platform, product, and market constraints, so vérifier the current Squarespace requirements.

Ce que “Squarespace Commerce SEO” signifie

Si vous sell products on Squarespace, you’re running a store on top of a regular Squarespace site. General Squarespace SEO covers le site-wide basics — the automatic sitemap, HTTPS, balise canonicals, and the big gotcha que modification une URL doesn’t créer a redirection pour vous. Ce guide is à propos de the commerce parts que sit on top of que: votre products, votre product categories, and getting les trouvé and affiché in search.

Ce que Squarespace handles pour votre store automatically

• Product SEO fields. Every product has its propre SEO title and description box, separate from votre site settings. Vous écrire ces; si vous skip the description, Squarespace falls back to votre product description text.
• Product données pour search (schema). Squarespace automatically adds “structured données” to votre product pages — price and si the item is in stock — qui is ce que peut give vous a nicer-looking result in Google.
• Variant pages stay tidy. Quand a product comes in sizes or colors, Squarespace garde les tout on un product page with a dropdown. It fait pas créer a separate web adresse pour every size/color combination — so there’s aucun messy duplicate-page problem to clean up (qui is a réel headache on some autre platforms).
• Sold-out products stay up. Quand something sells out, Squarespace garde the page live with a “Sold Out” étiquette au lieu de deleting it. That’s en réalité the correct déplacer pour le SEO — vous garder lune page’s rankings pour quand it’s back in stock.
• Google Shopping (with strings attached). Squarespace peut send votre products to Google Shopping via a built-in Google connection — but seulement si you’re fondé in the US, votre site language is English (United States), and vous sell physical products.

Ce que vous encore have to handle

• Category pages can’t obtenir custom SEO settings. Unlike votre regular pages and votre individual products, the category pages Squarespace builds from votre product tags/categories don’t have leur propre SEO title/description boxes. Ce is the unique biggest limitation to know à propos de.
• Écrire réel product descriptions. Don’t paste the manufacturer’s copy. Unique, utile descriptions are ce que aider a product page rank.
• Reviews don’t ajouter star ratings to search. Squarespace has a customer-reviews fonctionnalité, but there’s aucun sign it feeds the “star rating” données que montre up in Google. Si vous vouloir examiner stars, that’s a manual, custom-code job.

The chose la plupart personnes obtenir incorrect

Personnes assume Squarespace soit “has no product feed for Google” (it fait — simplement a narrow un) or que its category pages fonctionner comme Shopify’s (ils don’t — aucun custom SEO fields). Les deux assumptions cost vous. Know what’s automatic, what’s limited, and what’s simply pas là, and you’ll spend votre effort in the correct places.

Vouloir the practitioner version — the character limites, the exact schema gaps, the 200-vs-10 000 product limite, and où Squarespace beats Shopify (and où it loses)? Switch to the Avancé tab.

TL;DR — Squarespace Commerce SEO is the store couche on top of the platform baseline. Products expose leur propre SEO title/description (Squarespace suggests 50–300 characters, 400 max) and auto-generate Product schema with price and availability. The structural win is réel: variants render as dropdowns on a unique product URL, so there’s aucun per-variant duplicate-content problem to canonicalize — unlike Shopify or Magento variant-URL sprawl. The ceilings are equally réel: category/sub-category contrôle, generated schema fields, catalog limites, and the native Google Shopping integration vary by Squarespace version and eligibility. Sold-out pages stay live and indexé — qui matches current meilleur pratique.

The frame: scope ce contre general Squarespace SEO

La plupart “Squarespace ecommerce SEO” content re-explains sitemaps, HTTPS, and canonical tags — tout of qui are site-wide platform behavior que s’applique si or pas vous sell anything. I’ve kept que in the general Squarespace SEO guide (robots.txt lockdown, the no-auto-redirect-on-URL-change gotcha, the six auto-generated schema types, AMP’s February 2025 deprecation, Core Web Vitals generalities). Ce guide is seulement the commerce-specific mechanics: product-page fields, category-page limites, variants, catalog size, sold-out handling, Product schema completeness, reviews, and the Merchant Center feed. Où a topic is site-wide, I lien out au lieu de repeating it.

Product page SEO fields

Products obtenir leur propre SEO panel, separate from le site-level SEO settings. Editing a product, vous ouvrir the SEO tab (or the SEO and URL section in the newer editor) to définir the SEO title and description and to customize the product’s URL slug. Squarespace’s guidance is to garder the SEO description roughly 50–300 characters, with a hard 400-character limite. Si vous leave it blank, the engine falls back to the product description as the meta text — so an vide SEO description isn’t “no description,” it’s “whatever’s in your product body copy, truncated.”

The practical takeaway is the même un Kristine Neil rend in her Squarespace product-page SEO writing: écrire unique, keyword-considered descriptions plutôt que pasting manufacturer copy, parce que that’s le contenu que en réalité earns the ranking. Fill the SEO title and description on every product que matters; don’t rely on the fallback.

Remarque the product URL chemin convention: Squarespace product detail pages live sous a /store/ (or votre store page’s) chemin segment by par défaut — worth knowing quand you’re mapping redirections or reading explorer données. And the même platform-wide gotcha from the general guide s’applique ici with a commerce-specific trigger: renaming a product slug ne fait pas auto-create a 301. Rebrand a SKU, modifier its slug, and you’ve broken every inbound lien and lost lune page’s equity unless vous ajouter the redirection yourself in URL Mappings premier. On a store, slug changements are courant (seasonal renames, SKU rationalization), so ce bites plus souvent que on a static site.

Category / store page SEO — the sharpest ceiling

Here’s the limitation que competitors gloss over: category and sub-category pages generated from votre product taxonomy ne peut pas have leur propre custom SEO title and description. Top-level pages obtenir an SEO panel. Individual products obtenir an SEO panel. The category pages construit from votre product categories/tags do pas — vous can’t hand-write leur meta title or description the façon vous pouvez on Shopify or WooCommerce, où collection pages obtenir complet meta contrôler.

Categories and tags are indexé — Squarespace dit so directement, and ils aider site-search aussi — but “indexed” isn’t the même as “optimizable.” Vous pouvez’t tune the title tag or meta description of a category listing page. Ce is the unique biggest category-page SEO gap versus Shopify/WooCommerce, and it’s under-documented; au-delà the community-forum corroboration, Squarespace’s propre title-format aider doc confirms it directement: “It’s pas possible to customize the title format quand linking to content filtered by a category or tag.” It’s the raison practitioners reach pour custom code (voir ci-dessous) to influence how collection pages render at tout.

Un plus nuance from the docs: quand vous ajouter a nouveau category to an unpublished collection item, que category isn’t ajouté or indexé jusqu’à the item is publié — so category pages seulement “exist” pour search une fois ils have live products in les.

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

Ce is où Squarespace quietly beats la plupart ecommerce platforms on a classic SEO problem. Product variants — size, color, material — afficher as dropdown selectors on a unique product URL. Squarespace fait pas mint a separate URL per variant combination. Comparer que to a Shopify or Magento setup où chaque variant peut spawn its propre crawlable URL, and vous inherit a duplicate-content problem vous alors have to canonicalize away.

On Squarespace, que problem mostly doesn’t exist. Un product, un URL, un canonical — the canonicalization headache que plagues variant-URL platforms simply doesn’t appliquer ici. The limites: up to 6 options and 250 variant combinations per product, and variants can’t be ajouté to download (digital) products.

The tradeoff is the flip side of the même coin: parce que there’s seulement un URL, there’s aucun built-in façon to deep-link to a pre-selected variant (e.g. lien an ad straight to “the blue one”). Doing que exige custom JavaScript. So Squarespace trades away variant deep-linking to buy vous clean canonicalization — a bon trade pour la plupart stores, occasionally annoying pour paid campaigns pointing at a spécifique SKU variant.

Catalog size: the 200 vs 10 000 product limite

Store page product counts are version-dependent, and it’s an SEO/crawl-architecture problème, pas simplement a fonctionnalités footnote:

• Squarespace 7,1: a store page peut hold up to 10 000 products (aussi the site-wide cap).
• Squarespace 7,0: a store page is capped at 200 products (site-wide cap encore 10 000).

Pour a grand catalog on 7,0, que 200-per-page ceiling forces vous to split products à travers multiple store pages or collections — qui fragments votre lien interne equity and explorer paths à travers extrune pages vous didn’t vouloir. Si you’re on 7,0 with a big catalog, the store-page limite is a réel raison to plan a migration to 7,1 plutôt que papering over it with awkward supplémentaire collections.

Sold-out and out-of-stock products

Squarespace’s par défaut behavior ici aligns with current meilleur pratique. Quand a product sells out, lune page stays live and indexé with a customizable “Sold Out” étiquette; customers can’t ajouter it to the cart, but Squarespace fait pas auto-noindex, 404, or redirection lune page. Squarespace même frames displaying sold-out products as a façon to advertise demand.

That’s the SEO-correct par défaut. Google’s out-of-stock guidance is to garder lune page live plutôt que 404 or noindex it, so vous preserve its rankings and liens pour quand the item renvoie — voir out-of-stock products pour the platform-agnostic treatment. On Squarespace vous don’t have to do anything to obtenir ce correct; simplement resist the urge to “clean up” by deleting sold-out pages, and garder optimizing the title/meta pendant que the item’s out. Customize the étiquette text si “Sold Out” doesn’t fit votre brand.

Product données structurées: what’s automatic, what’s manquant

Squarespace auto-generates Product schema on commerce pages, and vous pouvez neither supprimer nor natively edit it. It covers the core fields — price and availability — qui is suffisant to be eligible pour basic product résultats enrichis. But mesuré contre Google’s Product données structurées spec, the auto schema has documented gaps: Google’s product-snippet requirements formally exiger seulement name plus un of offers, review, or aggregateRating — but a genuinely utile listing En pratique aussi nécessite image, price, and availability, and Google recommends going plus loin with aggregateRating/review, hasMerchantReturnPolicy, and shippingDetails. Practitioners (e.g. Collaborada’s schema write-up) flag manquant fields comme hasMerchantReturnPolicy; retourner policy and complet examiner/rating markup aren’t in the built-in output.

Parce que vous pouvez’t edit the native schema, the standard pratique is to supplement via Code Injection / a Code Block with votre propre JSON-LD pour the manquant fields — that’s normal, pas a sign vous did something incorrect. Two cautions: don’t emit conflicting Product/Offer données que contradicts the auto schema, and garder quelconque examiner/rating markup vous ajouter tied to genuine on-page reviews. (Pour the field-by-field detail, voir product schema and the broader données structurées treatment.)

Customer reviews — and the structured-data gap

Squarespace has a native customer reviews fonctionnalité: customers peut leave a written examiner (up to 1 500 characters) and a 1–5 star rating per item, with la requête sent roughly 14 days après fulfillment and a 120-day examiner window. Utile pour conversion and on-page content.

The SEO gap: the docs décrire afficher mechanics but dire nothing à propos de structured données, and practitioner consensus is que ces reviews do pas automatically populate Review/AggregateRating schema. So the stars montrer up on votre product page pour shoppers, but there’s aucun documented chemin from the native reviews fonctionnalité to review-rating résultats enrichis in search. Si examiner stars in the SERP matter to vous, that’s un autre Code-Injection JSON-LD job — à nouveau, tied to the réel reviews on the page. Ce is a genuine gap versus platforms with native review-schema plugins.

Google Shopping: the native feed and its hard limites

Ce corrects a courant myth. You’ll lire que “Squarespace has aucun product feed pour Google Shopping” — pas vrai. Squarespace has a native Google Merchant Center integration que pushes votre catalog into Google Shopping. But it’s gated, and the gates are strict. To utiliser it vous doit:

• Be located in the United States and définir votre site language to English (United States).
• Sell physical products (digital products, services, subscriptions, and memberships are excluded).
• Ajouter a shipping option in Squarespace.
• Be on a qualifying plan (Core, Plus, Avancé, Commerce Basic, or Commerce Avancé).
• Have a Google Merchant Center account (multi-client accounts aren’t pris en charge), with 200 or fewer données sources lié 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 aucun native Bing Shopping integration. Squarespace’s propre auto-sitemap inclut votre product and category URLs, but there’s aucun separate product-feed sitemap format; the Merchant Center integration is the feed mechanism. Si you’re outside the US or selling non-physical products and vous besoin Shopping visibility, you’re building a feed by autre signifie — the native integration won’t cover vous.

Subscriptions, digital, and membership products

Ces are a structurally différent commerce cas. Subscription products (subscription boxes, recurring goods/services), digital downloads, and memberships are pas eligible pour the Google Shopping integration ci-dessus — que feed is physical-goods-only. Ils aussi carry différent transaction-fee tiers by plan (plus élevé plans reduce or zero out fees on courses/memberships/digital products), qui is pourquoi sellers pick ces product types and alors demander “pourquoi isn’t my course in Google Shopping?” The réponse is structural, pas a misconfiguration: the feed doesn’t accept les. SEO pour ces products leans back on the fundamentals — strong product/landing pages, réel descriptions, lien internes — plutôt que quelconque feed-driven distribution.

The practitioner workaround: custom collection code

Parce que collection/category pages are so uniform and can’t prendre custom SEO settings, the practitioner-standard workaround is custom code to style and customize individual collection pages — Va Myers-style code snippets are the community référence point pour ce. I’m flagging it as a workaround, pas endorsing quelconque spécifique paid product: it’s how experienced Squarespace builders obtenir autour the platform’s uniform collection-page limitation quand a client nécessite collection pages que don’t tout regarder and behave identically. Treat it as a dernier resort après you’ve exhausted the native options, and remember custom code is yours to maintain à travers Squarespace updates.

Squarespace vs Shopify pour ecommerce SEO specifically

Garder ce narrow — the general platform comparison lives in the sibling articles; ici it’s seulement the commerce-SEO differences que matter:

Shopify’s genuine ecommerce-SEO edge is automated technical contrôler — it prompts vous to créer a 301 the moment vous modifier une URL, and it has a far broader feed/app ecosystem. Squarespace’s genuine edge is the cleaner variant-URL model (aucun per-variant contenu dupliqué to manage) and simplicity. Squarespace’s genuine weaknesses are the no-custom-category-SEO ceiling, the narrow Merchant Center feed, and the manual redirection requirement. WooCommerce, Magento, BigCommerce, and PrestaShop chaque land differently on ces axes — but on Squarespace specifically, ceux four traits are ce que you’re en réalité choosing entre.

AI summary

A condensed prendre on the Avancé version:

• Squarespace Commerce SEO = the store couche on top of general Squarespace SEO (qui covers sitemap, HTTPS, canonicals, robots.txt lockdown, no-auto-redirect gotcha, AMP deprecation). Lien out pour the baseline; ce is commerce-only.
• Product pages: propre SEO title/description fields; Squarespace suggests 50–300 characters, 400 max; blank description falls back to the product description. Écrire unique descriptions, pas manufacturer copy.
• Category pages: the sharpest ceiling — category/sub-category pages can’t prendre custom SEO title/description (unlike Shopify/WooCommerce collection pages). They’re indexé, simplement pas optimizable.
• Variants: the structural win — dropdowns on un product URL, so aucun per-variant contenu dupliqué to canonicalize (vs Shopify/Magento variant-URL sprawl). Limites: 6 options / 250 combinations; aucun variant deep-linking sans JS.
• Catalog size: 200 products/store page on 7,0 vs 10 000 on 7,1 (site-wide cap 10 000). Grand 7,0 catalogs fragment à travers pages — a raison to déplacer to 7,1.
• Sold-out products: stay live and indexé with a customizable étiquette; aucun auto-noindex/404/redirection. Matches current out-of-stock meilleur pratique.
• Product schema: auto-generated (price + availability), can’t supprimer/edit; gaps in retourner policy and examiner/rating markup — supplement via Code Injection.
• Customer reviews: afficher 1–5 stars, 1 500-char text; don’t apparaître to feed AggregateRating schema — a réel gap.
• Google Shopping: native GMC feed exists (corrects the “no feed” myth) but is US-only, English-US-only, physical-goods-only, nécessite a shipping option, ≤200 données sources; aucun 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.

Documentation officielle

Primary-source docs from Squarespace and Google/Bing.

Squarespace — commerce SEO mechanics

• Ajout SEO descriptions — the 50–300 character guidance, 400-char limite, and the fallback-to-product-description behavior.
• Ajout products to votre store — the SEO and URL section per product.
• Ajout product variants — the single-URL dropdown model, 6 options / 250 combinations, aucun variants on downloads.
• Categories and tags — categories/tags are indexé; unpublished-item indexation behavior.
• Modification title formats pour le SEO and navigateur tabs — confirms directement que vous pouvez’t customize the title format pour content filtered by a category or tag.
• Page limites — the 200 (7,0) vs 10 000 (7,1) store-page product limites.
• Sold out products — the Sold Out étiquette; pages stay live.
• Customer reviews — 1–5 stars, 1 500-char reviews, ~14-day requête, 120-day window (afficher seulement; aucun structured-data statement).
• Displaying products in Google Shopping — the US/English-US/physical-only requirements, plan liste, and 200-data-source cap.
• Subscription products — the recurring-revenue product type (pas Shopping-feed-eligible).
• Sell on Squarespace — sellable types and the plans que unlock commerce.
• Site launch checklist — pre-launch commerce items.
• SEO checklist — Squarespace’s propre SEO checklist (treats products comme blog posts; aucun dedicated commerce section).

Squarespace — developer / URL convention

• Retrieve a spécifique product (Commerce API) — confirms the /store/ product-detail URL chemin convention.
• Retrieve tout products (Commerce API).

Google / Bing

• Product données structurées — ce que a complet Product schema nécessite (and où Squarespace’s auto schema falls short).
• Merchant listing experiences / requirements — what’s requis pour products to surface in free listings/Shopping.
• Canonicalization — applied ici to pourquoi the single-URL variant model sidesteps the variant-canonical problem.
• Sitemaps overview — Squarespace’s auto-sitemap inclut product/category URLs.
• Microsoft Merchant Center (formerly Bing Merchant Center) — noting Squarespace has aucun native Bing/Microsoft Shopping equivalent.

Quotes from the source

On-the-record statements from Squarespace’s propre documentation. Chaque lien deep-links to the quoted passage on the source page. Everything sinon in ce 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 title and description helps search engines connect customers with your product.” Jump to quote

Squarespace — categories and tags are indexé

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

Squarespace — category/tag pages can’t prendre 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 Shopping 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 Center account.” Jump to quote

Squarespace-specific commerce SEO audit checklist

Prioritized by impact — top items déplacer the needle la plupart on a Squarespace store.

Élevé impact

• Every important product has a written SEO title + description (50–300 chars, 400 max) — pas the auto-fallback product-description text.
• Unique product descriptions, pas manufacturer copy, on votre priority SKUs.
• Sold-out products left live — confirmer you’re pas deleting/noindexing/404ing out-of-stock pages; garder leur titles/meta optimized.
• Product slug changements have manual 301s — quelconque renamed SKU has une URL Mapping redirection (Squarespace won’t auto-create it).
• Catalog vs version vérifier — si you’re on 7,0 with >200 products per store page, plan pour pagination/supplémentaire collections or a déplacer to 7,1.

Données structurées

• Confirmer the auto Product schema is firing (price + availability) via Google’s Résultats enrichis Tester.
• Decide si to supplement manquant fields (hasMerchantReturnPolicy, examiner/rating) via Code Injection JSON-LD — tied to réel on-page données.
• Si vous vouloir examiner stars in search, ajouter AggregateRating/Review JSON-LD yourself (the native reviews fonctionnalité doesn’t apparaître to emit it).

Category / collection pages

• Accept que category pages have aucun custom SEO fields — plan on-page content (headings, intro copy) and lien internes to compensate.
• Confirmer categories seulement “exist” une fois leur collection items are publié.
• Si collection-page uniformity is a réel limitation, evaluate custom code (Va Myers-style) as a deliberate, maintained workaround.

Google Shopping (physical products seulement)

• Eligible? US-based, site language English (United States), physical products, shipping option configuré, Core/Plus/Avancé/Commerce Basic/Commerce Avancé.
• Merchant Center account lié (unique, pas multi-client), ≤200 données sources.
• Non-physical products (digital/subscription/membership)? Accept they’re excluded from the feed — don’t chase Shopping pour les.
• Besoin Bing Shopping? There’s aucun native integration — plan a separate feed.

The baseline-plus-commerce framework

Audit a Squarespace store in two layers so the store-specific fonctionner ne fait pas obtenir lost à l’intérieur generic platform advice.

Couche 1: the Squarespace site baseline

Confirmer the platform-wide contrôle premier: the generated sitemap, balise canonicals, HTTPS, URL Mappings, page metadata, Code Injection, and the limites autour robots.txt and schema. Ces behaviors are shared by ordinary pages and commerce pages, so fix les une fois at le site level.

Couche 2: the commerce surface

Alors audit the outputs unique to selling: product SEO fields, unique product copy, category-page limitations, one-URL variants, sold-out handling, Product schema gaps, native reviews, catalog-size limites, and Merchant Center eligibility.

Pour chaque commerce item, classify it as:

• Automatic: vérifier it plutôt que rebuilding it — un URL per product’s variants, sold-out pages staying live, and the core Product schema.
• Editable: utiliser the provided contrôler — product titles/descriptions and product slugs, with a manual URL Mapping pour every slug modifier.
• A platform ceiling: design autour it — aucun custom category metadata, aucun native review-rating schema, and the narrow US/English-US/physical-goods Shopping feed.

Ce garde the audit honest: commencer with the shared baseline, ajouter the commerce couche, and ne faites pas promise a native contrôler où Squarespace has seulement a workaround.

Squarespace Commerce SEO cheat sheet

What’s automatic vs yours

Product SEO description

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

Variants

• Unique product URL, dropdown selectors (aucun dup content).
• Limites: 6 options, 250 combinations; none on digital downloads.
• Aucun variant deep-linking sans custom JS.

Catalog size (store page)

• 7,0: up to 200 products.
• 7,1: up to 10 000 products.
• Site-wide cap: 10 000 soit façon.

Google Shopping gates

• US-based + English (United States) site language.
• Physical products seulement; shipping option requis.
• Core / Plus / Avancé / Commerce Basic / Commerce Avancé.
• ≤200 données sources; aucun multi-client accounts; aucun native Bing.

Don’ts

• Don’t paste manufacturer product copy.
• Don’t delete/noindex/404 sold-out products.
• Don’t rename a product slug sans une URL Mapping redirection.
• Don’t expect custom SEO fields on category pages.
• Don’t assume native reviews créer rating résultats enrichis.
• Don’t chase Google Shopping pour digital/subscription/membership products.

Squarespace Commerce SEO mistakes to éviter

Assuming Squarespace has aucun Google Shopping feed

Pourquoi it’s incorrect: A native Merchant Center integration exists, but it is tightly gated. Do ce à la place: vérifier the US emplacement, English (United States) language, physical-product, shipping, plan, and data-source requirements avant choosing a separate feed solution.

Treating category pages comme Shopify collections

Pourquoi it’s incorrect: Squarespace category and sub-category pages ne faites pas expose custom SEO title or description fields. Do ce à la place: strengthen headings, visible introductory content, taxonomy, and lien internes, and utiliser maintained custom code seulement quand the business cas justifies it.

Deleting sold-out products

Pourquoi it’s incorrect: Deleting, noindexing, or 404ing a temporarily sold-out product throws away lune page and its accumulated signals. Do ce à la place: garder lune page live with the Sold Out étiquette and mettre à jour the copy jusqu’à stock renvoie.

Renaming a product slug sans URL Mapping

Pourquoi it’s incorrect: Squarespace ne fait pas créer the redirection automatically, so the old product URL breaks. Do ce à la place: ajouter and tester the permanent mapping avant the slug modifier.

Assuming native reviews produce rating-résultats enrichis

Pourquoi it’s incorrect: Squarespace documents examiner afficher but ne fait pas document native Review or AggregateRating output. Do ce à la place: inspect the rendered schema and supplement it seulement with truthful markup tied to visible reviews.

Ajout a second conflicting Product object

Pourquoi it’s incorrect: Custom JSON-LD peut contradict the Product and Offer données que Squarespace déjà emits. Do ce à la place: supplement manquant properties, garder valeurs aligned with the visible page, and validate the combined output.

Courant Squarespace Commerce SEO problèmes

Examiner stars ne faites pas apparaître in search

Symptom: Reviews and star ratings apparaître on the product page, but the Rich Results Tester trouve aucun Review or AggregateRating données.

Probable causer: The native customer-reviews fonctionnalité displays reviews sans ajout the rating markup nécessaire pour search eligibility.

Fix: Ajouter supplemental JSON-LD tied to genuine visible reviews, éviter conflicting with Squarespace’s existing Product données, and rerun the Résultats enrichis Tester.

Google Shopping rejects or ne va pas connecter the catalog

Symptom: The native Shopping setup is unavailable or products are rejected avant the feed is utile.

Probable causer: Un of the eligibility gates is unmet: seller emplacement, site language, physical product type, shipping setup, qualifying plan, Merchant Center account type, or data-source count.

Fix: Vérifier chaque gate contre the live store and Merchant Center account. Si the catalog is ineligible by design, arrêter debugging the Squarespace connector and utiliser an appropriate external feed chemin à la place.

A renamed product URL renvoie 404

Symptom: The nouveau product URL fonctionne, but the old slug ne … plus resolves.

Probable causer: The slug modifié sans a corresponding URL Mapping; Squarespace ne fait pas créer un automatically.

Fix: Ajouter a permanent mapping from the exact old chemin to the nouveau product chemin, alors récupérer the old URL and confirmer it reaches the intended product sans a chain.

A category page has generic search metadata

Symptom: A product category is indexé but its search title or description ne peut pas be edited in the normal SEO panel.

Probable causer: Category and sub-category pages ne faites pas prise en charge custom SEO settings.

Fix: Améliorer the category’s visible heading, content, taxonomy, and internal liens. Treat custom collection code as a maintained workaround, pas a manquant toggle.

Validate commerce SEO changements après publishing

Tester supplemental Product or examiner schema

Tester to run: Publish le code Injection or Code Block modifier and run the product URL via Google’s Résultats enrichis Tester.

Attendu result: Lune page’s Product données remains valid, the intended supplemental properties are présent, and valeurs agree with visible price, availability, renvoie, and reviews.

Échec interpretation: The custom block is malformed, pas rendering on the product page, or conflicts with Squarespace’s auto-generated Product or Offer données.

Monitoring window: Immediate après the publié page is disponible.

Rollback trigger: Supprimer the custom block si it creates invalid, duplicate, or contradictory Product données.

Tester a product-slug redirection

Tester to run: Après ajout l’URL Mapping and modification the slug, requête the exact old product URL and inspect the final destination.

Attendu result: The old chemin permanently redirections to the matching nouveau product URL in un hop.

Échec interpretation: The mapping is manquant, ordered ci-dessous a conflicting rule, or points at the incorrect chemin.

Monitoring window: Immediate; the HTTP réponse is authoritative as soon as the mapping is active.

Rollback trigger: Restore the original slug or mapping si the old URL 404s, loops, chains, or lands on a différent product.

Outils pour Squarespace Commerce SEO

• Recherche Google Console — submit the auto-generated sitemap, inspect product and category URLs, confirmer what’s en réalité indexé, and watch pour the manual-redirect breakage après slug changements.
• Bing Webmaster Outils — second sitemap submission and explorer visibility (and votre seulement chemin to Bing, since there’s aucun native Bing Shopping feed).
• Google Résultats enrichis Tester / Balisage de données structurées Validator — confirmer the auto Product schema (price, availability) is valid, and tester quelconque supplemental JSON-LD vous ajouter via Code Injection.
• Google Merchant Center — où the native Squarespace integration writes; vérifier disapprovals and the ≤200-data-source cap (US/physical-product sellers seulement).
• Screaming Frog / Ahrefs Site Audit — explorer the store to voir how category and product URLs are structured, spot thin category pages, and confirmer sold-out pages are staying indexé.
• Squarespace Code Injection / Code Block — où vous ajouter the JSON-LD Squarespace omits (retourner policy, examiner/rating) and quelconque custom collection-page code.
• PageSpeed Insights — Core Web Vitals on product/category pages (Squarespace’s code is largely fixed; voir the general Squarespace SEO guide pour the platform-wide performances context).

Ressources utiles

On-site, connexe

• Squarespace SEO — the platform-wide baseline (sitemap, robots.txt lockdown, the no-auto-redirect gotcha, the six auto schema types, AMP deprecation). Lire it premier; ce guide is the commerce couche on top.
• Canonicalization — the mechanics behind pourquoi Squarespace’s single-URL variant model sidesteps the variant-canonical problem.
• Faceted navigation and out-of-stock product handling — the platform-agnostic ecommerce-SEO context.

Squarespace official

• Displaying products in Google Shopping — the Merchant Center integration requirements.
• Ajout product variants and Sold out products.

Google official

• Product données structurées — the yardstick pour ce que the auto schema is manquant.
• Merchant listing requirements.

From autour 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: Complet 2025 Guide — keyword/pillar strategy and the Va Myers custom-code workaround pour collection pages.
• SEOSpace — Is Squarespace Bon or Bad pour le SEO? — the honest schema-editability and page-speed critique.
• Collaborada — Squarespace schema guide — Product-schema field gaps (e.g. manquant hasMerchantReturnPolicy).
• Ottawa SEO — Squarespace vs Shopify SEO and hiagency — Squarespace vs Shopify SEO — the redirect-automation and feed-ecosystem contrast, applied ici to product URL changements.
• Squarespace community forum — SEO settings pour sub-category pages — community corroboration of the category-page no-custom-SEO ceiling (practitioner-tier, pas official docs).

Testez vos connaissances: Squarespace Commerce SEO

Five rapide questions on optimizing a Squarespace store. Pick an réponse pour chaque, alors vérifier.

Journal des modifications