For Squarespace

Squarespace agent readiness

Squarespace is the most locked-down builder on this list: code injection is limited to head and footer snippets, there is no filesystem, and there is no way to add a route or change a response header. What Squarespace does give you natively (SSL, a generated sitemap, SEO fields) is genuinely solid; everything past that needs to be added from outside the platform.

85

Native ceiling

Best achievable score without fronting

100

Cloudflare-fronted ceiling

Worker in front of your DNS, zero code changes

What agents currently see

A default Squarespace site is server-rendered, so content-readability generally passes, and the built-in SEO panel gives real control over title, meta description, and Open Graph tags per page, so meta hygiene is usually fine or close to it. HTTPS is forced platform-wide and a sitemap.xml is generated automatically for every site.

What is not achievable through the Squarespace dashboard at all: a raw file at /agents.md, /llms.txt, or /.well-known/verified.md, an MCP server card at /.well-known/mcp.json, custom response headers, or branching a response on the Accept header for markdown content negotiation. Head and footer code injection can add structured data as inline JSON-LD, which does work, but it cannot touch anything that requires a genuinely different HTTP response at a different path.

Your ceiling, and why

85 to 90 natively, mostly from what the SEO panel and code injection already cover: meta hygiene, an existing sitemap, structured data via a footer script, forced SSL. The checks that require a new route or a custom header (agents.md, llms.txt, the MCP card, .well-known/verified.md, content negotiation, x402 signaling) have no path through Squarespace's own settings. Cloudflare edge delivery is effectively required to close that gap: a Worker in front of your Squarespace domain can serve every missing file and header without Squarespace ever seeing the difference.

Which delivery model fits

Cloudflare edge is the realistic path to a high score on Squarespace, since so much of the gap sits outside what the platform's own settings expose. The Agent Ready Kit can still close the achievable pieces (meta hygiene tightening, structured data via a code injection snippet) if a Cloudflare migration is not on the table right now.

What is typically failing

  • agents.md
  • llms.txt / llms-full.txt
  • MCP server card
  • .well-known/verified.md
  • Content negotiation (Accept: text/markdown)
  • x402 payment signaling

See where you stand

Run a free scan, or start with the self-serve kit if you already know you need it.

Scan for free Get the kit