Schema Markup Validator
Check every JSON-LD block on a page against schema.org and Google's rules, and see how well it describes your business.
What the schema markup validator checks
Enter a URL and the validator fetches the page, finds every JSON-LD block and checks it in four layers.
Syntax. The block has to parse. Trailing commas and comments are errors: they aren't valid JSON, so a strict parser rejects the whole block. The validator still reads the rest of the block and gives you the same markup as strict JSON to paste back.
Vocabulary. Every @type and property is compared with the schema.org vocabulary, so a misspelled property, or a property attached to a type that does not have it, shows up by name.
Google's rules. For the types Google documents, such as Article, Product, Organization, LocalBusiness, SoftwareApplication and BreadcrumbList, the validator compares your markup with the required and recommended properties in Google's structured data gallery.
The entity layer. The validator scores how completely the markup describes your organization, your authors and your products, and whether the pieces connect. That layer has its own section below.
The validator reads the HTML your server returns. Google can also read JSON-LD that a script adds after the page loads, so for a page built that way, run Google's Rich Results Test as well. Google recommends JSON-LD where your setup allows it, and JSON-LD is the format this tool reads today.
How to read errors, warnings and no rich result
Every finding carries one of three labels.
The third label exists because a green check can mislead. Google states that it does not guarantee structured data will show up in search results, even when the Rich Results Test passes. The validator therefore tells you what each block can earn, and a valid FAQPage block reads "no Google rich result" with no missing-property error attached.
Two free tools sit on either side of this one. The Schema Markup Validator at validator.schema.org checks that markup is used in widely understood ways and leaves out checks for specific Google products. Google's Rich Results Test shows which rich results a page can generate. This validator puts the schema.org view and the Google view in one result.
The entity layer
Google's Organization documentation says the markup helps Google disambiguate your organization in search results. It has no required properties and recommends several, including name, url, logo, sameAs, description and address. The schema.org definition of sameAs is a URL of a reference web page that unambiguously indicates the item's identity, which makes it the property that ties your Organization to its LinkedIn page, its Crunchbase record or its Wikipedia entry.
The entity score looks for the properties that make a business identifiable:
Organization: name, url, a logo of at least 112x112 pixels that Google can crawl, sameAs links, a description and an address.
Authors: a separate Person for each author, with a name and a url or sameAs, which is what Google's Article documentation asks for.
Products and offers: an Offer with price, currency and availability.
Connections: @id values, so the Organization, the Article and its author describe one connected graph instead of separate blocks.
What entity markup can and can't do
Google says there is no special schema.org markup to add for AI Overviews or AI Mode, and an Ahrefs test of 1,885 pages that added JSON-LD found no major change in citations on AI Overviews, AI Mode or ChatGPT.
Entity markup does what structured data was built to do, which is state plainly who is behind a page. Search engines read it, and we make no promise that it changes what AI engines cite.
Common failures and how to fix them
Invalid JSON
Curly quotes pasted from a document, trailing commas and unescaped quotation marks inside a value break parsing. Use straight quotes and escape any quote inside a string with a backslash.
Product with no offers, review or rating
Google's product snippet rules require a name plus one of review, aggregateRating or offers, and an Offer needs a price. Add availability and priceCurrency. A priceValidUntil date in the past can stop the snippet from displaying.
SoftwareApplication with no rating or review
Google's software app rules require a name, offers.price (0 for a free app) and one of aggregateRating or review. Add real reviews when you have them. Without them the markup is valid and earns no rich result, so leave the ratings out.
LocalBusiness with no address
The local business rules require name and address, and geo coordinates need at least five decimal places.
BreadcrumbList with one item
The breadcrumb rules need at least two ListItem entries with a position. Google shows breadcrumbs on desktop only.
Article dates with no time zone
Google says to include one, or it assumes Googlebot's. Keep author.name to the name alone and move job titles to their own property.
Markup for content the page does not show
Google's guidelines say to avoid marking up content that is not visible to readers, and a violation can cost the page its rich result eligibility through a manual action.
An @id that points nowhere
A reference to an @id defined nowhere on the page leaves an entity with no description. Define the node once and refer to it by @id everywhere else.
After the fixes, run the validator again, then Google's Rich Results Test. Once the page is live, Search Console's rich result status reports and the URL Inspection tool show whether Google found the markup. Starting from scratch? Build the markup in the generator.
Tenpoint's angle
Tenpoint Labs measures how AI engines describe B2B companies, and the entity layer is where we start fixing it. Our Growth and Scale tiers include knowledge graph and entity work: consistent Organization and Person markup, sameAs links to the profiles that identify you, and Product and Offer data that matches the page. The validator shows what your markup says about you today. The free AI visibility audit shows what ChatGPT, Perplexity, Gemini and Claude say.
More free checks: check which AI crawlers can reach your site and check your domain rating. Related reading: whether schema helps AI Overviews, structured data in a technical SEO audit, and what an entity and structured data review covers.
Key facts
A plain summary of the validator, written for people and for the systems that summarize pages.
- Input
- A URL, or JSON-LD and HTML pasted in (up to 500,000 characters)
- Format read
- JSON-LD; Microdata and RDFa on the page are reported, not graded
- Checks
- Syntax, the schema.org vocabulary, Google's required and recommended properties, and an entity score
- Labels
- Error, warning, and no Google rich result
- Report
- A PDF by email; the entity fix pack shows on screen once you give an email
- Price
- Free, no signup
- Made by
- Tenpoint Labs
Questions about schema markup
What is a schema markup validator?
A schema markup validator reads the structured data on a page and reports whether it is well formed, uses real schema.org types and properties, and meets the rules of the search feature you want. This one reads every JSON-LD block on a URL, checks Google's required and recommended properties for common types, and scores how completely the markup describes your organization.
What is the difference between the Schema Markup Validator and Google's Rich Results Test?
The Schema Markup Validator at validator.schema.org checks that markup is used in widely understood ways and leaves out checks for specific Google products. The Rich Results Test shows which Google rich results a page can generate. Markup can pass the first and earn nothing in the second, so run both. This validator reports the schema.org view and the Google view in one result.
Why does my schema pass validation but show no rich result?
Valid markup is the entry requirement. Google says it does not guarantee that structured data will show up in search results, even when the Rich Results Test passes. Common causes are a type that no longer has a rich result (FAQPage since May 2026, HowTo since 2023), a missing required property for that feature, markup that describes content the page does not show, and a quality guideline violation.
What is the difference between an error and a warning in structured data?
An error means a property that Google requires is missing or invalid, and Google says items without all required properties are not eligible for rich results. A warning means a recommended property is missing. The markup stays eligible, and Google says the more recommended properties you provide, the higher quality the result is to users.
Do I still need FAQ schema?
Google stopped showing FAQ rich results on May 7, 2026 and removed the documentation on June 15, 2026, so new FAQ markup earns nothing in Google Search. Existing FAQPage markup is valid schema.org, and Google's 2023 announcement told site owners they did not need to remove it. The validator labels it "no Google rich result" and reports no missing-property error.
Does schema markup make ChatGPT or Google AI Overviews cite my site?
The evidence shows no reliable citation lift. Google says no special schema.org markup is needed to appear in its AI features, and an Ahrefs study of 1,885 pages that added JSON-LD found no major change in citations on AI Overviews, AI Mode or ChatGPT, among pages that were already heavily cited. Schema still tells search engines what a page and its organization are, which is why the validator checks it.
Which format should I use: JSON-LD, Microdata or RDFa?
Google supports all three and recommends JSON-LD where your setup allows it. JSON-LD sits in a script tag apart from the visible text, which makes it easier to write and to nest. This validator reads JSON-LD today.
