Skip to content
50% OFF $299 $599
Lock in
§ 2.7.2 ARTICLE
Published VerifiedEvery 6 weeks Sources4 named Authored bySquareRank Team

E-commerce SEO · Product URL · § 2.7.2

Squarespace Product URLs, Explained

Squarespace Commerce serves every product at /{store-slug}/p/{product-slug}1. The /p/ segment is fixed and cannot be removed; the {store-slug} can be renamed in Settings > Commerce; the {product-slug} is per-product. URL stability is a ranking signal — every rename forces a redirect chain and a small re-indexing dip. Pick the store path before launch, set product slugs carefully, and never rename either.

This page covers the URL pattern, why the /p/ segment exists, how to rename the store path with URL Mappings if you must, and the per-product slug rule. Pair this with the duplicate content leaf for how Squarespace handles variant and query-string URLs.

The Squarespace product URL pattern in 2026

Every product URL on Squarespace Commerce follows the same three-segment pattern: /{store-slug}/p/{product-slug}. Default store-slug is /shop/ on most current templates (some legacy templates default to /store/); the /p/ segment is fixed and identifies the URL as a product page rather than a category or collection page; the product-slug is per-product and editable on the product editor. A new Squarespace store launching in 2026 will most commonly see URLs like /shop/p/cold-press-juicer-x150, /shop/p/linen-shirt-natural, /shop/p/coffee-subscription-monthly.

The pattern is consistent across 7.1 templates and across most 7.0 commerce templates. It is one of the few URL patterns Squarespace standardises across template upgrades — meaning a migration from 7.0 to 7.1 typically preserves product URLs without forcing a redirect chain. The store slug is the only segment that varies meaningfully across stores, and the choice between /shop/ and /store/ is a minor brand decision rather than a ranking decision.

What the URL segments do

/p/

the fixed Squarespace Commerce product-identifier segment — unremovable, included in the sitemap.

Squarespace Help · 2026-Q1
Renameable

the store-slug — editable via Settings > Commerce. Default /shop/ on most 7.1 templates.

Squarespace Help · 2026-Q1
Per-product

the product slug — editable on the product editor. The most-leveraged segment for SEO.

Google Search Central · 2026-Q1

Why the /p/ segment cannot be removed — and why it doesn't matter

The /p/ segment is Squarespace Commerce's internal URL router signal. It identifies the URL as a product page (rather than a category, blog post, or static page) so the platform can route the request to the right template. Google's URL-structure guidance is explicit that category-style URL segments do not penalise ranking — clean URLs without /p/ rank the same as URLs with /p/ when other signals are equal. The segment looks like a 'Squarespace tax' to migrants from Shopify, but it is not actually a ranking factor.

The Shopify equivalent (/products/{product-slug}) carries a similar segment for the same reason — the platform needs to identify which template to render. WordPress's WooCommerce uses /product/ or /shop/{product-slug} patterns. The /p/ segment on Squarespace is shorter, which is arguably an aesthetic upside. Google's URL guidance3 reads URLs for descriptiveness and consistency, not for category-segment elegance.

Renaming the store path safely with URL Mappings

The store path can be renamed via Settings > Commerce > Store Page > URL slug. The rename is a destructive operation — every product URL changes the moment you save. To avoid losing rank and breaking inbound links, set up URL Mappings before saving: /shop/p/{product-slug} -> /store/p/{product-slug} 301 (using the wildcard syntax to cover all products at once). Save the rename, verify a sample of old URLs redirect cleanly to the new pattern, and notify Google via Search Console of the URL change.

The URL Mappings syntax2 supports wildcards for exactly this case. The mapping /shop/p/[name] -> /store/p/[name] 301 redirects every old product URL to the corresponding new URL in a single line. Without the wildcard mapping, each product URL would need its own redirect — manageable for ten products, unworkable for a hundred. The full URL Mappings reference lives in the URL Mappings syntax leaf.

The rename cost is real even with redirects: Google takes one to four weeks to fully consolidate the old and new URLs in its index, and during that window the product pages may rank below their pre-rename position. The recommendation: rename only if there is a strong brand reason (the store path is materially confusing as currently configured), and never rename more than once.

Product slug best practice

The per-product slug is the most-leveraged URL segment for SEO. Best practice: lowercase, hyphen-separated, descriptive, three to six words, with the primary keyword included once. Avoid numeric SKU slugs (/p/product-1234), random hashes (/p/x7h3kl9), and stop-word-heavy slugs (/p/the-best-cold-press-juicer). A clean slug like /p/cold-press-juicer-x150 reads as topical and customer-facing, matches the product title, and feeds the URL keyword signal Google reads when ranking the product.

The slug is editable on the product editor under the SEO section. Set it once before launch and match it to the product title in lowercase-hyphenated form. Changing slugs after launch costs a redirect and a small ranking dip per product — manageable for a one-off correction, unworkable for a wholesale rename. Pick the slug carefully the first time and avoid the temptation to refine later.

Keep reading · § 2.7.2