# AEO Readiness Checker (`tori-tic/aeo-readiness-checker`) Actor

Answer engine optimization (AEO) audit for any URL: checks AI crawler rules in robots.txt, llms.txt, schema markup and structured data, sitemap and answer-first text. One row per page with a 0 to 100 score and a fix for each weak check.

- **URL**: https://apify.com/tori-tic/aeo-readiness-checker.md
- **Developed by:** [Tori TIC](https://apify.com/tori-tic) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $10.00 / 1,000 page 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

## AEO Readiness Checker

**Checks whether AI answer engines and search engines can read a web page, and tells you what to fix.** Give it up to 100 page addresses. You get one row per page with a 0 to 100 readiness score and, for every failed or weak check, a plain-language fix.

### What it checks

- **Crawler rules.** Whether `robots.txt` lets the main AI search and assistant crawlers and the big search engines in, and whether the training crawlers are allowed or blocked (reported, not scored).
- **Indexing signals.** `noindex`, canonical link, page title, description and language.
- **Structured data.** JSON-LD that parses, and which schema types it declares.
- **Answer-first text.** Whether the first paragraph is a direct answer of about 40 to 60 words.
- **Headings.** Exactly one H1, and subheadings with enough of them written as questions.
- **Site files.** A sitemap, an `llms.txt`, a Bing site tag, and a visible date.

The score says whether engines can read and lift the page. It is not a prediction that any engine will mention you.

### Input

| Field | What it does |
|---|---|
| `urls` | 1 to 100 public web pages. Each is fetched once, plus that site's `robots.txt`, `sitemap.xml` and `llms.txt`. |
| `includeFixFiles` | Off by default. When on, also writes starting files per page: a `robots.txt` block, an `llms.txt`, and FAQ structured data built only from question headings that already have an answer paragraph on the page. |

Private, local and non-web addresses are refused. There is no option to change that.

### Output

One dataset row per page:

```json
{
  "url": "https://example.com/guide",
  "finalUrl": "https://example.com/guide",
  "status": "ok",
  "score": 74,
  "checks": [
    {"id": "answer", "title": "Answer-first paragraph", "result": "warn", "message": "First paragraph is 112 words.", "fix": "Open with a 40 to 60 word direct answer."}
  ],
  "robots": "found",
  "sitemap": 200,
  "llmsTxt": null,
  "error": null,
  "fetchedAt": "2026-10-09T12:00:00Z",
  "checkerVersion": "1.0.0"
}
```

`status` is `unreadable` (with the reason in `error`) when the page cannot be fetched or answers an HTTP error. Open the **Overview** view for a table, or **All checks** for every check with its fix. With `includeFixFiles`, the starting files are in the run's key-value store under `FIX_FILES`.

### Price

Pay per event: **USD 0.01 per page audited** and **USD 0.02 per page for the starting files** (only when you turn them on). Pages that cannot be read are never charged. Set a maximum charge for the run and it stops there. Platform usage is included in these prices.

### How it behaves

- One request a second to any one site, at most 4 pages at a time. It identifies itself as `AEO-Readiness-Checker/1.0`.
- It fetches only the pages you list and that site's `robots.txt`, `sitemap.xml` and `llms.txt`. It sends no cookies and does not log in anywhere.
- It does not rank your page against others, track citations, or tell you what to write. It checks technical readiness only.
- It cannot see pages that need JavaScript to show their text: it reads the HTML the server sends.

### Support

Open an issue on this Actor's page, or write to hello@ticassociation.com. Made by Tori, under the name TIC.

# Actor input Schema

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

Public web pages to check, 1 to 100. Each one is fetched once, plus that site's robots.txt, sitemap.xml and llms.txt. Private, local and non-web addresses are refused.

## `includeFixFiles` (type: `boolean`):

For each page, also write a robots.txt block, an llms.txt and (only where the page has question headings with answers) FAQ structured data, built only from what the page already says. Charged as a separate event per page.

## Actor input object example

```json
{
  "urls": [
    {
      "url": "https://tori-tic.github.io/"
    }
  ],
  "includeFixFiles": false
}
```

# Actor output Schema

## `overview` (type: `string`):

No description

## `allChecks` (type: `string`):

No description

## `fixFiles` (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 = {
    "urls": [
        {
            "url": "https://tori-tic.github.io/"
        }
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("tori-tic/aeo-readiness-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 = { "urls": [{ "url": "https://tori-tic.github.io/" }] }

# Run the Actor and wait for it to finish
run = client.actor("tori-tic/aeo-readiness-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 '{
  "urls": [
    {
      "url": "https://tori-tic.github.io/"
    }
  ]
}' |
apify call tori-tic/aeo-readiness-checker --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,tori-tic/aeo-readiness-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/jXBG8NNX8gZSD9K0a/builds/d0jzfUNOsXF2XXM7I/openapi.json