PublishedVerifiedEvery 6 weeksSources10 namedAuthored bySquareRank Team
The 2026 playbook for Squarespace × AI search
Squarespace AI Search Optimization
AI search is a new category of traffic that doesn't behave like Google.
ChatGPT3, Perplexity5, Google's AI Overviews6, Gemini, and Bing Copilot answer questions directly — and the sites they cite are the ones their crawlers can actually read.
Squarespace 7.1 ships an AI-exclusion toggle that lists 26 named bots and defaults to unchecked2 — meaning a fresh site allows them. The real visibility problem is twofold: owners who ticked the box on after 2024-era “block AI bots” advice are now invisible to ChatGPT, Perplexity, Claude and Gemini retrieval; and live-retrieval bots like ChatGPT-User and Perplexity-User aren’t on the toggle list at all. There’s no native llms.txt9, the SEO panel grades you on the wrong exam, and the AI Visibility tool is locked to the Advanced plan. This pillar is the 2026 playbook for fixing every one of those gaps — verified against a named 2026 primary source per cluster.
The seven sub-clusters in this pillar
InfrastructurePlatform-level setup that gates every engine below.
AI search is the set of new query surfaces where the engine answers the user directly — ChatGPT, Perplexity, Google AI Overviews, Gemini, and Bing Copilot — instead of returning a list of blue links. Citations replace clicks: your job is no longer just to rank, it is to be the source the engine quotes.
Three categories of search now bring traffic to small-business websites. Classical search still drives most of it: Google and Bing return a ranked list of links, the user picks one, the site gets a visit. Answer engines — Google's AI Overviews block6 and Bing Copilot8 — sit above the classical results and synthesise a direct answer, citing three to six sources inline. Generative engines — ChatGPT, Claude, Perplexity, Gemini — answer entire questions in a conversation and cite the sources they drew from, sometimes prominently, sometimes as a footnote.
The same site shows up differently in each. A site that ranks #4 on Google might be quoted at the top of an AI Overview, ignored entirely by ChatGPT, and cited by Perplexity in second position. Each engine reads the page through a different lens, and the engineering decisions Squarespace made about how its 7.1 templates render HTML mean the lens for some engines does not focus.
The traffic shape changes in 2026
25%
drop in traditional search volume projected this year as users shift to AI answer engines.
The shift is not theoretical. Customers searching for a wedding photographer in Asheville, a therapist who takes evening appointments, or a tax attorney who handles estate planning are asking ChatGPT first and Google second — and what ChatGPT recommends is a function of which sites are crawlable, parseable, and citable in the form generative models prefer1.
§02The platform gap
Why Squarespace owners need a different playbook
Squarespace 7.1 ships a series of platform defaults that make AI search harder than it needs to be: the AI-exclusion panel lists 26 named bots and defaults to unchecked (so a fresh site allows them — but the bots that actually cite you live aren't on that list), the platform does not allow root-level file uploads (so llms.txt requires a workaround), section-based 7.1 templates fragment HTML in ways AI Overviews struggles to extract, and the AI Visibility panel is paywalled to the Advanced plan.
Every generic AI-SEO guide tells you to allow GPTBot3, add schema, and write more content. None tells you what Squarespace specifically does behind the scenes — and the gap matters. Four platform behaviours collide with the AI-search playbook in ways that need Squarespace-specific fixes, not generic ones.
Three more platform-specific gaps land in their own clusters: 7.1's section-based HTML break (which fragments H1/H2 hierarchy in ways AI Overviews extraction struggles with), the AI Visibility panel paywall (Advanced plan only, ~$72/mo, monitors one engine of five), and Squarespace's auto-emitted JSON-LD that occasionally conflicts with hand-injected schema.
§03The framework
The 5-step AI Visibility Framework
Five steps install AI visibility on a Squarespace site: unblock the right AI crawlers, install the right schema, ship llms.txt via the URL Mappings workaround, wire your entity through Person + Organization + sameAs, and restructure your top pages for the 134-167 word self-contained passage AI engines extract from.
The framework is sequential — each step depends on the previous one. Unblocking crawlers without installing schema produces noise; installing schema without entity wiring produces anonymous citations; entity wiring without passage-level structure produces pages AI engines can identify but won't quote. Skip a step and the next one underperforms.
01. Crawlers
Squarespace's AI-exclusion panel lists 26 named training bots and defaults to unchecked, meaning a fresh site allows them. The audit is: confirm the box is still unchecked, then recognise that the retrieval bots which actually cite you live (ChatGPT-User, OAI-SearchBot, Claude-User, Claude-SearchBot, PerplexityBot, Perplexity-User, Applebot) aren't on Squarespace's list at all — they pass through unless a higher-level platform block intervenes.
The distinction between retrieval bots and training bots is the part most generic guides skip — and it’s the distinction Squarespace’s toggle box gets wrong. Retrieval bots (ChatGPT-User4, OAI-SearchBot3, Perplexity-User, Claude-User7, Claude-SearchBot) fetch a page on demand when a user asks a live question — these are the bots that produce live citations. Training bots (GPTBot, ClaudeBot, Google-Extended6) scrape content to train future model versions — blocking them does not affect current-engine citations. Squarespace’s 26-bot exclusion list is exclusively training-class; the retrieval bots that decide whether you get cited tonight aren’t on it at all.
The AI Crawlers cluster has the full 26-bot exclusion list, the toggle-state audit, the retrieval-bot map, and a free crawler-check tool that audits your live site in 60 seconds.
02. Schema
Install Article, Person, and Organization JSON-LD via Code Injection on every editorial page. LocalBusiness for service-area businesses; Service for productised offerings; Product for ecommerce. Every Article's author field points to your founder Person entity, which carries sameAs links to LinkedIn, podcast appearances, and a Wikidata Q-ID where available.
Schema is not optional in 2026. AI engines use structured data as the fastest path to entity recognition: which site is "Asheville Family Photography", what is the entity behind that site, and is the author credible? A well-shipped JSON-LD graph10 collapses days of crawl-and-infer work into a single read.
JSON-LDMinimal Article schema with author pointing to /founder/
{"@context":"https://schema.org","@type":"Article","headline":"How to be cited by ChatGPT from a Squarespace site","datePublished":"2026-05-18","dateModified":"2026-05-18","author":{"@type":"Person","name":"Your Name","url":"https://yoursite.com/founder/"},"publisher":{"@type":"Organization","name":"Your Brand","url":"https://yoursite.com/"}}
Ship a /llms.txt file that lists your most important pages, structured for AI consumption. Squarespace does not allow root-level file uploads, so install via URL Mappings: redirect /llms.txt to a Squarespace page that returns the manifest content.
llms.txt9 is the emerging standard for telling AI engines which pages on your site are canonical, what topics they cover, and which ones to prioritise. Adoption is still uneven — not every engine reads it yet — but the ones that do (Perplexity, several enterprise AI-search products) treat it as a primary index.
The Squarespace workaround is documented in detail in the llms.txt cluster. The free llms.txt generator outputs a copy-paste manifest tailored to your business type.
04. Entity
Wire your founder Person schema with sameAs links to LinkedIn, Twitter/X, podcast appearances, conference talks, and a Wikidata Q-ID if you have one. Every article's author field points to this single Person entity.
AI engines disambiguate entities by following the sameAs graph. A founder Person entity with five strong sameAs links (LinkedIn, Twitter, a podcast appearance, a published book on Google Books, a Wikidata Q) is far easier for an AI to confidently attribute than an anonymous byline. The result: when a user asks the AI for "the wedding photographer in Asheville who writes about pricing", a recognised entity is more likely to be the cited answer than an unrecognised one.
05. Citation hygiene
Restructure your top pages so every H2 section opens with a bolded 1-2 sentence lead answer (134-167 words), followed by expansion. Cite 2-3 named 2026 sources inline per article.
The 134-167 word passage rule is the most underrated change in AI-search optimisation in 2026. Search Engine Land's GEO research1 consistently finds that AI engines lift answers from passages of roughly that length — long enough to carry a full thought, short enough to fit a citation card. Pages that lead each H2 with a bolded answer get cited; pages that bury the answer in the third paragraph get read but not quoted.
This pillar uses the format throughout. Notice that every H2 in this article opens with a bolded lead that stands alone — that's not a stylistic choice, it's the citation-hygiene rule applied to the playbook describing it.
§04Quotability
What gets cited, and what gets ignored
AI engines prefer named-source format ('According to Search Engine Land, ...'), dated claims ('as of March 2026, ...'), specific numbers over adjectives, and self-contained passages that answer the question without requiring the reader to click anywhere else. Bare assertions, undated 'studies show' framings, and answers buried inside long preambles get skipped in favour of competitors who shape their content to be quotable.
The pattern is easy to test. Search ChatGPT for "best practices for [your industry]" and inspect the citations: every cited passage tends to follow a tight format — a clear thesis sentence at the start, named sources inline, dates next to claims, and an answer that holds up on its own. Pages that do not look that way may rank in Google but they will not be quoted in a generative response.
§05Measurement
Measuring whether it's working
AI-search traffic is harder to measure than Google traffic because most AI engines do not send referrer headers — visits arrive as 'direct' even though they came from a ChatGPT citation. The 2026 measurement stack: Search Console for indexed coverage, manual AI-engine queries on a tracked schedule, brand-mention monitoring, and (on Squarespace Advanced) the AI Visibility panel for ChatGPT-only signal.
The dark-traffic problem is real and not solvable inside Squarespace alone. The practical workaround is a tracking spreadsheet: a list of 10-15 queries you want to be cited for, run weekly across each AI engine, with screenshots logged when you appear. Pair that with Google Search Console for indexed-page health, and you have a workable measurement loop.
The free SquareRank audit runs this measurement pass for you in 60 seconds and returns three scores: SEO, AEO, and GEO. It's the same scan we run on every $299 install before and after.
§06FAQ
Frequently asked questions
The five questions Squarespace owners ask most often about AI search, answered in the format AI engines prefer.
Will Squarespace's built-in AI Visibility panel cover this for me?
No. The Advanced-plan AI Visibility panel monitors whether ChatGPT mentions your site — it does not unblock crawlers, install schema, ship llms.txt, restructure content, or address the other four AI engines. It is a measurement tool, not a fix.
Can I do this without code injection?
Partially. The Crawlers panel is point-and-click. Everything else — JSON-LD schema, llms.txt via URL Mappings, robots meta directives, author E-E-A-T markup — requires Code Injection, which is locked to Business plan and above.
Does ranking in Google still matter if I am cited by ChatGPT?
Yes. AI engines pull from indexed content. A page that is invisible to Google is generally invisible to AI engines too. Classical SEO is the floor; AI search optimization is the ceiling.
How long until I get cited?
Initial crawler-unblocking effects appear within days. Schema and entity recognition typically take 2-6 weeks to influence AI engine output, depending on engine refresh cadence. The cluster pages on this site detail each engine's pattern.
What's the difference between AEO and GEO?
Answer Engine Optimization (AEO) targets engines that return a direct answer — Google AI Overviews, Bing Copilot. Generative Engine Optimization (GEO) targets engines that synthesise an answer from many sources — ChatGPT, Claude, Perplexity, Gemini. The tactics overlap; the citation surfaces differ.