What a rich results test tells a founder about schema markup
Treat Google's verdict as a gate, not a growth metric, and keep schema healthy between checks with seogeoaeo.ai.
The rich results test is Google's free check of whether a page's structured data qualifies for the richer search listings that show a price, a rating, an event date or a breadcrumb trail. For a founder, treat the result as a gate rather than a growth number: a pass means the page may get the richer listing, and Google still decides on every search. To keep schema healthy between Google checks, our pick is the schema check from seogeoaeo.ai, which tests JSON-LD against Google's rules and points out the types a page is missing.
Read the result as a business signal
Google's test, at search.google.com/test/rich-results, takes a URL or a pasted snippet and returns one of a handful of statuses. Each one means something different for the company.
| Result | What it means | Who acts |
|---|---|---|
| Valid items detected | The page is eligible for that rich result | Nobody, unless a recommended field would show something useful |
| Valid with warnings | Still eligible, but the listing may show less | Content or marketing, when the warning is about a price, image or rating |
| Some or all invalid | Those items cannot get a rich result | Engineering |
| Syntax errors detected | The parser stopped before it could tell what the item was | Engineering, today |
| No items detected | No supported type was found | Check whether you expected one |
| URL cannot be crawled | Google could not fetch the page | Engineering: robots.txt, noindex, DNS or SSL |
The two worth escalating are invalid items and syntax errors, because they turn a page you meant to stand out into a plain blue link.
Which pages deserve the effort
Rich results pay off on pages where the extra detail helps someone choose. Search Console keeps separate reports for types such as product snippets, merchant listings, review snippets, events, job postings, recipes, videos and breadcrumbs, which is a fair list of where to spend time.
Two types are not worth new work in November 2026. Google dropped HowTo results in 2023, and FAQ rich results stopped appearing on May 7, 2026. If an agency still sells FAQ schema as a quick win, ask what it expects to show.
What a pass does not tell you
- It is not a ranking report. The test checks eligibility for a display feature.
- It is not a promise. Google's guidelines say correct markup does not guarantee that structured data shows in results.
- It is not permanent. Markup must match what the page shows. Google can take away a page's rich result eligibility with a structured data manual action.
A routine a small team can keep
- Before launch: paste the JSON-LD for new templates into the seogeoaeo.ai checker. It flags blocks that fail to parse, missing required and recommended properties, an Offer with no price, and retired types. A run costs 8 credits, shown before it starts.
- After deploy: put the live URL through Google's test with the default smartphone crawler.
- Every month: open the rich result reports in Search Console and look for new invalid items.
The first step is the one teams skip, and it is cheap to hand off. The checker also runs over MCP and REST, so the engineer or coding agent that ships the template can check its own markup and rerun until the result is clean. More on the agent setup is on seogeoaeo.ai.
When the free test is enough
If you are checking one page once, Google's test alone will do, and it reads Microdata and RDFa as well as JSON-LD. The checker earns its place when schema ships with every release or when nobody on the team wants to remember to open a browser tab. It does not render JavaScript, so markup added by a tag manager still needs Google's test.