JSON-LD Extractor - Schema.org Structured Data & Rich Snippets avatar

JSON-LD Extractor - Schema.org Structured Data & Rich Snippets

Pricing

from $0.50 / 1,000 results

Go to Apify Store
JSON-LD Extractor - Schema.org Structured Data & Rich Snippets

JSON-LD Extractor - Schema.org Structured Data & Rich Snippets

$0.5/1K ๐Ÿ”ฅ JSON-LD structured data extractor! Pull Schema.org markup โ€” products, articles, recipes & events โ€” from any URL. No API key. Export JSON, CSV, Excel or API in seconds. Perfect for SEO audits & RAG โšก

Pricing

from $0.50 / 1,000 results

Rating

0.0

(0)

Developer

ninhothedev

ninhothedev

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

3 days ago

Last modified

Share

JSON-LD Structured Data Extractor ๐Ÿงฉ

Extract the schema.org structured data that any website already publishes for Google โ€” Product, Article, Recipe, Event and more โ€” as clean JSON. No API key. Datacenter-proxy friendly.

Modern sites embed machine-readable structured data (<script type="application/ld+json"> and HTML microdata) so search engines can build rich results. This Actor reads exactly that publicly-published markup and hands it back to you as one dataset item per schema.org entity โ€” flattening @graph blocks, handling arrays, and skipping malformed JSON automatically.

Perfect for SEO audits, rich-result debugging, product/recipe extraction, and feeding clean entities into RAG / LLM pipelines.


โœจ What it does

  • Fetches each URL with a real Chrome TLS fingerprint (curl_cffi chrome124) and a plain urllib fallback.
  • Parses every application/ld+json block on the page โ€” json.loads each, handling arrays and @graph.
  • Flattens @graph into individual entities (a single WordPress/Yoast block often expands to Article + WebPage + BreadcrumbList + Organization + Recipe).
  • Optional microdata extraction (itemscope / itemprop) โ€” used automatically as a fallback when a page has no JSON-LD.
  • Returns each entity tagged with its source URL, its @type, and a best-effort name.

๐Ÿ“ฅ Input

FieldTypeDefaultDescription
modeselectextractOperation mode (only extract today).
urlsarrayโ€”Page URLs to extract from. https:// is added if missing.
includeMicrodatabooleanfalseAlso extract legacy HTML microdata. Off = microdata used only as a fallback.
maxItemsinteger100Max entities to output across all URLs (max 1000).
{
"mode": "extract",
"urls": [
"https://www.allrecipes.com",
"https://www.apple.com/iphone-15-pro/"
],
"includeMicrodata": false,
"maxItems": 100
}

๐Ÿ“ค Output

One dataset item per top-level schema.org entity:

{
"url": "https://www.loveandlemons.com/guacamole-recipe/",
"schema_type": "Recipe",
"name": "Best Guacamole Recipe",
"data": { "@context": "https://schema.org", "@type": "Recipe", "recipeIngredient": ["..."], "...": "full JSON-LD object" },
"source": "json-ld",
"scraped_at": "2026-07-23T12:00:00+00:00"
}
  • schema_type โ€” the raw @type (string or array, preserved as published).
  • name โ€” name / headline / title, whichever is present (nullable).
  • data โ€” the full structured-data object, untouched.
  • source โ€” json-ld or microdata.

All fields are nullable. Pages with no structured data are skipped with a warning.

๐Ÿ’ก Use cases

  • SEO structured-data audits โ€” see exactly what Google sees on every page.
  • Product / recipe extraction โ€” pull prices, ratings, ingredients, steps straight from the source markup.
  • RAG enrichment โ€” clean, typed entities for embeddings and LLM context.
  • Rich-result debugging โ€” verify Product, FAQ, Recipe, Event, Breadcrumb markup before it hits Search Console.

๐Ÿ’ฐ Pricing

Pay-per-result, roughly ~$0.50 per 1,000 entities extracted, plus Apify platform usage. Datacenter proxies are fine โ€” no residential proxy or login required.

๐Ÿท๏ธ Keywords

json-ld, structured data, schema.org, microdata, rich results, seo audit, product schema, recipe schema, article schema, event schema, rich snippets, google rich results, rag, metadata extractor, web scraping


This tool only reads data that websites publish publicly for search engines. Respect each site's Terms of Service and robots.txt.