Skip to content
Sitequiry
Free tool

Check the schema markup (JSON-LD) of a page

Enter a public URL. The checker reads every JSON-LD block in the page, reports blocks that do not parse, lists the schema.org types and compares seven common types with the properties Google documents. No account required.

Reads the HTML the server sends. Markup that a script adds after loading is not seen.

What is compared

For Organization, LocalBusiness, Product, Article, BreadcrumbList, Event and Recipe the checker knows the properties Google lists as required and a selection of the recommended ones (Google Search Central). A missing required property is an error, a missing recommended one a note. Organization and Article have no required properties at all. Other types are listed but not compared, which says nothing about whether they are correct.

FAQ markup no longer gives a rich result

Google stopped showing the FAQ rich result on 7 May 2026 and removed its documentation in June (Google Search Central updates). FAQPage markup is still valid schema.org and does no harm, but it no longer changes how a result looks in Google. The checker says so instead of asking you to complete it.

An example from ge-ko.si

On 11 November 2026 the home page of ge-ko.si, the agency behind Sitequiry, carried one JSON-LD block with five entities. Organization had the recommended properties the checker looks for; ProfessionalService, compared as a LocalBusiness, had the required name and address and lacked only the recommended geo; WebSite and Person were listed without comparison; FAQPage was reported as a type without a rich result.

Limits of this check

This is not Google's Rich Results Test, which renders the page and applies every rule of each feature. Correct markup makes a page eligible for a rich result; Google does not guarantee one. Structured data is also not a switch for AI answers: Google states that its AI features need no special schema.org markup (Google Search Central). Microdata and RDFa are counted, not checked.

Frequently asked questions

Why does my JSON-LD not parse?

The usual causes are a comma before a closing bracket, a quotation mark inside a text that is not escaped, or a template that printed nothing where a value should be. The checker reports the line of a trailing comma when it finds one.

Is a missing recommended property a problem?

No. Recommended properties make a rich result more complete; only required ones decide eligibility. Add those you have real values for and leave out the rest. Markup must describe what the visitor can see on the page.

Does schema markup improve rankings?

Structured data helps a search engine understand a page and makes it eligible for rich results. This checker does not measure rankings, and correct markup is not a promise of a better position.

See how the whole page does

The free analysis checks a page for SEO, speed with Google PageSpeed, AI answer readiness and AI citability.