Cloudflare

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.

No Agent Skills file

No Agent Skills file. Agent Skills is an open standard (from Anthropic, now adopted by 30+ agent tools) for packaging specialized knowledge and workflows that AI agents load on demand. Sites that publish skills make it dramatically easier for agents to work with their platform.

Fix: Create a skills folder with a SKILL.md file at /skills/SKILL.md: --- name: your-product-name description: What AI agents can do with your product. Used for skill discovery. --- # [Your Product] Agent Skill ## Overview This skill teaches AI agents how to work with [Your Product]. ## Key workflows 1. How to authenticate 2. How to perform the main action 3. Common troubleshooting For the full spec see agentskills.io

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.

No x402 payment endpoint

No x402 payment endpoint detected. The x402 protocol allows AI agents to pay for services autonomously using micropayments. Niche now but growing fast as agentic commerce expands.

Fix: Implement an x402-compatible endpoint. See x402.org for the spec. Expose /.well-known/pay with a JSON response describing your payment terms for AI agents.