Paste any URL. We extract every JSON-LD block, list the entity types you are declaring, and flag the missing required properties that quietly disqualify you from rich results.
Schema either works or it does not, and there is no warning either way. A single trailing comma invalidates an entire block. A missing author property disqualifies an Article from rich results. Search Console only reports on the types it happens to support, which leaves most of your markup unchecked.
JSON-LD is parsed whole. If a block fails to parse, every entity declared in it is discarded — not just the offending line. Plugins and manual edits fighting over the same block is the usual cause.
Your markup can parse perfectly and still be ineligible. Article without an author, Product without a name, Event without a start date — syntactically fine, functionally rejected.
When a theme, an SEO plugin and a page builder each emit their own Organization block, search engines have to guess which describes the business. Ambiguity here weakens everything downstream.
Article, BlogPosting, NewsArticle need headline, author and datePublished. Missing author is the single most common reason editorial markup fails — and the one most often introduced by a theme change.
Organization needs name and url. LocalBusiness and ProfessionalService additionally need a valid address. A malformed address here silently removes you from local eligibility.
Product needs a name. Event needs name, startDate and location. JobPosting needs title, hiringOrganization and datePosted.
BreadcrumbList needs itemListElement. VideoObject needs name, thumbnailUrl and uploadDate. WebSite needs url. Person needs name.
We fetch the page, extract every JSON-LD block, walk the full node tree including nested entities, and report what is declared and what is missing.
Reads the public HTML only. No crawling, no signup, nothing stored.
Invalid JSON or a missing required property. The affected markup is being ignored, so you are getting no benefit from it at all.
Missing @context, or competing entity declarations. Not fatal, but it introduces ambiguity that weakens how confidently your entity is understood.
Notes about how a type behaves in practice — such as FAQPage no longer producing rich results for most sites since Google narrowed eligibility in 2023.
Schema does not raise rankings. Google has been explicit and consistent about this. Adding markup to a page nobody wants to read changes nothing. Anyone selling schema as a ranking lever is misrepresenting it.
It makes you eligible for rich results, and it resolves ambiguity about what your entities are. That second part matters increasingly for AI systems, which lean on explicit structure when deciding what a page is about and whether to cite it.
Rich Results Test only reports on types Google supports for rich results, so most of your markup goes unexamined. This validates everything you declare, including nested entities, and flags conflicts between blocks that Google’s tool does not surface.
Either works. What matters is that they do not contradict each other. Problems arise when a theme, an SEO plugin and a builder each emit their own Organization or Article block with different values.
For rich results, generally not — since 2023 Google shows FAQ rich results only for government and health sites. It is not harmful, and it may still help machines parse your content, but it will not produce the SERP feature most people add it for.
Yes, Google supports microdata and RDFa. JSON-LD is the recommended format because it is separate from your markup and far easier to maintain. We flag when microdata is present so you know both formats are in play.
Search Console only validates types eligible for rich results. If you declare types outside that set, or your markup fails in ways Google does not report on, it stays invisible there.
Structured data makes you legible to machines. Whether they choose you as the source is a question of authority and evidence.