auditlamp schema check // free

does your schema even parse?

Paste your JSON-LD, or a whole page of HTML, and we pull out every schema block, parse it, list what it declares, and flag the problems that actually matter: syntax errors with line hints, missing basics like a business name or URL, and rating markup with no reviews behind it. Everything runs in your browser. Nothing is uploaded. No email.

free / no email / instant / stays on your machine

auditlamp schema check example readout
blocks1 JSON-LD block found
typesLocalBusiness, PostalAddress, AggregateRating
passparses as valid JSON / @context declared
flagLocalBusiness has no url. Engines cannot connect this markup to your domain.
flagAggregateRating with no Review markup behind it. A rating number with nothing under it reads as fake.
parses, with 2 flagscheck the flags
this is what a result looks like. paste your own markup above. for the authoritative rich-result check, use validator.schema.org.

schema is 1 of the 116 checks in the full auditlamp audit

what the schema checker looks for

Parse first. Then the honesty questions.

One stray comma silently kills an entire schema block. Browsers do not warn you, your page looks fine, and engines get nothing. So we check the boring thing first, then move to the problems that make markup useless or dishonest even when it parses.

One honest caveat: we are not Google and this is not the official validator. For the authoritative word on syntax and rich-result eligibility, run validator.schema.org after us. What we add is the plain-language reading and the flags a syntax validator will never raise.

schema questions, answered straight

The honest version.

What is JSON-LD schema markup?

JSON-LD schema markup is a small block of structured data, written in JSON and placed inside a script tag, that tells search engines and AI engines exactly what a page is: a local business, a product, an article, an event. It uses the shared vocabulary at schema.org, and Google recommends the JSON-LD format over the older alternatives because it sits in one clean block instead of being woven through your HTML. Machines read it verbatim, which is why a single syntax error voids the entire block.

Does schema markup improve my Google rankings?

Not directly. Google says structured data is not a ranking factor. What valid schema does is make your pages eligible for rich results, the enhanced listings with stars, prices, and event details, and it helps both Google and AI engines identify your business without guessing. That eligibility is worth having, but anyone promising that schema alone will raise your position is selling folklore. The honest frame: schema removes ambiguity, and ambiguity is what keeps good pages from being used.

Why is my schema valid but I still get no rich results?

Valid markup makes you eligible; it never guarantees display. Google decides per search whether a rich result appears, and it ignores markup that does not match what is visible on the page. That last part catches the most sites: a rating in the code with no reviews a visitor can see, or product details the page never shows. That is exactly why this checker flags honesty problems and not just syntax, and why the fix is usually to change the page, not the markup.

one check of the whole picture

Schema is one signal. We read the other 111.

This tool reads markup you paste. The full AuditLamp audit fetches your live page and runs all 116 checks: whether engines can reach you at all, whether anything blocks your snippets, whether there is an answer worth quoting near the top, and whether your schema matches what the page actually shows. The free scan is the diagnosis: full score, every failure, plain language, no email taken.