How to add llms.txt to Squarespace (URL mapping method)

Squarespace won't let you upload a file to your domain root — but it has a built-in feature most platforms lack: URL Mappings, which can 301-redirect /llms.txt to a copy of your file hosted anywhere. That makes Squarespace one of the easier locked platforms to work around. Here's the mapping method step by step, plus the cleaner edge alternative.

The two workable methods

Since direct upload is out, you either redirect the path to a hosted file (Squarespace-native, five minutes) or serve the path from an edge layer in front of your domain (cleaner, needs Cloudflare or similar). For most Squarespace owners the mapping method is the right call — no extra services.

First: create and host the file

1. Build your llms.txt with the free llms.txt Generator — site name, one-line summary, curated links with descriptions. See real examples for what good files look like.
2. Host the file somewhere stable that serves plain text. Easy options:
   • GitHub: put llms.txt in a public repo and use the raw-file URL.
   • Any static host (Netlify, S3, etc.) — a single-file deploy is fine.

Copy the hosted file's direct URL — you'll need it next.

Method 1: Squarespace URL Mapping (recommended)

1. In Squarespace admin, go to Settings → Developer Tools → URL Mappings (on some plans: Settings → Advanced → URL Mappings).
2. Add this line, substituting your hosted URL:

/llms.txt -> https://raw.githubusercontent.com/you/repo/main/llms.txt 301

3. Save, then visit yoursite.com/llms.txt — you should land on your Markdown file.

That's the whole method. When you update the file, you edit it at the host; the mapping keeps pointing at it. The trade-off is the redirect hop — fetchers follow 301s, so it works in practice, but the file technically resolves on another domain.

Method 2: Serve directly via an edge rule (cleaner, more setup)

If your domain's DNS runs through Cloudflare, you can answer /llms.txt directly with a Worker — the file then genuinely lives at your root with no redirect:

export default {
  async fetch() {
    const body = `# Your Site\n\n> One line about your site.\n\n## Key pages\n- [About](https://yoursite.com/about): Who we are\n`;
    return new Response(body, {
      headers: { "content-type": "text/plain; charset=utf-8" },
    });
  },
};

Bind it to the route yoursite.com/llms.txt only; everything else passes through to Squarespace. Choose this if you already use Cloudflare or care about avoiding the redirect hop; otherwise Method 1's simplicity wins.

Verify

1. Load yoursite.com/llms.txt — you should end at plain Markdown, not Squarespace's 404 page.
2. Paste the URL into the llms.txt Validator — it follows the redirect and checks the file against the spec.
3. Sanity-check your AI-crawler access overall with the AI Crawler Access Checker; Squarespace's managed robots.txt is permissive by default, but it's worth confirming what's actually being served.

Keep the file worth reading

Whichever method serves it, the content is what matters: a curated dozen-or-so links that answer the questions people actually ask an AI about you — what you do, pricing, services, contact, your best content. Update it when key pages change; a mapping pointing at a stale file teaches AI systems to distrust it. For the full picture of what the file is and why it's worth these five minutes, see what is llms.txt.