Blog / Technical SEO /
Separating schema validation errors from rich result eligibility
The validator shows a red error. Panic: we’ve lost our rich results! Meanwhile another page has a clean report and still shows no enhanced result at all.
Validation and eligibility are related, but they answer different questions. Mixing them up is how teams end up promising a display outcome that structured data can’t guarantee.
So the first step is to understand what the tool actually tested and what the search feature actually requires.
Confirm what the validation error means
Find the exact markup, page and reported field. Some errors mean invalid syntax or a missing required property for a feature. Others are just warnings about recommended information. Read the tool’s documentation and the current feature requirements instead of treating every message as equally serious.
Inspect the rendered page and structured data. Confirm that the markup describes visible, accurate content and is associated with the correct entity. A technically valid JSON-LD block can still contain a wrong price, product or organisation.
Check whether the markup is generated by a theme, plugin or custom code. Multiple sources may output overlapping entities. Fix the underlying generator and verify the public output after changes.
Understand eligibility separately
A page can be valid for a rich result feature and still not get the display. Eligibility isn’t a promise. The query, the page quality, the policy requirements and the search system’s own decisions all play a part.
Check the page against the feature’s current content and policy rules. Markup can’t create a review, product attribute or event that isn’t really there, and I’d never add fields just to trigger a visual treatment.
Check whether the feature exists for the page type and market being considered. Search result appearance can differ by device, query and location. Do not use one screenshot as evidence that every user sees the same result.
Test with the right tools
Use a structured data validator to check syntax and a rich result testing tool for supported features. These tools have different scopes. A schema.org validator may confirm vocabulary and syntax without evaluating a search engine’s feature eligibility; a search feature test may focus on a subset of structured types.
After deployment, check the Search Console reports and note the exact URL and date. Reports can lag or show sampled examples. Fix real errors, but don’t assume a warning explains a traffic change.
If markup changes, test representative pages and variants. A product template may output correct data for one item but fail when a price, availability or review is missing. Include empty and unusual states.
Keep claims and expectations accurate
When you report to stakeholders, say “the markup passes validation” or “the page is eligible based on the current test” only when that’s what the evidence shows. Never promise a rich result or a ranking benefit.
I’d document the implementation, the test, the feature rules checked, the date and any known limitations. If requirements change, revisit the markup and documentation. Assign an owner for structured data generated by an app or plugin.
Do not use invalid or misleading markup to make a result more attractive. Structured data should represent the page accurately for users and systems.
Check the visible content and policy
Structured data should describe what visitors can see and what the page actually offers. Review whether the page content meets the feature’s content requirements, whether the markup is generated from accurate fields and whether any reviews or ratings are genuine and eligible for inclusion. A syntactically valid property does not make a prohibited or unsupported claim acceptable.
If a validator reports missing recommended fields, decide whether they are relevant and available. Do not fill fields with fabricated defaults. If an error comes from a plugin, check whether the setting can be corrected at the source rather than layering a second markup block over it.
Rich result tests can indicate eligibility conditions at a point in time; search systems may still choose a different presentation. Record the test date and URL. If the page changes, rerun the test on the rendered version.
A useful report says what was validated, which feature was checked and what’s still unknown.
Communicate findings to non-technical stakeholders
A schema review report should distinguish defects that affect markup, issues that affect eligibility and uncertainty about display. Explain the practical consequence for the page, not only the technical field name. This helps stakeholders decide whether a fix is urgent or informational.
If a rich result is not showing, avoid promising that a schema change will make it appear. Verify that the feature is supported, the page meets policy and the markup is correct. Then monitor the appropriate reports and communicate that search systems retain discretion over presentation.
Keep a screenshot or test result for the review date, labelled with the tested URL and tool. A visual result can change between queries and users.
If the output shows several errors, fix one source of duplication at a time and rerun the test. That’s how you tell whether a change helped or created a new conflict. Record the test environment and the exact page version.
Related reading
- Schema markup in 2024: what’s still worth adding
- How to assess URL parameters without blocking useful pages
- What to inspect when important pages disappear from search
So, with a schema warning in front of you, can you say whether it’s a syntax issue, a feature requirement or a separate eligibility question, and verify each with the right tool?