← Platform guides

Squarespace: The Site Assistants Love to Recommend

2026-07-19 · Platform guides · squarespaceoperational layerengagementadoption

Squarespace sites are built to impress humans. But the next visitor deciding whether your business gets chosen may be an AI agent, sent by a user who asked it to "find a caterer and request a quote." Agents don't admire your design — they look for what they can operate. A site that publishes an operational layer — machine-readable context declaring your service, its operations, and a consent gate — becomes adoptable. On Squarespace you can get a working layer live in about an hour, using two features you already have: code injection and file upload.

What an agent sees on your Squarespace site today

Clean HTML (better than most builders), a managed sitemap, some structured data on commerce pages. All descriptive. No /llms.txt, no declared operations, no consent statement, no map of how enrolling or buying actually works. Squarespace does not allow uploading arbitrary files to your domain root at paths like /llms.txt — file uploads land under a storage path (typically /s/filename). That means your layer will be linked rather than sitting at conventional root paths. Less ideal, still effective — discovery links exist precisely for this.

Step 1 — Write your llms.txt

Draft it as plain text: service name and one-line definition, who it's for, key pages, your JSON manifest URL, and the consent declaration. Upload it via a link on any page (Pages → your page → add a link that uploads a file) or through Assets, then note the URL Squarespace assigns — usually https://www.yoursite.com/s/llms.txt. Check the file uploader accepts .txt; if not, upload as a downloadable file from a link block, which typically accepts text files.

Step 2 — Publish a JSON manifest via file upload

Write your manifest (below), save it as service-control-map.json, and upload it the same way. It will resolve at something like /s/service-control-map.json. This single file can be your starter layer; add per-page .json twins for pricing, booking, and shop pages as you grow.

Step 3 — Add the consent gate and transparency declaration

Inside both files, include:

The published layer identifies the authorized site publisher and explains that supported operations remain subject to the user's confirmation. Payment stays in the platform's normal human-confirmed checkout.

Open publication and explicit confirmation make the source and authority easier to assess, but do not eliminate prompt-injection, authorization, or platform-specific risks.

Step 4 — Map 3–5 core operations in a starter Service Control Map

Use the Adoption + Operation categories (evaluate · enroll · transact · configure · use · manage) and declare each operation's actuation — interface controls for most Squarespace sites, API endpoints where you have them:

{
  "service": "Example Catering (Squarespace)",
  "layer": "operational",
  "consent_gate": "Explicit user consent required before any operation.",
  "operations": [
    {
      "id": "evaluate",
      "type": "interface_control",
      "url": "https://www.example.com/menus",
      "intent": "Review offerings and pricing"
    },
    {
      "id": "enroll.quote_request",
      "type": "interface_control",
      "url": "https://www.example.com/contact",
      "inputs": ["name", "email", "event_date", "headcount", "message"],
      "expected_result": "Quote request received; reply within 1 business day"
    },
    {
      "id": "transact.shop",
      "type": "interface_control",
      "url": "https://www.example.com/shop",
      "notes": "Checkout is Squarespace-hosted and human-confirmed."
    },
    {
      "id": "manage.account",
      "type": "interface_control",
      "url": "https://www.example.com/account"
    },
    {
      "id": "manage.support",
      "type": "interface_control",
      "url": "https://www.example.com/contact"
    }
  ]
}

Step 5 — Link it all for discovery

This is the critical step on Squarespace, because your files aren't at root paths:

1. Code injection (header): Settings → Developer Tools → Code Injection (requires a plan that supports code injection — check yours). Add:

<link rel="alternate" type="application/json" href="/s/service-control-map.json" title="Operational layer">

2. Footer line: in Footer code injection or a footer text block: "This site publishes an operational layer for AI agents — llms.txt" with the link to your uploaded file.
3. Cross-reference: your llms.txt lists the manifest URL; the manifest lists the llms.txt URL. One found file reveals the whole layer.

Honest limitations on Squarespace

• No root-path files: agents that only probe /llms.txt by convention won't find yours — the head link and footer line carry the weight. This is a real gap; be honest with yourself about it and compensate with strong discovery links.
• Code injection is plan-gated; on lower tiers you may only have per-page header injection or none — check your plan.
• Uploaded file URLs can change if you delete and re-upload; update links when you do.
• No backend: you cannot serve dynamic endpoints, so your layer is static files plus links. For most service businesses that is entirely sufficient.
• Squarespace checkout and member areas are platform-hosted; map them as human-confirmed handoffs.

FAQ

Is a linked layer as good as root files?

Nearly. Convention paths help cold discovery, but a rel=alternate head link on every page is a standard, crawlable pointer — any agent reading your HTML finds the layer in one hop.

Do I need Squarespace's developer platform?

No. File upload plus code injection covers the whole starter layer. The developer platform only matters for advanced custom serving.

What should I map first?

Whatever earns you money or leads: the quote form, the booking page, the shop. Three to five operations is a complete starter map.

Want it generated for you?

The Free plan makes your most important page agent-ready — one hosted page, free, forever. The Basic plan (14-day trial, then $29/month) covers your full site, and Pro ($99/month) keeps a managed layer current as agent platforms evolve.

swa:1:aHR0cHM6Ly9zaGFyZXdpdGhteWFnZW50LmFpL3BsYXRmb3Jtcy9zcXVhcmVzcGFjZS5qc29u

Keep reading