Artificial IntelligenceMartech Zone AppsMartech Zone Query ToolsPaid and Organic Search Marketing

Schema Validator: Check The Structured Data on Your Site or Page

A visitor can tell that a page is a product, a recipe, or a news story, while a crawler or a model sees only a string of text, a number, and a name and has to decide what each one is. When that decision is only a probability, a price can be read as a year, a quoted expert can be stored as the author, and two companies with the same name can be merged into one. Structured data replaces guesses with labeled statements in a shared vocabulary, saying this URL is the product, that the number is its price, and that the person who wrote the article works for the organization.

People notice structured data when it changes how a search result looks, creating a rich result in the SERP. The same graph is what a system uses when it cites a source, answers a question, or decides that two pages are the same entity, because a type and a stable identifier give it something to look up. The writing can still make the argument, while the markup records the facts those sentences never quite pin down.

To see what a page actually publishes, paste an address into the checker below. It reads the first HTML response, the document a client receives before any script runs, and lists the JSON-LD, Microdata, and RDFa it finds. When that response has no structured data, it loads the page in a browser and compares the two. Markup that appears only after JavaScript runs is invisible to many AI crawlers and other bots that don’t execute scripts.

Schema Validator v1.0.6Last Update: Nov 17, 2026

Enter a page address. Each schema tag opens as a hierarchy: the full tag, then every type and the properties nested under it.

Required — The full https address of the page whose structured data you want to read.
Check schema
Was this helpful?

Schema

Schema.org is a public vocabulary, maintained as a tree. Thing is the root. Under it sit Action, CreativeWork, Event, Intangible, Organization, Person, Place, and Product, along with whole branches most marketing sites should never publish, including medical entities and biochemical entities. A second, smaller tree holds data types such as text, number, and date.

You do not publish the tree. You publish the single most specific type that names the thing on that URL, then connect it to the other things with properties. A blog index is a CollectionPage. A CollectionPage is already a WebPage, the same way a NewsArticle is already an Article. A second, generic WebPage node for that same address does not create a hierarchy. It creates two identities for one page. The hierarchy that matters is the link: the page is part of the website, the article is the main entity of the page, and the offer belongs to the product.

On an article, two nodes are correct, and they are not a parent and a child of the same kind. The WebPage is the page. The Article is the work on that page. The article points at the page with mainEntityOfPage. Nesting a CollectionPage under a separate WebPage for the same URL is a different, and worse, pattern.

Rich Results Are a Short List

Google uses structured data for two jobs. One is understanding. The other is drawing a richer search result when the type is on a list Google still supports. That list is shorter than schema.org, and it changes. The Rich Results Test only knows the short list. A correct CollectionPage can pass the Schema Markup Validator and show nothing in the Rich Results Test. That is not a broken page. It means Google has no special drawing for that type.

Google’s gallery documents these rich results: Article, Breadcrumb, Carousel, Course list, Dataset, Discussion forum, Education Q&A, Employer aggregate rating, Event, Image metadata, Job posting, Local business, Math solver, Movie, Organization, Product, Profile page, Q&A, Recipe, Review snippet, Software app, Speakable, Subscription and paywalled content, Vacation rental, and Video. A carousel is not its own content. It has to be paired with a recipe, a course list, a restaurant, or a movie.

Several types of people still paste in no longer produce a rich result. How-to steps lost theirs in September 2023. FAQ rich results were restricted in August 2023 and are absent from the current gallery. The old author snippet is gone, and ProfilePage is what replaced it. ClaimReview, SpecialAnnouncement, and JobTraining no longer draw a result. The markup can still help an AI system when the page really is that thing. Markup that describes something the visitor cannot see is a spam signal.

I wrote a shorter, SERP-focused version of this years ago: Enhance Your Google SERP Presence With These Rich Snippets. The piece below is the site-type map that article did not have.

Publish JSON-LD

Put the statements in JSON-LD, inside one script element whose type is application/ld+json. Microdata and RDFa can express the same vocabulary as HTML attributes. They break more easily when a template moves a headline or a price. JSON-LD stays in one block, which is also the form Google asks for.

Open Graph is not a substitute for Schema. Those tags describe the card a social network shows when someone shares the URL. Schema.org describes the entity. A site needs both, and they answer different questions.

A minimal page node looks like this. The @id is the stable name of the entity. The url is where it lives. isPartOf points at the website node, which you publish once and reuse.

{
  "@context": "https://schema.org",
  "@type": "CollectionPage",
  "@id": "https://example.com/#webpage",
  "url": "https://example.com/",
  "name": "Example",
  "isPartOf": { "@id": "https://example.com/#website" }
}

Choose the Site You Actually Run

