Enter any page address. MrKeyword fetches it live, reads every JSON-LD block and checks each item against Google's rich result rules: missing required and recommended properties, broken JSON, and types Google has limited or retired.
Free, no account needed. MrKeyword fetches the page live and shows only what it found.
Built on first-party data from Google and Bing
A schema markup validator reads the structured data on a page and tells you whether search engines can use it: whether each JSON-LD block parses, which schema.org types it describes, which properties Google requires or recommends for that type, and whether Google still shows a rich result for it.
Structured data is a short block of code, usually JSON-LD inside a <script type="application/ld+json"> tag, that describes the page in a fixed vocabulary from schema.org: this page is an article by this author, this business is at this address, this product costs this much. Google uses it to understand the page and, for some types, to show a rich result such as a product price, an event date or a breadcrumb trail.
The validator fetches the page the way a search engine would, reads every JSON-LD block, and checks each item against the same rules MrKeyword's site audit uses, written from Google's structured data documentation. Each item gets its Google status (Supported, Limited, Retired or No rich result), its errors and its warnings, and you can open the raw JSON of every block.
Each schema.org item on the page gets a card: its type, whether Google shows a rich result for it today, the missing required properties (errors) and the missing recommended ones (warnings).
Every JSON-LD block is listed with its raw code, so you can see exactly what Google receives. A block that isn't valid JSON is flagged, because Google ignores all of it.
The fictional northwind-plumbing.example has a blog post with three JSON-LD blocks: a LocalBusiness block for the company that leaves out the address, an Article block for the post that has no image, and an FAQPage block for the questions at the end. The validator reads them and shows:
Local business: Supports business details such as address, hours and phone number.
Errors
Article: Helps Google show the right headline, image and dates for articles.
Warnings
FAQ: Google shows FAQ rich results only for well-known government and health websites.
No missing properties.
{"@context":"https://schema.org","@type":"LocalBusiness","name":"Northwind Plumbing","url":"https://northwind-plumbing.example/","telephone":"+44 113 496 0000","image":"https://northwind-plumbing.example/van.jpg","openingHours":"Mo-Fr 08:00-18:00","geo":{"@type":"GeoCoordinates","latitude":53.8,"longitude":-1.55}}{"@context":"https://schema.org","@type":"Article","headline":"How to bleed a radiator","datePublished":"2026-09-14","dateModified":"2026-10-20","author":{"@type":"Person","name":"Sam Northwind"},"mainEntityOfPage":"https://northwind-plumbing.example/blog/bleed-a-radiator/"}{"@context":"https://schema.org","@type":"FAQPage","mainEntity":[{"@type":"Question","name":"How often should I bleed my radiators?","acceptedAnswer":{"@type":"Answer","text":"Once a year, before the heating season, or whenever a radiator is cold at the top."}}]}Example result for a fictional website (northwind-plumbing.example). It is produced by the checker's own code from the setup described above; run the checker for your own pages.
The LocalBusiness item has one error: address is required for local business details, so without it the block cannot support the business's address, hours and phone in Google. The fix is a PostalAddress with the street, town, postcode and country exactly as they appear on the contact page. The Article item parses and has its headline, dates and author, but no image, which Google recommends for article results; add the post's main photo as an absolute URL. The FAQPage block is valid, and the note explains why it will not earn the dropdowns most sites remember: Google limited FAQ rich results to well-known government and health sites in 2023. Our SEO audit guide covers structured data alongside the other checks a page needs to pass.
One trailing comma, a smart quote or an unescaped line break makes the whole block invalid, and Google ignores all of it. Generate JSON-LD with code or a plugin rather than by hand, and open the raw block to find the break.
Each rich result type has properties it cannot work without, such as address for a local business or name and offers, reviews or a rating for a product. Add the real value from the page, never a placeholder.
Recommended properties, such as image and dateModified for an article, are optional but give Google more to show. Add the ones that are true and visible on the page.
Structured data must describe what visitors can see. FAQ questions that are not on the page, or ratings that are not shown, break Google's guidelines and can lead to a manual action.
Ratings that a business puts on its own LocalBusiness or Organization item are not eligible for review stars. Mark up reviews of products or services the page is about instead.
Validate it whenever the code that writes it changes, because structured data usually comes from a template or plugin and one change reaches every page built from it.
Schema markup, or structured data, is code that describes a page in the schema.org vocabulary, such as the business name and address, an article's author and dates, or a product's price. Google recommends adding it as JSON-LD in a script tag, separate from the visible HTML.
No. Google has said structured data is not a ranking factor. It helps Google understand a page and can make it eligible for rich results, which can earn more clicks, but valid markup does not move a page up the results on its own.
Google limited FAQ rich results in August 2023: they now show only for well-known, authoritative government and health websites. FAQPage markup on other sites is still valid and does no harm, but it will not produce the dropdowns it used to. Google also stopped showing HowTo rich results in 2023.
Google reads JSON-LD, microdata and RDFa, and recommends JSON-LD because it sits in one block instead of being woven through the HTML, which makes it easier to add and maintain. This validator checks JSON-LD and notes when the page also uses microdata.
No. Google's Rich Results Test renders the page with Google's own systems and is the final word on eligibility. Use this validator for a quick read of every block, its Google status and the raw JSON, then confirm important pages in the Rich Results Test and watch the enhancement reports in Search Console.