Zapier

No Content-Signal header

No Content-Signal header. AI systems have to guess whether they're allowed to use your content for training, search, or as agent input. Declaring your policy proactively builds trust with AI platforms.

Fix: Add a Content-Signal HTTP response header to tell AI systems your content permissions: Content-Signal: ai-train=yes, search=yes, ai-input=yes In Next.js (next.config.js): headers: async () => [{ source: '/(.*)', headers: [{ key: 'Content-Signal', value: 'ai-train=yes, search=yes, ai-input=yes' }] }] This header is part of the emerging Content Signals standard (contentsignals.org) adopted by Cloudflare and others. It declares explicitly what AI can do with your content.

OKF knowledge bundle (/okf/index.md)

No OKF bundle. Google's Open Knowledge Format (June 2026) lets AI agents navigate your business knowledge as a graph of linked markdown files. Less than 0.1% of sites have this.

Fix: Create an OKF bundle starting with /okf/index.md. Use Faro's OKF Generator to build a complete bundle automatically.

/agents.json (agent capability manifest)

No /agents.json. This file tells AI agents what actions they can take, what APIs you expose, and how to interact with your business.

Fix: Create /agents.json at your root: { "name": "Your Company", "description": "What you do", "url": "https://yourdomain.com", "capabilities": ["Browse products", "Check pricing", "Start trial"], "api": { "docs": "https://yourdomain.com/docs" }, "pricing_url": "https://yourdomain.com/pricing", "auth": ["api_key"] }

No A2A Agent Card

No A2A Agent Card at /.well-known/agent.json. Google's Agent-to-Agent (A2A) protocol enables AI agents to communicate with and delegate tasks to each other , including your product.

Fix: Publish an A2A Agent Card at /.well-known/agent.json: { "name": "Your Company Agent", "description": "What this agent can do", "version": "1.0", "url": "https://yourdomain.com/agent", "capabilities": { "streaming": false, "pushNotifications": false }, "skills": [{ "id": "your-main-skill", "name": "Main capability", "description": "..." }] }

No OAuth discovery

No OAuth discovery endpoint. AI agents that need to act on behalf of users can't automatically discover your auth flow.

Fix: If your product supports OAuth, publish a discovery document at /.well-known/openid-configuration following the OpenID Connect Discovery spec. This enables AI agents to authenticate users automatically without hardcoded auth URLs.