How Do You Test Your Schema Markup?
Updated 28 September 2026
Jump to section
Test your schema markup with two free tools that answer different questions. Google's Rich Results Test shows which Google rich results your code can generate. The Schema Markup Validator checks that your markup is valid schema.org, across JSON-LD, RDFa, and Microdata. Use the first for "will Google show a rich result?" and the second for "is my code correct?". Test before you rely on any markup, and again after every redesign.
Which free tool checks what?
Two free tools cover almost every schema check, and they do not overlap. Google's Rich Results Test is scoped to Google features; the Schema Markup Validator is scoped to the schema.org vocabulary itself.
The Rich Results Test reports which "Google rich results can be generated" by your markup. It only covers Google-supported types like Product, Review, and Breadcrumb, and it is the tool to reach for when you want a search feature.
The Schema Markup Validator, hosted at validator.schema.org, does the opposite job. It confirms markup is valid schema.org "without Google feature specific warnings," nothing more. By design it checks the vocabulary and syntax, not whether your content fits any specific Google feature, so it stays neutral on rich results. It replaced the old Structured Data Testing Tool.
| Tool | What it checks | Reach for it when |
|---|---|---|
| Rich Results Test | Which Google rich results your markup can generate | You want a rich result (product, review, breadcrumb) |
| Schema Markup Validator | Whether the code is valid schema.org (JSON-LD, RDFa, Microdata) | You want to confirm the markup itself is correct |
| URL Inspection (Search Console) | What structured data Google actually read on the live page | You want the deployed result, not a draft |
Source: tool scopes from Google Search Central and schema.org documentation, accessed September 2026.
The third option belongs to Google Search Console. Its URL Inspection tool shows the structured data Google read on the real, indexed page, so it catches markup that a template stripped after launch. That is often the first place to look when a page is not showing up on Google as expected.
How do you read the results?
Read the results by separating errors from warnings first. An error means the markup is invalid or missing a required property, so the rich result cannot appear. A warning means a recommended property is missing, and the result can still show without it.
Both tools list the detected types and the properties inside each one. If a required field is absent, fix it before anything else. Recommended fields are worth adding when the data genuinely exists on the page, since a fuller result tends to earn more attention.
A pass is not a promise. The Rich Results Test confirms your page is eligible for a rich result, not that Google will always show one. Eligibility is the gate; Google still decides per query whether the feature appears.
What the Rich Results Test will not tell you
The Rich Results Test will not validate schema types Google has no feature for. If your markup uses a valid schema.org type that produces no Google rich result, the test simply reports nothing to show, which reads like failure but is not.
FAQPage is now that case. Google stopped showing FAQ rich results in Search on 7 May 2026 (Google Search Central changelog, accessed September 2026), and the Rich Results Test no longer lists the type. It finds nothing to show, while the Schema Markup Validator still passes the same code as valid.
And neither tool judges honesty. Google requires structured data to match content the visitor can see (Google Search Central, accessed September 2026). Marking up information the visitor cannot see violates its policies.
A tool confirms the syntax; only you can confirm the markup tells the truth, the same white-hat discipline behind answer engine optimization.
In our experience auditing local sites, we look first at whether the LocalBusiness details in the code still match the contact details on the page. The two drift apart when a business moves or changes a number.
Re-test after every design change too, since template changes can quietly strip or alter the JSON-LD.
Frequently asked questions
Is the Rich Results Test free?
Yes. Both the Rich Results Test and the Schema Markup Validator are free, with no paid tier and no account required for a basic check. You can test a live URL or paste a code snippet directly. For the live-page view inside Search Console's URL Inspection, you do need a verified Search Console property, which is also free.
What is the difference between the Rich Results Test and the Schema Markup Validator?
The Rich Results Test checks whether your markup can produce a Google rich result, so it only reports Google-supported types. The Schema Markup Validator checks whether your markup is valid schema.org across JSON-LD, RDFa, and Microdata, with no Google-specific rules. Use the first when you want a search feature, and the second when you want to confirm the code itself is correct.
Does passing the test improve my ranking?
No. A passing test means your schema markup is valid and eligible for a rich result, not that your page ranks higher. Google presents structured data as a way to become eligible for rich results, not as a ranking boost. The gain is an enhanced listing that can earn more clicks at the same position, plus content that machines read more accurately.
Why does the test show a valid result but no rich result appears in Google?
Because eligibility and display are separate. The test confirms your page qualifies; Google still decides per search whether to show the feature. A discontinued type, such as FAQPage, still passes the Schema Markup Validator but no longer registers in the Rich Results Test. A brand-new page may also wait until Google re-crawls it before any rich result shows.
How often should I test my schema markup?
Test before you launch new markup, and re-test after any redesign or template change. Structured data lives inside your page code, so a theme update or a new layout can break it without warning. A quick check on your key pages every few months, plus one after every design change, catches most silent failures.
Check the code, then check it tells the truth
Storming Solutions builds and maintains Malaysian business websites from Kuala Lumpur, and clean, tested structured data is part of how we hand them over. We mark up only what genuinely appears on the page, because a tool can confirm valid syntax but never confirm honesty.
Not sure what your site currently carries, or whether a redesign broke it? Ask us for a structured-data check on WhatsApp, or see how it fits our web development service. Getting the labels right is groundwork for the wider SEO work in Malaysia that follows.