The full type list is hundreds of classes. Printing all of them hides the decision. Pick the closest site type. Each panel has the types to publish on that kind of site, the types to add only when the page visibly contains them, and the reason either choice matters. If the menu does not run, every panel is on the page in order.

Every Website

Publish These

  • Organization, or a more specific subtype you qualify for, with name, url, logo as an ImageObject, and sameAs links that really are your profiles.
  • WebSite with name, url, publisher, and inLanguage. Add a SearchAction only when the target URL runs a real search.
  • A page node at a stable @id. Use WebPage, or a subtype when the page is one: CollectionPage for a listing, AboutPage, ContactPage, SearchResultsPage, CheckoutPage, ItemPage, ProfilePage.
  • BreadcrumbList on internal pages. Leave it off the homepage. A breadcrumb describes the path back to the root, and the root has no parent.

Add When the Page Shows It

  • ImageObject with creator, credit, and license, so image search can show attribution.
  • PostalAddress and a contact point when the address and phone are on the site.

This is the identity layer. Rich results for breadcrumbs and organization details come from it. AI systems use the same nodes to decide which organization a page belongs to, and to avoid inventing a second entity when the name is ambiguous.

Publisher or Blog

Publish These

  • BlogPosting or Article with headline, image, datePublished, dateModified, author, and publisher.
  • WebPage for the article URL, and mainEntityOfPage on the article pointing at that page’s @id.
  • Person for the author, with url and sameAs. The byline on the page and the Person node should name the same human.
  • CollectionPage on the home page and on category archives. Add an ItemList of the posts actually rendered on that page.
  • BreadcrumbList from the home page through the section to the article.

Add When the Page Shows It

  • Blog as the series the posts belong to.
  • Speakable only for passages you would stand behind in audio playback.
  • Review or AggregateRating only when the reviews are visible on that URL.

Article markup is what makes a post eligible for article rich results, including a larger image. The dates and the author are also how a model judges freshness and who is responsible for the claim. A CollectionPage without an ItemList says the page is a list and then fails to name a single item on it.

Newsroom

Publish These

  • NewsArticle, or a closer subtype when it fits: ReportageNewsArticle, AnalysisNewsArticle, OpinionNewsArticle, BackgroundNewsArticle, or ReviewNewsArticle.
  • NewsMediaOrganization as the publisher, with a logo Google’s article guidelines accept.
  • headline, image, datePublished, dateModified, and the author Person.

Add When the Page Shows It

  • LiveBlogPosting for a story that is updating in place.
  • Speakable for the sentences you want read aloud.
  • ClaimReview only on a real fact check. Google no longer draws a rich result for it.

The subtype is the point. An opinion labeled as reportage trains both search and AI to treat a column as a news account. Inclusion in a news surface still depends on more than markup, but the markup is how you stop the wrong type from sticking to the story.

Local Business

Publish These

  • The most specific LocalBusiness subtype that fits: Store, AutoDealer, Dentist, LegalService, LodgingBusiness, or another child. Do not stop at LocalBusiness when a child exists.
  • PostalAddress, GeoCoordinates, telephone, image, url, and OpeningHoursSpecification that match the door.
  • The page node isPartOf the WebSite, with the business as the main entity.

Add When the Page Shows It

  • AggregateRating and Review only for reviews the page displays.
  • priceRange, department, and a menu or appointment URL when those are real.

Google can show hours, location, and actions from this markup, and it also leans on the Business Profile you manage separately. Schema does not replace that profile. Do not use ProfessionalService or Attorney. Both are retired on schema.org. Use the specific service type instead.

Restaurant

Publish These

  • Restaurant, with address, servesCuisine, opening hours, and telephone.
  • Menu or hasMenu pointing at the menu the guest can open.

Add When the Page Shows It

  • MenuSection and individual offers when you publish prices.
  • A reservation or order URL, and ratings only when shown.

Restaurant is the LocalBusiness subtype Google pairs with a carousel. FoodEstablishment is the parent. Prefer Restaurant unless you are a bar, cafe, or other child that fits more tightly. The menu in the markup has to be the menu on the page.

Online Store

Publish These

  • Product with name, image, description, and brand.
  • Offer with price, priceCurrency, availability, and url. The offer is not optional if the page shows a price.
  • sku, gtin, or mpn when you have one. Do not invent one.
  • ItemPage or a WebPage whose main entity is that product.
  • CollectionPage and an ItemList on category pages, one list item per product the visitor can see.
  • BreadcrumbList through the catalog.

Add When the Page Shows It

  • AggregateRating and Review for on-page reviews.
  • Shipping and return policies when you publish them as structured policy, not as a paragraph you hope a model will parse.

Price and availability are the product rich result. They are also the facts an AI shopping answer will repeat. A stale OutOfStock flag, or a price that does not match the page, is worse than leaving the offer off.

