Schema validator for pasted JSON-LD
Find syntax problems and supported product-markup errors in pasted JSON-LD or local HTML. Your text and files stay in your browser.
Selected checks
Fix supported errors
JSON-LD blocks
1
Supported nodes
2
Schema errors
0
Google errors
2
Unsupported checks
0
shoppa product rules v1. A local pass covers only the checks described below.
Fix supported errors. 1 blocks. 2 supported nodes checked.
Findings by block and node
Check the JSON-LD you paste
This schema validator finds JSON syntax problems and supported product-markup errors before you publish a template. Paste a JSON-LD object, an array or HTML containing application/ld+json scripts.
You can also choose a local UTF-8 file. HTML is read as inert content. Scripts never run, and the tool never requests a live URL or uploads your file.
Each script receives a block number. Paths such as Block 1 $.@graph[0].offers.price identify a node and field. Arrays and @graph are traversed, and exact @id references can resolve across supplied blocks.
A syntax error shows its block, line and column before any type-specific checks run. The location is where parsing fails, so inspect the preceding comma or quotation mark too. Semantic counts become unavailable until every block parses.
Separate schema rules from Google requirements
Valid JSON only establishes that the text parses. Schema.org describes types and properties. Google adds requirements for particular search features.
The bundled shoppa product rules v1 recognises Product, Offer, AggregateRating and Organization. The Schema profile checks selected text-property shapes and flags properties outside its list. It does not enforce a complete Schema.org vocabulary.
Selected text checks cover name, description, SKU, MPN, legal name, email, telephone and currency. Property recognition also covers product identifiers, brand, offers and ratings. Offer prices and rating numbers receive the Google checks only in the Google profiles.
The Snippets profile checks a product name and the presence of offers, review or aggregateRating. For direct Offer prices, it checks decimal format and recommends a currency code. These checks follow Google’s product snippet requirements.
The Merchant profile adds required product images and offers, and requires a direct offer price greater than zero and a currency code. The currency check covers three-letter uppercase format, not membership in the currency register. Google’s merchant listing requirements also cover rules outside this tool.
Both Google profiles check ratingValue against its stated scale, defaulting to 1 to 5. AggregateRating needs a positive whole-number ratingCount or reviewCount. Organization has selected vocabulary and text checks, with no Google eligibility assessment.
Repair a product offer example
The hypothetical linen shirt example opens with a price of "$89.95" and no priceCurrency. Its JSON parses, but the Merchant profile reports two Google errors.
Remove the dollar sign from the price and add "priceCurrency": "AUD". The corrected example has no errors in the supported checks.
The recommendation about genuine reviews remains. Reviews or ratings are optional when a product snippet has offers. Add only ratings that exist and appear on the product page.
Switch the broken example to Snippets. The malformed price remains an error, while the missing currency becomes a recommendation. In Schema, a text price is permitted by the bundled shape check. Schema.org’s Offer definition permits Number or Text for price.
Interpret errors, warnings and unsupported checks
Fix syntax errors first. A schema error identifies a failed bundled property check. The selected Google profile reports errors when its supported requirements fail. Recommendations can improve the markup without being required by those checks.
Unsupported means unchecked. An unfamiliar type or property can be legitimate Schema.org. This tool never labels the whole document valid schema, and a result with unsupported findings needs further checks.
With a plain Schema.org context, full type URLs and plain names are recognised. Custom contexts, aliases, language objects and JSON-LD expansion are outside coverage. References need an exact supplied identifier with one definition. Remote references and duplicate definitions remain unchecked.
Review, AggregateOffer, nested priceSpecification and ImageObject details need separate validation. So do availability values, price-expiry dates, shipping rules and return policies. The report shows up to 1,000 findings, with traversal capped at 60 levels and 10,000 values.
Passing local checks cannot guarantee indexing, rich-result appearance or Google selection. This tool cannot confirm image access, visible page content or whether your template emits the markup you pasted.
After publishing, run the actual product page through Google’s Rich Results Test. Check the rendered markup and fix critical errors before relying on rich results.