Structured Data Validator
Enter a page address to list the structured data it contains and check common types against what search engines require and recommend for rich results.
Ta treść jest po angielsku.
Rozwiązane przykłady
Product markup that is complete
A JSON-LD block with a Product name and an offer price pasted in
(Illustrative) Product: name and offers present, required properties found, rich result requirements met.
Required properties must be present for rich results, while recommended ones make them more complete.
Event markup missing a date
A JSON-LD block for an Event with no startDate pasted in
(Illustrative) Event: required property startDate missing, so the item is not eligible for a rich result.
Microdata types are listed but not checked, so only JSON-LD blocks get this detail.
O narzędziu Structured Data Validator
Structured data is extra markup in a page that describes what the page is about, such as an article, a product with a price, a list of questions and answers, or a local business with an address. Search engines use it to understand the page and to show richer results. A missing or wrong value can make the markup ineligible for a rich result, and a single misplaced comma can make a whole block unreadable. This validator loads a page, finds every JSON-LD block, parses it and lists each item with its type and properties.
Common types are then checked against the published guidance from search engines for rich results: Article, Product, FAQPage, BreadcrumbList, Organization, LocalBusiness, Recipe, Event, WebSite, VideoObject and Review. Each problem is labelled clearly as required, recommended or an incorrect value, so you know what must be fixed and what is optional. The tool also flags invalid JSON, a missing context, mistyped type names, empty values, malformed dates and prices, and lists any microdata types it finds. Nothing about the page is changed, so you can run it as often as you like while you work.
Jak korzystać z narzędzia Structured Data Validator
- Enter the address of the page that contains the markup.
- Select Validate and wait while the page is read.
- Fix any invalid JSON and any items marked Needs fixing, starting with the required properties.
- Add recommended properties where they are true for the page, then run the check again.
Typowe zastosowania
- Checking product pages for price and availability markup
- Confirming article markup after a template change
- Finding why a page is not eligible for a rich result
- Reviewing markup produced by a plugin or theme
- Checking that breadcrumb and organisation details are complete
Najczęstsze pytania
What is the difference between required and recommended?
Required properties must be present for a page to be eligible for the rich result of that type. Recommended properties are optional, but they give search engines more to work with and often make the result more useful. The validator marks the two differently, so you can fix the required ones first and treat the rest as improvements.
Does a valid result guarantee a rich result?
No. Passing the checks makes a page eligible, but search engines decide whether to show a rich result, and may not for quality, policy or relevance reasons. Markup should also describe content that visitors can actually see on the page. The rules also change over time, so confirm important pages with the search engine's own testing tool.
What formats are checked?
JSON-LD is fully parsed and validated, because it is the format most search engines recommend and most sites now use. Microdata types found in the page are listed so you know they exist, but they are not validated. Markup added to a page by a script after it loads is not seen, because only the page as first received is read.
Why does it say my JSON is invalid?
The text inside the script tag could not be parsed as JSON. The usual causes are a trailing comma, a missing quote or bracket, a line break inside a text value, or a stray character from a template. The message includes the nearby text, which usually points straight to the mistake. Search engines ignore the whole block until it is fixed.
What is the sitelinks search box and FAQ note about?
Search engines have changed which rich results they show. The sitelinks search box that used to be driven by WebSite markup is no longer shown, and FAQ rich results are now limited mostly to well-known government and health sites. The markup can still be valid, and the validator notes this so you do not expect a result that will not appear.
Can it check types that are not on the list?
Yes, in a limited way. Any type is parsed and its properties are listed, and obvious mistakes such as a misspelt type name, an empty value or a missing context are still flagged. For types without rich result rules the tool says so plainly rather than guessing, so you know those items were listed but not validated.