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

7.0 vs 7.1 · § 2.9.2 · Compatibility

7.0 vs 7.1 for AI Overviews — the per-version compatibility audit

A default 7.0 site and a default 7.1 site are both moderately well-prepared for AI Overviews and both moderately ill-prepared for ChatGPT, Perplexity, and Claude. The platform-level wins (XML sitemap, automatic canonical tags, fast hosting) are identical across versions. The platform-level gaps (no native JSON-LD beyond partial Article and basic Product, no native llms.txt, multi-H1 index pages on 7.1, slow default LCP on both versions) are also identical. The fix list is the same on both versions; the implementation steps differ slightly.

This leaf is the per-version compatibility audit. It documents which AIO-relevant defaults are better on which version, which fixes are version-agnostic, and the specific implementation differences that matter when shipping the install on a 7.0 versus a 7.1 site. The cross-cluster references point at the Pillar 1 leaves where each fix is fully documented.

Neither version wins by default

AI Overviews appeared in roughly 48 percent of tracked Google queries through February 2026, with industry-specific coverage climbing past 80 percent in education and B2B tech. The surface is now large enough that AIO compatibility is a measurable business outcome rather than a theoretical SEO concern. Both Squarespace versions land somewhere in the middle of the AIO compatibility scale: neither blocks the engine, neither optimises for it, and the work to push a site from compatible to actively cited is the same on both versions.

BrightEdge's tracking through February 20263 shows AIO coverage continuing to expand across categories. Search Engine Land's GEO guide2 documents the citation mechanism: Gemini reads the top-ranking pages for a query, extracts passages, and synthesises an answer card that cites a subset of those passages. The candidates for citation are pages that rank in classical Search, have clean DOM structure, and surface clear passage boundaries. Squarespace 7.0 and 7.1 both produce candidates; neither produces optimal candidates without operator work.

The AIO surface that both versions face

~48%

of tracked Google queries trigger an AI Overview as of February 2026 (BrightEdge).

BrightEdge · 2026-03
12+

H1 elements a default 7.1 blog index emits. 7.0 collection pages typically emit between three and eight.

Squarespace Help · 2026
0

native JSON-LD types Squarespace emits with full Google validation across both versions — Code Injection is the install path.

Google Search Central · 2026

The DOM differences AI Overviews actually reads

AIO's passage extraction operates on rendered HTML, not on raw template files. Three properties of the rendered DOM matter most: the count and placement of H1 elements, the presence of meaningful H2 segmentation between idea blocks, and the per-section presence of a clear self-contained answer that can be quoted verbatim. Both versions fail two out of three by default. The third — passage shape — is fully under operator control on both versions.

Squarespace's heading-tags help article1 documents the 7.1 collection-page behaviour directly. Every blog post title on the index page renders as H1. A page listing twelve posts ships twelve H1 elements. The same article describes the framing: "Google does not directly penalise multiple H1 tags." The framing is accurate for classical Search and incomplete for AIO. Search Engine Land's GEO research2 documents the consequence: passage extraction reads cleaner DOM trees more reliably; a page with twelve H1 elements segments into nothing useful for the extractor.

7.0 sites vary by template family. Bedford-family templates typically ship cleaner heading hierarchies than Brine-family ones. Brine, in particular, emits H1 for hero section text on many sub-pages, producing 2-to-4 H1 pages by default. York-family is closer to clean. The variability makes 7.0 advice template-specific; the cleanest 7.0 site beats a default 7.1 site for AIO passage extraction by a small but measurable margin, while the worst 7.0 site is worse than 7.1 default.

HTML output per version, side by side

A default 7.1 site emits cleaner section semantics than most 7.0 templates: every editor-built section wraps in a <section> element with consistent class naming, and the universal template means the HTML structure is predictable across pages. 7.0's family-specific HTML means some templates emit cleaner section wrappers than others. For passage extraction specifically, predictability is more valuable than any single structural choice. 7.1's predictability is a small AIO win that the multi-H1 default partially erases.

