AI SEO & GEO Audit: Can ChatGPT & Perplexity Read Your Site?

---

Audits whether a page is readable by AI agents and answer engines. Six checks: whether the content is in the HTML or only appears once JavaScript runs, whether robots.txt lets assistant crawlers in, whether llms.txt is published, whether the page declares structured data and metadata a machine can read, and how much of the payload is markup rather than content. Returns the specific problems and how to fix each one, rather than a score with no explanation. Built for SEO and GEO audits, and for anyone who wants to be cited by ChatGPT, Claude or Perplexity.

What you get

• A score. How readable the page is to an agent, out of 100.
• Named problems. Each failing check by name, with what we saw and what to change. Not a score with no explanation.
• JavaScript dependence. Whether the content is in the HTML or only appears after scripts run, which is the difference between being read and being skipped.
• Crawler access. Whether robots.txt lets assistant crawlers in, and whether llms.txt is published.
• Structured data and metadata. Whether the page declares what it is in a form a machine can read.
• Markup bloat. How much of the payload is markup rather than content, because an agent pays for both.
• The actual output. The markdown an agent receives for the page, so you can see the result rather than trust the score.

Results export to JSON, CSV or Excel, or stream straight to your own database through the Apify API.

Common use cases

• GEO and AI SEO. Find out why ChatGPT, Claude or Perplexity are not citing your pages.
• Pre-launch checks. Audit a new site before it ships, while the fixes are cheap.
• Client reporting. Run a list of client URLs and hand back named problems with fixes.
• Competitor comparison. See which sites in your space are actually readable by agents.

Input

One field: URLs, one per line. Use full URLs, including https://.

{
  "urls": [
    "https://stripe.com",
    "https://vercel.com"
  ]
}

Output

One row per URL. A URL we cannot resolve is skipped rather than returned empty, and you are not charged for it. The run log names every one that was skipped, so a short result is never a mystery.

Field	Description
url	URL
score	Score
failed	Failed checks
problems	Problems

The table view shows the columns that scan best; the full record is in the JSON, CSV and Excel exports.

Example output

{
  "url": "https://example.com",
  "score": 72,
  "pagesSampled": 3,
  "passed": 5,
  "warned": 1,
  "failed": 1,
  "problems": "robots.txt allows AI agents; llms.txt is present",
  "fixes": [
    "robots.txt allows AI agents: Remove the GPTBot disallow rule."
  ],
  "sampleTitle": "Example Domain"
}

How it works

1. Paste your URLs into the input box, or point a task at a saved list.
2. Run it. Each URL is resolved on its own, so one bad entry cannot lose the batch.
3. Take the results as JSON, CSV or Excel, or have Apify push them straight to your own store.

You are charged per row returned. A URL we could not resolve is skipped and costs you nothing, which means a run's cost matches what you can actually use.

FAQ

What does the score mean?

How much of the page an AI agent can actually read and use. The named checks matter more than the number: they say what to change.

Why does JavaScript matter?

Many crawlers do not execute it. If your content only appears after scripts run, they see an empty shell.

What is llms.txt?

A convention for telling AI agents which pages matter and how to read your site, similar in spirit to robots.txt.

Do I need to fix everything it finds?

No. The checks are ordered by impact, and each failing one carries a specific fix.

Automate it

Save your input as a task and put it on a schedule to keep a list current. Apify can call a webhook when a run finishes, so results land in your own system without anyone watching the run.

Everything here is also available over the Apify API, which means any language with an HTTP client.

Use it in your own stack

For ongoing use, going direct is cheaper per record and adds the rest of the API: scraping, crawling, search, structured extraction, MCP access and webhooks. The same data, without the Store in the middle.

There are typed clients for Python, Node, Go, Ruby, Rust and PHP, and an MCP server so Claude, Cursor and Codex can call it directly.

hydrafetch.com · Docs · MCP

Other Actors by Hydrafetch

• Company Enrichment API: Domain to Logo, Colors & Firmographics: turn a list of domains into full company records: name, description, logo, brand colors, fonts, socials and industry.
• Bulk Company Logo Finder: Logos, Colors & Sizes by Domain: give it a list of domains and get a direct image URL for each company logo, with dimensions and dominant color.
• Website Color Palette Extractor: Colors, Fonts & Buttons: read a site's real design system: colors by role with contrast ratios, the type scale, corner radius and button styling.

Terms of use

The results are yours. You keep whatever rights you have in the inputs you submit and the output you get back, and we claim none of it. What we sell is the fetching and the processing, not the data.

Two things that follow from that. Third parties may hold rights in the underlying web content, and nothing here grants you rights over it. And because you choose the URLs, the legality of fetching a given target and of what you do with the result is yours.

Full terms: hydrafetch.com/terms

Support

Something not working? Open an issue on the Issues tab with the input you used.

---