# AI SEO & GEO Audit: Can ChatGPT & Perplexity Read Your Site? (`hydrafetch/ai-seo-geo-audit`) Actor

Check whether an LLM or AI agent can actually read your pages, and get the specific reasons when it cannot.

- **URL**: https://apify.com/hydrafetch/ai-seo-geo-audit.md
- **Developed by:** [Hydrafetch](https://apify.com/hydrafetch) (community)
- **Categories:** SEO tools, Developer tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $27.00 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

<div align="center">

<img src="https://hydrafetch.com/brand/mark-512.png" alt="Hydrafetch" height="64" />

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

**Check whether an LLM or AI agent can actually read your pages, and get the specific reasons when it cannot.**

`Pay per result` · `No API key` · `No signup` · Powered by [Hydrafetch](https://hydrafetch.com?utm_source=apify\&utm_medium=readme\&utm_content=ai-seo-geo-audit)

</div>

***

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://`.

```json
{
  "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

```json
{
  "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](https://docs.apify.com/platform/schedules) 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](https://hydrafetch.com?utm_source=apify\&utm_medium=readme\&utm_content=ai-seo-geo-audit) · [Docs](https://hydrafetch.com/docs?utm_source=apify\&utm_medium=readme\&utm_content=ai-seo-geo-audit) · [MCP](https://hydrafetch.com/mcp?utm_source=apify\&utm_medium=readme\&utm_content=ai-seo-geo-audit)

### Other Actors by Hydrafetch

- [Company Enrichment API: Domain to Logo, Colors & Firmographics](https://apify.com/hydrafetch/company-enrichment-api): 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](https://apify.com/hydrafetch/bulk-company-logo-finder): 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](https://apify.com/hydrafetch/website-color-palette-extractor): 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](https://hydrafetch.com/terms?utm_source=apify\&utm_medium=readme\&utm_content=ai-seo-geo-audit)

### Support

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

***

<div align="center">
Built by <a href="https://hydrafetch.com?utm_source=apify&utm_medium=readme&utm_content=ai-seo-geo-audit">Hydrafetch</a>. Clean web data for developers and agents.
</div>

# Actor input Schema

## `urls` (type: `array`):

The URLs to process, one per line. Full URLs including https://.

## Actor input object example

```json
{
  "urls": [
    "https://stripe.com"
  ]
}
```

# Actor output Schema

## `results` (type: `string`):

AI SEO & GEO Audit: Can ChatGPT & Perplexity Read Your Site? records (the run's default dataset).

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "urls": [
        "https://stripe.com"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("hydrafetch/ai-seo-geo-audit").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "urls": ["https://stripe.com"] }

# Run the Actor and wait for it to finish
run = client.actor("hydrafetch/ai-seo-geo-audit").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "urls": [
    "https://stripe.com"
  ]
}' |
apify call hydrafetch/ai-seo-geo-audit --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,hydrafetch/ai-seo-geo-audit"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/KgYN4RNGU3v7Ncahj/builds/QjIJMFqomoAzE3XBZ/openapi.json
