Intercom

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.

/pricing.md (machine-readable pricing)

No /pricing.md. AI procurement agents that evaluate and compare software prefer plain-text pricing they can read directly , no JavaScript, no tables to parse. Buffer, Resend, WorkOS, and Supabase all publish /pricing.md.

Fix: Create a plain-text Markdown file at /pricing.md. It should include: - Plan names and exact prices (e.g. "$9/month") - What's included in each plan (bullet list) - Annual pricing if available - A link to your full pricing page Serve it at /pricing.md with content-type text/markdown or text/plain. In Next.js, place the file in /public/pricing.md , Next.js serves public/ files automatically. Example: https://byfaro.ai/pricing.md

/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 MCP Server

No MCP Server Card or live endpoint detected. Model Context Protocol (MCP) is the dominant standard for AI agent integrations, adopted by Claude, Cursor, VS Code, GitHub Copilot, Gemini CLI, and 30+ others. Without it, agents can't take actions in your product.

Fix: Publish a machine-readable MCP Server Card at /.well-known/mcp.json: { "mcpVersion": "1.0", "name": "Your Company MCP Server", "description": "What AI agents can do with your product", "endpoint": "https://yourdomain.com/mcp", "capabilities": ["tools", "resources"], "auth": { "type": "bearer" } } If you don't have an MCP server yet, consider building one , it lets AI agents like Claude take actions in your product directly (create accounts, run searches, fetch data). This is the fastest-growing AI integration standard right now.