# AI Crawler Access Checker (`sagnato/ai-crawler-access-checker`) Actor

See which AI crawlers each site lets in: GPTBot, ClaudeBot, PerplexityBot, Google-Extended and 18 more, read from robots.txt the way RFC 9309 crawlers read it. Also checks llms.txt and noindex/noai tags.

- **URL**: https://apify.com/sagnato/ai-crawler-access-checker.md
- **Developed by:** [Sagnato](https://apify.com/sagnato) (community)
- **Features:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

Pay per usage

This Actor is paid per platform usage. The Actor is free to use, and you only pay for the Apify platform usage, which gets cheaper the higher subscription plan you have.

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

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

Find out which AI crawlers a website lets in. For every site you list, this actor reads robots.txt the way crawlers that follow RFC 9309 read it and tells you, for 22 known AI and search crawlers, whether each one is allowed, partly blocked or blocked, and which line decided it.

### What it checks

- **robots.txt, per crawler**: GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, Claude-SearchBot, Claude-User, anthropic-ai, PerplexityBot, Perplexity-User, Google-Extended, Googlebot, Bingbot, Applebot, Applebot-Extended, Amazonbot, Meta-ExternalAgent, Meta-ExternalFetcher, DuckAssistBot, CCBot, Bytespider, cohere-ai and MistralAI-User, plus any names you add.
- **Each crawler's purpose**: training, search, fetching for a user, or an opt-out token, so you can see at a glance whether a site blocks training but stays visible in AI search.
- **llms.txt and llms-full.txt**: whether the site publishes them, the title, and how many links they hold.
- **Home page signals**: noindex, noai and noimageai in the X-Robots-Tag header or robots meta tag.

### Why the results are right

Many quick checks only look for a `Disallow` line next to a bot's name. Crawlers don't read robots.txt that way. This actor follows the rules crawlers use:

- A group that names a crawler replaces the `*` group completely, so a site that names ClaudeBot with no rules lets it in even if `*` is blocked.
- The longest matching rule wins, and `Allow` wins a tie.
- `*` and `$` wildcards in paths are supported.
- A missing robots.txt (4xx) allows everything; an unreachable one (5xx or no answer) means "stay out".

### Input

| Field | What it does |
|---|---|
| `sites` | Domains or URLs, one per line. Up to 1,000 per run. |
| `paths` | Paths to test each crawler against. Default `/`. |
| `extraBots` | More user-agent names to test. |
| `checkLlmsTxt` | Look for llms.txt (default on). |
| `checkHomepage` | Read home page noindex/noai signals (default on). |

### Output

One dataset item per site, with each crawler's access and the deciding rule, a summary (counts, blocked crawlers, whether training is blocked while search is allowed), llms.txt details and notes. A readable Markdown report is saved as `REPORT.md` in the run's key-value store.

```json
{
  "origin": "https://example.com",
  "summary": { "allowed": 19, "partlyBlocked": 0, "blocked": 3, "blockedBots": ["GPTBot", "Google-Extended", "CCBot"], "trainingBlockedSearchAllowed": true, "hasLlmsTxt": true },
  "bots": [{ "bot": "GPTBot", "operator": "OpenAI", "purpose": "training", "access": "blocked", "rule": "Disallow: /" }]
}
```

### Good to know

- robots.txt is a request, not a lock. A firewall or CDN rule (such as a "block AI bots" setting) can still turn crawlers away by address, and no outside check can see that. The actor says so in every result.
- It reads at most three small files per site (robots.txt, llms.txt, the home page), one request at a time per site, at least a second apart, and it obeys robots.txt for its own user agent, `SagnatoBot`.
- It collects no personal data and uses no AI at run time.

# Actor input Schema

## `sites` (type: `array`):

Domains or URLs to check, one per line (example.com or https://example.com/blog). Only each site's robots.txt, llms.txt and home page are read. Up to 1,000 per run.

## `paths` (type: `array`):

Paths to test each crawler against. Defaults to the home page (/). Example: /blog/, /products/.

## `extraBots` (type: `array`):

Other user-agent tokens to test besides the 22 built in.

## `checkLlmsTxt` (type: `boolean`):

Look for /llms.txt and /llms-full.txt.

## `checkHomepage` (type: `boolean`):

Read the home page for noindex, noai and noimageai in the X-Robots-Tag header or robots meta tag.

## `maxConcurrency` (type: `integer`):

How many different sites are checked in parallel. Each single site is always read one request at a time, a second apart.

## Actor input object example

```json
{
  "sites": [
    "apify.com",
    "nytimes.com"
  ],
  "paths": [
    "/"
  ],
  "checkLlmsTxt": true,
  "checkHomepage": true,
  "maxConcurrency": 5
}
```

# Actor output Schema

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

One result per site: each AI crawler's access with the deciding robots.txt rule, llms.txt and home page signals.

## `report` (type: `string`):

The same results as a readable Markdown report.

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

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

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

```

## MCP server setup

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

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/zNTLHpnP6p9acL061/builds/ApNcAtjWoPNraQUUY/openapi.json