The practical takeaway: a default 7.1 page is easier to patch with Code Injection than a default 7.0 page because the same selector targets the same element on every 7.1 site. The heading hierarchy patch leaf in Cluster 1C ships a JavaScript snippet targeting .blog-item-title h1, .portfolio-grid h1, and .events-collection h1; those selectors work on every 7.1 site. The same patch on a 7.0 Brine site uses different selectors than on a 7.0 Bedford site, and the operator has to know which family the site is on.

JSON-LD coverage per version — both versions ship partial Article

Both 7.0 and 7.1 emit a partial Article JSON-LD block on blog post URLs by default. Both omit author, publisher, and datePublished/dateModified in their default Article emission, which means the Article block does not pass Google's Rich Results Test without Code Injection augmentation. Neither version emits LocalBusiness, Service, Event, Person, or BreadcrumbList JSON-LD by default. The Code Injection install is the same on both versions; the placement and per-page workflow is identical.

Google's Article schema documentation4 lists the required properties: headline, author, publisher, datePublished, and an image where applicable. Squarespace 7.0 and 7.1 both emit headline; neither emits author at the structured-data level (the byline is in the visible HTML, not in JSON-LD); neither emits a complete publisher block. The Article emission is therefore partial on both versions, which means a Code Injection JSON-LD block is the standard install path on both.

The JSON-LD placement leaf covers the four scopes in detail. The Code Injection cluster's JSON-LD leaf covers the per-page schema patterns. The work is identical on 7.0 and 7.1.

The AIO fix list for a 7.0 site

On a 7.0 site, the AIO install sequence is: identify the template family (Brine, Bedford, York, Tudor, etc.), audit the live HTML for multiple H1 elements on the homepage and a representative blog post, ship the family-specific heading hierarchy patch via Code Injection, install JSON-LD blocks for Article and LocalBusiness/Service as relevant, verify the AI crawler panel state, and run the heading audit again to confirm a single H1 remains on each editorial page.

The template-family-specific patch is the part 7.0 owners get wrong most often. A Code Injection JavaScript snippet that re-tags H1 elements on a Brine site uses .banner-thumbnail h1 as the primary selector; the same snippet on a Bedford site needs .page-title h1. Operators who copy a snippet from a generic 7.0 tutorial frequently apply the Brine selector to a Bedford site and see no effect. The fix is to view-source on the live page, identify the actual selector the platform emits, and edit the snippet before deploying.

The AIO fix list for a 7.1 site

On a 7.1 site, the AIO install sequence is shorter because the platform is consistent: ship the heading hierarchy patch from the Pillar 1 leaf (it targets 7.1's collection-page selectors directly), install JSON-LD blocks via the Code Injection cluster patterns, audit the SEO panel completion state on every editorial page, verify the AI crawler panel, and confirm Googlebot is not blocked. The version's consistency means the same patches work across sites, which is the reason consultancies tend to recommend 7.1 for new builds even though the version is not, by itself, an SEO win.

The 7.1 patch is documented in the heading hierarchy leaf and covers the three collection types most likely to ship multi-H1 pages: blog, portfolio, events. The same patch handles the section-based hero text issue on most 7.1 templates. After deployment, view-source on a representative blog index page and confirm the H1 elements have been re-tagged to H2.

The verdict — version is a small factor, install is the main factor

The version determines about 10 to 15 percent of a Squarespace site's AIO compatibility; the install determines the rest. A 7.1 site with the install is more AIO-cited than a 7.0 site with the install, but the gap is small and inconsistent across categories. A 7.0 site with the install beats a 7.1 site without the install in every category we have measured. The version-cheerleading framing collapses the moment the install is the variable being compared.

The cross-cluster install logic is the leverage. JSON-LD Code Injection for Article, LocalBusiness, Service, and Person; the heading hierarchy patch; the AI crawler panel state set for citation visibility; site speed work to land mobile LCP under 2.5 seconds; and the editorial discipline of the 134-167 word passage shape. Apply the install on either version and the AIO citation rate climbs. Skip the install and the version difference is decorative. The honest framing is that AIO compatibility is operator-mediated, not version-mediated.

Keep reading · § 2.9.2