Software or SaaS

Publish These

  • SoftwareApplication, or WebApplication or MobileApplication when that is the specific product.
  • name, description, applicationCategory, operatingSystem, and the publisher Organization.
  • An Offer when a public price is on the page. Skip the offer when the only price is a request to contact the vendor.

Add When the Page Shows It

  • screenshot, featureList, downloadUrl, or installUrl.
  • AggregateRating only for ratings you display.

This is the software-app rich result. A SaaS homepage that marks itself as a Product with a fake review count is a common way to lose the feature and to feed an AI a rating you do not have.

Marketplace

Publish These

  • Each listing as its own Product or Service, with its own Offer and a seller Organization.
  • The index as a CollectionPage with an ItemList.

Add When the Page Shows It

  • Brand, Review, and return policy on the listing that actually shows them.

One Product node wrapped around a grid of other people’s listings describes the wrong object. The page of many things is a collection. The page of one thing is that thing. Mixing them is how a marketplace ends up with a single price that belongs to nobody.

School or Training

Publish These

  • Course with name, description, and a provider Organization.
  • A list page as an ItemList of courses. That list is the course-list rich result.
  • EducationalOrganization or a tighter subtype for the school itself.

Add When the Page Shows It

  • CourseInstance with course mode, start date, and location when a specific session is on the page.
  • EducationalOccupationalCredential when you grant one.
  • An offer when tuition is published.
  • MathSolver on a page that actually solves a math problem, and an education question page only when that is the page’s real format.

Google’s documented rich result here is the course list, not a decorative badge on a single sales page. Mark the course the student can enroll in, and the provider who teaches it.

Events

Publish These

  • The closest Event subtype: BusinessEvent, ConferenceEvent, EducationEvent, Festival, MusicEvent, SportsEvent, TheaterEvent, or another child.
  • name, startDate, endDate, eventStatus, eventAttendanceMode, image, and organizer.
  • Place for an in-person event, VirtualLocation for an online one, or both when attendance is mixed.
  • Offer when tickets have a visible price.

Add When the Page Shows It

  • performer, sponsor, and an EventSeries when the event repeats as a named series.

Event rich results need a real time and a real place. An online conference marked as a generic Event with no VirtualLocation looks like a meetup that forgot its address. Cancelled and postponed states belong in eventStatus, not in a sentence in the deck.

Jobs and Recruiting

Publish These

  • JobPosting with title, description, datePosted, hiringOrganization, and validThrough.
  • jobLocation as a Place, or a remote flag, matching what the posting says.

Add When the Page Shows It

  • baseSalary as a MonetaryAmount, employmentType, and directApply when the apply button is on the page.
  • EmployerAggregateRating on the employer page only when the ratings are shown there.

This is the job rich result. A posting that stays in the markup after it expires keeps sending people to a closed role. Set validThrough, and remove or update the node when the role closes.

Recipes

Publish These

  • Recipe with name, image, recipeIngredient, and recipeInstructions.
  • author and datePublished.

Add When the Page Shows It

  • prepTime, cookTime, totalTime, recipeYield, nutrition, and a video.
  • AggregateRating when ratings are on the page.

Recipe is a subtype of HowTo, and it is the one that still gets a rich result, including a recipe carousel. A generic HowTo no longer does. Use Recipe for food, and do not expect a how-to rich result for a marketing tutorial.

Video

Publish These

  • VideoObject with name, description, thumbnailUrl, uploadDate, and either contentUrl or embedUrl.
  • duration in ISO 8601 form.

Add When the Page Shows It

  • Clip nodes for key moments, with a start offset and a name.
  • BroadcastEvent when the video is a live stream.

Video rich results, including key moments, come from these fields. A thumbnail that is not the frame people see, or a duration that does not match the file, is the usual reason the result never appears.

Podcast

Publish These

  • PodcastSeries for the show, with name, description, image, and webFeed if you have one.
  • PodcastEpisode for each episode, partOfSeries pointing at the show.
  • AudioObject as associatedMedia, with a content URL.

Add When the Page Shows It

  • actor or author, duration, and transcript.

Google’s current rich-result gallery does not list a podcast feature. Publish the types anyway. Apps, assistants, and models use them to tell the show from the episode and the episode from a random audio file embedded in a post.

Real Estate

Publish These

  • RealEstateListing as the page type. It is a WebPage subtype, so it replaces a generic WebPage for that URL.
  • The property details that are on the page: address, image, floor size, number of rooms, and the offer or price.

Add When the Page Shows It

  • Accommodation or a tighter residence type when you are describing the dwelling itself, separate from the listing.
  • geo coordinates.

