Toolkit ShelfFind

Utility Tools

JSON-LD Structured Data Checker

Use this JSON-LD structured data checker to verify parseable schema markup before publishing, requesting indexing, debugging rich results, or handing off a launch page.

Method shown June 6, 2026Source note includedFree tool

Live checker

JSON-LD structured data checker

Status
Run a guarded HTML check to parse JSON-LD structured data.
Final statusNot checked

No request is sent until you run the check.

JSON-LD scriptsNot checked

Parses script tags with type application/ld+json.

@type valuesNot checked

Detected types appear after parsing.

Review notes
  • Checks one public HTML URL. Local, private, reserved, non-http, and credentialed URLs are blocked.
Scope note

This checker parses JSON-LD syntax and reports detected types. It does not validate every schema.org property, eligibility rule, or search-result enhancement requirement.

Quick answer

JSON-LD Structured Data Checker: what it checks

JSON-LD Structured Data Checker checks JSON-LD structured data report from page URL, HTTP status, final URL, JSON-LD scripts, parse validity and schema @type values, and additional inputs. The visible check method is Structured data report = guarded HTML fetch + redirect follow + application/ld+json extraction + JSON parse + @type and @graph summary.

Check outputJSON-LD structured data report
InputsPage URL, HTTP status, Final URL, JSON-LD scripts, Parse validity, Schema @type values, Graph nodes, Structured data warnings
Check methodStructured data check method

Check method

Structured data check method

Structured data report = guarded HTML fetch + redirect follow + application/ld+json extraction + JSON parse + @type and @graph summary

The checker fetches one public HTML URL, follows up to 5 redirects, and blocks local, private, reserved, credentialed, and non-http destinations before each request.

How to use

Steps

  1. Paste the exact public page URL you want to inspect.
  2. Run the check to fetch the final HTML response and extract application/ld+json scripts.
  3. Review script count, parse validity, detected @type values, @graph node counts, and warnings.
  4. Fix broken JSON, missing @type values, or unexpected markup before validating rich-result eligibility in platform tools.

Example

Sample check

Tool pageConfirm FAQPage, WebApplication, or BreadcrumbList markup parses cleanly
Article pageCheck Article, WebPage, and BreadcrumbList JSON-LD before publication
SEO handoffCopy script counts, detected types, and parse warnings into a launch ticket

Checker use

Best for

  • Use this JSON-LD structured data checker to verify parseable schema markup before publishing, requesting indexing, debugging rich results, or handing off a launch page.
  • Checking structured data check method with the method and assumptions visible.
  • Comparing the output with the sample check and benchmark table before using it elsewhere.
  • Browser-side link, file, format, and web utility tasks that need an output now.

Before relying on it

Check first

  • Using the JSON-LD structured data report without checking that page URL, HTTP status and final URL, and additional inputs match the same task and context.
  • Ignoring that the checker fetches one public HTML URL, follows up to 5 redirects, and blocks local, private, reserved, credentialed, and non-HTTP destinations before each request.
  • Skipping the source notes when the formula, benchmark, or warning depends on outside context.
  • Publishing a generated file or code without testing it in the real destination.

Details

What to know before using the output

These notes make the assumptions explicit, especially where the same search query can mean slightly different things.

GuardrailsPublic http/https only

Localhost, private networks, reserved IPs, credentials, and non-http redirects are blocked to avoid internal-network fetches.

Validation scopeSyntax and type summary

The checker parses JSON-LD and summarizes @type and @graph data. It does not validate every schema.org property or rich-result eligibility rule.

Fetch scopeOne HTML response

The checker reads fetched HTML only. It does not execute JavaScript or crawl linked pages.

Source notes

References used for this checker

Google Search CentralDocuments structured data for Google Search and rich result eligibility guidance.Schema.orgDocuments schema vocabulary types and properties used in structured data.MDN Web DocsDocuments JSON syntax and parsing behavior used to validate JSON-LD blocks.

Benchmarks

How to read the output

This checker is a decision aid, not a fixed rule. Use the output to compare scenarios and document your assumptions. Benchmark ranges are broad planning heuristics unless this page names a specific source for the range.

JSON-LD scripts: Parse cleanly.

Broken JSON-LD cannot be interpreted reliably by search engines or QA tools.

@type values: Present.

Typed nodes make it clear what entities the markup is describing.

Eligibility: Validate separately.

Passing syntax checks is only the first step. Use search platform validators for rich-result-specific requirements.

Method and limitations

Methodology and assumptions

The method, inputs, example, and limitations are shown so the check is transparent, not just a pass/fail label.

Check method

Structured data report = guarded HTML fetch + redirect follow + application/ld+json extraction + JSON parse + @type and @graph summary

Inputs used

Page URL, HTTP status, Final URL, JSON-LD scripts, Parse validity, Schema @type values, Graph nodes, Structured data warnings

Limitations

Utility outputs depend on the encoded payload, file format, target app, scanner, printer, browser, and real-world testing before sharing.

Last reviewed

June 6, 2026

Cite this page

Toolkit Shelf. JSON-LD Structured Data Checker. Last reviewed June 6, 2026. https://toolkitshelf.com/tools/structured-data-checker

FAQ

Common questions

Does this replace Google's Rich Results Test?

No. It checks whether JSON-LD scripts are present and parseable, then summarizes detected types. Use platform validators for rich-result eligibility and enhancement-specific errors.

Does it execute JavaScript?

No. It reads the fetched HTML response only. Use a rendering crawler or Search Console inspection when JSON-LD is injected client-side.

Why does the checker block private or localhost URLs?

A public structured data checker must not fetch internal network targets. Blocking local, private, reserved, credentialed, and non-http destinations reduces SSRF and proxy-abuse risk.

Do utility tools upload my payload?

Use the page notes for each tool. Browser-side utilities can generate outputs locally, but the final file or code may still reveal whatever you encode or share.

Why should I test the generated output?

Scanners, printers, file viewers, apps, and platform previews can behave differently, so test the exact downloaded output before using it publicly.

Why might another checker show a different output?

Different tools may use different rounding, assumptions, default rates, methods, formulas, or input timing. Compare the visible method and inputs before relying on the output.