Can AI crawlers read Squarespace sites?

Out of the box

15/100

With the Fix Kit

80/100

Hybrid

Readability depends on how the site is configured.

v2 scoring Estimated on the four-pillar score. A default Squarespace install earns 15/35 for raw-HTML readability; schema depth, llms.txt and AI-crawler rules depend on your setup, so they start at 0. The Fix Kit supplies those three (up to 65 points) but cannot change how Squarespace renders.

Squarespace serves most page content in HTML but loads galleries, summary blocks and some newer sections client-side, so parts of the page go missing for AI crawlers.

What is actually happening

Core text blocks render server-side and arrive in the initial HTML. Summary blocks, gallery sections and several of the newer 7.1 layout blocks hydrate after load, which means the content they hold does not exist in the raw response at all. Because those are exactly the blocks people use for "our latest work" and "featured posts", the parts of a Squarespace site that showcase what you do are disproportionately the parts a crawler cannot see.

13 of the major AI crawlers — including GPTBot, OAI-SearchBot, ChatGPT-User — fetch your HTML and parse it without running a JavaScript engine. Anything your page adds after hydration is not part of what they read.

What to do on Squarespace

01Move your key claims into plain text blocks rather than summary, gallery or list sections. A summary block is a convenience for visitors and a blind spot for crawlers.
02Add JSON-LD via Settings → Advanced → Code Injection for site-wide Organization schema, and per-page injection for Article or Product blocks.
03Write real meta descriptions per page in the page SEO panel rather than letting Squarespace generate one from the first text it finds.
04Add H2 subheadings inside long text blocks. The default styling encourages one continuous block, which chunks into a single undifferentiated passage.
05Replace text that lives inside uploaded images with real text blocks. The visual editor makes image-only pages easy to build and they contain literally nothing readable.

What trips people up

You cannot edit robots.txt on Squarespace, so you cannot add explicit Allow groups for individual AI crawlers. Squarespace manages the file, which is fine until you need to state an intent it does not express for you.
llms.txt cannot be served from the site root without a workaround, because Squarespace does not serve arbitrary files from the root path.
The visual editor makes it easy to build a page entirely out of images with text baked into them. It looks finished and contains zero readable content.
Blog post excerpts shown on index pages often come from a summary block, so an index that looks content-rich in the browser can be nearly empty in the HTML.

Where the files go on Squarespace

robots.txt is managed by Squarespace and not editable. llms.txt requires hosting it elsewhere and pointing a subdomain at it.

Stop guessing where your site sits

The baseline above is the platform. The free scan measures your actual site: how many words a crawler reads, whether your pages come back as empty shells, and which crawlers your robots.txt lets in.

Scan my Squarespace site