# SEO Page Snapshot: meta, structured data, on-page checks (`cheering_unicorn/seo-page-snapshot`) Actor

Returns one row per URL with title, meta description, robots, canonical, hreflang, Open Graph, Twitter Card, JSON-LD and microdata types, H1s, word count, image alt coverage, internal/external link counts, status code, redirects and response time, plus a list of on-page issues. Fast HTTP fetch...

- **URL**: https://apify.com/cheering_unicorn/seo-page-snapshot.md
- **Developed by:** [Akshay Irudayaraj](https://apify.com/cheering_unicorn) (community)
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.00 / 1,000 page analyseds

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 Page Snapshot

Paste a list of URLs and get one row per page with everything an on-page SEO audit needs: title and meta description (with lengths), robots directives (meta and `X-Robots-Tag`), canonical, `html lang`, hreflang alternates, Open Graph and Twitter Card tags, JSON-LD and microdata types (with the raw JSON-LD if you want it), H1s and heading counts, word count, image alt coverage, internal/external/nofollow link counts, status code, redirect chain, response time and server header. A short `issues` list flags the usual problems (missing title, long description, multiple H1, noindex, canonical mismatch, no structured data, thin content and so on).

It is a plain HTTP fetch with an HTML parser, so it runs at hundreds of pages a minute and costs a fraction of a browser-based crawler. It does not render JavaScript; for client-side-rendered pages the snapshot reflects the HTML the server sends, which is also what most crawlers see first.

### What you get

```json
{
  "url": "https://example.com/",
  "finalUrl": "https://example.com/",
  "statusCode": 200,
  "redirectChain": [],
  "contentType": "text/html",
  "htmlBytes": 1256,
  "responseTimeMs": 182,
  "server": "nginx",
  "xRobotsTag": null,
  "error": null,
  "title": "Example Domain",
  "titleLength": 14,
  "metaDescription": null,
  "metaDescriptionLength": 0,
  "metaRobots": null,
  "canonical": null,
  "lang": "en",
  "viewport": "width=device-width, initial-scale=1",
  "charset": "utf-8",
  "hreflang": [],
  "feeds": [],
  "ampUrl": null,
  "favicon": "data:,",
  "h1": [],
  "headingCounts": {"h1": 0, "h2": 0, "h3": 0, "h4": 0, "h5": 0, "h6": 0},
  "wordCount": 24,
  "images": 0,
  "imagesMissingAlt": 0,
  "links": {"internal": 0, "external": 0, "nofollow": 0, "total": 0},
  "openGraph": {},
  "twitterCard": {},
  "jsonLdTypes": [],
  "jsonLd": [],
  "microdataTypes": [],
  "issues": ["missing meta description", "missing canonical", "missing h1", "missing og:image", "no structured data", "thin content (<100 words)"],
  "scrapedAt": "2026-10-22T19:04:11+00:00"
}
```

### Input

| Field | Type | Notes |
|---|---|---|
| `urls` | array | Pages to analyse. Duplicates are removed. |
| `respectRobotsTxt` | boolean | Default on. Disallowed pages come back as rows with `error: "blocked by robots.txt"`. |
| `includeJsonLd` | boolean | Attach parsed JSON-LD blocks (default on). |
| `includeLinkList` | boolean | Attach every link with anchor text (default off). |
| `concurrency` | integer | 1-20 parallel fetches; same-host requests are always spaced out. |
| `userAgent` | string | Custom User-Agent. |
| `maxUrls` | integer | Cap. |

Example:

```json
{
  "urls": ["https://www.yoursite.com/", "https://www.yoursite.com/pricing", "https://www.yoursite.com/blog/"],
  "includeLinkList": true
}
```

Tip: feed it the URLs from a sitemap (any sitemap extractor Actor on Apify Store outputs a URL list you can pass straight in).

### Pricing

Pay per event: **$0.002 per page analysed** ($2 per 1,000 pages), plus Apify's standard Actor start fee. Pages that return an error (4xx/5xx, timeout, non-HTML, blocked by robots.txt) are charged too, because the request is still made and the status is useful audit data. A 500-page site audit costs about $1.

### Use cases

- **Site audits**: run on a sitemap's URLs, export to Google Sheets, sort by `issues`.
- **Structured-data checks**: find pages missing `Product`, `Article` or `FAQPage` markup after a template change.
- **Monitoring**: schedule weekly and diff `title`, `canonical`, `metaRobots`, `statusCode` to catch regressions.
- **Competitor research**: titles, descriptions, schema types and word counts across competitor landing pages.
- **AI agents and RAG pipelines**: a cheap pre-check (status, canonical, noindex, word count) before crawling full content.

### Notes

- Redirects are followed (up to 20); the chain is reported so you can spot redirect loops and HTTP→HTTPS hops.
- Only the first 5 MB of HTML is parsed.
- The Actor identifies itself in the User-Agent and honours `robots.txt` by default. It collects page metadata only, not personal data.

### FAQ

**My page is a JavaScript app and the snapshot is almost empty.** That is what the server sends to crawlers. Check `wordCount` and `h1`: if they are empty, your SEO depends on pre-rendering. For rendered audits, pair this with a browser-based crawler.

**Can I pass a sitemap URL?** Not directly; use a sitemap extractor Actor first and pass its URL list.

# Actor input Schema

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

Pages to analyse, one per line. `https://` is added when the scheme is missing.

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

Skip pages that the site's robots.txt disallows for generic crawlers (they are still returned as rows with an `error`).

## `includeJsonLd` (type: `boolean`):

Attach every parsed JSON-LD block under `jsonLd` (types are always listed in `jsonLdTypes`).

## `includeLinkList` (type: `boolean`):

Attach every link on the page (href, anchor text, internal/external, nofollow) under `linkList`. Counts are always included.

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

Pages fetched in parallel (1-20). Requests to the same host are spaced out regardless.

## `userAgent` (type: `string`):

Custom User-Agent header. Default identifies the Actor.

## `maxUrls` (type: `integer`):

Stop after this many URLs. 0 = all. You pay per page analysed.

## Actor input object example

```json
{
  "urls": [
    "https://apify.com/",
    "https://en.wikipedia.org/wiki/Search_engine_optimization",
    "https://example.com/"
  ],
  "respectRobotsTxt": true,
  "includeJsonLd": true,
  "includeLinkList": false,
  "concurrency": 5,
  "maxUrls": 0
}
```

# Actor output Schema

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

No description

## `invalidUrls` (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": [
        "https://apify.com/",
        "https://en.wikipedia.org/wiki/Search_engine_optimization",
        "https://example.com/"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("cheering_unicorn/seo-page-snapshot").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": [
        "https://apify.com/",
        "https://en.wikipedia.org/wiki/Search_engine_optimization",
        "https://example.com/",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("cheering_unicorn/seo-page-snapshot").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": [
    "https://apify.com/",
    "https://en.wikipedia.org/wiki/Search_engine_optimization",
    "https://example.com/"
  ]
}' |
apify call cheering_unicorn/seo-page-snapshot --silent --output-dataset

```

## MCP server setup

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

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/MLdNRbtRcNgwERhBa/builds/dULQW1TlV98bg0wes/openapi.json