How to Check Schema Markup on a Website

How to check schema markup on a website depends on what you need to prove. Use Google's Rich Results Test to check eligibility for supported Google rich results, the Schema Markup Validator to validate any Schema.org vocabulary, and Search Console after publishing to confirm Google can process the live page. This guide is for owners, marketers, and developers checking a page before release.

Short answer: Open the live URL in Google's Rich Results Test, fix errors tied to the page's visible content, then run the same URL through the Schema Markup Validator. After deployment, inspect the URL in Search Console and monitor the relevant rich-result report. Valid markup can make a page eligible; it does not guarantee a rich result.

What schema markup checks actually tell you

Schema markup is machine-readable information embedded in a page. It can describe an article, organization, product, local business, or another entity. Google says structured data helps it understand page content and may enable richer search appearances, while the Schema.org vocabulary can be used by other systems too (Google's structured-data introduction).

The key distinction is between syntax, eligibility, and performance:

Check	Question answered	Best tool
Syntax	Is the JSON-LD, Microdata, or RDFa parseable?	Schema Markup Validator
Google eligibility	Could this page qualify for a supported rich result?	Rich Results Test
Live discovery	Did Google process the deployed page?	URL Inspection and Search Console reports

Do not treat a green validation result as a ranking promise. Google explicitly says structured data does not guarantee that a rich result will appear, and the markup must represent content visible to readers (Google's general structured-data guidelines).

Step 1: Test the live page with Google's Rich Results Test

Publish or stage the page at a URL that the tester can fetch.
Open the Rich Results Test.
Choose URL input for a deployed page, or code input while developing a small snippet.
Review detected items, errors, warnings, and the preview for supported features.
Open each error and compare the property with the visible page.

URL testing is the useful final check because it includes the response Google can fetch. A local script or CMS preview can hide blocked resources, template changes, or a different canonical URL.

Step 2: Validate all Schema.org types

Google's tester focuses on Google-supported rich-result features. It is not a complete validator for every Schema.org type. Paste the page URL into the Schema Markup Validator when you use types or properties that do not map to a Google feature.

Check these common failure points:

The @type matches the page's real subject.
Required properties have the correct data type.
Dates use an unambiguous ISO format.
URLs resolve to the same entity and canonical page.
Names, prices, ratings, and availability match visible text.
No private, hidden, or invented content is marked up.

For a blog article, compare the headline, author, publication date, modified date, and image in JSON-LD with the rendered article header. For a local business, compare the name, address, phone, and service details with the business's public information.

Step 3: Check the deployed page in Search Console

After deployment, use Search Console's URL Inspection tool to test the exact canonical URL. Confirm that the page is indexable, the selected canonical is expected, and the rendered page contains the markup. Then check the applicable enhancement report for recurring errors.

Search Console performance data is useful for the next question: whether the page earns impressions and clicks. Google recommends comparing pages over time and filtering by URL rather than assuming a rich result caused a change (Performance report guidance).

Common schema-checking mistakes

Testing only the homepage

Every page needs markup that describes that page. A homepage test cannot prove that an article template, service page, or location page is valid.

Marking up invisible claims

Do not add a five-star rating, price, address, or FAQ that readers cannot see. This can make the page ineligible even when the JSON is syntactically correct.

Mixing entities

An article author, publisher, and business can be related but are not interchangeable. Use stable names and URLs so crawlers can distinguish them.

Stopping after development

Templates change during deployment. Re-run the live URL test after a release and keep a dated record of errors in your issue tracker.

Schema markup checklist

Identify the page's primary visible entity.
Choose the narrowest accurate Schema.org type.
Add only properties supported by visible content.
Test the live URL in Rich Results Test.
Run Schema Markup Validator for complete vocabulary validation.
Inspect the canonical URL in Search Console after release.
Compare impressions and clicks before and after the change.

If you want a quick first pass, use the VisiScan schema checker, then verify important fixes in Google's tools.

FAQ

Is schema markup the same as SEO?

No. Schema markup is a machine-readable description of page content. It can help Google understand a page and make it eligible for some rich results, but it does not replace useful copy, crawlability, links, or other SEO fundamentals.

Which tool should I use to check schema markup?

Use Google's Rich Results Test for Google feature eligibility and Schema Markup Validator for general Schema.org validation. Use Search Console's URL Inspection and enhancement reports after deployment. Running only one tool leaves part of the check untested.

Can valid schema markup improve rankings?

Valid markup can make a page eligible for a richer search appearance, but Google does not guarantee that appearance and says structured data does not directly guarantee higher web-search rankings. Measure impressions, clicks, and conversions instead of assuming an uplift.

Conclusion

To check schema markup on a website reliably, test the exact live URL, validate both Google eligibility and general Schema.org syntax, and confirm the deployed canonical in Search Console. Keep markup synchronized with visible content, then measure the page over time. Start with the schema checker and use official validators for the final decision.

Sources

Google: Introduction to structured data (reviewed August 2026)
Google: General structured-data guidelines (reviewed August 2026)
Google: Performance report tasks (reviewed August 2026)