PublishedVerifiedEvery 6 weeksSources5 namedAuthored bySquareRank Team
AI Overviews · § 1.3.5 · Diagnostic
Why Is My Squarespace Site Not in AI Overviews?
Five live checks tell you exactly why a Squarespace site is not appearing in AI Overviews on a target query. Crawlability (can Googlebot read the page?), ranking position (is the page in the top 10 of the classical SERP?), heading hierarchy and passage shape (is the answer extractable?), schema validation (do Article and Person JSON-LD pass?), and query-level AIO triggering (does AIO show up on the query at all?). Most causes fit one of these five; the diagnostic narrows the cause in under ten minutes.
Run the checks in order — each one filters out a class of cause. If check 1 fails, the issue is downstream of crawl access and nothing else will help until that is fixed. If check 5 fails, the rest of the work is fine; AIO just does not trigger on the query you tested. The deep-fix leaves are linked from each check; this page is the routing layer.
§01The short answer
TL;DR — five checks in under ten minutes, in order
The five-check diagnostic is sequential because each check filters out a class of cause. Step one verifies Googlebot can reach the page; if it cannot, nothing else matters. Step two confirms the page already ranks for the target query in classical Search; if it does not, AIO inclusion is unlikely. Step three audits heading hierarchy and passage shape — the editorial side. Step four validates Article and Person JSON-LD. Step five confirms the target query actually triggers AIO in the first place, because plenty of queries simply do not. Most Squarespace sites that are missing from AIO fail one of checks 2, 3, or 4.
Two non-Squarespace-specific notes before the checks. First, AIO appearance is not a binary — some queries trigger it, some do not, and the same query may trigger it for one user but not another based on personalisation. Test queries in a private window with a fresh session to minimise personalisation noise. Second, AIO citation is not the same as classical ranking; a page can rank #1 and never get cited, and a page ranking #6 can get cited prominently. The two surfaces are correlated but not identical.
§02Check 1
Check 1 — Confirm Googlebot can reach the page
AI Overviews is generated from Google's main Search index, which means Googlebot is the bot that decides eligibility. The Squarespace AI exclusion checkbox does not control Googlebot; the search-engine checkbox above it does. Open robots.txt in a private window, confirm Googlebot is not in any Disallow rule, and confirm Settings > Crawlers > search-engine checkbox is on. If anything here fails, no other check matters — fix this first.
The audit is fast. Open yoursite.com/robots.txt in a private browser window. Search for Googlebot. If it appears under a Disallow rule, Googlebot is being told to stay out and the page will not be indexed. If Googlebot does not appear in the file at all, the default rules permit crawling and the bot is allowed.
bashThe 60-second Googlebot reachability check
# Fetch robots.txt and check for Googlebot Disallow rules
curl -shttps://yoursite.com/robots.txt| grep -A1"User-agent: Googlebot"# Live test with the Googlebot user-agent
curl -I-A"Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)"https://yoursite.com/your-page/# Expected: HTTP/2 200 OK
The Squarespace-specific gotcha: the AI exclusion panel4 ships with 26 bots but Googlebot is not on the list. Toggling the AI checkbox affects training-class bots only; it does not change Googlebot reachability. The bot you care about for AIO eligibility is governed by the search-engine checkbox immediately above the AI checkbox — verify it is on.
§03Check 2
Check 2 — Verify the page already ranks for the target query
AI Overviews draws its citation candidates from the top of the classical SERP for the query. A page ranking outside the top 10 has a vanishingly small chance of being cited in the AIO above the same SERP. Open Google Search Console, find the target query in the Performance report, and check the page's average position. If it is outside the top 10, the next move is classical SEO, not AIO-specific optimisation.
Search Console1 is the authoritative source for position data on your own site. Open the Performance report. Filter by the target query in the Queries tab. Click into the query and check the average position over the last 28 days. If the position is above 10, the page is in the candidate set; AIO citation depends on the other four checks. If the position is below 10, address classical ranking first — AIO will follow.
§04Check 3
Check 3 — Audit heading hierarchy and passage shape
With crawlability and ranking confirmed, the editorial side becomes the next filter. View source on the target page. Count H1 elements (expect one; the heading hierarchy leaf covers the patch if you have more). Read the first 200 words and ask whether they answer the target query directly. Read the opening passage under each H2 — same test. If the answer arrives in paragraph three or hides inside an accordion, AIO extraction passes the page over.
The audit is mostly editorial. The view-source pass confirms the DOM is clean; the read-through confirms the editorial discipline is in place. Pages with multiple H1 elements often correlate with pages that also have buried answers — both are symptoms of a section-based editorial approach that prioritises visual variety over passage discipline. The heading hierarchy leaf covers the DOM fix; the passages leaf covers the editorial fix.
§05Check 4
Check 4 — Validate Article and Person JSON-LD
Run the page URL through Google's Rich Results Test. Confirm Article schema is detected with zero errors. Confirm the author field references the founder Person URL, not a fresh inline Person object. Open the /founder/ URL separately and confirm Person JSON-LD validates there too. Schema errors are silent — a page with broken Article markup is treated as if it has no markup, which weakens it relative to competitors who got the markup right.
Google's Rich Results Test2 remains the canonical validator. Submit the page URL, wait for the parse, and read the report. Article detection should pass with zero errors. Common Squarespace-specific issues: duplicate Article blocks (one from Squarespace's auto-emit, one from your Code Injection), missing image fields on Article (Squarespace auto-emits the feature image; Code Injection should not duplicate it), and Person blocks missing the URL field (the author reference works only if it points to a real URL).
The Person validation pass on /founder/ matters because the Article author reference depends on it. If Google fetches the /founder/ URL and finds no valid Person JSON-LD there, the author reference resolves to nothing and the article reads as authored by an anonymous string. Validate /founder/ separately whenever you validate an article. The E-E-A-T leaf ships the production Person block to paste into /founder/'s Code Injection.
What the diagnostic typically surfaces
5
checks in the standard diagnostic. Most missing-from-AIO Squarespace sites fail at check 2, 3, or 4.
Check 5 — Confirm the target query actually triggers AIO
The most common cause of 'my Squarespace site is not in AI Overviews' is that AI Overviews simply does not appear on the query the owner tested. AIO triggers on roughly 48% of tracked queries as of February 2026, but coverage varies dramatically by industry and query intent. Education queries trigger AIO around 83% of the time; B2B tech around 82%; restaurants around 78%. Commercial-transactional queries trigger it less. Test five to ten relevant queries; if AIO never appears, your category is in the low-triggering set.
BrightEdge's nine-industry tracker3 through February 2026 shows the variance: industries with informational query mixes (education, B2B tech) trigger AIO on most queries, while industries with transactional mixes (commercial restaurants, retail) trigger it less. The interpretation matters. If your category is in the low-triggering set, optimising for AIO is still worthwhile — the trigger rate is climbing — but the immediate ROI is smaller than for high-triggering categories.
The pragmatic move: test ten queries that map to your top pages. Note which queries trigger AIO at all. Among the AIO-triggering queries, note which ones your site is cited on. The two numbers (trigger rate, citation rate) tell you the realistic AIO ceiling for your site. A 30% trigger rate with 0% citation rate is an editorial problem (checks 3 and 4). A 0% trigger rate is a category problem (no editorial fix changes it).
§07The fix
What to do once you find the cause
Each check routes to a specific leaf in this cluster for the deep fix. Check 1 failure routes to the AI Crawlers cluster for the panel walkthrough. Check 2 failure is classical SEO — the broader Pillar 2 mechanics work, not AIO-specific. Check 3 failure routes to the heading hierarchy and passages leaves. Check 4 failure routes to the FAQ schema and E-E-A-T leaves. Check 5 confirmation means your work is done — wait for the category trigger rate to rise, or refocus optimisation on the surfaces (ChatGPT, Perplexity) where your category does see citations.
The checklist in the next section of this cluster (checklist leaf) ships the operational version of all the fixes in one 18-item reference list. Use the diagnostic to find the cause, then use the checklist to track the fixes through to verification.
