Google Schema Markup in 2026: How to Tell What Google Actually Uses

Google schema markup works only for the 25 structured data features listed in its Search Gallery, and only from the version of a page it has indexed. To see what Google actually extracted, check three Search Console views: URL Inspection's indexed result, the rich result status reports and the Performance report. A validator such as the Rich Results Test only tells you what is in your code.

That gap explains a common frustration: the markup passes every validator, the Rich Results Test says the page is eligible, and weeks later the search result still looks like every other blue link. Below is what Google supports in 2026, what it switched off in the last year, and how to find which step failed.

Which schema types does Google support in 2026?

Google supports 25 structured data features for its search results. Schema.org defines hundreds of types, but Google's Search Gallery, last updated 16 October 2026, lists only these. Everything outside that list can still be valid markup, and other search engines or AI systems may read it, but it will not produce a Google rich result.

The 25 features, as listed by Google:

• Content and publishing: Article, Breadcrumb, Carousel, Image metadata, Speakable, Subscription and paywalled content, Video
• Commerce and local: Product, Review snippet, Local business, Organization, Employer aggregate rating, Vacation rental, Software app
• Listings and data: Course list, Dataset, Event, Job posting, Movie, Recipe
• Community and education: Discussion forum, Q&A, Education Q&A, Math solver, Profile page

One caveat on that list: Dataset is still in the gallery, but Google's documentation log says Dataset markup is used by Dataset Search, not by Google Search results. If you mark up a type that is not on the list, Search Console will not report on it. Google's URL Inspection help says so directly: unsupported types "might be present and valid on the page, and can appear in Search results, but won't appear in the tool." That is why a site can have hundreds of valid items and an empty enhancements panel. For copy-ready templates of the types worth adding, see our schema markup examples for 2026.

Which check tells you what Google did with your markup?

Only Search Console shows what Google extracted from the indexed page; validators show what your code says. Each tool answers one question, so pick by the question:

Tool	Question it answers	Scope	What it cannot tell you
Schema Markup Validator (validator.schema.org)	Is this valid Schema.org markup?	One URL or code snippet	Whether Google supports the type or uses it
Rich Results Test	Could this page be eligible for a Google rich result now?	One URL, live fetch	Whether Google has indexed that version or will show the result
URL Inspection, indexed result	What did Google detect the last time it indexed this page?	One URL, with a daily inspection limit per property	Unsupported types, and some enhancements it does not show yet
Rich result status reports	Is a template producing valid or invalid items over time?	One report per supported type, sampled	A full inventory of every marked-up page
Performance report, Search appearance	Is the rich result actually showing and earning clicks?	Pages with impressions	Why a result is not showing
Site crawl	Did markup disappear or break anywhere since last time?	Every crawled page	What Google itself extracted

Our guide to schema markup testing tools covers the two validators in depth, including the order to run them in. To see every JSON-LD block a page carries and which high-value types it is missing entirely, the free schema markup checker gives you that inventory in one pass. This post is about the Search Console half, the part that shows what Google did.

Does Google still show FAQ rich results?

No. FAQ rich results stopped appearing in Google Search for every site on 7 May 2026, and that was the latest of several retirements Google documented between November 2025 and June 2026. Most guides still describe the 2023 FAQ and HowTo restrictions as the latest change. The set of Google schema markup that still does something has shrunk since then:

Date	Change	Source
5 Nov 2025	Google said it was phasing out the practice problem and Dataset structured data types from Google Search results, with practice problem support leaving Search Console reporting and the Rich Results Test from January 2026.	Search Central blog and documentation updates
6 Jan 2026	Practice problem documentation removed; the type "is no longer shown in Google Search results".	Search Central documentation updates
7 May 2026	FAQ rich results stopped appearing in Google Search, for every site.	Deprecation notice added 8 May 2026
15 Jun 2026	FAQ rich result documentation removed.	Search Central documentation updates

The sources are the November 2025 Search Central post and Google's documentation update log. Check that log before you add a type to your templates: it is the one place where retirements are dated. FAQPage is still a valid Schema.org type and can still describe a real Q&A section; our guide to checking FAQ schema now that the rich result is gone covers when it is worth keeping. Whether to delete other retired markup is a separate question, and our piece on what schema markup does for SEO and when it breaks covers it.

How do you see what structured data Google extracted?

Use Search Console, in this order: URL Inspection for one page, the rich result status reports for templates, and the Performance report for results. A validator tells you what is in your code. These three views tell you what Google did with it, and they answer different questions.

