Schema Markup Validator

It reads the JSON-LD on a page (or markup you paste), confirms each block has a valid @context and @type, and checks the required and recommended properties for the types in its rule set — Article, Product, Offer, Organization, LocalBusiness, Person, FAQPage, BreadcrumbList, Event, Recipe, Review, HowTo, VideoObject, WebSite and more. Not all of those still earn a Google rich result: Article, Breadcrumb, Local business, Organization, Product and Profile page are in Google’s current search gallery, among others, while FAQ and HowTo are not — HowTo rich results went away in 2023 and Google ended FAQ rich results on 7 May 2026 (developers.google.com/search/docs/appearance/structured-data/search-gallery, read 2026-09-23). Where a rich result still exists, an error means the item likely won’t be eligible; warnings are properties Google recommends. For the types without one, the check is that the markup is unambiguous, not that it wins a listing.

It’s a fast first pass that runs instantly, explains exactly which properties are missing, and reports on types Google’s tool no longer covers — the Rich Results Test only checks the types that still have a rich result, so a FAQPage or HowTo block reports nothing there (Google dropped FAQ testing from it in June 2026). What clean markup reliably buys you is machine-readability: it removes ambiguity for anything that parses the page, and keeps you eligible for the rich results Google still supports. It is not a way to get cited in AI answers — no AI engine documents structured data as something it uses to decide what to cite. For the final, authoritative word on rich-result eligibility, click “Test in Google Rich Results” — we link straight to it with your URL pre-filled.

No — it validates JSON-LD, which is the format Google recommends and what our generators produce. No AI engine documents a preferred structured-data format either way, so treat JSON-LD as the practical choice rather than an AI requirement. If your structured data is in Microdata or RDFa, convert it to JSON-LD (our Schema Generator can help) and validate it here.

Google ended FAQ rich results on 7 May 2026, so FAQPage schema no longer shows the expandable accordion under your listing and FAQ is no longer in Google’s search gallery. Here is where the rest of the evidence stands, because it changed. Google’s AI optimization guide states that structured data is not required for its generative AI features and that there is no special markup to add (last updated 2026-07-10, read 2026-09-23). Microsoft is the one operator that claims a benefit, saying schema helps its AI systems read content with more confidence for Copilot and AI answers in Bing (Microsoft Advertising blog, 2025-10-08, read 2026-09-23). OpenAI and Perplexity publish nothing either way, and a May 2026 difference-in-differences study by Ahrefs (an SEO tool vendor) found no citation uplift from adding schema — though every page it measured was already cited heavily, so it says nothing about pages AI has not found yet. So mark up your Q&As because it makes the question-and-answer pairing unambiguous to anything parsing the page, not because it will get you cited. The validator flags this so your expectations are accurate.