Content scoring is useful, but a site that blocks GPTBot in robots.txt will not be cited no matter how good its schema is — and that is a one-line fix. Run the readiness check first, then work the graded issues. It is a lite scan by design: five dimensions, one grade, returned in under a second, with the deeper multi-platform audit sold separately.
A checker for whether a page is in a shape that answer engines can cite. It grades a URL from A to F across structured data, meta tags, content quality, technical configuration and AI-specific signals, and separately reports whether the crawlers behind those engines are allowed in at all.
- A quick grade and score for a URL plus the top 3 issues blocking citation — `get_aeo_score`
- The full breakdown across all five dimensions with the complete issue list and prioritised recommendations — `analyze_aeo`
- Crawler access checked: whether GPTBot, ClaudeBot, PerplexityBot and OAI-SearchBot are blocked, whether `/llms.txt` exists, and other access signals — `check_ai_readiness`
- The five dimensions themselves: JSON-LD schema markup; title, description and OpenGraph; headings, word count, FAQ and citable sentences; robots.txt, llms.txt, sitemap and speed; speakable schema, statistics and direct-answer format
Nothing — no account, no key, no auth. It is a remote server over Streamable HTTP; the endpoint recorded in its server manifest is `https://aeo-mcp-server.amdal-dev.workers.dev/mcp`, and the README also documents `https://citedbyai-mcp-server.citedbyai-gmail.workers.dev/mcp`. Add either as a `streamable-http` server in your client config. The same audit is also reachable as a plain REST call at `GET /audit?url=example.com`, which returns the full JSON result.
One command — npx -y mcp-remote https://citedbyai-mcp-server.citedbyai-gmail.workers.dev/mcp