Online Tool Store
· 4 min read
How to Check Markup Can Earn a Rich Result
Heshan Fernando
Co-founder & COO
The recipe pages have Recipe markup. It validates. Six months later they still show as plain blue links while a competitor’s show cook time, ratings and a photo.
Valid markup is necessary for a rich result. It is not sufficient, and the gap between the two is where most of the confusion lives.
Required properties are a hard gate
Every rich result type has properties that must be present. Miss one and the page is not eligible at all, regardless of how much other markup it carries.
For Recipe, that includes the name, image and — for the cook time and rating elements specifically — the properties that populate them. A recipe with name and recipeIngredient and nothing else is valid Schema.org and ineligible for the rich result.
Recommended properties are different. They improve the result’s richness and its chances, and their absence does not disqualify.
The distinction is worth checking before concluding that markup “does not work”. Most of the time the markup is fine and one required property is missing.
| Property status | Missing means |
|---|---|
| Required | Not eligible for the rich result |
| Recommended | Eligible, less rich |
| Optional | No effect on eligibility |
Eligibility is not a guarantee
Even with everything required present, search engines decide whether to show a rich result. That decision depends on the query, the device, the site’s overall quality assessment, and how the result competes against others on the page.
That is genuinely outside your control, which makes the correct expectation “eligible” rather than “will appear”. A page that meets every requirement and shows as a plain link has not failed technically.
What you can control is being eligible. What you cannot control is the rest, and treating rich results as guaranteed leads to a lot of wasted effort chasing something that was never a lever.
Markup must match the visible page
This is the requirement with actual consequences.
Structured data describing content a user cannot see on the page violates search engine guidelines and can lead to a manual action — a penalty applied by a human reviewer, which affects the whole site and takes time to lift.
The patterns that trigger it are consistent: FAQ markup on a page with no visible questions, review markup with ratings not shown anywhere, Product markup on a category listing, and event markup for events that are not on the page.
None of these are ambiguous edge cases. They are all “the markup says something the page does not”, and it is the one structured data mistake with a real downside beyond not working.
Test the live page, not the snippet
Markup that validates in isolation frequently fails on the page it is meant to be on.
The common causes: the page renders the JSON-LD only after JavaScript runs, and the crawler saw the pre-render version; a caching layer strips inline scripts; a tag manager injects it after the crawler’s snapshot; or a second conflicting block of markup exists elsewhere on the page.
None of those show up when a snippet is pasted into a validator, because the snippet is exactly what you intended.
Testing by URL rather than by paste exercises the real rendering path. It is the only way to catch the class of problem where the markup is correct and the page does not serve it.
Common mistakes to avoid
- Assuming valid markup means a rich result will appear.
- Marking up content that is not visible on the page.
- Adding markup to a page type that has no corresponding rich result, which produces valid markup and no possible benefit.
- Leaving markup in place after the underlying content changes, so the two diverge.
- Using several conflicting types on one page and letting search engines choose.
How to do it with Rich Result Preview
The Rich Result Preview shows what the markup could produce and what it is missing.
- Paste the JSON-LD exactly as it appears on the page.
- Check the required properties first — a missing one is the usual reason nothing appears.
- Look at the preview as an illustration of what is possible rather than a prediction.
- Confirm everything in the markup is visible to a user on the page.
Google’s structured data guidelines set out the visibility requirement. Other SEO tools are in the tools directory.
Frequently asked questions
Does valid markup guarantee a rich result?
No. Valid markup with all required properties makes a page eligible. Whether a rich result appears depends on the query, device and the search engine’s own assessment.
What is the difference between required and recommended properties?
Required properties gate eligibility — missing one means no rich result at all. Recommended ones improve the result and its chances without being a condition.
Does markup have to match the visible page?
Yes, and this is the requirement with teeth. Describing content a user cannot see violates guidelines and can result in a manual action against the site.
Final thought
Check the required properties, then check the page shows what the markup claims. The first decides whether you are eligible; the second decides whether you stay that way.