# On-Page SEO Audit & Meta Tags Checker (`sampon/seo-meta-tags-checker`) Actor

On-page SEO audit for any public page: check the title, meta description, canonical, robots, headings, hreflang, Open Graph and structured data. One row per page with a ready-made list of problems.

- **URL**: https://apify.com/sampon/seo-meta-tags-checker.md
- **Developed by:** [Sampon](https://apify.com/sampon) (community)
- **Categories:** SEO tools, Developer tools, Marketing
- **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 Meta Tags Checker

Give this Actor a list of web pages and it reads the tags that search engines and link previews rely on: the title, meta description, canonical, robots rules, headings, hreflang, Open Graph, Twitter card and JSON-LD. Each page comes back as one row, and every row already has a plain list of what to fix, such as "Title is longer than the limit (72 characters)" or "Canonical points to a different URL".

It can also follow the internal links of a site one or two steps deep, mark titles and descriptions that several pages share, and tell you what changed since your last run.

### What you put in

The only required setting is the list of pages:

```json
{
  "startUrls": [
    { "url": "https://www.python.org/" },
    { "url": "https://www.apache.org/" }
  ]
}
```

To check a small site rather than single pages, add a crawl depth:

```json
{
  "startUrls": [{ "url": "https://www.example.com/" }],
  "crawlDepth": 1,
  "maxPages": 200
}
```

| Setting | What it does |
|---|---|
| `crawlDepth` | 0 (default) checks only the listed pages. 1 also checks the pages they link to on the same site, 2 goes one step further. |
| `maxPages` | Stops after this many pages in total (default 50). With several sites, the budget is shared between them. |
| `includeSubdomains` | Counts `blog.example.com` as part of `www.example.com` when following links. |
| `compareWithPrevious` | Remembers this run and marks each page as `new`, `changed` or `unchanged` next time. |
| `onlyChanges` | Saves only new and changed pages. Useful for a daily or weekly schedule. |
| `monitorName` | Runs with the same name are compared with each other. Use one name per site you watch. |
| `titleMinLength`, `titleMaxLength` | Title limits in characters. Defaults 30 and 60. |
| `descriptionMinLength`, `descriptionMaxLength` | Meta description limits in characters. Defaults 70 and 160. |
| `minWords` | Below this word count a page is reported as thin (default 50). |
| `maxConcurrency`, `requestDelayMs` | Speed. At most 4 pages at a time, and at least 1 second between requests to the same site by default. |

### What you get

One row per page. A shortened example:

```json
{
  "url": "https://www.python.org/",
  "finalUrl": "https://www.python.org/",
  "statusCode": 200,
  "redirectChain": [],
  "title": "Welcome to Python.org",
  "titleLength": 21,
  "metaDescription": "The official home of the Python Programming Language",
  "metaDescriptionLength": 52,
  "canonical": null,
  "canonicalIsSelf": null,
  "metaRobots": null,
  "xRobotsTag": null,
  "indexable": true,
  "h1Count": 5,
  "h1": ["Functions Defined", "All the Flow You'd Expect", "..."],
  "h2Count": 9,
  "hreflang": [],
  "openGraph": {
    "title": "Welcome to Python.org",
    "description": "The official home of the Python Programming Language",
    "image": "https://www.python.org/static/opengraph-icon-200x200.png",
    "type": "website",
    "url": "https://www.python.org/",
    "siteName": "Python.org"
  },
  "twitterCard": { "card": null, "title": null, "description": null, "image": null },
  "structuredDataTypes": ["WebSite"],
  "lang": "en",
  "viewport": "width=device-width, initial-scale=1.0",
  "wordCount": 1029,
  "imagesTotal": 1,
  "imagesWithoutAlt": 0,
  "internalLinks": 126,
  "externalLinks": 78,
  "issues": ["TITLE_TOO_SHORT", "META_DESCRIPTION_TOO_SHORT", "CANONICAL_MISSING", "MULTIPLE_H1"],
  "issueCount": 4,
  "issueSummary": "Title is shorter than the minimum (21 characters); Meta description is shorter than the minimum (52 characters); No canonical link; More than one <h1> (5)",
  "duplicateTitleUrls": [],
  "duplicateDescriptionUrls": [],
  "changeStatus": null,
  "checkedAt": "2026-10-10T07:48:40+00:00"
}
```

`issues` holds short codes that are easy to filter on. `issueSummary` says the same thing in words, so you can hand the table to someone who does not know the codes.

The problems it reports:

- Status: the page fails to load, answers 4xx or 5xx, redirects, or is blocked by robots.txt
- Title: missing, too long, too short, more than one
- Meta description: missing, too long, too short, more than one
- Canonical: missing, more than one, or pointing to another URL
- Indexing: `noindex` or `nofollow` in the meta robots tag or in the `X-Robots-Tag` header
- Headings: no `<h1>`, or more than one
- Other basics: no `lang` on `<html>`, no viewport tag, images without an `alt` attribute (an empty `alt=""` is fine), no `og:title`, an hreflang list that leaves out the page itself, JSON-LD that is not valid JSON, very little text
- Site-wide: the same title or meta description on more than one indexable page of the same site. These marks are added at the end of the run, once every page is known, and `duplicateTitleUrls` / `duplicateDescriptionUrls` tell you which other pages share it

A short summary of the run (pages checked and how many pages have each problem) is saved as `SUMMARY` in the run's key-value store.

### Price

Free for now. You only pay Apify's usual platform usage. In our tests the three example pages took about 5 seconds to check, and 19 pages from two sites at depth 1 took about 37 seconds, so a run of that size uses only a small fraction of a compute unit. A price per page may be added later. If that happens, it will be shown on this page before it applies to you.

### How it treats the sites it reads

- It only reads the pages you list and, if you ask for it, pages of the same site linked from them.
- It reads each site's robots.txt first and follows it, including `Crawl-delay`. Pages that robots.txt closes are not requested. A listed page that is closed still gets a row saying so.
- By default it loads two pages at a time and waits at least one second between requests to the same site. You can make it slower, but never more than four requests at a time.
- It does not keep the text of the pages. Only counts (words, characters, links, images) and the tags themselves are saved, and e-mail addresses or phone numbers that appear in titles, descriptions or headings are replaced with `[email removed]` and `[phone removed]`.

### Limits

- It reads the HTML the server sends. Tags that a site adds later with JavaScript are not seen.
- Some sites refuse automated requests or show a challenge page. Those pages come back with their status code (often 403) and are reported as errors.
- Title and description limits are counted in characters, not in pixels as search results are drawn.
- The comparison with the previous run knows only the pages that runs actually checked. A page that simply was not reached this time is not reported as removed.
- Word counts are low for languages written without spaces, such as Japanese or Chinese, so the thin content check also looks at the number of characters.

This Actor is an independent tool. It is not affiliated with Google, any search engine, or the owners of the sites it reads.

# Actor input Schema

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

Public web pages to check, one per line. With a crawl depth above 0, links to other pages of the same site are followed from these pages.

## `crawlDepth` (type: `integer`):

0 checks only the pages you listed. 1 also checks the pages they link to on the same site. 2 goes one step further.

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

Stop after this many pages in total. When several sites are listed, the budget is shared between them.

## `includeSubdomains` (type: `boolean`):

When on, links from www.example.com to blog.example.com count as internal and are followed.

## `compareWithPrevious` (type: `boolean`):

Remember this run and mark each page as new, changed or unchanged next time. The fields that changed are listed in "changes".

## `onlyChanges` (type: `boolean`):

Leave unchanged pages out of the results. Turns on the comparison.

## `monitorName` (type: `string`):

Runs with the same name are compared with each other. Use a different name for each site or task you monitor.

## `titleMinLength` (type: `integer`):

Titles shorter than this many characters are reported.

## `titleMaxLength` (type: `integer`):

Titles longer than this many characters are reported.

## `descriptionMinLength` (type: `integer`):

Descriptions shorter than this many characters are reported.

## `descriptionMaxLength` (type: `integer`):

Descriptions longer than this many characters are reported.

## `minWords` (type: `integer`):

Pages with fewer words than this (and fewer than five times as many characters) are reported as thin.

## `maxConcurrency` (type: `integer`):

How many pages to load at the same time. Capped at 4.

## `requestDelayMs` (type: `integer`):

Minimum time between two requests to the same site. A longer Crawl-delay in the site's robots.txt always wins.

## Actor input object example

```json
{
  "startUrls": [
    {
      "url": "https://www.python.org/"
    },
    {
      "url": "https://www.apache.org/"
    },
    {
      "url": "https://www.debian.org/"
    }
  ],
  "crawlDepth": 0,
  "maxPages": 50,
  "includeSubdomains": false,
  "compareWithPrevious": false,
  "onlyChanges": false,
  "monitorName": "default",
  "titleMinLength": 30,
  "titleMaxLength": 60,
  "descriptionMinLength": 70,
  "descriptionMaxLength": 160,
  "minWords": 50,
  "maxConcurrency": 2,
  "requestDelayMs": 1000
}
```

# Actor output Schema

## `results` (type: `string`):

One row per page: status, SEO tags, counts and the list of problems.

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

Pages checked and how many pages have each problem.

# 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://www.python.org/"
        },
        {
            "url": "https://www.apache.org/"
        },
        {
            "url": "https://www.debian.org/"
        }
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("sampon/seo-meta-tags-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 = { "startUrls": [
        { "url": "https://www.python.org/" },
        { "url": "https://www.apache.org/" },
        { "url": "https://www.debian.org/" },
    ] }

# Run the Actor and wait for it to finish
run = client.actor("sampon/seo-meta-tags-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 '{
  "startUrls": [
    {
      "url": "https://www.python.org/"
    },
    {
      "url": "https://www.apache.org/"
    },
    {
      "url": "https://www.debian.org/"
    }
  ]
}' |
apify call sampon/seo-meta-tags-checker --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,sampon/seo-meta-tags-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/CbxirbGDRNOsdt3ED/builds/z3Qnh15mnViq4rOXS/openapi.json
