Every Schema Type Google Supports in 2026 (And Everything It Deprecated)

Google has retired eleven structured data features since 2023. If you implemented schema a few years ago and haven't revisited it, some of what you built no longer produces anything visible in Search, and a great deal of the advice still circulating online references features that no longer exist.

This is the complete current picture, verified directly against Google Search Central's structured data gallery rather than secondhand summaries. Every supported type below appears in Google's own documentation as of its June 15, 2026 update.

Every type Google currently supports

Google's structured data gallery lists 25 features. Grouped by purpose:

Commerce

Product: Information about a product, including price, availability, and review ratings.

Product has expanded into a family of shopping features, each with its own documentation: Product snippet (review stars, ratings, price, availability), Merchant listing (advanced commercial cards), Variants (size, colour, and configuration handling), Loyalty program, Merchant return policy, and Merchant shipping policy. If you run an online store, this is the highest-value markup available to you.

Vacation rental: Property name, description, images, location, rating, and reviews.

Business and entity

Local business: Business details in the Google knowledge panel, including opening hours, ratings, directions, and actions to book appointments or order items.

Organization: Logo, legal name, address, contact information, and company identifiers, which can appear in knowledge panels and other visual elements.

Event: Concerts, festivals, and other scheduled happenings, showing date, location, and ticket information.

Profile page: A page focused on a single person or organization affiliated with the site.

Breadcrumb: Navigation indicating the page's position in the site hierarchy.

Content and media

Article: News, sports, or blog articles displayed with the title and larger-than-thumbnail images.

Video: Video results with playback, video segments, and live-stream support.

Movie: The movie carousel, for pages listing films.

Image metadata: Creator, licensing, and credit information shown in Google Images.

Speakable: Marks news content for text-to-speech on Google Assistant devices.

Subscription and paywalled content: Distinguishes paywalled content from cloaking, which violates Google's spam policies.

Carousel: A sequential list or gallery from a single site. It can't be used alone; it must be combined with Recipe, Course list, Restaurant, or Movie.

Community and Q&A

Discussion forum: User-generated content followed by threaded or non-threaded discussion.

Q&A: Pages containing one question followed by its answers.

Education Q&A: Education-related questions and answers that help students discover flashcards.

Q&A and Education Q&A are alive and well. They're distinct from FAQPage, which is not. More on that below.

Jobs

Job posting: Feeds the Google for Jobs experience with your logo, reviews, ratings, and job details.

Employer aggregate rating: An evaluation of a hiring organization shown in the job search experience.

Food, education, and data

Recipe: Recipes as an individual rich result or part of a host carousel.

Course list: A list of educational courses, including course title, provider, and short description. It remains in Google's supported gallery today.

Math solver: Math problem types and step-by-step walkthroughs.

Dataset: Large datasets surfaced through Google Dataset Search.

Cross-cutting

Review snippet: A review excerpt or rating average. It isn't standalone: it applies to Book, Recipe, Movie, Product, Software App, and Local business.

Software app: Rating information, description, and a link to the app.

Which of these actually matter for you

Twenty-five features is more than any single site needs, and the temptation is to implement broadly. Resist it. Most sites are well served by three to six types, chosen for what the site actually is.

