AI / AEO monitoring — stay visible to AI answer engines.
Relvato checks whether answer engines — ChatGPT, Perplexity, Claude, Google AI Overviews — can actually find and cite your site: llms.txt, AI-crawler access, structured data, a sitemap, snippet metadata, and server-rendered content.
- ✓/llms.txt present and valid
- ✓AI citation crawlers (GPTBot, PerplexityBot, ClaudeBot…) allowed in robots.txt — and actually reachable, not 403’d by your host or WAF
- ✓Content Signals in robots.txt — declaring how AI may use your content (search / ai-input / ai-train)
- ✓schema.org structured data and a sitemap
- ✓Content is in the server HTML, not JS-only
- ✓WebMCP tools and the AI catalog (ai-catalog.json) — what Lighthouse's Agentic browsing audits look at
AI answers are becoming a real traffic source, and being cited depends on signals most sites never check — is GPTBot allowed, is there an llms.txt, is your content in the HTML or only rendered by JS. Relvato scores your AEO readiness and flags what’s blocking a citation. It also checks what AI agents in the browser can use — WebMCP tools and the AI catalog; try any page with the free WebMCP checker.
Blocked from AI answers without knowing it? Our guide explains why AI bots can't crawl some sites — and how to unblock GPTBot, PerplexityBot and Claude.
- Checks for /llms.txt and parses robots.txt for the citation crawlers — GPTBot, OAI-SearchBot, PerplexityBot, ClaudeBot.
- Reads Content Signals in robots.txt (Content-Signal: search / ai-input / ai-train) — your explicit declaration of how AI may use your content.
- Verifies JSON-LD structured data, a sitemap, snippet metadata (title/description/OG), and that content is in the server HTML.
- Checks agent readiness: the WebMCP tools the homepage registers or declares on its forms (checked the way Chrome and Lighthouse check them), and the AI catalog (ai-catalog.json) against Lighthouse's schema.
- Advisory by design: warns on missing signals, fails only on real breakage like malformed structured data or a 5xx llms.txt.
What is AEO?
Answer Engine Optimization — being found and cited by AI answer engines. It overlaps with SEO but adds signals like llms.txt and AI-crawler access.
What are Content Signals?
A new robots.txt convention (Content-Signal: search / ai-input / ai-train) for declaring how AI systems may USE your content, separate from whether they may crawl it. Setting ai-input=yes is the explicit “yes, you may use my content to answer AI questions” that helps you get cited; ai-input=no opts you out. Relvato flags when none are declared, or when you’ve opted out.
Does it need a plugin?
No — AEO readiness runs on any site with a verified domain.
My host blocks AI bots to save bandwidth — will I know?
Yes. Relvato requests your homepage as each answer-engine crawler (GPTBot, PerplexityBot, ClaudeBot, OAI-SearchBot). If your host, CDN or a WAF rule returns a 403 or challenge — a common bandwidth-saving default — it’s flagged, even when robots.txt looks fine.
Put this monitor on autopilot.
Free forever on one site — 100 runs a month, started by you or weekly, no card. Pro re-runs your monitors by itself after every update.