Squarespace 7.1 SEO: The Quirks That Show Up on Every Audit
Published: January 20, 2026 · Last updated: April 7, 2026
Squarespace 7.1 is a great product for visual people and a tricky one for SEO people. I’ve audited enough 7.1 sites now to have a running list of the same issues showing up in the same places. Most of them are platform behavior, not client mistakes. Some are fixable inside Squarespace, some need code injection, and a few you just have to live with.
Here’s the running list, why each one matters, and what I actually do about them.
Gallery pages and the ?itemId= sprawl
Squarespace’s gallery blocks generate individual item URLs when users click into a photo or case study. Those URLs look like `/portfolio?itemId=abc123` and inherit the parent page’s title, meta description, and body copy. To a crawler, it looks like you have 50 pages with duplicate content.
Squarespace canonicalizes these correctly by default, so Google usually consolidates the signals to the parent page. But the audit tool flags them anyway, and Google Search Console will report them under “Alternate page with proper canonical tag.” That’s not a problem, it’s working as intended.
The real issue is when a photographer or portfolio site wants each project to rank for its own keywords. Canonical consolidation means those item pages won’t rank on their own. The fix is structural: build dedicated project showcase pages with their own URLs, H1s, and content, instead of relying on gallery items to do double duty. I’ve had to do versions of this on architect sites where every project really did need to rank on its own terms.
Multiple H1 tags from the template itself
Squarespace 7.1 templates frequently generate more than one H1 per page. The site title becomes an H1 in the header, the page title is an H1 in the banner, and any section headings configured as H1 will stack on top. I’ve seen pages with 5, 6, even 7 H1 tags, all coming from template structure rather than anything the owner added.
Google has said explicitly that multiple H1s are not a ranking penalty. That’s true. But it is an accessibility issue and a semantic clarity issue, and audit tools will flag it every time. When I find this, I document it as a medium-severity finding and recommend editors demote section headings from H1 to H2 wherever possible. The site title H1 and the banner H1 are template-level and stuck as they are.
You can’t edit robots.txt
This one surprises people. In Squarespace 7.1, there is no way to edit robots.txt directly. You get a Crawlers panel in settings that lets you block AI bots (OAI-SearchBot, GPTBot, ClaudeBot, and so on) but that’s the full extent of your control. You cannot disallow specific directories, cannot add a sitemap reference manually, cannot do anything that a WordPress owner takes for granted.
For most small to mid-sized sites this is fine. The default robots.txt on Squarespace is reasonable. If you have a specific crawl-budget problem or need to block parameter URLs, you’ll have to do it through code injection at the page level or through canonical and noindex meta tags, not through robots.txt.
The low text-to-HTML ratio red herring
Every Squarespace audit I run flags “low text-to-HTML ratio” on most pages. The pages that earn this flag are usually clean, well-built marketing pages with a reasonable amount of copy. The issue is that Squarespace’s underlying HTML is verbose. Lots of wrapper divs, lots of inline styles, lots of class names for every element.
Here’s what I tell clients: text-to-HTML ratio is not a Google ranking factor. Google cares about whether your content answers the query. It does not care about how heavy the markup is on a given page. If I’m auditing a Squarespace 7.1 site, I note the flag, explain that it’s platform behavior and not a problem to solve, and move on.
The thing is, a lot of audit reports leave this flag in the “critical” or “high” tier because the tool scores it that way. If you’re buying an audit, make sure the person reading it understands what’s real and what’s noise. This flag is noise.
Meta titles default to the full page title
Squarespace will use your page title as the meta title tag by default. If your page title is “Wedding Photography Services for Twin Cities Couples and Families,” that entire string becomes the title tag, and Google will truncate it at roughly 60 characters in search results.
The fix is straightforward. Go into the page settings, find the SEO section, and write a custom meta title under 59 characters. I use 59 as my personal cap because it gives a few characters of buffer against Google’s dynamic truncation rules. (Google’s own title link documentation walks through how titles get rewritten in the SERP.)
Worth saying: if you have 50+ pages to fix, this becomes a real project. Squarespace has no bulk editor for meta titles. You’ll do them one at a time.
Blog tags and categories behave as indexable pages
This one catches a lot of site owners by surprise. When you tag a blog post on Squarespace, the platform generates a tag archive page at a URL like `/blog/tag/tag-name`. Same thing for categories. Those tag and category pages are indexable by default, which means Google can and will crawl them.
On a well-run blog, this is fine. Tag pages can act as topic hubs if the tags are thoughtful and the blog has enough posts per tag to make the page useful. On a poorly tagged blog, you end up with dozens of thin archive pages, each with one or two post snippets, competing with your real content.
My default on a Squarespace blog audit is to look at the tag list first. If there are 30 tags and most have fewer than three posts, the tags are not ready to be indexable. The fix is either to consolidate tags down to a working set of topic hubs, or to noindex the tag archive pages until the blog grows enough to earn them.
The “summary blocks” link equity trap
Squarespace has a feature called summary blocks, which pull content from other parts of your site into a feed view. They look clean on the front end and are a common way to show recent blog posts on a service page or a homepage.
The thing is, summary blocks render links to the source content, and those links count as internal links for crawl purposes. That’s usually a good thing. The trap is when summary blocks are configured to pull from a category that includes pages you don’t want prioritized, or when they link to pages with low content value from pages with high content value. You end up flowing link equity to the wrong places without realizing it.
When I audit a Squarespace site with heavy use of summary blocks, I map where every summary block lives, what it pulls from, and what pages it’s feeding link equity to. About one in three site audits I run uncovers a summary block configuration that’s working against the site’s priority pages.
My honest take on Squarespace 7.1 for SEO
Squarespace is not broken. It has opinions. Most of those opinions are fine for a 10 to 30 page site where the owner or marketing lead wants to publish beautiful work without thinking about the HTML.
The place Squarespace gets hard is when a site grows past about 50 pages, wants to rank for competitive terms, or needs bulk technical edits. The platform was not designed for that workflow, and you will feel every constraint.
I still recommend Squarespace for clients who value design time and can live within the platform’s constraints. I don’t recommend it for content-heavy publishers, for sites that need granular technical control, or for anyone who wants to touch their own raw HTML. Pick the tool that fits the job. (If you’re weighing content-forward verticals like food blogging or higher education, the platform question matters even more than it does here.)
What I actually check on every Squarespace 7.1 audit
For anyone running their own audit, here’s my short list:
- Meta titles: are any above 59 characters? Is any page missing a custom title?
- Meta descriptions: missing, duplicated across pages, or longer than 160 characters?
- Gallery pages: is the parent page the one you want ranking, and are the item pages correctly canonicalized?
- H1 count per page: more than one? Which are template-level and which are editable?
- Page indexing in GSC: what percentage of your submitted URLs are actually indexed?
- Sitemap vs. live URLs: any orphans, any old paths that should be pruned?
None of this is glamorous. All of it matters.
Beyond that short list, the audit also includes: a check of tag and category archive pages for thin-content risk, a map of summary blocks and where they flow link equity, a review of code injection for any custom schema or noindex rules, and a comparison of the live sitemap against what’s actually published. Squarespace audits are finicky because the platform’s defaults are so opinionated, but once you know the quirks, the work is mostly pattern recognition.
The takeaway
Squarespace 7.1 is a design-first platform. Treat it that way. Use its strengths for the parts of the site where visual polish matters most, and work around its constraints everywhere else. Most of the issues on this list are either platform noise that can be explained away in an audit report or fixable quirks that a single editing pass can clean up.
If this list helped you recognize a flag you’ve been worrying about and realize it wasn’t actually a problem, that was the point. The goal was never to make you a Squarespace expert. It was to help you stop losing sleep over noise and focus on the handful of things that actually move the needle. If you want a second set of eyes on a Squarespace site before you change anything, you know where to find me.
About the author
Victoria Temiz is the founder of Vita Digital, an independent SEO consultancy based in Minneapolis. She is certified in Digital Marketing and in Project Management from the University of St. Thomas, and holds an SEO credential from UC Davis Extension. She has been building and running her own websites since 2007 and has focused specifically on SEO and search since 2020. She is also a working jazz vocalist. More about her work.
