Zapier's Agent-Readiness Gap
Public-surface analysis of zapier.com. Surfaces checked: HTTP response headers, robots.txt, 11 sitemap files, visible HTML + JSON-LD on /, /pricing, /agents, /mcp, /ai, llms.txt, and /.well-known/ endpoints. No auth, no internal tooling, no proprietary data.
Zero JSON-LD on /agents (Framer-rendered). The page describing Zapier's primary AI product, "Meet your new AI teammates," has no Service, SoftwareApplication, or Product schema. Agent retrieval pipelines have no structured anchor to attribute the offering to the entity.
Zero JSON-LD on /mcp (Framer-rendered). The page for Zapier MCP, their core agent-integration product, carries no Service or TechArticle schema. The h1 'Your AI can talk. Zapier MCP makes it act.' is invisible to structured retrieval.
SoftwareApplication on /pricing declares a single Offer: { price: "0", priceCurrency: "USD" }. Paid tiers (Pro, Team, Enterprise) aren't represented in structured data. An agent querying pricing via schema sees only a free product.
/pricing doesn't appear in any of the 11 sitemap files listed in robots.txt. The static marketing sitemap (5 entries) covers /page/webhooks, /page/welcome-start and three similar paths. The pricing page is crawlable but not sitemap-declared.
The rel=service-desc (OpenAPI), rel=service-doc (SDK reference), and rel=describedby (llms.txt) Link headers are present on the homepage. They're absent from /pricing, /agents, and /mcp, the pages an agent would most likely land on for capability lookup.
robots.txt declares Content-Signal: ai-train=yes, search=yes, ai-input=yes and explicitly allows GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, Claude-User, Claude-SearchBot, Google-Extended, PerplexityBot, and DuckAssistBot. AI crawler access is fully open.
154-line llms.txt at /llms.txt with stable section anchors (#mcp, #sdk, #agents, #auth, #integrations, #tables, #interfaces). Cross-references subdomain llms.txt files for docs.zapier.com. Well-structured for agent context.
/.well-known/agents.json present and valid: declares Zapier MCP with protocol: mcp and endpoint mcp.zapier.com/mcp. /.well-known/ai-plugin.json returns 404 (deprecated format, so absence isn't a gap).
- 1. Add Service + SoftwareApplication JSON-LD to /agents and /mcp. Both are Framer pages. The fix is injecting structured data via Framer's custom code injection (head section), not rebuilding the pages. One afternoon of work.
- 2. Expand the /pricing Offer array. Replace the single
{ price: "0" }with an AggregateOffer that includes Free, Pro, Team, and Enterprise tiers. Content is already on the page. - 3. Propagate Link headers to product and pricing pages. The homepage sets the right pattern. Extending it to /agents, /mcp, and /pricing is a framework headers config change for the Next.js-rendered pages, and a Framer custom code addition for the Framer pages.
- 4. Add /pricing to a sitemap. Lowest effort, lowest urgency. The page is already indexed, but for completeness it should appear in the static-statics sitemap or a new marketing sitemap.
Methodology note: all findings are based on public HTTP responses as of 2026-06-10. Rendered HTML was fetched without JavaScript execution. Framer pages serve SSR HTML to crawlers, so this reflects what a search or AI crawler receives. No claims are made about internal systems, analytics, revenue, or implementation quality beyond what is directly observable in the crawl output.
Want this read of your site?
Send your URL. We run the same public-surface diagnostic and hand you a prioritized roadmap of what to fix first.
Get the next teardown
Technical teardown, no fluff. One email when the next agent-readiness teardown goes live.