# SEO Data Extractor - On-Page Tags for Any URL (`dltik/seo-data-extractor`) Actor

Extract on-page SEO data from any list of URLs: title, meta description, canonical, robots, H1/H2 headings, Open Graph & Twitter Card tags, lang, viewport and word count. Pure HTTP, no browser — fast and cheap for bulk audits.

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

## Pricing

$3.00 / 1,000 page extracteds

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/platform/actors/running/actors-in-store#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## SEO Data Extractor — On-Page Tags for Any URL

> ⭐ **Bookmark this actor** so bulk on-page SEO extraction is one click away on your next audit.

Extract **on-page SEO data** from any list of URLs in bulk. For each page you get the title, meta description, canonical, robots directive, H1/H2 headings, **Open Graph** and **Twitter Card** tags, `lang`, viewport and an approximate word count. Pure HTTP + HTML parsing — no browser, fast and cheap.

### What it extracts

| Field | Notes |
|---|---|
| `title` + `title_length` | flag too-long/too-short titles |
| `meta_description` + `description_length` | flag missing/oversized descriptions |
| `canonical` | detect canonical issues |
| `meta_robots` | catch `noindex` / `nofollow` |
| `h1` + `h1_count`, `h2` + `h2_count` | heading structure (multiple/zero H1s) |
| `og_title`, `og_description`, `og_image`, `og_type`, `og_site_name` | social preview tags |
| `twitter_card`, `twitter_title`, `twitter_image` | Twitter Card tags |
| `lang`, `charset`, `viewport` | technical basics |
| `word_count` | thin-content detection |
| `status`, `final_url` | redirects + non-200s |

### Input

| Field | Type | Description |
|---|---|---|
| `urls` | array | List of page URLs (missing scheme defaults to `https://`) |
| `url` | string | Convenience field for a single URL |
| `timeoutSecs` | integer | Per-URL timeout, 1–60 (default 15) |
| `concurrency` | integer | Parallel fetches, 1–30 (default 10) |

#### Example input

```json
{ "urls": ["https://stripe.com", "https://stripe.com/pricing"] }
```

### Output

One record per URL:

```json
{
  "url": "https://stripe.com/pricing",
  "status": 200,
  "title": "Pricing & Fees | Stripe",
  "title_length": 23,
  "meta_description": "Find Stripe fees and pricing information...",
  "h1": ["Simple, transparent pricing"],
  "h1_count": 1,
  "og_title": "Stripe Pricing",
  "word_count": 1240
}
```

### Use cases

- **Bulk SEO audits** — pull title/meta/H1 for an entire URL list and spot gaps in a spreadsheet.
- **Content QA** — find missing meta descriptions, duplicate titles, multiple/zero H1s, thin content.
- **Social preview checks** — confirm Open Graph and Twitter Card tags exist before a launch.
- **Migration validation** — compare on-page tags before vs after a redesign.

### Pricing

Pay-per-event: **$0.003 per page extracted**. Up to 1,000 pages per run — split larger lists across runs.

### Next step: AI search readiness

On-page SEO is for Google. To see whether **ChatGPT, Claude and Perplexity** can read and cite these pages, run **[GEO Site Audit](https://apify.com/dltik/geo-site-audit)** — it scores robots.txt, `llms.txt`, Schema.org, meta tags and content extractability for AI crawlers.

***

Built by [dltik](https://apify.com/dltik). Pure HTTP — no browser, fast and cheap.

# Actor input Schema

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

List of page URLs to extract SEO data from (missing scheme defaults to https://).

## `url` (type: `string`):

Convenience field for a single URL. Merged with the 'urls' list if both are set.

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

Per-URL request timeout in seconds (1-60).

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

How many URLs to fetch in parallel (1-30).

## Actor input object example

```json
{
  "urls": [
    "https://stripe.com",
    "https://stripe.com/pricing"
  ],
  "timeoutSecs": 15,
  "concurrency": 10
}
```

# Actor output Schema

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

On-page SEO data for each URL.

# 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://stripe.com",
        "https://stripe.com/pricing"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("dltik/seo-data-extractor").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://stripe.com",
        "https://stripe.com/pricing",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("dltik/seo-data-extractor").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print("💾 Check your data here: https://console.apify.com/storage/datasets/" + run["defaultDatasetId"])
for item in client.dataset(run["defaultDatasetId"]).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://stripe.com",
    "https://stripe.com/pricing"
  ]
}' |
apify call dltik/seo-data-extractor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "command": "npx",
            "args": [
                "mcp-remote",
                "https://mcp.apify.com/?tools=dltik/seo-data-extractor",
                "--header",
                "Authorization: Bearer <YOUR_API_TOKEN>"
            ]
        }
    }
}

```

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/acts/1khU18f0Si2YMYSJm/builds/SE0aFyrMehwsHfb5Q/openapi.json