# On-page SEO Checker (`vizellie/seo-page-checker`) Actor

Checks the title, headings, canonical tag, indexability, links, structured data and page weight of each URL you give it. One row per page with a 0 to 100 score and what to fix. $0.003 per page. General information only.

- **URL**: https://apify.com/vizellie/seo-page-checker.md
- **Developed by:** [Vi Zellie](https://apify.com/vizellie) (community)
- **Categories:** SEO tools, Marketing, Developer tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $3.00 / 1,000 page checkeds

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

## On-page SEO Checker

Check the on-page signals of public pages. Each page gets one row: a score from 0 to 100, a letter grade, and a short list of fixes in plain language.

General information only.

This is the per-page check. It does not read a sitemap. Use the sitemap auditor when you want a cheaper pass over every URL in a sitemap.

### What you get

For each public page:

- Whether a title is present, and how long it is. The title text is not saved.
- How long the meta description is. The description text is not saved.
- How many H1 headings the page has, and whether the heading levels stay in order.
- Whether a canonical tag is present, and whether it points at this page.
- Whether the page asks not to be indexed or not to be followed, from the page or from the response.
- Whether hreflang tags, when present, use a language code and a full URL.
- How many images have no alt text.
- How many links stay on the site and how many leave it. When you turn on link checking, how many of the first internal links do not respond.
- A word count, and a flag when the page has very little text. The text is not saved.
- Whether Open Graph and a Twitter card are present. The card text is not saved.
- Which structured data types were found, and whether that data parsed. The data itself is not saved.
- Whether an HTTPS page loads anything over plain HTTP.
- How large the page is, how long it took to respond, and how many redirects led to it.

Unreachable pages are stored with no score and are not charged. Private addresses, internal names, and URLs on a port other than 80 or 443 are skipped and are not charged. The summary counts every URL you supplied, how many were accepted, and how many of those unsafe URLs were skipped. A run whose addresses are all private still finishes, with nothing checked.

Turn on **Summary row** to add one row for the whole run, with those counts and the average score.

### What is not collected

Page text is never saved. Titles, meta descriptions and Open Graph text are not saved. Email addresses, phone numbers and form contents are not saved. Query strings and fragments are not saved. IP addresses are not saved.

### How to use it

1. Paste page URLs under **Page URLs**. Use a full URL such as `https://example.com/pricing`.
2. Leave **Check internal links** off unless you want this run to request links found on each page. At most 50 internal links are checked on a page.
3. Leave **Summary row** on if you want one roll-up row as well as the page rows.
4. Set **Max pages** if you want a hard cap. The limit is 1000 pages in one run.
5. Start the run. Open the dataset for one row per page, or the **REPORT** record in the key-value store for the same findings as a page.

### Pricing

You pay a small fee when the run starts, plus a fee for each public page that could be analysed. A page that is down, or a URL that is private, is free.

| Event | Price |
| --- | --- |
| Run start | $0.00005 |
| Page checked | $0.003 |

### Limits

Up to 1000 pages in one run. Each request times out, redirects are capped, and response bodies are capped. Only `http` and `https` URLs on ports 80 and 443 are accepted. Requests stay polite, with a limit per website. Link checking is off unless you turn it on.

### Disclaimer

These findings flag likely on-page issues. General information only. A high score does not mean a page will rank.

# Actor input Schema

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

Public page URLs to check. Up to 1000. Private and internal addresses are skipped and are not charged.

## `checkLinks` (type: `boolean`):

Also request up to 50 internal links on each page and count how many do not respond. Leave this off for a faster run.

## `includeSummary` (type: `boolean`):

Add one summary row for the whole run, with counts and the average score.

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

Maximum number of pages to check in one run.

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

How many pages to check at the same time.

## Actor input object example

```json
{
  "urls": [
    "https://example.com/"
  ],
  "checkLinks": false,
  "includeSummary": true,
  "maxPages": 100,
  "concurrency": 4
}
```

# Actor output Schema

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

One dataset row per page.

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

The OUTPUT record in the default key-value store.

## `report` (type: `string`):

The REPORT record in the default key-value store.

# 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://example.com/"
    ],
    "maxPages": 100,
    "concurrency": 4
};

// Run the Actor and wait for it to finish
const run = await client.actor("vizellie/seo-page-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": ["https://example.com/"],
    "maxPages": 100,
    "concurrency": 4,
}

# Run the Actor and wait for it to finish
run = client.actor("vizellie/seo-page-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": [
    "https://example.com/"
  ],
  "maxPages": 100,
  "concurrency": 4
}' |
apify call vizellie/seo-page-checker --silent --output-dataset

```

## MCP server setup

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