How to extract JSON-LD from HTML
Start with the page source you want to inspect. Paste it into the HTML document field, upload an .html or .htm file, or enter a public HTTPS address in Fetch Public URL. JSON-LD Extractor keeps each matching script as its own result, so you can inspect the block, its parsed values, and any parse error separately.
- Choose Paste / Upload HTML or Fetch Public URL.
- Paste markup into HTML document, or choose browse files and select an
.htmlor.htmfile. - For URL mode, enter a public
https://address in Public HTTPS URL. The page must return server-rendered HTML without a login. - Review each Script # result. Choose Download JSON for one parsed block, Copy combined JSON or Download combined JSON for the full set, and Clear to remove the current input and results.
How JSON-LD blocks are found
The extractor selects script elements whose type is application/ld+json. It keeps document order, so the first match is Script #0. A result can show byte size, a script ID, top-level array structure, @context, @type, and @graph entities when those values are present.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Product",
"name": "Example Widget"
}
</script>This example produces a parsed result with @context set to https://schema.org and @type set to Product. A top-level JSON array is read item by item for the displayed contexts, types, and graph entities.
What happens when JSON-LD is malformed
Each block is parsed independently. An empty block or invalid JSON gets Status: Parse error, its error message, its raw content, and a Download raw JSON control. Valid blocks still appear in their original positions.
When the HTML has no matching script, the workspace reports that no JSON-LD blocks were found and hides the combined export bar. The extractor reads JSON-LD script blocks only. It leaves the source markup unchanged and does not inspect microdata or RDFa, or check Schema.org validity and Google rich-result eligibility.
How to extract JSON-LD from a public URL
Fetch Public URL requests raw server-rendered HTML for a public HTTPS address. The request sends no cookies or credentials and runs no JavaScript. It follows up to five HTTPS redirects, rejects a redirect that leaves HTTPS, reports responses over 5 MB, and uses a 10-second connection and total timeout.
JSON-LD added by JavaScript after page load is absent from the fetched source. Copy the rendered HTML from DevTools Elements and paste it into Paste / Upload HTML when that happens. Pasted and uploaded HTML is parsed in the browser, without a content request from this page.
What the extracted results can show
- A Product block can be checked for its
@context,@type, and name before the rest of the page source is reviewed. - Separate Script # results let you compare blocks in server-rendered HTML and download one parsed block for review.
- Saved HTML files can be uploaded one at a time, with script indexes, parse errors, and the combined JSON kept in the results.
When to use JSON-LD Extractor
Use JSON-LD Extractor when your starting material is HTML and the data is embedded in script tags. The parent JSON Extract Tools category covers related JSON extraction tasks. Use JSONPath Extractor when you already have a JSON document and need JSONPath queries, expandable-tree path building, or exported matches in JSON, JSONL, CSV, or plain text.
Frequently asked questions
How do I extract JSON-LD from HTML?
Paste the HTML into Paste / Upload HTML, upload an .html or .htm file, or use Fetch Public URL for public HTTPS HTML. The results list matching script blocks in source order.
How do I find every JSON-LD block in a page?
The extractor finds every script with type application/ld+json and labels them Script #0, Script #1, and so on. It also reports when no matching blocks are present.
What happens if one JSON-LD block has invalid JSON?
The invalid block receives a parse error and keeps its raw content for inspection or download. Valid blocks continue to parse independently.
Can I extract JSON-LD from a public URL?
Yes, Fetch Public URL accepts public HTTPS pages and reads their raw server-rendered HTML. It does not run JavaScript, so paste rendered HTML when a page adds JSON-LD after loading.
Does JSON-LD Extractor validate Schema.org markup?
No, it parses and reports the published JSON-LD without judging Schema.org validity or Google rich-result eligibility. It also skips microdata and RDFa markup.