AEO & AI Visibility Checker — free AI-readiness audit for any website

Is your business cited when customers ask ChatGPT, Perplexity, Claude or Google AI? This free Actor audits any URL against the 7 AEO (Answer Engine Optimization) criteria and returns a score, the exact fixes, and — optionally — a ready-to-publish llms.txt draft. No browser, no proxy: a fast HTTP audit in a few seconds.

Use this tool when...

• You want to know if a website can be read, understood and cited by AI engines (ChatGPT, Claude, Perplexity, Gemini, Google AI Overviews)
• You need an AEO/GEO score (0–7) with the exact technical fixes, in one API call
• You want a generated llms.txt starter file for any website
• You build AI agents that vet local businesses, vendors, or leads for AI visibility
• You run SEO/AEO audits at scale for clients or prospects — as a service or a lead magnet
• You want to monitor AEO readiness over time: schedule it weekly on your own domains

Why AEO matters in 2026

More and more buying decisions start inside an AI answer, not a list of blue links. When a user asks "best hotel booking software in Luxembourg" or "who builds AI agents for SMEs", the engines cite businesses whose sites are machine-readable: structured data, clear entities, AI-friendly robots.txt, and an llms.txt identity card. Sites that fail these checks are invisible in AI answers — even if they rank well on Google. This Actor measures exactly that layer, for any URL, for free.

What it checks (7 criteria)

#	Criterion	Why it matters for AI citations
1	Structured data (JSON-LD)	AI engines extract facts from schema.org blocks
2	Business schema type	LocalBusiness/Organization declares who you are
3	Meta description	First text AI reads to understand the business
4	H1 heading	Confirms the page's main subject
5	Open Graph tags	Used for sharing and entity understanding
6	/llms.txt file	The identity card AI engines look for
7	AI bots allowed in robots.txt	Most sites block GPTBot/ClaudeBot without knowing

Every failed criterion comes with a concrete fix in topFixes — actionable by a developer or an AI agent without interpretation.

Input

Field	Type	Required	Description
url	string	yes	Full URL of the site to audit (homepage is scanned, plus /llms.txt and /robots.txt)
generateLlmsTxt	boolean	no	Also generate a ready-to-publish llms.txt draft (default: true)
dryRun	boolean	no	When true, the full audit runs but no pay-per-event fee is charged — use it to test your integration for free (default: false)

Output

One dataset record per run:

{
  "url": "https://example.lu",
  "score": 5,
  "scoreLabel": "5/7",
  "title": "Example — Services Luxembourg",
  "jsonLdTypes": ["ProfessionalService", "FAQPage"],
  "checks": {
    "json_ld": true,
    "schema_type": true,
    "meta_description": true,
    "h1": true,
    "open_graph": true,
    "llms_txt": false,
    "robots_ai": false
  },
  "robotsBlockedBots": ["gptbot"],
  "topFixes": [
    {"criterion": "llms.txt file", "fix": "Publish /llms.txt summarizing who you are for AI engines."},
    {"criterion": "AI bots allowed", "fix": "Remove Disallow rules on GPTBot/ClaudeBot/PerplexityBot/Google-Extended/CCBot."}
  ],
  "generatedLlmsTxt": "# Example — Services Luxembourg\n..."
}

The llms.txt draft is also stored in the key-value store as the record llms.txt (plain text).

Cost

Pay-per-event pricing (near-zero compute: no proxy, no browser — a fast HTTP audit in a few seconds):

Event	Price	When
run-started	$0.01	Once per run (flat fee)
audit-completed	$0.05	Once per completed audit (score + fixes + optional llms.txt)

A full audit costs $0.06. Set dryRun: true to test the whole pipeline for free — billing is skipped, output is identical.

Integration

API-first and AI-agent ready: call it from Python, JavaScript, curl, or via the Apify MCP server so any LLM agent can audit websites mid-conversation.

x402 / agentic payments

This Actor is reachable through Apify's x402 agentic payment rail (USDC on Base): agents can call it end-to-end with X-APIFY-PAYMENT-PROTOCOL: X402 — no Apify account needed.

FAQ

Does it work on any website? Yes — any public URL. JavaScript-heavy single-page apps may under-report JSON-LD if it is injected client-side (the audit is HTTP-only, which is exactly what most AI crawlers see).

Is a good classic SEO score enough for AI citations? No. Google ranking and AI citability are different layers: AEO criteria (schema, llms.txt, AI bots access) are not ranking factors in classic search. Sites with great SEO regularly score 3–4/7 here.

Can I audit my competitors or prospects? Yes — batch it over a list of URLs to benchmark a market's AI readiness, or to qualify leads for an AEO service.

How often should I re-audit? After every site change touching templates, <head>, or robots.txt — or schedule a weekly run and compare scores over time.

Who maintains this Actor? Adaga solutions, a Luxembourg software studio running AI agents and data APIs in production for real clients.

Related Actors by Travel Monitor Lab

• Google Maps Business Scraper — local business data at scale
• Google Maps Review Alerts (Review Radar) — new-review monitoring with Slack alerts
• API Breaking-Change Impact Radar — OpenAPI diff monitoring for the APIs you depend on
• RAG Web Browser — crawl pages into LLM-ready text

---

Built and maintained by Adaga solutions — full-stack & AI agents in production, Luxembourg. Site web · AEO guides · More data APIs

Pricing

Pay only for the events listed below. Apify platform usage may also apply.

• Run started (run-started): $0.01 per event.
• Audit completed (audit-completed): $0.05 per event.

A free or low-cost dry-run option is provided where supported by the input schema.

Related Actor

Pair this workflow with local-ai-presence-audit for an end-to-end Adaga solutions data pipeline.

Support and feedback

Open an issue on the Actor page if a run fails or the output differs from this README. After a successful real run, an honest review helps other users evaluate the Actor. Report the input, run status and expected output; never include credentials or private data.