# SEO Site Audit Scraper: On-Page Issues for Every Page (`scrapemint/seo-site-audit-scraper`) Actor

Crawl any website and get an SEO audit row per page: title and meta checks, H1s, canonical, noindex, redirect chains, broken internal links, image alt coverage, word count, and a ready-made issues list. No browser, no API key. Pay per page.

- **URL**: https://apify.com/scrapemint/seo-site-audit-scraper.md
- **Developed by:** [Ken M](https://apify.com/scrapemint) (community)
- **Categories:** SEO tools, Marketing
- **Stats:** 10 total users, 3 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$3.00 / 1,000 audited page rows

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

## SEO Site Audit Scraper: On-Page Issues for Every Page

Run a technical SEO audit on any website and get one clean JSON row per page. Each row carries the on-page facts (title, meta description, H1s, canonical, robots directives, image alt coverage, word count, structured data, redirect chain, response time) plus a ready-made `issues` list, so you can filter straight to the problems. No browser, no API key, no seat license.

Built for SEO agencies and freelancers who deliver recurring audits, in-house teams watching their own sites, and anyone wiring SEO health into a dashboard. Put it on a weekly schedule per client site and diff the issues over time.

### What you get

One row per audited page, with:

- `title`, `titleLength`, `metaDescription`, `metaDescriptionLength`, `metaRobots`, `canonical`, `lang`
- `h1Count`, `firstH1`, `h2Count`, `wordCount`, `structuredDataBlocks`, `hasOgTitle`
- `imageCount`, `imagesMissingAlt`
- `httpStatus`, `redirectChain`, `redirectHops`, `responseMs`, `htmlBytes`
- `internalLinkCount`, `externalLinkCount`, `brokenLinks` (URL + status), `brokenLinkCount`
- `issues` — e.g. `missing_meta_description`, `title_too_long`, `duplicate_title`, `multiple_h1`, `noindex`, `redirect_chain`, `broken_internal_links`, `thin_content`, `images_missing_alt`
- `issueCount`, `depth`, `auditedAt`

Duplicate titles and meta descriptions are detected across the whole crawl, not per page.

### Input

- `startUrls` (pages to start from)
- `maxPages` (default 20, up to 1000)
- `maxDepth` (default 3)
- `includePatterns` / `excludePatterns` (URL substring filters)
- `checkBrokenLinks` (HEAD-check every discovered internal link once, default on)
- `useSitemap` (seed the crawl from sitemap.xml)

### Example input

```json
{
  "startUrls": ["https://example.com"],
  "maxPages": 100,
  "useSitemap": true,
  "checkBrokenLinks": true
}
```

### Example output

```json
{
  "url": "https://example.com/pricing",
  "httpStatus": 200,
  "redirectHops": 0,
  "title": "Pricing",
  "titleLength": 7,
  "metaDescription": null,
  "h1Count": 2,
  "wordCount": 96,
  "imagesMissingAlt": 4,
  "brokenLinkCount": 1,
  "brokenLinks": [{ "url": "https://example.com/old-plans", "status": 404 }],
  "issues": ["title_too_short", "missing_meta_description", "multiple_h1", "thin_content", "images_missing_alt", "broken_internal_links"],
  "issueCount": 6,
  "responseMs": 312
}
```

### Uses

- Weekly scheduled audit per client site; diff `issues` against last week and report changes
- Pre-launch checks: crawl staging, fail the deploy if `noindex` or broken links appear
- Content audits: find thin pages, missing metas, and duplicate titles at scale
- Feed an agency dashboard or a white-label report with structured rows instead of CSV exports
- Chain with the Website Tech Stack Detector and Website Contact Scraper on the same domains

### Pricing

Pay per audited page. Unreachable URLs and non-HTML responses are never pushed or charged, and the broken-link HEAD checks are free. The first 2 pages of every run are free so you can validate output before you scale up.

### Notes

- Plain HTTP fetching: server-rendered and statically generated sites (most marketing sites, blogs, docs, stores) audit accurately. Single-page apps that render everything client-side are out of scope.
- Redirects are followed manually so `redirectChain` shows every hop with its status code.

# Actor input Schema

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

Pages to start crawling from. The crawler follows same-site links breadth-first up to Max pages / Max depth.

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

Hard cap on pages audited per run. Controls total cost.

## `maxDepth` (type: `integer`):

0 audits only the start URLs, 1 adds pages they link to, and so on.

## `includePatterns` (type: `array`):

If set, only URLs containing at least one of these substrings are crawled (start URLs are always fetched). Example: /blog/

## `excludePatterns` (type: `array`):

URLs containing any of these substrings are skipped.

## `checkBrokenLinks` (type: `boolean`):

HEAD-check every discovered internal link once and report broken ones per page. Adds a little time, no extra charge.

## `useSitemap` (type: `boolean`):

Also seed the crawl with URLs from the site's sitemap.xml (subject to the same filters and caps).

## `proxyConfiguration` (type: `object`):

Optional. Auditing your own or client sites needs no proxy.

## Actor input object example

```json
{
  "startUrls": [
    "https://books.toscrape.com/"
  ],
  "maxPages": 20,
  "maxDepth": 3,
  "includePatterns": [],
  "excludePatterns": [],
  "checkBrokenLinks": true,
  "useSitemap": false,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

# 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": [
        "https://books.toscrape.com/"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("scrapemint/seo-site-audit-scraper").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": ["https://books.toscrape.com/"] }

# Run the Actor and wait for it to finish
run = client.actor("scrapemint/seo-site-audit-scraper").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": [
    "https://books.toscrape.com/"
  ]
}' |
apify call scrapemint/seo-site-audit-scraper --silent --output-dataset

```

## MCP server setup

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

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/vgmrrN075eCN6E7b8/builds/SAwPuTjnl5J25hHB0/openapi.json