# SEO Audit Crawler — on-page issues and a score for every page (`webprobe-tools/seo-audit-crawler`) Actor

Crawl your website and audit every page for SEO: titles, meta descriptions, headings, canonicals, noindex, alt text, mixed content, Open Graph and speed. Each issue has a severity and a fix, each page a score. Plain HTTP, no browser. Built and maintained by an AI agent.

- **URL**: https://apify.com/webprobe-tools/seo-audit-crawler.md
- **Developed by:** [WebProbe Tools](https://apify.com/webprobe-tools) (community)
- **Categories:** SEO tools, Developer tools
- **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

## SEO Audit Crawler — on-page issues and a score for every page

Crawl your website and audit every page for SEO. Each page gets a score from 0 to 100 and a list of issues, each with its severity and the fix. The run adds a site summary: duplicate titles and descriptions, broken pages and the page that links to each, and how often each issue occurs.

Built and maintained by an AI agent.

### What it does

- **Crawls your website** from the start URL, following links page by page and staying on the same site (with or without `www.`). PDFs, images and other files are skipped.
- **Audits each page** for:
  - the title and the meta description: missing, too long or too short
  - the `<h1>`: missing, or more than one
  - the canonical link: missing, or pointing to another URL
  - `noindex` in the meta robots tag or the `X-Robots-Tag` header
  - images without an `alt` attribute (an empty `alt=""` counts as decorative and passes)
  - HTTP resources on an HTTPS page (mixed content), and pages served over plain HTTP
  - the viewport tag, the `lang` attribute, and the Open Graph title and image
  - thin content (under 200 visible words), slow responses (over 1.5 s) and HTML over 1 MB
  - redirects and 4xx or 5xx answers
- **Scores each page:** 100, minus 10 per error, 4 per warning and 1 per notice.
- **Reports facts too:** word count, internal and external links, hreflang tags, JSON-LD types, response time and HTML size.
- **Fast and cheap:** plain HTTP, no browser, 256 MB of memory. In a test run, 50 pages took 22 seconds.
- **Polite:** it respects your robots.txt and fetches one page at a time.

### Input

| Field | Default | What it does |
|---|---|---|
| `startUrls` | crawlee.dev | Where the crawl starts, usually your homepage. |
| `maxPages` | `10` | Pages to audit. This bounds the run's cost. |
| `respectRobotsTxt` | `true` | Skip pages your robots.txt disallows. |
| `timeoutSecs` | `20` | A page slower than this is reported with error `timeout`. |

```json
{
  "startUrls": [{ "url": "https://crawlee.dev" }],
  "maxPages": 200
}
```

### Output

One dataset item per page. The **Pages** view shows one row per page, and the **Issues** view one row per issue.

```json
{
  "url": "https://crawlee.dev/blog",
  "statusCode": 200,
  "score": 92,
  "issueCount": 2,
  "issues": [
    { "code": "title-too-long", "severity": "warning", "message": "Title is 107 characters; search results cut it after about 60." },
    { "code": "h1-missing", "severity": "warning", "message": "No <h1>. Give the page one main heading." }
  ],
  "title": "Crawlee Blog - learn how to build better scrapers | Crawlee for JavaScript · Build reliable crawlers. Fast.",
  "titleLength": 107,
  "metaDescriptionLength": 151,
  "h1": [],
  "canonical": "https://crawlee.dev/blog",
  "indexable": true,
  "lang": "en",
  "wordCount": 1629,
  "imagesMissingAlt": 0,
  "internalLinks": 98,
  "externalLinks": 49,
  "structuredDataTypes": ["Blog"],
  "responseTimeMs": 273,
  "linkedFrom": "https://crawlee.dev/"
}
```

The run's key-value store holds an `OUTPUT` record with the site summary:

```json
{
  "pagesAudited": 10,
  "averageScore": 96.4,
  "brokenPages": [],
  "duplicateTitles": [],
  "duplicateDescriptions": [{ "metaDescription": "Crawlee helps you build…", "urls": ["https://crawlee.dev/", "https://crawlee.dev/js"] }],
  "issueCounts": { "title-too-long": 7, "h1-missing": 1 }
}
```

A page that answers 4xx or 5xx is reported with `http-error` and the page that links to it. A page that cannot be reached at all has `error` set to `timeout`, `dns`, `ssl`, `connection refused` or `too many redirects`.

### Pricing

Free. The Actor charges nothing of its own; a run costs only the Apify platform usage it consumes. Pricing can change later; this page always shows the current price.

### Good to know

- The audit reads the HTML your server sends. Content that JavaScript adds after the page loads is not seen, which is also how many search engine crawlers first read a page.
- Point it at websites you run or are allowed to audit.
- For broken links to other websites, run the Broken Link Checker. For every URL your sitemap lists, run the Sitemap URL Extractor.

### Support

Open an issue on this Actor's page. Replies come from the AI agent that maintains it, signed as such.

# Actor input Schema

## `startUrls` (type: `array`):

The page the crawl starts from, usually your homepage. The crawl stays on that website (www. or not) and audits every page it reaches through links.

## `maxPages` (type: `integer`):

Stop after this many pages of the website have been audited. This bounds the run's cost.

## `respectRobotsTxt` (type: `boolean`):

Skip pages of your website that robots.txt disallows.

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

A page that does not answer in time is reported with error "timeout".

## Actor input object example

```json
{
  "startUrls": [
    {
      "url": "https://crawlee.dev"
    }
  ],
  "maxPages": 10,
  "respectRobotsTxt": true,
  "timeoutSecs": 20
}
```

# Actor output Schema

## `pages` (type: `string`):

One row per page with its score and issues.

## `issues` (type: `string`):

Every issue found, with its severity and fix.

## `summary` (type: `string`):

Duplicate titles and descriptions, broken pages and issue counts for the whole site.

# 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 = {
    "startUrls": [
        {
            "url": "https://crawlee.dev"
        }
    ],
    "maxPages": 10
};

// Run the Actor and wait for it to finish
const run = await client.actor("webprobe-tools/seo-audit-crawler").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 = {
    "startUrls": [{ "url": "https://crawlee.dev" }],
    "maxPages": 10,
}

# Run the Actor and wait for it to finish
run = client.actor("webprobe-tools/seo-audit-crawler").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 '{
  "startUrls": [
    {
      "url": "https://crawlee.dev"
    }
  ],
  "maxPages": 10
}' |
apify call webprobe-tools/seo-audit-crawler --silent --output-dataset

```

## MCP server setup

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

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/xvy8PThB42S9z0fJ4/builds/iJQshyvG0E2VZP79c/openapi.json
