AISEO SiteCHECK THE INPUT BEFORE EXPLAINING THE RESULT
JSON-LD syntax checker
Check pasted JSON-LD for parsing errors and declared types. Then verify visible facts and use Google’s feature tests for rich-result eligibility.
Start a check
Calculators and snippet preview run in your browser. Syntax checks send input to this server without publishing a result page. Do not paste tokens, passwords or private client data.
Result and scope
Waiting for input. No result is not zero.
Use the check to solve a problem
- Paste the JSON inside the script, without HTML tags.
- Confirm the declared facts are visible on the page.
- Use the official feature test for eligibility and required fields.
Separate JSON syntax from rich-result eligibility
Paste the JSON inside the application/ld+json script without the script tags. Start with malformed quotes, commas or brackets if parsing fails. The returned type names tell you what was declared, not whether those types or their fields meet Google's requirements.
Compare every claim with visible page facts before adding fields. Do not invent ratings, stock, price or reviews to make a warning disappear. This checker does not perform JSON-LD expansion, validate every Schema.org constraint or decide rich-result eligibility.
Run Google's Rich Results Test for the feature you intend to support. In Search Console, use the matching enhancement or product report when available, inspect affected examples and validate a deployed fix. An eligible page still may not receive an enhanced result.
Separate JSON syntax from factual and feature validity
Paste raw JSON-LD, not the script wrapper. This basic check parses syntax and declared types; it does not run Google’s Rich Results Test.
On a narrow screen, scroll the table sideways to read the verification column.
| What you observe | What to do | What to retain or verify |
|---|---|---|
| Valid JSON with a declared type | Compare every material claim with visible content, then use the matching official feature test. | A parse pass does not check required feature fields, eligibility, accuracy or actual display. |
| Invalid JSON | Find the syntax location, repair quoting/brackets and retest without changing the product facts. | Retain the valid document and separately inspect the delivered page. |
Work through the distinction
Teaching example: an Article object with a headline is syntactically JSON. That alone cannot establish a Product price, a real review or a Google feature entitlement.