# AI Crawler Access Auditor (robots.txt + llms.txt) (`honestagentkit/ai-crawler-access-auditor`) Actor

For each domain: which AI crawlers (GPTBot, ClaudeBot, Google-Extended, PerplexityBot, CCBot, Bytespider, etc.) robots.txt allows or blocks, whether /llms.txt and /llms-full.txt exist, and sitemap presence. One row per domain.

- **URL**: https://apify.com/honestagentkit/ai-crawler-access-auditor.md
- **Developed by:** [Honest Agent Kit](https://apify.com/honestagentkit) (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 $2.00 / 1,000 domain auditeds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

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

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
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.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## 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.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## AI Crawler Access Auditor (robots.txt + llms.txt)

Paste in a list of domains. For each one you get a row that shows which AI crawlers its robots.txt **allows**, **partially allows** or **blocks**, whether `/llms.txt` and `/llms-full.txt` exist, and which sitemaps it declares. You don't need a login, proxies or setup.

**Bots checked (14):** GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, anthropic-ai, Claude-User, Google-Extended, PerplexityBot, CCBot, Bytespider, Applebot-Extended, Meta-ExternalAgent, Amazonbot, cohere-ai.

### Use cases

- **SEO / GEO audits:** check whether a client's site can show up in AI search and answer engines, or whether it blocks them by accident.
- **Competitor research:** see which competitors opt out of AI training and which ones publish an `llms.txt`.
- **Publisher policy tracking:** schedule a weekly run over a list of sites and spot when a robots.txt policy changes.
- **Agency onboarding:** run one quick, repeatable check on every new client domain.
- **Dataset and compliance prep:** before you collect data, record which sites have opted out of AI crawlers.

### Input

```json
{ "domains": ["apify.com", "nytimes.com", "github.com"], "timeoutSecs": 10, "maxDomains": 500 }
```

### Sample output (one row per domain, trimmed)

```json
{
  "input": "nytimes.com",
  "origin": "https://nytimes.com",
  "ok": true,
  "robotsTxtStatus": 200,
  "llmsTxt": false,
  "llmsFullTxt": false,
  "aiBotsChecked": 14,
  "aiBotsBlocked": 13,
  "bots": { "GPTBot": "blocked", "ClaudeBot": "blocked", "Google-Extended": "blocked", "PerplexityBot": "blocked", "CCBot": "blocked", "Amazonbot": "partial", "...": "..." },
  "sitemaps": ["https://www.nytimes.com/sitemaps/new/sitemap.xml.gz", "..."],
  "checkedAt": "2026-10-10T09:18:38.000Z",
  "error": null
}
```

The `bots` values mean:

- `allowed`: `/` isn't disallowed.
- `partial`: some paths are disallowed.
- `blocked`: `Disallow: /` applies to that bot.

### 3 test audits (live run, 2026-10-10)

| Domain | AI bots blocked (of 14) | Pattern | llms.txt | llms-full.txt | Sitemaps declared |
|---|---|---|---|---|---|
| apify.com | 0 | All 14 allowed | yes | no | 1 |
| nytimes.com | 13 | All blocked except Amazonbot (partial) | no | no | 25 |
| github.com | 1 | Bytespider blocked; the other 13 partial (some paths disallowed) | yes | yes | 0 |

### Pricing

You pay per audited domain (`domain-audited`). If a domain is unreachable or invalid, you get a free error row. Set a max cost per run and the actor stops at your budget.

### Limits

- It checks the rules for the root path `/` only.
- It reads robots.txt as written. It doesn't test whether a firewall or CDN actually blocks a bot.
- Results show the site at the moment it was checked (`checkedAt`).

# Actor input Schema

## `domains` (type: `array`):

e.g. example.com or https://example.com

## `timeoutSecs` (type: `integer`):

Timeout for each HTTP request, in seconds.

## `maxDomains` (type: `integer`):

Maximum number of domains to audit in one run.

## Actor input object example

```json
{
  "domains": [
    "apify.com"
  ],
  "timeoutSecs": 10,
  "maxDomains": 500
}
```

# Actor output Schema

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

No description

# 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 = {
    "domains": [
        "apify.com"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("honestagentkit/ai-crawler-access-auditor").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 = { "domains": ["apify.com"] }

# Run the Actor and wait for it to finish
run = client.actor("honestagentkit/ai-crawler-access-auditor").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 '{
  "domains": [
    "apify.com"
  ]
}' |
apify call honestagentkit/ai-crawler-access-auditor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,honestagentkit/ai-crawler-access-auditor"
        }
    }
}
```

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/VOaH59rsVm6SM4ih6/builds/84SC3wXHfaQTb1LyZ/openapi.json