Short answer
Schema markup is a short block of code, usually JSON-LD, that tells a search engine in plain fields what a page is: a recipe with a cooking time of 40 minutes and a rating of 4.9 from 268 readers, a product with a price, a news article with an author and a date. It makes the page eligible for a rich result. It does not raise rankings.
On 15 November 2026 I checked what 100 big US sites actually put in their pages. 24 of the 57 homepages I could read still ship markup for a Google feature that was switched off on 21 November 2024. On the pages that earn money, the same sites get it right every time I looked. Below are the numbers, the dead types with dates, and a five-minute check for your own site.
What schema markup is
The vocabulary comes from schema.org, which Google, Microsoft and Yahoo started in 2011; Yandex joined the same year. There are three ways to write it on a page:
| Format | How it sits in the page | What I saw on 57 big homepages |
|---|---|---|
| JSON-LD | A separate <script type="application/ld+json"> block | 38 homepages (67%) |
| Microdata | itemscope and itemprop attributes inside the HTML | 4 homepages used it alone |
| RDFa | typeof and property attributes inside the HTML | none used it alone |
Google recommends JSON-LD because it does not have to be woven into the HTML. Here is a real example, trimmed, from a Bon Appétit recipe page on 15 November 2026:
{
"@type": "Recipe",
"name": "Curried Lentil Soup With Coconut and Tomatoes",
"totalTime": "40 minutes",
"recipeYield": "4 servings",
"aggregateRating": { "@type": "AggregateRating", "ratingValue": 4.9, "ratingCount": 268 }
}
Every field points at something a visitor sees on that page: the title, 40 minutes, 4 servings, and 4.9 stars from 268 ratings under the headline. That is the idea in one sentence: markup does not add information, it labels information that is already there.
What markup does and does not do
Markup makes a page eligible for a rich result: stars, a price, a cooking time, a video thumbnail. Google decides whether to show it, and the gallery page says plainly that the actual appearance may differ. Markup is not a ranking signal: when Google announced the retirement of seven types in June 2025 it wrote that the change would not affect how pages are ranked.
Why bother, then? Because a richer result can get more clicks. Google's own case studies, on the same introduction page, cite 25% higher click-through on Rotten Tomatoes pages with markup and 82% higher click-through for Nestlé pages that showed as rich results. These are Google's and the companies' numbers, without years or an independent check. My own experience with review stars is more sober, and it is further down.
What I found on 100 big US sites
The method, so you can repeat it: a plain GET request to the homepage of 100 big US sites in 8 categories (shops, news, recipes, health and reference, travel, local services and jobs, tech, media), with a Chrome user agent and en-US, then up to 2 inner pages per site picked from the homepage links (a product, a recipe, an article where possible). No JavaScript rendering and no attempt to get past bot protection. 179 pages in total, all dated 15 November 2026. The script and the full data are in the files from the video.
The first finding has nothing to do with schema: 43 of the 100 homepages did not answer a plain request (403, 429, 202 or a connection error). Local service and job sites (8 of 10) and travel sites (7 of 10) close the door first; shops blocked 10 of 20. Everything below is about the 57 that answered.
- 74% of homepages had some markup, 67% used JSON-LD, and not one JSON-LD block failed to parse. Big sites generate markup from templates, so syntax is not their problem.
- 15 homepages had no markup at all, among them Wikipedia, YouTube, Reddit, GitHub and Netflix. A brand homepage does not need stars: nobody searches for Reddit and needs a rating in the snippet.
- Inner pages: 87% had markup (67 of 77). That is where rich results earn money.
The types Google no longer shows
Here is where advice ages fastest. Five changes in three years, each confirmed on Google's own pages, which I read on 15 November 2026:
The sitelinks search box. It needed a WebSite block with potentialAction of type SearchAction on the homepage. Google removed the box on 21 November 2024 and wrote that unsupported markup "won't cause issues in Search". In my crawl, 24 of 57 homepages still ship it: Walmart, Apple, Nike, Sephora, The New York Times, CNN, Pinterest, and 7 of the 10 recipe sites in the sample. That is 63% of the homepages that use JSON-LD at all. It does no harm, and other engines may still read it. But if a guide written in 2026 tells you to add it for the search box, that guide is out of date.
FAQ rich results. From August 2023 they appeared only for government and health sites, and on 7 May 2026 Google stopped showing them altogether. Three sites in my sample still carry FAQPage markup: a travel site, a software company and a health publisher. Fewer than with the search box, so somebody did clean up. I had to as well: two cards of my own audit checklist still said that FAQ works for health sites and that the search box is worth adding. I corrected them while preparing this article.
June 2025 and January 2026. Google announced seven types for retirement; six went: course info, claim review, estimated salary, learning video, special announcement and vehicle listing. Book actions got a reprieve on 5 November 2025, because a Google feature still uses that markup. Practice problems followed on 6 January 2026, according to the Search Central changelog. None of these changes moved rankings, by Google's statement; they only changed what a result can look like.
Where big sites get it right
The Google gallery listed 25 features on 15 November 2026, among them Article, Breadcrumb, Product, Recipe, Review snippet, Video, Event, Job posting and Local business. On the pages built for those features, the big sites in my sample did not miss:
| Page type | What I checked | What the markup had |
|---|---|---|
| Recipe | 5 recipe pages on Bon Appétit, Taste of Home, Epicurious | All 5: Recipe with AggregateRating; the 11 category pages next to them had only BreadcrumbList and ItemList |
| Product | 2 product pages of a big beauty retailer | Product, Offer, AggregateRating, Review, BreadcrumbList on both |
| News article | 20 article pages picked from the homepages of 13 news sites | NewsArticle on 18 of 20; 12 of the 13 sites used it |
| Paywalled article | The New York Times, The Guardian, Los Angeles Times | Product plus isAccessibleForFree: the markup for subscription content, not a product |
The pattern is simple: the markup matches the page type. One page, one main thing, marked once and fully. On smaller sites in several languages I keep seeing the opposite: the same Organization and FAQ block pasted on every page, whatever the page is about.
Now the stars. Every client wants them. On client sites I have watched for about five years, stars in the snippet never showed a clear link with click-through or with position, and Google shows them far less often now, for all sites. Clients like seeing them; the data does not care. One warning: rating markup that does not match real reviews on the page is the one thing in this article that Google's structured data policies treat as spam, with a manual action possible. I have not seen one for ratings in five years, but that makes it a bet, not a free win.
What to put on your own site
Start from page types, not from the list of a plugin:
| Page | Markup | What it can earn in Google |
|---|---|---|
| Homepage | Organization: name, logo, profiles (sameAs) | Helps Google connect your brand; no rich result of its own |
| Every inner page | BreadcrumbList | The breadcrumb trail instead of a raw URL in the snippet |
| Product page | Product with price, availability and real reviews | Price, stock and rating in the snippet |
| Article | Article or NewsArticle with author and dates | Better article features; dates read correctly |
| Recipe, event, job, video | Their own types | Cooking time, dates, salary, thumbnail |
| Local business | LocalBusiness with the address and hours of your Google profile | Consistent business details |
| FAQ, HowTo, search box | Nothing new | No rich result in Google anymore; keep valid existing markup if another engine uses it |
One rule above all: mark up only what a visitor can see on the page. The cheat sheet below the article has this table with dates and links to each Google page.
Check your own site in five minutes
- Open Google's Rich Results Test and paste your most valuable page. Not the homepage: the page that earns money.
- Look at what it detects. "No items detected" on a product or recipe page is your biggest win.
- Open the page source, search for
ld+jsonand read the@typevalues. Anything from the dead list above earns nothing in Google. - Compare the numbers in the markup with the page: price, rating, review count. If they do not match, fix that first.
For more than a handful of pages, the audit script runs the same checks on a list of URLs and flags dead types, and the review prompt has an AI agent compare the markup with the visible page. The dataset has every page of my crawl, so you can compare your numbers with the big sites.
Who this is not for, and the limits
If your site has no product, recipe, article or event pages, a brand homepage and a few service pages, markup will not change much in Google beyond the breadcrumbs and Organization. And if your platform already outputs correct markup, there is nothing to add for the sake of it.
The limits of my numbers:
- No JavaScript. Markup that a script adds after load was invisible to my crawler. Google says it can read JavaScript-generated structured data, so treat my percentages as a floor.
- 43 sites blocked me. The blocked share is highest among local service and job sites (8 of 10) and travel sites (7 of 10), so those categories are underrepresented.
- Inner pages were picked from homepage links, 1 or 2 per site. They show what a page type looks like, not a census of each site.
- One day. Everything is dated 15 November 2026, and Google has changed the list four times in two years.
Markup is the last layer of the technical foundation, after rendering, server responses and indexing. If those are not sorted out, start with technical SEO optimization. And if you want your markup checked together with the rest, I do it as part of a technical SEO audit.
