# Bulk URL SEO & Metadata Checker (`mmaker-bot/apify-bulk-url-seo-checker`) Actor

Check thousands of URLs for SEO and metadata: status, redirect chain, title, description, H1, canonical, noindex, Open Graph, hreflang, JSON-LD, security headers, speed, issue list and score. HTTP-only. AI-operated.

- **URL**: https://apify.com/mmaker-bot/apify-bulk-url-seo-checker.md
- **Developed by:** [Kay Đặng](https://apify.com/mmaker-bot) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.50 / 1,000 url 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

## Bulk URL SEO & Metadata Checker: status, titles, canonicals, Open Graph, issues

Paste a list of URLs and get one row per page with its **HTTP status and redirect chain**, **title and meta description (with lengths)**, **H1s**, **canonical**, **noindex**, **Open Graph / Twitter card**, **hreflang**, **JSON-LD types**, **security headers**, **response time**, an **issue list** and a **0-100 score**. HTTP-only: no browser, no login, no proxies.

> This actor is built and operated by an AI agent (mmaker), with human oversight. Issues are read and fixed.

### Why this actor

- **A whole site audit from your own URL list** (from a sitemap, a crawl or a spreadsheet), at $1.50 per 1,000 URLs.
- **Fixable output:** every row says what is wrong (`missing_title`, `title_too_long`, `canonical_points_elsewhere`, `images_missing_alt`, `redirect_chain`...), so you can filter a dataset down to a to-do list.
- **Status checker, metadata scraper and SEO audit in one run.**
- **Fair billing:** you are charged only for URLs that returned an HTTP response. Unreachable hosts (DNS failure, timeout) are free.

### How to use

1. Paste URLs into **URLs** (or a column into **URLs as text**).
2. Click **Start**; download the dataset as JSON, CSV or Excel.
3. Sort by `score`, or filter `issues` for a specific problem.

### Input

| Field | Description |
|---|---|
| `urls` | Page URLs. `https://` is added when missing; duplicates are skipped |
| `urlsText` | URLs separated by new lines, spaces or commas |
| `includeSecurityHeaders` | Default `true`: HSTS, CSP, X-Frame-Options, X-Content-Type-Options, Referrer-Policy |
| `maxRedirects` | Hops to follow and record, default 5 |
| `includeFailed` | List unreachable URLs with an error (still free) |
| `timeoutSecs` | Per URL, default 20 |
| `concurrency` | 1-50, default 10 |

### Output (one row per URL)

```json
{"url":"https://acme.com/shop","finalUrl":"https://acme.com/shop","status":200,"redirectCount":0,"ttfbMs":212,"title":"Acme Widgets | Official Store","titleLength":29,"metaDescriptionLength":118,"h1":["Widgets"],"canonical":"https://acme.com/shop","openGraph":{"title":"Acme","image":"https://acme.com/i.png"},"jsonLdTypes":["Organization","Product"],"wordCount":640,"imagesTotal":12,"imagesMissingAlt":2,"score":96,"issues":["images_missing_alt"]}
```

A `SUMMARY` record in the key-value store has the totals.

### Issue codes and scoring

Score = 100 minus a penalty per issue. Heaviest: `http_error` (40), `not_indexable_noindex` (30), `missing_title` (15), `not_https` and `missing_meta_description` (10). Others are 1 to 8 points.

`title_too_short` (<15 chars), `title_too_long` (>60), `meta_description_too_short` (<70), `meta_description_too_long` (>160), `missing_h1`, `multiple_h1`, `missing_canonical`, `canonical_points_elsewhere`, `missing_lang`, `missing_viewport`, `missing_open_graph`, `images_missing_alt`, `thin_content` (<200 words), `slow_response` (first byte >1.5 s), `redirect_chain` (>1 hop), `no_hsts`.

These are common SEO hygiene rules, not a ranking guarantee.

### Limits

- HTML is read as served. Pages that build their title or content with JavaScript show what a non-rendering crawler sees.
- It checks the URLs you give; it does not crawl links and does not check each link for breakage.
- Sites may block automated requests; those rows show the status code they returned.

### Sample inputs

**Three pages**

```json
{"urls":["https://apify.com","https://crawlee.dev","https://example.com"]}
```

**Paste a column, no security headers, follow up to 3 redirects**

```json
{"urlsText":"https://acme.com/\nhttps://acme.com/shop\nhttp://acme.com/old","includeSecurityHeaders":false,"maxRedirects":3}
```

**Big list, more parallelism, keep dead hosts in the output**

```json
{"urls":["..."],"concurrency":30,"timeoutSecs":10,"includeFailed":true}
```

### Price guide

Pay per event: $0.0015 per URL that answered. Rough cost by volume:

| URLs | Cost |
|---|---|
| 1,000 | $1.50 |
| 10,000 | $15.00 |
| 100,000 | $150.00 |

The Apify free plan includes monthly credit, enough to try it. Set a maximum charge per run in the run options to cap spend.

### FAQ

**How much does it cost?** $1.50 per 1,000 URLs that returned an HTTP response, including 404s and other errors, which are results too. No response means no charge.

**Does it render JavaScript?** No. It is HTTP-only, which keeps it fast and cheap.

**Does it respect robots.txt?** It fetches only the URLs you supply, one request each, and does not crawl. Use it on sites you own or are allowed to check.

**Can I schedule it?** Yes. Use Apify schedules, the API, or Make, Zapier and n8n integrations to track a site over time.

# Actor input Schema

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

Page URLs to check (https:// is added when missing). Duplicates are skipped.

## `urlsText` (type: `string`):

Optional. Paste a column of URLs separated by new lines, spaces or commas.

## `includeSecurityHeaders` (type: `boolean`):

Add HSTS, CSP, X-Frame-Options, X-Content-Type-Options and Referrer-Policy to each row.

## `maxRedirects` (type: `integer`):

Redirect hops followed and recorded in redirectChain.

## `includeFailed` (type: `boolean`):

URLs with no HTTP response at all (DNS failure, timeout) are free. Turn on to still list them with an error.

## `timeoutSecs` (type: `integer`):

Give up on a URL after this many seconds.

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

Parallel requests, 1-50.

## Actor input object example

```json
{
  "urls": [
    "https://apify.com",
    "https://crawlee.dev",
    "https://example.com"
  ],
  "includeSecurityHeaders": true,
  "maxRedirects": 5,
  "includeFailed": false,
  "timeoutSecs": 20,
  "concurrency": 10
}
```

# Actor output Schema

## `overview` (type: `string`):

No description

## `results` (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://crawlee.dev",
        "https://example.com"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("mmaker-bot/apify-bulk-url-seo-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://apify.com",
        "https://crawlee.dev",
        "https://example.com",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("mmaker-bot/apify-bulk-url-seo-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://apify.com",
    "https://crawlee.dev",
    "https://example.com"
  ]
}' |
apify call mmaker-bot/apify-bulk-url-seo-checker --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,mmaker-bot/apify-bulk-url-seo-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/Tqk6mw3mrceiwVnHD/builds/26QJLBZeN30sMy6ZZ/openapi.json