# JSON-LD & Schema.org Extractor (`andok/jsonld-extractor`) Actor

Extract structured microdata (JSON-LD) from webpages to audit SEO schema implementations and rich snippets.

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

## Pricing

from $0.47 / 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.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#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

## JSON-LD & Schema.org Extractor

Extract JSON-LD structured data and Schema.org markup from any web page without writing a custom parser. Structured data powers rich search results, knowledge panels, and product carousels -- yet validating it at scale is painful. Feed in a list of URLs and get every JSON-LD block parsed, validated, and returned as clean JSON objects ready for SEO audits or data pipelines.

### Features

- **Full JSON-LD extraction** — parses every `<script type="application/ld+json">` block on the page
- **Error reporting** — catches and reports malformed JSON so you can fix broken markup immediately
- **Schema.org support** — handles Product, Article, BreadcrumbList, LocalBusiness, Recipe, Organization, and all other types
- **Bulk processing** — scan hundreds of URLs in a single run with configurable concurrency
- **Clean structured output** — each JSON-LD object is returned as a parsed JavaScript object, not a raw string
- **Pay-per-event billing** — you only pay for each URL checked, with automatic charge-limit enforcement

### Input

| Field | Type | Required | Default | Description |
|-------|------|----------|---------|-------------|
| `urls` | `array` | Yes | — | List of page URLs to scan for JSON-LD structured data blocks. |
| `url` | `string` | No | — | Single URL to scan (for backwards compatibility). Use `urls` for bulk processing. |
| `timeoutSeconds` | `integer` | No | `15` | Maximum seconds to wait for each page response before timing out. |
| `concurrency` | `integer` | No | `10` | Number of URLs to process in parallel. Increase for large batches, decrease if you hit rate limits. |

#### Input Example

```json
{
  "urls": [
    "https://crawlee.dev/",
    "https://www.bbc.com/news",
    "https://www.amazon.com/dp/B09V3KXJPB"
  ]
}
```

### Output

Each URL produces one dataset item containing all parsed JSON-LD objects and any parse errors.

- `inputUrl` (`string`) — the URL you submitted
- `finalUrl` (`string`) — the URL after redirects
- `status` (`number`) — HTTP status code
- `jsonLdCount` (`number`) — number of JSON-LD blocks found
- `jsonLdData` (`array`) — list of parsed JSON-LD objects (each preserving its original `@type`, `@context`, etc.)
- `parseErrors` (`array`) — list of error messages for malformed JSON-LD blocks
- `error` (`string | null`) — error message if the URL could not be fetched
- `checkedAt` (`string`) — ISO 8601 timestamp of when the check was performed

#### Output Example

```json
{
  "inputUrl": "https://www.bbc.com/news",
  "finalUrl": "https://www.bbc.com/news",
  "status": 200,
  "jsonLdCount": 2,
  "jsonLdData": [
    {
      "@context": "https://schema.org/",
      "@type": "WebPage",
      "name": "BBC News",
      "url": "https://www.bbc.com/news"
    },
    {
      "@context": "https://schema.org/",
      "@type": "Organization",
      "name": "BBC News",
      "logo": "https://www.bbc.com/news/logo.png"
    }
  ],
  "parseErrors": [],
  "error": null,
  "checkedAt": "2025-01-15T10:30:00.000Z"
}
```

### Pricing

| Event | Cost |
|-------|------|
| URL Checked | Pay-per-event (see actor pricing page) |

The actor stops automatically when the per-run charge limit is reached, so you never overspend.

### Use Cases

- **SEO auditing** — verify that Schema.org markup is present and correctly structured across your entire site
- **Rich snippet QA** — check Product, Recipe, and Article schemas before deploying to production
- **Data extraction** — pull structured pricing, ratings, and author info without building a custom scraper per site
- **Competitive analysis** — compare which structured data types your competitors implement to identify gaps
- **Migration validation** — confirm that JSON-LD blocks survived a site redesign or CMS migration intact

### Related Actors

| Actor | What it adds |
|-------|-------------|
| [OpenGraph & Twitter Card Inspector](https://apify.com/andok/opengraph-inspector) | Checks OG and Twitter Card tags — combine with JSON-LD extraction for a complete metadata audit |
| [Website Tech Stack Analyzer](https://apify.com/andok/tech-stack-analyzer) | Detects the CMS and framework — understand which platform generates the structured data |
| [Sitemap URL Extractor](https://apify.com/andok/sitemap-extractor) | Extracts all URLs from a sitemap — feed the output into this actor to audit JSON-LD across an entire site |

# Actor input Schema

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

List of page URLs to scan for JSON-LD structured data blocks. Each page is fetched and all <script type="application/ld+json"> elements are parsed.

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

Single URL to scan (for backwards compatibility). Use the URLs field above for bulk processing.

## `timeoutSeconds` (type: `integer`):

Maximum seconds to wait for each page response. Increase for slow or geographically distant sites.

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

Number of URLs to process in parallel. Higher values speed up large batches but may trigger rate limits on some hosts.

## Actor input object example

```json
{
  "urls": [
    "https://crawlee.dev/"
  ],
  "timeoutSeconds": 15,
  "concurrency": 10
}
```

# Actor output Schema

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

No description

## `resultsCsv` (type: `string`):

No description

## `run` (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://crawlee.dev/"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("andok/jsonld-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://crawlee.dev/"] }

# Run the Actor and wait for it to finish
run = client.actor("andok/jsonld-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://crawlee.dev/"
  ]
}' |
apify call andok/jsonld-extractor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,andok/jsonld-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/zHnANJ8pUcEUEwJFt/builds/DXMX3QI6aoh1c3kgp/openapi.json