Squarespace lacks native llms.txt support, but a URL Mappings 301 redirect makes it work. Exact upload-and-redirect steps plus an honest read on what it does.
Squarespace will not let you put a file at /llms.txt the way you would on a static host. There is no public folder, no file-at-root option in the editor, and no setting labeled "serve this at the domain root." That is why most people assume llms.txt on Squarespace is impossible. It is not. You upload the file to Squarespace's own file storage, then point /llms.txt at it with a 301 redirect through URL Mappings. Three steps, about fifteen minutes, no plugins.
This guide walks that workaround accurately, then tells you the honest truth about whether it is worth doing. If you have not read the foundational explainer, start with what llms.txt actually is and why AI clients fetch it. This post assumes you know the format and want it live on a Squarespace site.
Squarespace has no native llms.txt feature as of mid-2026. Wix and Webflow both shipped native handling over the past year, where the platform generates or serves the file for you. Squarespace has not, which leaves the manual route as the only route.
Here is the mechanism in one sentence. Squarespace gives every uploaded file a permanent URL under a /s/ path, and Squarespace also has a built-in URL Mappings tool that creates redirects. Put those two features together: store your llms.txt as a file, then redirect the canonical /llms.txt path to the stored file with a 301. An agent that requests yoursite.com/llms.txt follows the redirect and reads your markdown. That is the whole trick, and it works on any Squarespace plan that includes URL Mappings.
Decide what goes in the file before you touch Squarespace. An llms.txt is plain markdown with a specific shape: an H1 with your site name, a one-line blockquote summary, then grouped sections of links written as markdown bullets. Each link gets a short description so an agent knows what it points to.
A minimal version for a small business site looks like this:
> Brooklyn-based ceramics studio selling handmade tableware and running weekend pottery classes.
## Shop
- [Tableware](https://acmestudio.com/shop/tableware): Plates, bowls, and mugs, made to order.
- [Wholesale](https://acmestudio.com/wholesale): Bulk pricing for cafes and restaurants.
## Classes
- [Weekend Workshops](https://acmestudio.com/classes): Beginner pottery, two-hour sessions.
## About
- [Our Story](https://acmestudio.com/about): Who we are and how we make things.
- [Contact](https://acmestudio.com/contact): Hours, location, and how to reach us.
Use absolute URLs, not relative paths. Agents that read the file from a redirected location may not infer your origin correctly, so spell out https://yoursite.com/ on every link. Keep the file focused: your top pages, your policies, your highest-value content. You do not need every URL. You can hand-write this in any text editor, or generate it from your live site if you would rather not curate by hand.
Save your markdown as a .txt file on your computer. Squarespace does not host bare .md files cleanly, so use a .txt extension. Name it something obvious like llms.txt.
Now get it into Squarespace storage. The reliable way is to attach it as a file link. Open any page in the editor, add or edit a text block or a button, and choose to add a link. In the link dialog, pick the option to attach or upload a file rather than link to a URL or page. Upload your .txt file there. Squarespace stores it and hands back a permanent URL that looks like https://yoursite.com/s/llms.txt (the exact path includes a storage identifier Squarespace assigns).
Copy that /s/ URL and save it somewhere. You need the exact path for the next step. You do not have to keep the visible link on a published page if you do not want it shown. The file stays hosted once uploaded, and you can remove or hide the link block. Confirm the file is live by pasting the /s/ URL into a browser. You should see your raw markdown, not a 404.
This is the step that puts the file at the path agents actually request. In your Squarespace settings, find URL Mappings. The location moves around as Squarespace updates its admin, so look under Settings, in the area covering advanced or developer options. It is a single text box where each line is one redirect rule.
Add this line, swapping in your real stored path:
/llms.txt -> /s/llms.txt 301
The syntax has three parts: the source path you want to catch, an arrow (->), and the destination followed by the status code. 301 means a permanent redirect, which is what you want here so agents and search engines treat the stored file as the canonical answer for /llms.txt. Save the mapping.
Test it from the command line: curl -IL https://yoursite.com/llms.txt should show a 301 hop to your /s/ URL, then a 200 with your markdown body. In a browser, visiting yoursite.com/llms.txt should land on the file. If you get a 404 instead, double-check that the stored path in your mapping matches the /s/ URL exactly, character for character.
Two things to be straight about before you call this done.
First, the file is static. Squarespace is not regenerating it. When you add a product, launch a new service page, or rewrite your policies, the stored llms.txt still describes the old site until you re-upload it and update the mapping. For a brochure site that changes a few times a year, that is fine. For a store that changes weekly, manual re-uploads get old fast, which is the case for an automated generator that refreshes the file for you.
Second, the honest part. Does adding llms.txt actually do anything? The truthful answer in 2026 is: maybe, at the margins, and not for the reason people often claim. llms.txt is genuinely read by some agent and LLM tooling that fetches a site's index before crawling. It is also genuinely not a confirmed search ranking factor. Google's John Mueller and Gary Illyes have both publicly downplayed llms.txt for Google Search, with Mueller comparing it to the keywords meta tag and noting no major AI crawler has committed to using it. So do not expect it to "boost your SEO" or guarantee you get cited. Treat it as a cheap, low-effort bet: if agent workflows that read llms.txt keep growing, you are already positioned, and the cost to position was fifteen minutes. That is the realistic frame. Skip anyone selling it as a ranking hack.
If your goal is squarespace ai optimization more broadly, a few changes do more reliable work than the llms.txt file itself, because they affect whether AI crawlers can read your pages at all.
robots.txt; make sure it does not disallow the bots you want reading your site. If you have toggled on any "block AI" option, that overrides everything else here.llms.txt ever matters.None of these require a redirect or a stored file. They are the foundation; llms.txt sits on top.
Written by Crawlytics Team. Crawlytics tracks AI bots, generates llms.txt, and powers WebMCP commerce, all from one snippet on any stack. See how it works →
No. As of mid-2026 Squarespace has no native llms.txt feature, unlike Wix and Webflow, which both added native handling over the past year. There is no setting in the editor that generates or serves the file. You add it manually by uploading the file to Squarespace file storage and using URL Mappings to 301-redirect /llms.txt to the stored /s/ URL. The workaround takes about fifteen minutes and works on plans that include the URL Mappings tool.
No, a single clean 301 redirect on the /llms.txt path does not hurt your SEO. The redirect only affects requests to /llms.txt itself, which is not a page your human visitors browse or that Google ranks. Your real pages, sitemap, and internal links are untouched. The one thing to avoid is chaining redirects or pointing the mapping at a path that 404s. Test with curl -IL to confirm you get one 301 hop straight to a working file, then you are done.
Generally yes, well-behaved crawlers follow a 301 redirect to the final file. A 301 is a standard HTTP instruction, and the agents and LLM tools that bother to fetch llms.txt at all are built to handle redirects. The honest caveat is that llms.txt adoption itself is still partial, so "the bot follows the redirect" matters only for the subset of tools that request the file in the first place. The redirect is not the weak link; whether a given agent reads llms.txt at all is the open question.
Update it whenever the structure or key content of your site changes meaningfully, not on a fixed clock. For a small brochure site, that might be once or twice a year. For a store or a site with an active blog, monthly is reasonable, and weekly if your catalog moves fast. Because the Squarespace method is manual, every update means re-uploading the file and confirming the mapping still points at it. If that cadence becomes a chore, an automated generator that regenerates and re-serves the file is the upgrade path.
Not by default in the standard configuration, but Squarespace has shipped controls that let you block AI crawlers, so check your settings. If you have enabled any "block known AI crawlers" option, that will stop bots from reading your pages regardless of whether you have an llms.txt file in place. Review your crawler and robots settings under your site's privacy or SEO options, and make sure the bots you want reading your content are allowed before you spend time on the llms.txt file.
This page is part of Crawlytics.app. View all pages: llms.txt · llms-full.txt