# JSON-LD Structured Data Lookup — Schema.org Extractor API (`accountable_eel/jsonld-structured-data-lookup`) Actor

Extract every schema.org JSON-LD object (Product, Article, JobPosting, Organization, and more) already embedded in a page's HTML for SEO. No rendering, no third-party API — reads what the page already publishes. Charged only when structured data is found.

- **URL**: https://apify.com/accountable\_eel/jsonld-structured-data-lookup.md
- **Developed by:** [Adrian Voss](https://apify.com/accountable_eel) (community)
- **Categories:** Lead generation, Developer tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.00 / 1,000 successful lookups

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 Structured Data Lookup

Extract every [schema.org](https://schema.org) JSON-LD object already embedded in a
page's HTML — `Product`, `Article`, `JobPosting`, `Organization`, `BreadcrumbList`,
`FAQPage`, and more. No third-party API, no rendering: this reads exactly what the
page already publishes in its `<script type="application/ld+json">` blocks for search
engines, and hands it back as clean structured JSON.

### Features

- **Full object extraction.** Every JSON-LD block on the page is parsed and returned,
  including objects nested inside a top-level `@graph`.
- **Type summary.** A deduplicated list of every `@type` found on the page (`Product`,
  `Article`, `JobPosting`, etc.), so you can see what's there without scanning the raw
  objects.
- **Resilient parsing.** A malformed JSON-LD block is skipped on its own — one bad
  block doesn't fail the whole page.
- **Bulk-friendly.** Feed in a list of URLs with adjustable `maxConcurrency`.

### How to use JSON-LD Structured Data Lookup — Schema.org Extractor API

1. **In the Apify Console.** Open the actor page and click **Start** — the `items` field is already pre-filled with a working example. Results land in the run's dataset as soon as each item is found.
2. **Via the API.** Call it directly with a POST request — no Console needed once you have an API token:
   ```bash
   curl "https://api.apify.com/v2/acts/accountable_eel~jsonld-structured-data-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>" \
     -X POST \
     -H "Content-Type: application/json" \
     -d '{"items":["https://www.nytimes.com"]}'
   ```
3. **On a schedule.** Save this actor as an Apify **Task** with the input you want, then add a **Schedule** (hourly, daily, weekly) so it runs on its own — no server of your own required.

### Input

```json
{
  "items": ["https://example.com/product/123"],
  "maxConcurrency": 5,
  "proxyConfiguration": { "useApifyProxy": true }
}
```

`items` is the only required field — a list of page URLs (a scheme is added
automatically if missing, defaulting to `https://`). One dataset row is returned per
URL; rows with `"found": false` are never charged. `maxConcurrency` (default 5, up to
20\) controls how many requests run in parallel. `proxyConfiguration` routes requests
through Apify Proxy.

### Output

```json
{
  "query": "https://example.com/product/123",
  "found": true,
  "data": {
    "url": "https://example.com/product/123",
    "objectCount": 2,
    "types": ["Product", "BreadcrumbList"],
    "objects": [
      {
        "@context": "https://schema.org",
        "@type": "Product",
        "name": "Wireless Headphones",
        "sku": "WH-1000",
        "offers": { "@type": "Offer", "price": "199.00", "priceCurrency": "USD" }
      },
      {
        "@context": "https://schema.org",
        "@type": "BreadcrumbList",
        "itemListElement": [ "..." ]
      }
    ],
    "truncated": false
  },
  "scrapedAt": "2026-08-20T12:00:00.000Z"
}
```

`objects` holds up to 25 raw JSON-LD objects found on the page; `truncated: true` means
more than 25 were present and the rest were cut off. A page with no
`application/ld+json` blocks — or where every block fails to parse — gets a dataset row
with `"found": false`, so you always get one row per input URL, but you're never
charged for it.

### Use cases

- **SEO audits** — confirm your product, article, or job pages actually emit the
  structured data you think they do, across a whole site.
- **Competitive SEO research** — see exactly what schema types and fields a competitor
  publishes for rich results.
- **Content pipeline enrichment** — pull structured `Product`/`Article`/`JobPosting`
  data out of pages without writing a custom parser per site.
- **Schema coverage monitoring** — track structured-data presence across a URL list
  over time to catch regressions after a site redesign.

### Pricing

$4 per 1,000 results, plus a $0.00005 start fee. Misses (`found:false`) are never charged.

### Use it from Clay, n8n, Make, or an AI agent

This actor runs synchronously over plain HTTP — call it directly from a script, a workflow tool, or an AI agent, no Apify Console needed once you have an API token.

```bash
curl "https://api.apify.com/v2/acts/accountable_eel~jsonld-structured-data-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>" \
  -X POST \
  -H "Content-Type: application/json" \
  -d '{"items":["https://www.nytimes.com"]}'
```

**n8n.** Add an HTTP Request node: Method `POST`, URL `https://api.apify.com/v2/acts/accountable_eel~jsonld-structured-data-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>`, Body Content Type `JSON`, JSON Body `{"items":["https://www.nytimes.com"]}` (swap in an expression from an earlier node for a real value).

**Clay.** Add an "HTTP API" column: Method `POST`, URL `https://api.apify.com/v2/acts/accountable_eel~jsonld-structured-data-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>`, Body `{"items":["{{value}}"]}`, mapping the row's value into the `items` array.

**MCP.** In Claude, Cursor, or any MCP client with the Apify MCP server, ask for "JSON-LD Structured Data Lookup | Apify" — the agent will find and run this actor.

### FAQ

**What counts as "not found"?**
A page with no `<script type="application/ld+json">` block, or where every block on
the page fails to parse as JSON, returns `"found": false` and is never charged.

**Does this render JavaScript to find dynamically-injected JSON-LD?**
No — this reads the raw HTML response as delivered by the server. If a site injects
JSON-LD client-side after page load via JavaScript, it won't be captured.

**Not every page type carries rich JSON-LD — is that expected?**
Yes. Coverage depends entirely on what the site chooses to publish: product, article,
recipe, and job-posting pages tend to carry the richest markup, while general
informational or homepage-type URLs often have little or none. A `found: false` result
on a page you expected to have data is worth spot-checking in your browser's "View
Page Source" first.

**What happens if one JSON-LD block on the page is broken?**
It's skipped individually — a malformed block doesn't prevent extraction of the other
valid blocks on the same page.

**Are objects inside a top-level `@graph` included?**
Yes — `@graph` arrays are flattened automatically, so every object inside one appears
in `objects` and contributes to `types`.

**Can I check thousands of URLs at once?**
Yes — `maxConcurrency` controls how many requests run in parallel (default 5, up to
20\).

# Actor input Schema

## `items` (type: `array`):

One item per line — see the item shape and examples below. Only the items we actually find are charged — never per run, and never for a miss.

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

Parallel requests. Keep conservative — this target has no browser fallback, so getting blocked costs more than slow-and-steady.

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

Apify Proxy config. Residential recommended for anti-bot-sensitive targets.

## Actor input object example

```json
{
  "items": [
    "https://www.nytimes.com"
  ],
  "maxConcurrency": 5,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}
```

# Actor output Schema

## `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 = {
    "items": [
        "https://www.nytimes.com"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("accountable_eel/jsonld-structured-data-lookup").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 = { "items": ["https://www.nytimes.com"] }

# Run the Actor and wait for it to finish
run = client.actor("accountable_eel/jsonld-structured-data-lookup").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 '{
  "items": [
    "https://www.nytimes.com"
  ]
}' |
apify call accountable_eel/jsonld-structured-data-lookup --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,accountable_eel/jsonld-structured-data-lookup"
        }
    }
}

```

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/guhXiJbOClAWEIb5S/builds/LrdoNRL6mpWZM1Dyi/openapi.json