# AI Crawler Access Auditor (`axelhu/ai-crawler-access-auditor`) Actor

Audit robots.txt access for major AI crawlers across selected paths and check llms.txt / llms-full.txt without crawling site content.

- **URL**: https://apify.com/axelhu/ai-crawler-access-auditor.md
- **Developed by:** [Axel Hu](https://apify.com/axelhu) (community)
- **Categories:** SEO tools, Developer tools, AI
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.25 / 1,000 site access 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

See which major AI crawlers a public site allows or blocks on the paths you care
about, and whether the site publishes usable llms.txt / llms-full.txt policy
files. The Actor returns rule-level evidence rather than crawling page content
or guessing from an AI-readiness score.

### Minimal input

```
{
  "sites": ["https://example.com"],
  "paths": ["/", "/blog/"]
}
```

Bare domains are treated as HTTPS. Each supplied URL is reduced to its origin;
use paths for the robots.txt decisions you want to test.

### What one result contains

One Dataset row represents one selected site:

- robots.txt status/outcome and declared Sitemap URLs
- 14 fixed AI crawler tokens, each with allow/block evidence for every requested path
- matched user-agent group, Allow/Disallow rule, pattern, and source line
- llms.txt / llms-full.txt presence and basic structure (H1, summary, sections, links)
- explicit findings and an error when the bounded audit is incomplete

The fixed crawler set includes GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot,
Claude-SearchBot, Claude-User, Google-Extended, PerplexityBot, Perplexity-User,
CCBot, Bytespider, Applebot-Extended, Meta-ExternalAgent, and Amazonbot.

### Scope and limits

- 1-100 sites, 1-10 paths, at most 10 sites audited concurrently
- public HTTP(S) only; URL credentials and nonstandard ports are rejected
- every redirect and resolved IP passes the shared public-target safety checks
- no browser, login, cookies, proxy configuration, arbitrary request headers, or paid API
- no TDM/meta/homepage signals, anti-bot impersonation, site content crawling, or history/monitor mode in v0.1
- robots.txt and llms files are bounded to 1 MB each; run-level request/byte ceilings apply
- a missing robots.txt is reported as allow-all for this audit; an unreachable/invalid robots file yields unknown decisions
- 404/410 llms files are reported as missing; HTML masquerading as llms.txt is not treated as a valid file

The Actor evaluates published policy files. It does not prove that a firewall or
CDN will actually admit the named crawler.

### Billing

The billable unit is one successfully completed unique site audit
(domain-audited) plus Apify's normal run-start event. Invalid or incomplete
sites produce diagnostic rows without the domain-audited charge. Billable
capacity is selected before network work so the user's maximum charge limit can
reduce the number of sites fetched.

Current launch price:

- $0.00005 per run start
- $0.00025 per successfully audited site ($0.25 per 1,000 successful sites)

A one-site successful run therefore costs $0.00030 before any pricing tier
discount. In the accepted 10-site private cloud sample, the observed owner-side
platform cost was about $0.01955 per 1,000 successful sites. Apify's current
standard developer payout is 80% of PPE revenue minus platform costs.

Private PPE readback confirmed these exact event names/prices. Budget run
`JlPDo6kPLSu2msFCb` requested three sites with `maxTotalChargeUsd=0.00030`
and selected/fetched exactly one site before charging one `domain-audited`
event plus the run-start event.

### Verified private example

Private build `YjUsyGG2u6LWNVcSH`, run `yxeI9aEM6l6REs4r2`, input:

```
{
  "sites": ["https://apify.com"],
  "paths": ["/", "/store/"]
}
```

Returned one successful row with:

- `robotsOutcome: "parsed"`
- 14 crawler policies evaluated; all 14 allowed on both requested paths
- `llmsTxtOutcome: "found"`
- `llmsFullTxtOutcome: "missing"`
- finding `LLMS_FULL_TXT_MISSING`

This is a source-bound example from the private acceptance run, not a guarantee
that Apify's policy files will remain unchanged.

### Cost / reliability guard

Pause expansion and re-check pricing or scope if observed successful-site
platform cost rises above $0.08 per 1,000, or if stable-public-site acceptance
falls below 95% once at least 20 representative observations exist. Support
burden is tracked separately; persistent manual support beyond the intended
low-maintenance profile also triggers a scope/price review.

### Support

Open an Issue on this Actor's Apify page with the run ID and a non-sensitive
reproduction. Never post access tokens, cookies, internal hosts, or private URLs.

# Actor input Schema

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

Public site origins or domains. Bare domains use HTTPS. Paths in these values are ignored; audit paths are configured separately.

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

Path/query strings evaluated against robots.txt for every supported AI crawler.

## `concurrency` (type: `integer`):

Maximum sites audited concurrently.

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

Deadline for each robots.txt / llms.txt fetch.

## `maxFileBytes` (type: `integer`):

Maximum transferred or decoded bytes accepted from one robots.txt or llms file.

## Actor input object example

```json
{
  "sites": [
    "https://apify.com",
    "https://www.anthropic.com"
  ],
  "paths": [
    "/",
    "/blog/"
  ],
  "concurrency": 5,
  "timeoutSecs": 15,
  "maxFileBytes": 500000
}
```

# Actor output Schema

## `dataset` (type: `string`):

No description

## `summary` (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 = {
    "sites": [
        "https://apify.com",
        "https://www.anthropic.com"
    ],
    "paths": [
        "/",
        "/blog/"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("axelhu/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 = {
    "sites": [
        "https://apify.com",
        "https://www.anthropic.com",
    ],
    "paths": [
        "/",
        "/blog/",
    ],
}

# Run the Actor and wait for it to finish
run = client.actor("axelhu/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 '{
  "sites": [
    "https://apify.com",
    "https://www.anthropic.com"
  ],
  "paths": [
    "/",
    "/blog/"
  ]
}' |
apify call axelhu/ai-crawler-access-auditor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,axelhu/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/Oy4Q0f4ZPPsGhPKKp/builds/mddMmnXoUqmggfHSM/openapi.json