Squarespace SEO, Page by Page

The boundary worth naming up front: Squarespace SEO is not a separate discipline from SEO. The on-page rules — unique titles, useful descriptions, fast pages, indexable content, named author entities — are the same rules every platform plays under. What's different is the path you take to apply them. On WordPress, a Yoast or Rank Math plugin exposes every field. On Squarespace, the same fields live across four panels (Settings, Page Settings, URL Mappings, Code Injection), and three of them require Business plan or above to reach¹.

The platform's design choice trades flexibility for speed. Owners cannot break their robots.txt because they cannot touch it. The cost: per-page granular control sometimes requires a workaround — URL Mappings instead of .htaccess, Code Injection instead of a plugin, the SEO Site Description field as a homepage fallback rather than a content management system. The 11 clusters in this pillar walk through every one of those workarounds with the named Squarespace help-center or Google Search Central source.

• The SEO completion panel is a checklist, not a validator. A 100% green Squarespace completion panel does not mean the site has schema installed, the canonical chain is clean, or the page will rank. It means the title and description fields are non-empty. Treat it as a sanity check, not a verdict.
• Google rewrites title tags about 61% of the time. Zyppy's 2022 study⁶ of roughly 80,000 title links found 61.6% were rewritten by Google in the SERP. The lever for owners: write the title for the page, not for the SERP, and trust Google to choose between yours and a better candidate it surfaces from H1 or anchor text⁴.
• The AI-exclusion default is OFF. The "Block known artificial intelligence crawlers" checkbox in Settings > Crawlers ships unchecked³, meaning a fresh Squarespace site allows the 26 named training bots to crawl. The retrieval bots that produce live citations (ChatGPT-User, Perplexity-User, Claude-User) are not on the Squarespace list at all.
• URL Mappings is the only redirect path Squarespace exposes. Settings > Advanced > URL Mappings accepts old-path -> /new-path 301 rules. No .htaccess, no nginx conf, no plugin. Bulk migrations and slug changes route through this single panel.
• Squarespace auto-generates /sitemap.xml. You do not author it⁷. The platform builds the file from indexable pages (omits noindex and password-protected pages automatically). Submit it once to Search Console; Google re-fetches on its own schedule.

The cluster hub at /squarespace-seo/seo-panel/ walks through each field with the Squarespace help-center anchor, the Google Search Central guidance on how the field is used in the SERP, and the field-by-field install pattern for a typical 7.1 site. The leaf articles cover meta description, title tag, URL slug, Open Graph, canonical, and the completion panel one by one.

Most "my Squarespace site is not showing on Google" tickets resolve to one of five causes, in order of frequency: (1) the site is too new (under 2-3 weeks; Google has not crawled it yet); (2) Search Console property was never verified; (3) a page-level noindex was left on from a draft state; (4) a robots.txt or X-Robots-Tag conflict from custom code; (5) genuinely thin content with no inbound links. The diagnose leaf walks through the five-check pass with screenshots.

 # The Squarespace sitemap is always at the same path https://yoursite.com/sitemap.xml # It is XML-formatted, lists every indexable page, and refreshes when # you publish a new page or change a slug. You cannot edit it by hand. 

Two limits worth naming: URL Mappings does not support regex with capture groups; the wildcard syntax is positional, and complex patterns sometimes need multiple rules. And there's no built-in audit for redirect chains — an old URL that redirects to a URL that redirects to a third URL eats crawl budget and slows users down. The cluster's bulk-redirects leaf documents the migration map pattern: spreadsheet-author the entire mapping before touching URL Mappings, paste in one go, audit with a free crawler tool.

The site-speed cluster (2D) covers each metric individually: the LCP leaf maps the hero-image fix patterns, the CLS leaf addresses Squarespace's font-loading shift, and the JavaScript-defer leaf documents what to do about Squarespace's built-in scripts you can't move. INP replaced FID as the responsiveness metric in March 2024¹¹, and on a typical 7.1 site INP is the metric that drifts when third-party tools (chat widgets, scheduling embeds) are added without discipline.

A field-test surprise: alt text in Squarespace image blocks is not always preserved when an image is duplicated across pages. The platform sometimes keeps the alt text and sometimes resets it to filename. The bulk-alt-text leaf documents the workflow for auditing this on a multi-product Commerce store, where 200+ product images each need a unique alt entry.

The local cluster (2F) covers the Google Business Profile integration pattern, multi-location architecture, NAP consistency audit, and city landing pages. The honest scope: Squarespace gets you to a clean platform layer; ranking in the local pack is mostly driven by Google Business Profile activity (posts, reviews, photos) plus citation consistency across third-party directories — both of which happen off the Squarespace site itself.

The duplicate-description trap is the most common ecommerce SEO failure on Squarespace. A store with 40 product variants of the same item often ships 40 product pages with near-identical descriptions, and Google's content-classifiers downgrade the entire site as a result. The fix is variant-aware copy with the differentiating feature (size, colour, material) in the description, plus canonical tags pointing variants at the master product where appropriate. The duplicate-content leaf covers the full pattern.

The honest tradeoff: noindex the tag pages, keep the category pages indexed if they have unique introductions, and ship the canonical URL on every blog post as /blog/post-slug/ rather than the platform's optional date-in-URL alternative. The post-not-ranking leaf is the most-read page in this cluster in field tests — it walks through the eight reasons a post can rank in Position 30 instead of Position 5, with named-source diagnostic steps.

The honest scope: most owners on 7.0 should not migrate to 7.1 for SEO reasons alone. The platform-version risk is real, the URL structure changes are non-trivial, and the SEO gains are smaller than the migration risk for an established 7.0 site. The exception: owners on a 7.0 template Squarespace has deprecated for active development, where the long-term lack of feature parity (no fluid engine, no template-system updates) eventually causes drag. The upgrade-impact leaf documents the cost-benefit math.

The H1 fix is the single most-applied Code Injection on 7.0 templates. Several 7.0 templates render the navigation logo as an H1, which doubles or triples the H1 count on every page and confuses every search engine and AI engine that parses the page. The h1-fix leaf documents the per-template CSS + JavaScript patch. The hreflang leaf covers multi-language sites, where Squarespace's lack of native hreflang support makes Code Injection the only viable install path.

The traffic-drop diagnostic page is the most-read in this cluster on field tests. The five most common causes of a post-migration drop, in order: missing redirects (old URLs return 404 instead of 301), template-emitted noindex that the previous platform did not have, removed pages that carried inbound links, schema lost in the migration that Google relied on, and crawl-budget thrash from a sudden surge of new URLs that Google needs days to re-prioritise. Every one is fixable; most are preventable.

The right reading order for an owner doing a full audit: start here for the platform mechanics, then read Pillar 3 (Schema) for the JSON-LD layer, then Pillar 1 (AI Search) for the new traffic surface. If your goal is fixing a specific symptom — not showing on Google, slow site, lost rankings after migration — jump to the matching cluster diagnostic and skip the rest until you've shipped the fix.