Toolkit Shelf
Find

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 and sources checked July 12, 2026Checks a public pageSource note included

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.

Data freshness

No live response has been fetched yet. Run the checker to record a point-in-time source timestamp.

Web QA reports are launch checks, not crawler verdicts. Search engines, social platforms, consent flows, JavaScript rendering, and cache timing can still change what users or bots see.

Quick answer

JSON-LD Structured Data Checker: what it checks

JSON-LD Structured Data Checker fetches one public page, parses its JSON-LD scripts, and reports syntax validity, detected @type values, graph nodes, and parsing warnings. It verifies the markup found in the fetched HTML but does not guarantee rich-result eligibility.

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 launch, migration, campaign, or support URLs before requesting indexing or handing the page to another team.
  • Capturing concrete page evidence such as redirects, headers, canonicals, robots directives, metadata, schema, headings, image alt text, or internal links.
  • Separating what the fetched HTML says from what still needs a browser crawl, Search Console inspection, platform debugger, or manual review.

Before relying on it

Check first

  • Treating one fetched URL as proof that every page, device, locale, redirect, or logged-in state behaves the same way.
  • Ignoring fetch guardrails, blocked private destinations, truncated bodies, JavaScript-rendered tags, or platform-specific preview caches.
  • Submitting or promoting a page before checking the final URL, canonical target, noindex signals, status code, and source-specific warnings together.

Details

What to know before using the output

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

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

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

Web utility checkers use bounded public fetches and visible parsing rules. They do not replace a full crawl, Search Console URL inspection, authenticated testing, or platform-specific debugging tools.

Method and sources checked

July 12, 2026. The documented method, source timing, validity conditions, and reliance limits were checked on this date.

Method provenanceExternal data · toolkitshelf.JSON-LD-static-HTML.v1
Maintained by
Toolkit Shelf
Calculation class
External data
Method version
toolkitshelf.JSON-LD-static-HTML.v1
Primary source
User-provided public URL
Source date
At each run
Source checked
July 12, 2026
Intended audience
Site owners, developers, editors, and launch reviewers checking one public URL at a time.
Valid when
JSON-LD must exist in the fetched static HTML and be valid JSON. Client-injected, authenticated, blocked, or truncated markup may be absent.
Reliance boundary
The report parses JSON-LD syntax and visible types; it is not Google Rich Results eligibility, schema-policy approval, or a rendered-DOM validator.
Data freshness
Each result is a point-in-time server request. Rerun the checker after the page, server, cache, or redirect behavior changes.
Cite this page

Toolkit Shelf. JSON-LD Structured Data Checker. Page version July 12, 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.