For Webflow

Webflow agent readiness

Webflow server-renders every page as static HTML, which is genuinely good for agents: there is real text in the response, not a blank div waiting on JavaScript. The gap is almost entirely the machine-facing layer that sits outside the visual designer.

87

Native ceiling

Best achievable score without fronting

100

Cloudflare-fronted ceiling

Worker in front of your DNS, zero code changes

What agents currently see

Because Webflow's canvas output is server-rendered HTML, content-readability usually passes without any work. The site settings panel also gives you real control over robots.txt, a generated sitemap.xml, and per-page title, meta description, and Open Graph fields, so meta hygiene and sitemap.xml are often already fine or one settings change away.

What Webflow does not give you: a way to publish a raw file with a non-HTML Content-Type at an arbitrary root path (so /agents.md, /llms.txt, and /.well-known/verified.md have no native home), custom response headers, or a route that can branch on the Accept header for markdown content negotiation. An MCP server card at /.well-known/mcp.json runs into the same wall: it needs a JSON response type Webflow's page system was not built to serve.

Your ceiling, and why

85 to 90 natively. Everything the Designer and site settings can reach (meta hygiene, sitemap, robots.txt, structured data via custom code embeds, SSL) is achievable without a workaround. The remaining checks all require serving a non-HTML response at a specific path or header, which sits outside what Webflow hosting exposes. Fronting the Webflow domain with a Cloudflare Worker closes that gap completely: the Worker intercepts requests for /agents.md, /llms.txt, /.well-known/mcp.json, and the Accept: text/markdown case before they reach Webflow, and passes everything else straight through untouched.

Which delivery model fits

If your DNS is not on Cloudflare yet, the Agent Ready Kit still gets you most of the way: structured data and meta hygiene through custom code embeds, robots.txt and sitemap through site settings, all with paste-ready steps for the Webflow Designer. Cloudflare edge delivery is the recommended path if you want the full 100, since it is the only way to add the file-and-header checks a page builder cannot expose on its own.

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