# Onpage Seo Bulk (`narrow_circle/onpage-seo-bulk`) Actor

Onpage Seo Bulk

- **URL**: https://apify.com/narrow\_circle/onpage-seo-bulk.md
- **Developed by:** [A Man](https://apify.com/narrow_circle) (community)
- **Categories:** SEO tools, Developer tools, Open source
- **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

## On-Page SEO Audit — Score & Issues (Bulk URLs)

**Audit any URL list in seconds.** Get a **0–100 on-page score**, a **prioritised issue list**, and every meta field agencies need — without a browser and without charging for failed URLs (when monetised).

Pipe URLs from the **Sitemap URL Harvester**, a CMS export, or a rank tracker. Export JSON/CSV or webhook into n8n, Make, Zapier, or Sheets.

### What you get

- **Score + issues** (missing title, thin content, empty body / SPA shell, noindex, non-HTML Content-Type, multiple H1s, missing alts, …)
- **Meta & social:** title, description, canonical, robots, H1, Open Graph, Twitter cards
- **Technical:** viewport, `html lang`, favicon, JSON-LD types (incl. `@graph` / top-level arrays), hreflang, internal/external links, image alt coverage, response `contentType`
- **Redirect chain** with status codes
- Up to **50 concurrent** fetches; optional Apify Proxy; retries on 429/5xx
- **Failed URLs** become error rows (invalid URL, SSRF block, HTTP errors, timeouts) — not billed when monetised

### Sample output

```json
{
  "requestedUrl": "https://example.com/",
  "finalUrl": "https://example.com/",
  "ok": true,
  "score": 58,
  "issues": [
    { "code": "missing_meta_description", "severity": "error", "message": "Missing meta description" },
    { "code": "thin_content", "severity": "warn", "message": "Thin content (~17 words)" }
  ],
  "title": "Example Domain",
  "h1": "Example Domain",
  "wordCount": 17,
  "links": { "internal": 0, "external": 1, "total": 1 },
  "redirectChain": [{ "url": "https://example.com/", "status": 200 }]
}
```

### Who it's for

- SEO agencies running client audits from a sitemap
- In-house SEO monitoring title / meta / canonical drift on a schedule
- Automation builders who need clean JSON, not a desktop crawler

### Example input

```json
{
  "urls": ["https://example.com/", "https://example.com/about"],
  "maxConcurrency": 10,
  "delayMs": 50
}
```

### Pricing (when monetised)

| Event | When | Suggested |
|---|---|---|
| **`page-audited`** | Each successful parse (`ok: true`) | Start **$0.003–$0.005** / page → hike after traction |

Failed rows → not charged. Empty `urls` → hard fail before work.

### Acceptable use (legal)

- Run only against URLs you are authorised to fetch (your sites, client sites with permission, or otherwise lawful public pages).
- Respect target `robots.txt`, rate limits, and site terms; use `delayMs` / concurrency for polite crawling.
- Private / loopback / cloud-metadata hosts are blocked (SSRF guard).
- You are responsible for lawful use of outputs (no credential stuffing, no paywalled content abuse).

### Limitations

- **No JS rendering** — SPA shells may look empty; use a browser Actor for those
- Not a site crawler — supply the URL list (pair with Sitemap URL Harvester)

### Local test

```bash
npm install && npm test
npm run battle   # live mixed URLs (404, JSON, SSRF, timeout, redirects)
node src/main.mjs
```

Built by **narrow\_circle**

# Actor input Schema

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

HTTP(S) page URLs to fetch and parse. HTML/static pages only — not suited for client-rendered SPAs (React/Vue/Angular).

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

How many pages to fetch in parallel.

## `requestTimeoutSecs` (type: `integer`):

Seconds before a single request is aborted.

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

Maximum number of redirect hops before stopping.

## `maxRetries` (type: `integer`):

Extra attempts after network failures, HTTP 429, or 5xx (0 = no retry).

## `delayMs` (type: `integer`):

Optional delay per URL fetch to reduce pressure on target servers.

## `proxyConfiguration` (type: `object`):

Optional Apify Proxy (or custom proxies). Helps when targets rate-limit datacentre IPs.

## Actor input object example

```json
{
  "urls": [
    "https://example.com/"
  ],
  "maxConcurrency": 5,
  "requestTimeoutSecs": 30,
  "maxRedirects": 10,
  "maxRetries": 1,
  "delayMs": 0,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

# Actor output Schema

## `seoResults` (type: `string`):

Default dataset: title, meta, canonical, H1, OG tags, redirect chain, and related on-page fields.

# 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/"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("narrow_circle/onpage-seo-bulk").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/"] }

# Run the Actor and wait for it to finish
run = client.actor("narrow_circle/onpage-seo-bulk").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/"
  ]
}' |
apify call narrow_circle/onpage-seo-bulk --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,narrow_circle/onpage-seo-bulk"
        }
    }
}
```

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/MY0dedMJXxuGyG90D/builds/xbaJXqZ9YIS6cYMle/openapi.json