The high-impact, broadly-applicable ones (the types worth almost every site's attention) are Organization for identity on every site, Breadcrumb for navigation on nearly every multi-level site, and then whichever content type matches your core pages: Product for stores, Article for publishers, LocalBusiness for physical businesses, Recipe for food sites, Event for venues and organizers. Review snippet layers on where you have genuine reviews.

The rest are situational. Job posting matters only if you post jobs. Dataset only if you publish datasets. Math solver, Vacation rental, Movie, Speakable: each serves a specific kind of site and is irrelevant to everyone else. There's no benefit, and some cost in complexity, to implementing a type that doesn't describe your content.

So read the full list below as a menu to select from, not a checklist to complete. The goal is complete, accurate markup on the types that genuinely describe your pages, not the maximum number of types.

Everything Google has deprecated

The June 2025 batch was announced by Google Search Product Manager Henry Hsu as a simplification effort: the features weren't commonly used and Google's analysis found they weren't providing significant additional value to users, with an explicit statement that rankings weren't affected. Documentation for those types was removed by September 2025.

Three details worth flagging. Sources differ on whether Practice Problems was retired in November 2025 or January 2026; either way it's gone. Google's documentation sidebar still contains pages for types like Fact check even though they don't appear in the supported features gallery, leftover documentation, not a sign of support. And Book Actions is a genuine exception in this table: unlike the other six June 2025 retirements, Google's own current documentation for it carries no deprecation notice and describes it as active, just limited to book providers with a wide enough catalogue to qualify. It's absent from the main 25-feature gallery, so it produces nothing for a typical site, but it isn't a hard deprecation the way the rest of the batch is.

The Course nuance most articles get wrong

Course Info was retired in June 2025. Course list was not.

These are different features. Course Info produced a detail-heavy display with price, duration, and structural information about an individual course. Course list produces a list of courses, with course title, provider, and short description, and it remains in Google's supported gallery today, and can be combined with Carousel.

So if you sell online courses, you haven't lost rich result eligibility. You've lost one presentation format and kept another. Plenty of published advice states flatly that "Course schema was deprecated," which is wrong, and following it will cost course creators visibility they could still be earning.

How to check what you currently have

Before implementing anything new, find out what your site already emits, you may be running retired types, duplicate blocks, or missing obvious wins.

View source on representative pages: a product or article page, a category page, the homepage. Search the raw HTML for application/ld+json and read the blocks. Do this in actual view-source, not the element inspector, since the inspector shows the post-JavaScript DOM rather than what a crawler first receives.

List the types you're emitting and check each against the supported gallery. Anything not on the current list, HowTo, FAQPage, a retired type, is producing no rich result, though it's not harming you either.

Check for duplicates. A theme, an SEO plugin, and a third-party tool can each emit overlapping markup. Two Organization blocks or two Product blocks on one page is a real problem worth resolving.

Run key templates through the Rich Results Test. It confirms eligibility for supported types and flags errors. Test one page per template, since a template fix or break applies to every page it renders.

Watch Search Console's Enhancement reports over time. They show how Google actually parsed your markup across the whole site after crawling, the definitive record, and where a template-level problem surfaces at scale.

This audit takes under an hour on most sites and tends to surface at least one of: a retired type you can stop worrying about, a duplicate to resolve, or a supported high-value type you're simply not using yet. Our documentation covers implementation details for any type you find you're missing.

A note on the sub-features

One reason "how many types does Google support" gets muddled: several supported features contain multiple sub-features, so the practical count is higher than a simple list suggests.

Product is the clearest example. Beyond the base Product result, it spans product snippets, merchant listings, variants, loyalty programs, merchant return policy, and merchant shipping policy, each documented separately with its own requirements. A store implementing "Product schema" is really choosing among a family of related enhancements, not toggling one feature.

Review snippet is another that isn't standalone: it attaches to Book, Recipe, Movie, Product, Software App, and Local business rather than existing on its own. Carousel similarly must combine with a qualifying parent type, Recipe, Course list, Restaurant, or Movie, rather than standing alone.

The practical implication: don't treat the supported list as a flat menu of independent options. Some entries are foundations that unlock several enhancements, and some are modifiers that only work attached to a parent. Reading the documentation for the specific feature you want, rather than assuming one block does everything, is what separates a complete implementation from a partial one.

FAQPage is gone, but Q&A isn't

Another distinction worth being precise about, because they're constantly conflated.

FAQPage: a page where the site publishes questions and its own answers, lost rich results on May 7, 2026 for every site, including the authoritative government and health sites that had retained eligibility since 2023.

Q&A: a page where users submit multiple answers to a question, remains supported. So do Education Q&A and Discussion forum.

The FAQPage markup pattern hasn't changed and isn't deprecated at schema.org. Only Google's willingness to render it as a visible enhancement ended. Full details in Is FAQ Schema Dead?.

What "deprecated" actually means

This causes more confusion than anything else in structured data, so precisely:

The schema.org vocabulary is unchanged. HowTo, FAQPage, and SpecialAnnouncement remain valid types. Validators will still consider your markup syntactically correct.

There's no penalty. Google has stated repeatedly that these changes don't affect rankings. They're presentation changes, not algorithmic ones, and Google's systems safely ignore unsupported structured data.

You simply aren't eligible for that visual treatment. That's the entire consequence.

Reporting disappears alongside it. Search Console retires appearance filters, rich result reports, and Rich Results Test support for retired features. If your QA process used the Rich Results Test as a "will this trigger" gate, that check no longer exists for those types.

Don't scrub old markup. Removing deprecated types gains nothing, costs time, and forfeits whatever value other systems derive from it. Bing and other engines process markup on their own terms, and AI crawlers parse structured data when building answers.

What to implement, by site type

The supported list is only useful once it's mapped to your actual type of site. Here's where the return is for common types of site, using only currently-supported features.

Online store. Product is your highest-value markup: it drives price, availability, and review stars, and its merchant-listing extensions add shipping and returns. Pair it with Organization for brand identity, Breadcrumb for category paths, and Review snippet where you display genuine reviews. This is the densest cluster of supported, high-impact types anywhere.

Local business. LocalBusiness (using the most specific subtype) plus Organization at the brand level. Breadcrumb on deeper pages. If you take bookings or list services, those extend the picture. Your structured data reinforces the same facts as your Google Business Profile, so keep them consistent.

Publisher or blog. Article or BlogPosting with real author and publisher entities, Breadcrumb, and Video where you embed media. If you run genuine community Q&A, that's QAPage or Discussion Forum, both supported, both frequently missed. Note that FAQPage no longer earns a result, so don't build your strategy around it.

Recipe or food site. Recipe is one of the most visually rewarded supported types: cards, cook times, ratings. Get the ISO 8601 timings and step structure right, and pair with Article and Video.

SaaS or software. Software app is supported and carries rating and price. Add Organization with a dense sameAs network, since software discovery leans heavily on third-party profiles.

Course provider. Course list still produces a rich result (Course Info, the per-course detail display, was the part retired). Model your catalogue as a list.

Job board or employer. Job posting feeds Google for Jobs, and Employer aggregate rating adds the organization evaluation. Both are supported, and it's a type few WordPress schema guides cover well.

The through-line: every one of these clusters is built from types that survived the retirements. None of them depends on a feature Google has removed, which is exactly the point: build on the durable core.

What this means for your strategy

The pattern is directional. Each retirement removes a SERP feature that gave third-party content extra display space, while Google's own AI Overview gains ground. Types describing fundamental entities, products, businesses, organizations, articles, have survived every round. Types tied to narrow vertical presentations have not. That's a reasonable guide to where implementation effort is safe.

Structured data was never a ranking factor. Google has confirmed this consistently, including throughout these retirements. What markup does is remove ambiguity: it states explicitly that this string is a price, this is an author, this is a cook time. That function is untouched by any deprecation.

Be careful with AI claims. Google now publishes specific guidance on optimizing for generative AI, and it's worth reading directly rather than relying on secondhand summaries. Structured data helps machines understand your content, but anyone telling you schema guarantees AI citation is overselling.

Verify before trusting any list, including this one. The supported set has narrowed four times since 2023, and Google's documentation update log shows changes land without a single, consistent announcement channel. Google's structured data gallery is the authoritative source. Bookmark it and check before major implementation work. Our schema types directory covers implementation for the types that apply to your site.

AI Schema Gen generates and validates structured data across 530+ schema types, so you can implement what's currently supported without hand-writing JSON-LD. Start free or see plans and pricing.