Agent view · Guides · 2026-10-03
Rich Results Test vs Schema Markup Validator vs CrawlCheck
This is the response this server returns to a client that asks for Accept: text/markdown at https://crawlcheck.io/guides/schema-validators-compared-rich-results-test-vs-schema-markup-validator: fetched when you opened this page, shown byte for byte. An assistant, a crawler that negotiates markdown, or anything reading our feed gets exactly this. The markdown leaves signed (RFC 9421, key in our key directory), so a crawler can prove the page it read is the page this server sent; the check is shown below.
| status | 200 |
|---|---|
| content-type | text/markdown; charset=utf-8 |
| vary | Accept |
| link | <https://crawlcheck.io/llms.txt>; rel="describedby"; type="text/plain", <https://crawlcheck.io/.well-known/api-catalog>; rel="service-desc"; type="application/linkset+json", <https://crawlcheck.io/guides/schema-validators-compared-rich-results-test-vs-schema-markup-validator>; rel="cite-as", <https://crawlcheck.io/.well-known/http-message-signatures-directory>; rel="http-message-signatures-directo |
| cache-control | public, max-age=900, stale-while-revalidate=2400 |
| bytes | 18,126 |
| words | 2,560 |
| sha-256 | 1cfb75ad58c8118c9a3d37c8794f4ea8aa547bcb212d56bd87777f1a70af4992 |
| repr-digest | sha-256=:HPt1rVjIEYyaPTfIeU9OqKpUe8shLVa9h3d/GnCvSZI=: ← matches the body shown |
| signature-input | sig1=("@authority";req "@path";req "repr-digest" "content-type");created=1795311487;expires=1795315087;keyid="1hHmE3fo1rg5Ig70wuFtJ5wBc7G-sUTgUJkxyPWFRps";alg="ed25519";nonce="fwekcKPTqpNC4ojYz1UMtQ";tag="crawlcheck-page" |
| signature | sig1=:iwaDOUCgDIPWcJBCFE+b2WNKLaP2CIJ898sGcf8uv3ryfzEZMUeolxM5PYsVnS6a66P92ghhQhmQc1UzpEIgAA==: |
| verified | yes — signature by key 1hHmE3fo1rg5Ig70… from https://crawlcheck.io/.well-known/http-message-signatures-directory (directory valid), valid for 3600 more s. Checked here exactly as a crawler would; redo it yourself: https://crawlcheck.io/api/tool/wba |
Guides · 2026-10-03 · By [VSNARY | Emmanuel Orta](/author) · 4 views
# Rich Results Test vs Schema Markup Validator vs CrawlCheck
Three free structured-data tools answer three questions: Google rich-result eligibility, schema.org validity, and whether the markup describes one business that matches the page.
Google's Rich Results Test checks which Google rich results your structured data can produce. The Schema Markup Validator checks that any schema.org markup is valid. CrawlCheck checks whether the live markup describes one coherent business: one entity per @id, the same name, address and phone as the visible page, coordinates, and sameAs profiles that link back. All three are free. Use the first two for syntax and eligibility, then compare the markup's facts with the page, because valid markup can still describe the wrong business.
Check your own site free
Check my site
About a minute. First scan free with your email, nothing installed.
On this page
- What does each validator check?
- Which one should you use?
- How common is valid markup that still confuses machines?
- A worked example: valid markup that describes two businesses
- Valid is not true: match, conflict, not established
- A five-step check, in order
- What does “sameAs links back” mean?
- Where is CrawlCheck weaker?
Three free tools read a page’s [structured data](/glossary/structured-data), and each answers a different question. Google’s Rich Results Test asks whether Google can generate rich results from it. The Schema Markup Validator asks whether it is valid schema.org. CrawlCheck asks whether it describes one coherent business: one entity per @id, the same name, address and phone as the visible page, coordinates, and outside profiles that link back. Markup can pass the first two and fail the third, and that is the failure we see most.
**Disclosure:** CrawlCheck publishes this comparison and is one of the products in it. Every statement about another company’s tool comes from that company’s own documentation, linked where it appears, read on 3 October 2026. Where CrawlCheck does less, the tables say so.
## What does each validator check? #
| | Google Rich Results Test | Schema Markup Validator (validator.schema.org) | CrawlCheck |
| --- | --- | --- | --- |
| Question it answers | Which Google rich results this markup can produce | Is this valid schema.org markup | Does this markup describe one resolvable entity |
| Scope | Only types Google supports for rich results | All schema.org types, “without Google feature specific warnings” | [LocalBusiness](/glossary/localbusiness)/Organization identity, @id graph, name, address, phone, coordinates, [sameAs](/glossary/sameas) |
| Compares markup with the page and the web | No | No | Yes: schema name, address and phone against the visible page; each sameAs profile checked for a link back |
| Finds duplicate or colliding entities | No | No | Yes: two unlinked organisation nodes (the same @id parsed twice is correctly one entity) |
| Tests a pasted snippet before publishing | Yes | Yes | No: reads only what is live |
| Price | Free | Free | First scan free, then $3 a scan |
Sources: [Google Search Central on structured data testing tools](https://developers.google.com/search/docs/appearance/structured-data), [validator.schema.org](https://validator.schema.org/).
## Which one should you use? #
- **Want stars, FAQs or product snippets in Google:** Rich Results Test.
- **Using schema.org types Google does not feature:** Schema Markup Validator.
- **Want search and AI systems to resolve your business correctly:** a CrawlCheck scan, after the other two pass.
## How common is valid markup that still confuses machines? #
Each of the following passes both Google tools, because every node is individually valid. Shares are across every CrawlCheck scan, read live:
| Problem | Share of scanned sites |
| --- | --- |
| Two organisation nodes that do not link to each other (an [entity collision](/glossary/entity-collision)) | 2.6% |
| A business entity with no coordinates | 6.2% |
| Directory listings the site does not declare | 3.6% |
| Business name drifting between schema and page | 0.6% |
## A worked example: valid markup that describes two businesses #
The commonest failure is not a syntax error. It is two separate nodes describing the business, added by two different plugins, with nothing tying them together:
```
{"@context": "https://schema.org", "@type": "LocalBusiness",
"name": "Example Fence Co", "telephone": "+1-303-555-0100"}
{"@context": "https://schema.org", "@type": "Organization",
"name": "Example Fence Company LLC", "url": "https://example.com/"}
```
Both blocks are valid schema.org, so the Schema Markup Validator reports no errors, and the Rich Results Test has no feature-specific reason to object. A machine reading the page now holds two entities with different names, one with a phone and no [URL](/glossary/url), the other with a URL and no phone, and no statement that they are the same thing. It has to guess.
The fix is to give both nodes the same `@id` (for example `https://example.com/#business`) so they merge into one record, or to delete the weaker one and move its properties into the other. Two nodes sharing an `@id` are one entity stated twice, which is correct; we once reported exactly that as a collision ourselves, and the rule for telling the two apart is in [JSON-LD @id errors](/guides/json-ld-id-and-iri-errors-what-breaks-and-how-to-fix-them).
## Valid is not true: match, conflict, not established #
A parser tells you the JSON is well formed. It cannot tell you the phone belongs to the business. To show the gap, we built six synthetic LocalBusiness records, each paired with a line of page text, and compared the fields literally:
| Question | Result on six synthetic records |
| --- | --- |
| Did the JSON parse? | 6 of 6 |
| Did the fields match the page text? | 1 of 6 |
| Did a field (phone, hours or name) contradict the page text? | 3 of 6 |
| Was there nothing on the page to compare? | 2 of 6 |
A syntax-only check marks all six ready. The three conflicts are not malformed; they are well-formed descriptions of a business the page does not describe, and that matters for answer engines because the graph is easier to lift than the prose. An answer quoting the graph is wrong, with a [citation](/glossary/citation) to a page whose text was right.
The two “not established” rows are abstentions, not passes. The markup made a claim the page neither repeated nor denied. Count them separately: scoring them correct rewards a claim nobody can check, scoring them wrong accuses a fact nobody disproved. Six records demonstrate the categories; they are not a measure of how often live sites do this. And where an address is intentionally absent, record that rather than inventing a storefront to fill the field.
Each step answers a different question. Passing one says nothing about the next.
## A five-step check, in order #
- **Rich Results Test on the live URL.** Confirms the markup Google features parses and shows which rich results it can produce.
- **Schema Markup Validator for everything else.** Types Google does not feature (a `Service`, a `Person`, a `DefinedTerm`) are still read by other systems.
- **Compare the served HTML with the rendered page.** If a script or tag manager injects the [JSON-LD](/glossary/json-ld) after load, a crawler that does not run JavaScript never sees it. View the page source (not the inspector) and search for `application/ld+json`.
- **Compare the markup’s facts with the visible page.** Write down the name, phone, address and hours from the JSON-LD and from the page text, compare them literally, and keep three counts: match, conflict, not on the page.
- **A CrawlCheck scan for coherence.** One entity per business, coordinates on the business node, and `sameAs` profiles that link back to the site.
## What does “sameAs links back” mean? #
`sameAs` lists the other places the same business appears: a [Google Business Profile](/glossary/google-business-profile), a Facebook page, a [Wikidata](/glossary/wikidata) item, a directory listing. Anyone can list any URL there, so the list alone proves nothing. A profile that also links back to the site is a two-way statement, the version machines can trust. CrawlCheck opens each declared profile and records whether it points back; neither Google tool does, because that is outside the question each answers. Why this matters for being identified at all: [what is entity SEO](/guides/what-is-entity-seo).
## Where is CrawlCheck weaker? #
CrawlCheck is not a general schema validator. It does not test rich-result eligibility, does not validate every property of every schema.org type, and cannot test a snippet before you publish it. For syntax and eligibility, Google’s two tools are the reference. For writing a local business node that passes all three, see [LocalBusiness schema for service-area businesses](/guides/localbusiness-schema-for-service-area-businesses).
Read live from the same counters the dataset page uses, at the moment this page was served. Bars are scaled to the largest value shown, not to 100%.
Written by
[Emmanuel Orta](/author) · VSNARY
I build CrawlCheck and write everything published here, from measurements the verification layer took. Where a post got something wrong, the correction stays in the post.
[Every post, and where I got it wrong →](/author) · [Follow on LinkedIn →](https://www.linkedin.com/in/emmanuelorta)
Share this finding: [LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fcrawlcheck.io%2Fguides%2Fschema-validators-compared-rich-results-test-vs-schema-markup-validator%3Futm_source%3Dlinkedin%26utm_medium%3Dsocial%26utm_campaign%3Dshare)[X](https://twitter.com/intent/tweet?url=https%3A%2F%2Fcrawlcheck.io%2Fguides%2Fschema-validators-compared-rich-results-test-vs-schema-markup-validator%3Futm_source%3Dx%26utm_medium%3Dsocial%26utm_campaign%3Dshare&text=Rich%20Results%20Test%20vs%20Schema%20Markup%20Validator%20vs%20CrawlCheck)[Email](mailto:?subject=Rich%20Results%20Test%20vs%20Schema%20Markup%20Validator%20vs%20CrawlCheck&body=https%3A%2F%2Fcrawlcheck.io%2Fguides%2Fschema-validators-compared-rich-results-test-vs-schema-markup-validator)[Follow Emmanuel on LinkedIn](https://www.linkedin.com/in/emmanuelorta)
## Questions this post answers
### What is the difference between the Rich Results Test and the Schema Markup Validator?
Google's Rich Results Test shows which Google rich results your structured data can generate and checks only the types Google supports for them. The Schema Markup Validator at validator.schema.org validates all schema.org markup without Google feature-specific warnings.
### Can valid schema still be wrong?
Yes. Markup can be valid node by node and still describe two unlinked organisations, omit coordinates, or state a name, phone or hours that differ from the page. Syntax validity is not factual correctness, and neither Google tool compares the markup with the page text.
### What does 'not established' mean when checking schema against a page?
The markup states a fact that the page text neither repeats nor contradicts. It is not a pass and not a fail; count it separately, so an uncheckable claim is neither rewarded nor treated as disproved.
### Does CrawlCheck validate schema.org markup?
Not as a general validator. CrawlCheck checks whether live structured data describes one coherent, resolvable business: one entity per @id, consistent name, address and phone, coordinates, and sameAs profiles that link back. Use Google's tools for syntax and rich-result eligibility.
### Which schema tool should I use for AI search?
Run the Rich Results Test and the Schema Markup Validator for syntax first, compare the markup's facts with the visible page, then run a CrawlCheck scan to confirm the entity is coherent. AI systems resolve businesses from consistent identity signals, not from rich-result eligibility.
### Are these schema tools free?
Yes. Google's Rich Results Test, the Schema Markup Validator and CrawlCheck scans are all free.
## Related findings
[2026-10-03 Verify GPTBot, ClaudeBot and PerplexityBot: tools compared How to verify GPTBot, ClaudeBot and PerplexityBot requests: published IP lists, CrawlCheck's free log check and Cloudflare verifie](/guides/how-to-verify-gptbot-claudebot-and-perplexitybot-tools-compared)[2026-10-03 How to test robots.txt for GPTBot and ClaudeBot: 5 tools compared How to test robots.txt for GPTBot, ClaudeBot and PerplexityBot: five tools compared, a two-minute test, and why delivery matters m](/guides/how-to-test-robots-txt-for-gptbot-and-claudebot)[2026-09-30 NAP consistency: how to check your name, address and phone Five NAP checks, from a missing map point to a directory printing another business name, how to run each by hand, and why a refuse](/guides/nap-consistency-audit-phone-address-and-coordinates)
The main product
Found this on your own site? **We fix it for $100.**
Scan free to see where you stand. The fix is one site, every finding implemented and re-measured, with a sealed before and after.
[Fix it all — $100](https://buy.stripe.com/4gM00j7OjawhdLEdyR2VG0v)
[What it covers](/pricing#fix) · [scan first, it is free](/)
Free browser extension
Check this on any site you open, **without leaving the page.**
CrawlCheck for Chrome grades every site you visit A–F and shows, from your own browser, what search engines and AI assistants are actually served. Free, no account.
[Add to Chrome — free](https://chromewebstore.google.com/detail/plgjengobhbdmbgckiiaaflgiepdbcpi?utm_source=crawlcheck.io&utm_medium=post)
[What it does](/extension)
Write for the library
Measured something yourself? **Submit an article.**
Send your finding, the data and the method. A person reads every submission and replies by email; accepted articles are published under your name with a link to your study. Free to submit. Articles are accepted on merit; no one can pay to have one published.
[Submit an article](/submit-finding#send)
[How it works](/submit-finding) · a reply within about a week
Spotted a mistake or a bug on this page? [Report an error](/report-error?k=article). Confirmed errors are fixed and logged on the [corrections page](/corrections).
## Comments
Comments are read before they appear. Nothing is published automatically, and no account is needed. An AI agent with a published signing key can post without the queue: it signs the request and the signature is checked against its own domain ([how](/api/comment/signed)). Those appear at once, marked *verified*.
Send for review
Writing about this? [Facts, live figures and marks](/press) — every number on that page is dated and traceable to a scan.
[All guides](/guides) · [The dataset](/data) · [How the dataset works](/policy)
We read your site the way crawlers do, from our own network, and every report says exactly what was asked for and what came back. [Who runs this](/author) · [Press kit](/press) · [Videos](/videos) · [Evidence for disputes](/evidence) · [YouTube](https://www.youtube.com/@crawlcheck) · [hello@crawlcheck.io](mailto:hello@crawlcheck.io)
#### How we measure, and our own machine files
CrawlCheck reads every site as itself. Its crawler-identity tests send named user-agent strings from its own network, never from an operator’s published range, so a site that verifies crawlers can tell them apart; every report says so. Results reflect what an anonymous non-browser client receives. [What we collect and how to opt out](/policy) · [how every report is timestamped](/proof) · [who runs this](/author) · [press kit](/press) · [hello@crawlcheck.io](mailto:hello@crawlcheck.io).
**Second vantage:** the [browser extension](/extension) measures what crawlers are served from your own address and after your JavaScript runs — the half this server cannot see. From 1.0.0 it sends the domain you ask about, on one button, and anonymous usage counts you can switch off; from 1.0.3 a footer switch turns off the hostname lookup for the grade on the icon; from 1.0.4 a share switch, on by default, sends a signed Two-vantages reading (status, size, words and a hash per identity; never page text); from 1.0.16 chips send the hostnames of search results and AI citations while the chips and grade switches are on; from 1.0.17 a readings switch, on by default, sends one signed page reading a day (numbers, the hostname and the page address with the query removed; never in incognito; at most 40 a day) and only while the share and grade switches are also on. Earlier versions send nothing.
**Our own machine layer for the agentic web:** [llms.txt](/llms.txt) · [llms-full.txt](/llms-full.txt) · [agents.md](/agents.md) · [SKILL.md](/SKILL.md) · [entitymap.json](/entitymap.json) · [media kit](/.well-known/media-kit.json) · [MCP server card](/.well-known/mcp/server-card.json) · [API catalog](/.well-known/api-catalog) · [OpenAPI](/openapi.json) · [robots.txt](/robots.txt) · [sitemap.xml](/sitemap.xml) · [security.txt](/.well-known/security.txt) — every one named in robots.txt, which is exactly what we check for on yours.
**Pages:** [Keys](/keys) · [/](/) · [Listing check](/listing-check) · [SDK](/sdk) · [Robots policies](/robots-policies) · [Conduct: Google read aloud](/agents/conduct/google-read-aloud) | **Datasets:** [Maryland](/datasets/state/maryland) · [Technologies: Onetrust](/datasets/technologies/onetrust) · [Problems: Robots legacy agent only](/datasets/problems/robots-legacy-agent-only) | **Guides:** [Block AI crawlers nginx apache caddy](/guides/block-ai-crawlers-nginx-apache-caddy) | **Glossary:** [sitemap index](/glossary/sitemap-index) · [Exact-match retrieval](/glossary/exact-match-retrieval)
[Contact](/contact) · [Partnerships](/partnerships) · [Terms of service](/terms) · [Refund policy](/refunds) · [Trust center](/trust) · [Subprocessors](/subprocessors) · [Changelog](/changelog) · [Report an error](/report-error)
Same body as a file: /guides/schema-validators-compared-rich-results-test-vs-schema-markup-validator.md · as data: /feed.json · what we tell agents site-wide: /llms.txt, /agents.md. To see any other site this way, from your own browser, after its JavaScript runs: the browser extension.