Squarespace ecommerce SEO

Squarespace store SEO within the platform's shape: title formats set once, redirects kept current, real pages instead of category filters.

Squarespace is a design-first platform, and its store SEO works best when you accept the structure and put the effort into content. Products sit under the store page's own path, so the store page slug becomes part of every product URL and is worth choosing carefully. Title formats are set once at site level and inherited, which is efficient for a catalogue and needs overriding on the pages that matter. There is a redirect tool, and it should be used every time a slug changes.

The part that catches most stores out is categories. Filtering a store page by category is a browsing feature rather than a set of landing pages, so the terms people search for often have no real page behind them. The fix is usually to build proper pages for the handful of categories with genuine demand, write them, and link to them from the navigation, rather than expecting a filtered view to rank.

The sitemap is generated for you and is not editable, which is fine, and it means indexing is controlled per page rather than by curating a file. Extra markup can be added through code injection, which is useful and easy to overdo.

We work in your site, keep changes inside the platform, and are clear about which limits are real.

Native on squarespace

Site-level and page-level title formats, inherited across the catalogue
Editable slugs for pages, products and the store page itself
The built-in URL redirect tool, edited as a list of rules
An automatically generated sitemap, with indexing controlled per page
Code injection for additional structured data or verification tags
Product descriptions and additional info sections that can carry real content

Settings that matter

Choose the store page slug before adding products

Every product URL includes the store page's own slug, so it is part of the address of your whole catalogue. Getting it right at the start costs nothing, and changing it later means redirecting every product. We pick something short and descriptive, and if a store has several product ranges we decide early whether they belong on one store page or several, because that decision is also baked into the URLs.

Set the title format once, then override what matters

The site-wide format keeps every page consistent and stops products publishing with a bare product name as the whole title. Then the collections and products that attract search demand get their own titles written for the query rather than assembled from a template. We keep a list of which pages have been written by hand, since a later change to the site format should not undo them.

Build real pages for the categories people search

A category filter on a store page is a browsing convenience, not a landing page with content of its own. Where a category matches genuine search demand, it deserves a page with a heading, an introduction, the buying advice and links to the relevant products. That is more work than tagging products, and it is the difference between having a filter and having something that can rank.

Keep the redirect list current

Redirects are managed as a list of rules, which makes them easy to maintain and easy to forget. Any time a product, page or store slug changes, the old path needs an entry. We audit the existing list for rules pointing at pages that no longer exist and for chains, then make adding a redirect part of the routine whenever anything is renamed or removed.

What we avoid

Treating store category filters as if they were landing pages that could rank on their own
Injecting structured data on top of what the template already outputs, so a product ends up described twice
Hiding product details inside collapsed sections when they are the answers a shopper came to find

Questions

The product slug is editable and so is the store page slug that sits above it, but the shape of the path is set by the platform. Changing the store page slug rewrites the address of every product under it, so it is a one-time decision rather than something to revisit. Add redirects at the same time as any change.

Because in most setups they are a filter rather than a page with its own content. There is nothing for a search engine to rank beyond a filtered grid. Building a small number of genuine category pages, with writing that answers the query and links into the relevant products, is the work that changes it.

No, it is generated automatically. That is less of a limitation than it sounds, because what actually matters is which pages you allow to be indexed, and that is controlled page by page. We go through the pages that should not be in search at all, such as thank-you and internal pages, and set them accordingly.

Through code injection, either site-wide or on specific pages. The important step first is checking what the template already outputs for a product, because adding a second description of the same product creates a conflict. We add markup only for what is genuinely missing, and we make sure the values match what a visitor sees on the page.

Send your squarespace store.

The plan is written for your store on the platform it runs on.