JSON-LD Extractor | Structured Data & Schema Types
Pricing
$5.00 / 1,000 completed checks
JSON-LD Extractor | Structured Data & Schema Types
Extract embedded application/ld+json blocks from HTML pages, preserve parsed JSON, list observed @type values and report invalid JSON blocks. Export structured data for product, article, organization and other schema processing workflows.
Pricing
$5.00 / 1,000 completed checks
Rating
0.0
(0)
Developer
Austin Aryain
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
6 days ago
Last modified
Categories
Share
JSON-LD Extractor | Structured Data & Schema Types
Extract embedded application/ld+json blocks from HTML pages, preserve parsed JSON, list observed @type values and report invalid JSON blocks. Export structured data for product, article, organization and other schema processing workflows.
How it works
Supply HTML pages that embed structured data in script elements with type application/ld+json. The Actor parses each block independently, preserves the original JSON structure, traverses nested objects and arrays to collect literal @type values, and reports the indexes of malformed JSON blocks. A page with no structured data is a useful completed check with zero blocks. A page containing malformed blocks is also charged because it returns a specific parsing result. This supports structured-data inventories and downstream product or article normalization without guessing a single universal schema.
Quick start
- Enter one or more public URLs in the Input tab, beginning with the supplied example.
- Set a maximum run charge. A completed check costs $0.005; checking 10 sources once costs $0.05.
- Start the Actor and inspect the dataset. Download JSON, CSV or Excel, or consume results through the Apify API.
- Inspect the OUTPUT run summary as well as the dataset: failed or unprocessed inputs appear there. Save the input as a task if you want to schedule future runs.
Pricing
$0.005 per completed check ($5 per 1,000), with platform usage included. There are no separate Actor-start or dataset-item fees. Empty and unchanged successful checks are charged. The maximum charge is checked before each source request and again before output. Failed network or format checks are free; see the specific HTTP-response cases below. Billing is per completed source check, not per nested array item, extracted URL, change or schema block.
Limits and interpretation
Pages must return HTTP 200 with an HTML Content-Type and fit within 2 MB after HTTP decompression. At most 100 blocks and 100,000 visited JSON values per page are accepted. This is JSON syntax parsing and extraction, not schema.org validation, JSON-LD expansion, rich-result eligibility validation, Microdata or RDFa extraction. Remote @context documents are never fetched. JavaScript-generated markup is unavailable because the Actor does not render pages. Oversized pages and network errors are free failures.
A run accepts 1-50 unique input URLs and requests them sequentially. Each check has an 18-second network deadline; new checks stop after 160 seconds. Use a 240-second run timeout and 512 MB memory. If the time or charge limit stops a batch, OUTPUT lists uncheckedUrls for a later run. No response exceeding the configured byte limit is accepted, and a complete record must fit within 6 MB. The Actor permits only public HTTP(S) destinations on standard ports, pins a validated DNS address per request, and refuses redirects into private networks or from HTTPS to HTTP.
The Actor uses direct HTTP requests, without a browser, residential proxy, login, CAPTCHA solving or access-control bypass. Rate limits and blocks may prevent checks. Avoid secret-bearing URLs. Results describe the source and network observed at check time.
Integrations and support
Connect the dataset and OUTPUT summary to your own n8n, Make, Zapier or API workflow. This Actor produces data; it does not automatically send email, Slack messages or webhooks to third parties. No external account credentials are needed for the supplied public examples. Report reproducible issues in the Actor Issues tab, including a non-sensitive input and run link. This is an independent utility and is not endorsed by the websites, standards bodies or services it reads.
Input example
{"urls": ["https://schema.org/"]}
See the Input tab for all supported fields. Results are available through the dataset API and can be downloaded as JSON, CSV or Excel.
Output fields
| Field | Meaning |
|---|---|
| inputUrl | Normalized supplied URL. |
| checkedAt | Check time in ISO format. |
| finalUrl | Final fetched page URL. |
| blockCount | Total JSON-LD script blocks. |
| validBlockCount | Blocks that parsed as JSON. |
| types | Unique sorted literal @type values found in parsed blocks. |
| blocks | blockIndex plus the parsed data, preserving arrays and @graph. |
| parseErrors | Block indexes with invalid JSON syntax; source snippets are omitted. |
Output example
Example from a public source check; live values vary. Long items, changes, groups and blocks arrays are shortened to two entries here for readability; the actual record contains the complete arrays within the documented limits.
{"inputUrl": "https://schema.org/","checkedAt": "2026-09-07T21:05:12.682Z","finalUrl": "https://schema.org/","blockCount": 1,"validBlockCount": 1,"types": ["Corporation","EntryPoint","Organization","Project","SearchAction","WebSite"],"blocks": [{"blockIndex": 0,"data": {"@context": "https://schema.org","@type": "WebSite","url": "https://schema.org","name": "Schema.org","potentialAction": {"@type": "SearchAction","target": {"@type": "EntryPoint","urlTemplate": "https://schema.org/docs/search_results.html?q={query}"},"query-input": "required name=query"},"about": {"@type": "Project","name": "Schema.org Project","description": "Schema.org is a collaborative, community activity with a mission to create, maintain, and promote schemas for structured data on the Internet, on web pages, in email messages, and beyond.","logo": "https://schema.org/docs/schemaicon.png","sameAs": "https://github.com/schemaorg/schemaorg/","foundingDate": "2011-06-2","founder": [{"@type": "Corporation","name": "Google","url": "https://google.com"},{"@type": "Corporation","name": "Microsoft","url": "https://microsoft.com"},{"@type": "Corporation","name": "Yahoo","url": "https://yahoo.com"},{"@type": "Corporation","name": "Yandex","url": "https://yandex.com"}],"publishingPrinciples": "https://www.w3.org/community/about/process/cla/"},"author": {"@type": "Organization","name": "Schema.org Community Group","sameAs": "https://www.w3.org/community/schemaorg/"}}}],"parseErrors": []}