1. URL Inspection, indexed version

Inspect the URL and open the enhancements section without running a live test first. Google describes this section as the enhancements "detected by Google on your URL the last time it was indexed." Expand detected items to see each structured data item and any issue attached to it.

Two limits matter. Google says the tool "does not yet show all possible enhancements," and unsupported types will not appear at all. And a live test proves only that the current page could qualify. Google's own answer to "Does a valid result mean that my page will be indexed?" is "No."

2. Rich result status reports

Each supported type you use gets its own report, with a chart of valid and invalid items over time. Valid means no critical issues, so the item can appear as a rich result. Invalid means at least one critical issue blocks it.

The report is a sample, not an inventory. Google says the reports "show a sample of detected items," that totals can be lower than the real count on your site, and that the example table is limited to 1,000 rows. A falling valid count still matters: it usually means a template change broke markup across many pages at once.

3. Performance report, before and after

Google's structured data introduction recommends a before-and-after test on a few pages, recording performance for a few months in the Performance report. Filter to the pages you marked up and compare clicks and CTR for the weeks before deployment against the weeks after. If the Search appearance tab lists your rich result type, those impressions are real. Note that Google aggregates Search appearance data by page, so its totals will not match the property-level chart above it.

Why is valid schema markup not showing a rich result?

Because valid only means eligible. Google's structured data policies are blunt about it: "Using structured data enables a feature to be present, it does not guarantee that it will be present." Beyond that, the usual causes are specific and checkable:

• Missing required properties. Per Google, "Items that are missing required properties are not eligible for rich results." Recommended properties improve the result but do not unlock it.
• Markup that describes hidden content. Google's guideline is "Don't mark up content that is not visible to readers of the page." Ratings, prices or answers that only exist in the JSON-LD are a manual action risk, not a shortcut.
• Markup that only exists after JavaScript runs. Google reads structured data that is in the DOM when it renders the page, so injected JSON-LD works. For Product markup, though, Google warns that dynamically generated markup "can make Shopping crawls less frequent and less reliable." Server-render product data if you can.
• A type Google has retired. FAQ markup can still validate perfectly on schema.org. It has not produced a Google rich result since 7 May 2026.
• The indexed copy is older than your fix. URL Inspection reports what Google saw at the last crawl. Until the indexed version shows the item, the change has not reached Google yet.

How long does a rich result take to appear?

There is no fixed time: wait until URL Inspection's indexed version shows the new markup, then give the Performance report a few weeks of data. Google's help gives no timeline for structured data. Its recrawl guidance says crawling "can take anywhere from a few days to a few weeks," and that requesting a crawl does not guarantee inclusion "instantly or even at all." Judging a rich result before Google has indexed the change measures nothing.

If the indexed version shows the item as valid and weeks pass with no rich result, the markup is not the problem. Look at whether the result type even appears for that query, and whether the page competes for queries where Google shows it.

What Google schema markup checks cannot tell you

Search Console works one property at a time and mostly one page at a time, and that leaves gaps:

• No site-wide inventory. URL Inspection has a daily inspection limit per property, and the status reports are samples. Neither tells you that last Tuesday's theme update stripped the Product block from 400 product pages.
• No view of unsupported types. Organization, WebSite or Service markup that Google does not turn into a rich result never shows up in the enhancement reports, even when it is valid.
• No view outside Google. Bing and AI systems may read the same markup, and nothing in Search Console reports what they did with it.
• No reason for a missing result. A valid item with no rich result gets no explanation; you can only rule causes out.

For site-wide coverage you need a crawl that reads every page's markup and compares it with the previous crawl. CrawlTide's site audit records the JSON-LD on every page it crawls, renders JavaScript when a site needs it, and flags high-value types that disappeared, blocks that stopped parsing and pages that lost their schema since the last crawl.

A practical routine for any site with Google schema markup on more than a few templates:

1. Pick one representative URL per template and confirm its items in URL Inspection's indexed view.
2. Check the rich result status report for each supported type monthly, and investigate any fall in valid items.
3. Remove or stop adding types Google has retired, using the documentation update log as the reference.
4. Crawl the site after every theme, plugin or CMS release, because that is when markup breaks quietly.

Start with step one on your highest-traffic template today. Then run that same page through the free CrawlTide schema markup checker to list every JSON-LD block on it, flag any block that fails to parse, and show which high-value types are missing.