The short answer
Use Google’s Rich Results Test to check whether a page qualifies for a Google result feature, and the Schema.org validator to check whether your markup is technically correct. They answer different questions and disagree constantly, which is the source of most confusion.
Valid markup is not the same as eligible markup, and eligible markup is not a promise of anything. Below is which tool to use when, and what the common errors actually mean.
Two people can validate the same page with two different tools and get opposite answers. Neither tool is broken. They are testing different things and nobody tells you that up front.
Which validator for which job
| Tool | Answers | Use it when | Blind spot |
|---|---|---|---|
| Google Rich Results Test | Does this page qualify for a Google rich result? | You want a rich result and need to know why you are not getting one | Ignores valid schema types Google has no feature for. Silence is not an error |
| Schema.org validator | Is this markup structurally valid? | Checking correctness, or using types Google does not surface | Says nothing about whether Google will use it |
| Search Console, Enhancements | What does Google see across my whole site? | Finding the pattern rather than one broken page | Lags by days. Only covers supported types |
| View source | What is genuinely on the page? | Always, as the first step | You have to read JSON-LD yourself |
Pro tip
Test the live URL, not pasted code. Pasted code validates the markup you think you have. A live test validates what your site actually emits after every plugin, cache layer and theme filter has had a turn. The gap between those two is where nearly every real problem lives.
The distinction that causes most confusion
Google’s own wording: “Google does not guarantee that features that consume structured data will show up in search results.” Source: Google Search Central, structured data general guidelines.
Two plugins writing the same schema node is the most common cause of a rich result quietly disappearing. The free conflict detector finds it in one screen. Download it free.
Errors nobody explains, decoded
| Message | What it means | Fix |
|---|---|---|
Invalid object type for field "author" |
You gave a plain string where a Person or Organization object is expected | Replace "author": "Jane" with "author": {"@type":"Person","name":"Jane"} |
Missing field "image" (warning) |
Optional for validity, required for most rich results | Add one. Warnings block features even though they do not block validity |
Unparsable structured data |
The JSON itself is malformed, usually a trailing comma or a smart quote | Paste the block into a JSON linter. Smart quotes from a visual editor are the classic cause |
Duplicate field |
Two plugins are both emitting the same node | Turn schema off in one of them. Do not try to make them agree |
The property X is not recognised by Google |
Valid Schema.org, but Google has no feature for it | Usually safe to ignore. It is a note, not a fault |
| Rich Results Test finds nothing at all | Either no supported type, or the markup is injected by JavaScript after render | Check view-source. If it only appears in the inspector, it is client-side and may not be seen |
The most expensive mistake
Two SEO plugins both emitting Organization or Article schema. It rarely produces a loud error. It produces two competing nodes, and the usual symptom is a rich result that quietly disappears weeks later with no warning in Search Console. If you run more than one plugin that touches schema, check your output directly rather than trusting either settings screen.
A five-minute audit
-
View source on your most important page
Search for
application/ld+json. Count the blocks. More than two or three is a warning sign in itself. -
Look for duplicate @type values
Two Organization nodes, or two Article nodes, means two systems are writing schema. Fix that before anything else.
-
Run the live URL through the Rich Results Test
Not pasted code. Note which features it detects, and which it says you are ineligible for and why.
-
Run the same URL through the Schema.org validator
This catches structural problems Google stays silent about because it has no feature for that type.
-
Check Search Console, Enhancements
One broken page is a page. The same error on 400 pages is a template bug, and only the site-wide view reveals which you have.
Does valid schema get you cited by AI engines?
This is the question behind a lot of schema validation in 2026, so it deserves a direct answer rather than an implication.
Documented
Structured data determines eligibility for specific Google result features. This is well documented and testable.
Weakly correlated
Pages with valid schema tend to be pages built with care. The correlation is real, the causation is not established.
Not evidenced
That adding schema causes ChatGPT, Claude or Perplexity to cite you. No provider has said this and no study has shown it.
So validate your schema, because broken markup costs you result features you already qualify for. Just do not expect it to move citations, and be sceptical of any tool whose pitch depends on that link.
Worth knowing
The genuine AEO benefit of structured data is unglamorous: it disambiguates. It states plainly what a page is, who wrote it, what the product costs. That helps any system, including a language model, avoid getting it wrong. Fewer wrong answers about you is a real benefit. It is just not the same as more citations.
Find schema conflicts without reading JSON by hand
The Schema Conflict Manager shows every node your pages emit and catches the duplicate Organization block another plugin is quietly adding.
- Never duplicate schema with Yoast or Rank Math
- See which plugin wins each field
- Free, no account, no card
Keep reading
Person schema and E-E-A-T for AEO: the setup that actually validates
Google says E-E-A-T is not a ranking factor. Here is what Person schema really does.
Speakable schema in 2026: what it still does and what it never did
A 2018 beta, US only, English only, Google Home only. Here is what to do instead.
Answer engine optimization for WordPress: the complete setup
Access, structure and measurement. Ordered by how much the evidence supports each step.
Frequently asked questions
What is the best schema validator?
It depends on the question. Google’s Rich Results Test tells you whether a page qualifies for a Google rich result. The Schema.org validator tells you whether your markup is structurally valid. Use the Rich Results Test for features and the Schema.org validator for correctness, and expect them to disagree.
Why does the Rich Results Test show no items when my schema is valid?
Usually because your markup uses a type Google has no rich result for, so it reports nothing rather than an error. The other common cause is schema injected by JavaScript after the page renders. Check view-source rather than the browser inspector to tell the difference.
What does “invalid object type for field” mean?
You supplied a plain text string where the specification expects an object. The usual case is an author given as a name rather than as a Person object. Replace the string with an object that has an @type and a name.
Can two SEO plugins cause schema errors?
Yes, and it is one of the most common causes of rich results disappearing. Two plugins emitting the same schema type produce duplicate or contradictory nodes. Disable schema output in one plugin rather than trying to make both agree.
Does valid schema help you get cited by AI engines?
There is no evidence that it does. Structured data determines eligibility for specific Google result features, which is documented. No AI provider has stated that schema influences citation decisions. Validate your markup for result eligibility and accuracy, not for citations.