# Schema Markup Extractor & Validator - JSON-LD, Open Graph (`sophisticated_occasion/schema-markup-metadata-extractor`) Actor

Extract JSON-LD, microdata, Open Graph and Twitter Card data from a URL list in one pass, plus a per-type check that lists missing recommended schema.org fields and a rich-result score. $0.00097 per page; failed pages free.

- **URL**: https://apify.com/sophisticated_occasion/schema-markup-metadata-extractor.md
- **Developed by:** [HUG0 S](https://apify.com/sophisticated_occasion) (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

$0.97 / 1,000 page metadata 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/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

## Schema Markup Extractor & Validator - JSON-LD, Open Graph

Extract **all structured data and metadata** from a list of pages in one pass: **JSON-LD** (including `@graph`), **Microdata**, **Open Graph**, **Twitter Card**, title, meta description/robots, canonical, `lang` and **hreflang**. Each page also gets a **rich-result readiness check**: for common schema.org types (Product, Offer, Article, LocalBusiness, Event, FAQPage, Recipe, JobPosting, VideoObject...) we list missing recommended fields and give a 0-100 score.

**$0.00097 per page** (1,000 pages = $0.97), no start fee. Pages that fail are free.

### Why this one

- **Everything in one pass per page:** JSON-LD (including `@graph`), microdata, Open Graph, Twitter Card, meta tags, canonical, `lang` and hreflang, instead of running several tools.
- **Tells you what to fix, not just what exists.** Each page gets a check per schema.org type (Product, Offer, Article, FAQ, LocalBusiness, Event and more) that lists the missing recommended fields, plus a `richResultScore`.
- **Built for whole sites:** feed it a URL list (for example from a sitemap) and get one row per page with `issues[]`, so template problems show up across hundreds of pages at once.
- **Failed pages are free;** no start fee.

### Quick start: example input, output and cost

Bulk extract JSON-LD, microdata, Open Graph and Twitter Cards with rich-result readiness checks per schema.org type. Pay per page, failed pages free.

**Example input**

```json
{
  "urls": [
    "https://blog.apify.com/"
  ]
}
```

**Cost example:** 1,000 pages x $0.00097 = **$0.97**.

### Use cases

- SEO audits of product or article templates before a release.
- Competitor research: which schema types and fields do they use?
- Link-preview QA (og:title / og:image present?).
- Feed a URL list from our *Sitemap URL Extractor* to audit a whole site.

### Output (one item per page)

`url, finalUrl, title, canonical, lang, meta, openGraph, twitterCard, hreflang, schemaTypes, jsonLd, microdata, issues[], richResultScore`.

The checks are our own pragmatic reading of schema.org and public rich-result guidelines. They do not guarantee rich results; search engines decide.

### Limits

- It reads the HTML the server sends (no browser), so text, links or markup added later by JavaScript are not seen.
- It reports what is on the page and flags broken JSON-LD. It is not Google's Rich Results Test and cannot promise rich results.

### Privacy and responsible use

Person nodes (authors, reviewers) are reduced to `{"@type": "Person"}`, and emails and phone numbers are redacted by default. Social networks and profile sites are not processed. We follow **robots.txt** (RFC 9309), make about one request per second per site, use an honest User-Agent (`SchemaReader/1.0`), and never log in or bypass bot protection.

| Event | Price |
|---|---|
| Page extracted | $0.00097 |

*Maintained by DigiVibeTech. Questions or bugs: use the Issues tab; we reply within 2–5 business days.*

# Actor input Schema

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

Pages to extract (up to 5000). Tip: get all URLs of a site with our Sitemap URL Extractor.

## `includeRawJsonLd` (type: `boolean`):

Include the full JSON-LD blocks (scrubbed) in each item.

## `redactContactDetails` (type: `boolean`):

Replace emails and phone numbers in the extracted data with \[redacted]. Person nodes are always reduced to their type.

## Actor input object example

```json
{
  "urls": [
    "https://blog.apify.com/"
  ],
  "includeRawJsonLd": true,
  "redactContactDetails": true
}
```

# Actor output Schema

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

All result items (overview view)

## `errors` (type: `string`):

Inputs that could not be processed, with the reason

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

Counts of processed, billed and failed items

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

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

# Run the Actor and wait for it to finish
run = client.actor("sophisticated_occasion/schema-markup-metadata-extractor").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://blog.apify.com/"
  ]
}' |
apify call sophisticated_occasion/schema-markup-metadata-extractor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,sophisticated_occasion/schema-markup-metadata-extractor"
        }
    }
}
```

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/WFeVGrfdsjAJvnoG6/builds/IarVHZ22qeTXW06Oa/openapi.json