# SEO Meta Tag Checker (robots.txt-respecting) (`petipeti/seo-meta-checker`) Actor

Audit title, meta description, canonical, Open Graph, H1 and indexability for URLs you own. Always obeys robots.txt and crawls politely.

- **URL**: https://apify.com/petipeti/seo-meta-checker.md
- **Developed by:** [peti peti](https://apify.com/petipeti) (community)
- **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 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

## SEO Meta Tag Checker (robots.txt-respecting)

Check the on-page SEO basics of a list of URLs in one run: title, meta description, canonical, H1, indexability (meta robots and `X-Robots-Tag`), Open Graph, viewport, `lang`, hreflang and images without `alt`. Each page comes back as one row with a plain-English **issues** list, so you can sort and fix.

Built for **site owners, SEO freelancers and agencies auditing sites they own or are authorised to audit**.

### Polite by design

- **robots.txt is always obeyed and cannot be switched off.** Disallowed URLs are reported as skipped and never requested, including when a redirect points into a disallowed path.
- If robots.txt cannot be reached (server error or network failure), the whole site is treated as disallowed, as RFC 9309 recommends.
- At least 1 second between requests to the same site (default 2 s). A longer `Crawl-delay` in robots.txt is honoured.
- Only the URLs you list are fetched. Links are not followed, nothing behind a login is accessed, and no personal data is extracted.
- The User-Agent identifies the tool: `SeoMetaChecker/1.0`. Site owners can block it in robots.txt.

### Input

```json
{
  "startUrls": [{ "url": "https://example.com/" }, { "url": "https://example.com/pricing" }],
  "delaySeconds": 2
}
```

### Output (one row per URL)

```json
{
  "url": "https://example.com/pricing",
  "finalUrl": "https://example.com/pricing",
  "status": 200,
  "redirectChain": [],
  "title": "Pricing – Example",
  "titleLength": 17,
  "description": null,
  "descriptionLength": 0,
  "canonical": "https://example.com/pricing",
  "canonicalIsSelf": true,
  "indexable": true,
  "h1": ["Simple pricing"],
  "h1Count": 1,
  "ogTitle": "Pricing", "ogImage": null,
  "imagesWithoutAlt": 2,
  "issues": ["Missing meta description", "Incomplete Open Graph (og:title / og:image)", "2 image(s) without alt"],
  "blockedByRobots": false,
  "error": null
}
```

Export as CSV / Excel / JSON, or schedule the Actor weekly to catch regressions after a deploy.

### Checks

| Check | Flagged when |
|---|---|
| Title | missing, under 10 or over 60 characters |
| Meta description | missing, under 50 or over 160 characters |
| H1 | none, or more than one |
| Canonical | missing, or points to a different URL |
| Indexability | `noindex` in meta robots or `X-Robots-Tag` |
| Language / mobile | missing `<html lang>` or viewport meta |
| Social | missing `og:title` or `og:image` |
| Images | `<img>` without `alt` |
| Redirects | more than one hop |

Length limits are common guidelines, not Google rules.

### Pricing

Pay per event, platform usage included:

| Event | Price |
|---|---|
| Actor start | $0.01 per run |
| `page-checked` – one page checked successfully | $2.00 per 1,000 pages |

URLs skipped because of robots.txt, errors or non-HTML responses are not charged. Example: auditing 500 pages costs $0.01 + $1.00 = $1.01.

### 日本語での説明

自分のサイト（または監査を任されたサイト）のURLを並べると、タイトル・説明文・canonical・H1・noindex・OGPなどをまとめて点検し、問題点を一覧にします。robots.txt は必ず守り（オフにできません）、同じサイトへは最低1秒あけてアクセスします。リンクはたどらず、ログインが要るページや個人情報は扱いません。

# Actor input Schema

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

Pages of websites you own or are authorised to audit. Only these URLs are checked; links are not followed.

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

Max URLs.

## `delaySeconds` (type: `integer`):

Minimum 1 second. If the site's robots.txt sets a longer Crawl-delay, that value is used instead.

## Actor input object example

```json
{
  "startUrls": [
    {
      "url": "https://apify.com"
    }
  ],
  "maxUrls": 100,
  "delaySeconds": 2
}
```

# Actor output Schema

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

Dataset items (Overview view).

# 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://apify.com"
        }
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("petipeti/seo-meta-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://apify.com" }] }

# Run the Actor and wait for it to finish
run = client.actor("petipeti/seo-meta-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://apify.com"
    }
  ]
}' |
apify call petipeti/seo-meta-checker --silent --output-dataset

```

## MCP server setup

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