lintpage
~/llms-txt/squarespace
§ Squarespace

llms.txt on Squarespace

Squarespace 7.1 has an llms.txt field in its SEO settings, disabled by default and empty until you write it. How to turn it on, what belongs in it, and what 7.0 sites can do instead.

Squarespace serves pages and assets it manages, plus the root files it has built settings for. On 7.1, llms.txt is one of them: you supply the text and the platform serves it.

§ how to serve it

Serving /llms.txt from Squarespace.

step 1

Turn the setting on in SEO settings

On version 7.1 sites, Squarespace exposes the file in the SEO/AI Visibility panel: SEO Settings, then the LLMS.txt tab. The field is disabled by default and starts empty, and the platform writes nothing for you, so enabling it without pasting content in achieves nothing.

step 2

Write the index yourself, then fetch the URL

Because the field starts empty, the quality of the file is entirely yours: an H1 with the site name, a one-line summary in a blockquote, then H2 sections listing the pages worth reading with a note on each. Save, publish, and read the path back on your live domain rather than trusting the settings screen.

bash
curl -s https://your-domain.com/llms.txt | head -10
step 3

On 7.0, the setting does not exist

Squarespace documents this for 7.1 only. On a 7.0 site the options are the ones that were always available: put a CDN or proxy in front of the domain so it answers /llms.txt before Squarespace sees the request, move the site to a host that lets you write to the root, or upgrade. Each is a larger decision than one file justifies for most sites, which is a legitimate reason to skip it.

step 4

Make sure the rest of your AI visibility is not broken

This is the part that matters most and the part most checklists skip. If AI crawlers cannot fetch your pages - because of a block, or because your content only appears after JavaScript runs - an llms.txt would not have helped anyway. Squarespace has a switch for exactly this: a "Block known artificial intelligence crawlers" setting, which its own documentation tells you to uncheck if AI visibility is what you are after. Check that one first, because a site serving an index to clients it also blocks is the same contradiction as the robots.txt case, just spread across two settings panels instead of two files. Worth verifying whether or not you ever fill in the llms.txt field.

§ what goes wrong here

What Squarespace gets wrong.

The failures below are specific to Squarespace. A generic llms.txt guide will not mention any of them.

01

Squarespace 7.1 only, and empty until you fill it

The Squarespace-specific trap now that the setting exists: a checklist can be ticked without a file existing. It ships disabled and blank, on 7.1 sites only, and the platform generates no starting content. In a probe of the 10,000 most popular sites, exactly one Squarespace site served a file at all - Squarespace itself. A capability and its use are not the same thing.

02

A page named "llms" is not the file

You can create a Squarespace page at /llms and paste your index into it. That is an HTML page at a URL nothing is looking for. It may be useful to human visitors; it satisfies nothing about the format.

03

Code injection still cannot create the file

The old workaround people reach for, and it cannot do the job. Squarespace documents code injection as inserting markup into the head, or before the closing body tag, of pages that already exist, and says separately that server-side code is not supported - so there is nothing in it that can answer a request for a path with no page behind it. Squarespace never addresses llms.txt in those articles, so treat that as our reading rather than a line in its docs. Guides written before the setting shipped still recommend trying it.

§ faq

Questions, answered.

Can I add an llms.txt to Squarespace?
Yes, on version 7.1. Squarespace added an LLMS.txt tab under SEO Settings in the SEO/AI Visibility panel, where you enable the file and paste in its content. It is off by default and the platform writes nothing for you. Guides saying the domain root is closed on Squarespace, including an earlier version of this page, predate that setting.
Does Squarespace generate the llms.txt for me?
No. Shopify generates an agents.md for every store and mirrors it at /llms.txt, and Wix generates and maintains a file on upgraded sites that have a custom domain and indexing enabled, pausing those automatic updates as soon as you edit it. Squarespace instead hands you an empty field and serves what you type into it. That is more work and more control: nothing appears at the path until you have decided what belongs there.
Does code injection work for llms.txt on Squarespace?
No. Squarespace documents code injection as inserting markup into the head or before the closing body tag of pages that already exist, and does not support server-side code, so nothing there can answer a request for a path that has no page. Squarespace does not discuss llms.txt in those articles, so that is our reading rather than its statement, though the conclusion is not really in doubt. Use the LLMS.txt setting on 7.1; on 7.0 the routes are a proxy in front of the domain or moving hosts.
What should I do instead?
Make sure your content is server-rendered and reachable, that your robots.txt is not blocking the AI crawlers you want, and that your pages have clear titles and descriptions. Those affect what AI assistants can actually see about your site today, which is more than an llms.txt currently does for anyone.

LintPage is not affiliated with any platform or plugin named on this page. The claims here were last checked against vendor documentation on 2026-09-18. Settings and defaults move quickly, so confirm against your own install before relying on one.

§ the part that matters

An llms.txt will not fix a site AI cannot read.

Before writing an index for AI clients, check that they can fetch your pages at all. LintPage runs 60 checks against a URL in about 30 seconds - free, no signup.

run a full scan →