A listing page is the listing, not a blog post that mentions a house. Vacation rentals are a different Google feature, with their own required fields. Do not mark a year-long listing as a vacation rental to chase that result.

Vacation Rental

Publish These

  • VacationRental and the properties in Google’s current vacation-rental guide: name, description, images, address, geo, and identifier.
  • Occupancy and other facts only when the page shows them.

Add When the Page Shows It

  • Rating and reviews that appear on the listing.
  • Amenity details the guest can read.

This rich result is stricter than a generic place page. Copy the current required fields from the guide rather than from an old theme, because incomplete rental markup is dropped rather than half-shown.

Forum or Q&A

Publish These

  • DiscussionForumPosting for a thread of user posts.
  • QAPage when the page is one question, with a Question and an accepted Answer.

Add When the Page Shows It

  • author on each post, commentCount, and interactionStatistic.

These are two different rich results. A forum thread is not a QAPage, and a publisher-written list of questions is not either one. That list is an FAQPage, which no longer earns a general rich result. Use FAQPage only when you want the questions available to AI and you accept that Google will not draw them.

Author or Profile

Publish These

  • ProfilePage whose main entity is one Person or one Organization.
  • name, url, image, description, and sameAs profiles that are actually theirs.

Add When the Page Shows It

  • jobTitle, worksFor, alumniOf, and knowsAbout.

ProfilePage is the current way to say this URL is about this person, which is what the retired author snippet was reaching for. Link articles to that Person @id so the byline and the profile are one entity, not two people who happen to share a name.

Dataset or Research

Publish These

  • Dataset with name, description, creator, and a distribution or download URL.
  • license and keywords when you publish them.

Add When the Page Shows It

  • DataCatalog when the dataset lives in a catalog.
  • temporalCoverage, spatialCoverage, and variableMeasured.

Dataset Search is the rich result. The same fields stop a model from treating a spreadsheet link in a blog post as the study, and the methodology page as a different, unnamed object.

Movies and Music

Publish These

  • Movie with name, image, and director when you are listing films. A list of movies uses an ItemList. That pairing is the movie carousel.
  • MusicGroup, MusicAlbum, and MusicRecording for a catalog of recordings, with tracks linked to the album and the album linked to the artist.

Add When the Page Shows It

  • duration, datePublished, and aggregateRating when shown.

Movie is on Google’s current gallery. A general music rich result is not. The music types are still worth publishing so a track, an album, and an artist stay three objects instead of one blob of titles.

Paywalled Publication

Publish These

  • The article types you would publish anyway.
  • isAccessibleForFree set to false, and a hasPart WebPageElement whose cssSelector matches the paywalled region.

Add When the Page Shows It

  • The subscription offer, if a price is public.

Google uses this to tell a paywall from cloaking. Hide the body from users and also from the markup, and the page looks like spam. Mark the wall, and keep the visible free portion in the HTML Google can fetch.

Health Practice

Publish These

  • The specific local type: Dentist, Physician, MedicalClinic, or a tighter child, with address, hours, and telephone.
  • MedicalWebPage only on pages that are actually medical content, not on the marketing homepage.

Add When the Page Shows It

  • availableService, and a Person for the clinician with their credentials as shown on the page.

Health pages are held to a higher standard. Do not mark a blog post as a MedicalCondition or a treatment claim as a medical entity to chase a result. There is no general medical rich result that rewards that, and the mismatch is exactly the ambiguity structured data is supposed to remove.

Nonprofit

Publish These

  • NGO or the closest Organization subtype, with name, url, logo, address, and sameAs.
  • The same page, website, and breadcrumb layer as any other site.

Add When the Page Shows It

  • DonateAction when a donation flow is on the page.
  • Event for a fundraiser with a date and a place.

An NGO node stops the organization from being classified as a company or as a person who shares its name. DonateAction is useful only when the action is real. A donate button in the footer is not a reason to mark every article as a donation.

Check the Graph Before You Ship It

Run through this list on the template, not only on one example page. A field that is right on the homepage can still be wrong on a category or a product.

  • Keep each @id stable. Changing it when a headline changes splits one entity into two.
  • Write dates as a full ISO 8601 timestamp with a timezone offset.
  • Match the price, the availability, the author, and the address to what a person sees on the page.
  • Add a review node only when the review is on that URL.
  • Skip BreadcrumbList on the homepage, and skip SearchAction unless the target URL searches.
  • Run the Rich Results Test for Google’s display, and the Schema Markup Validator for the vocabulary. Then retest after a template change, because that is when the graph silently drifts.

Start with the organization, the website, the right page type, and breadcrumbs. Add the type for the thing that page is about. Stop when the page has nothing further to declare. Extra types do not make a page more understandable. They give a machine more chances to believe something you did not mean.

Related Articles