Can Your B2B Site Get a Carousel Rich Result in Google?

Can a B2B website get a carousel rich result in Google?

Almost certainly not. Google's carousel structured data works with only four content types: Course list, Movie, Recipe and Restaurant. If you sell software or services to other businesses, none of those describe your pages. The markup will validate and still never produce a carousel.

This comes up in almost every technical SEO conversation we have. A marketing lead sees a competitor's recipe site showing a row of swipeable cards in Google and asks why their blog index cannot do the same. The honest answer is that the feature was never built for them.

That answer is more useful than it sounds. Once you know which rich results are actually open to a B2B site, you can spend your markup effort where it pays instead of chasing a format Google has closed off.

What is carousel structured data, exactly?

It is a wrapper. Google's documentation says that to be eligible for a host carousel rich result, you add ItemList structured data "in combination with one of the following supported structured data features". The ItemList does not stand alone. It groups items that already carry their own supported markup.

The vocabulary comes from schema.org. ItemList is the list container and ListItem is each entry inside it. Google reads that markup and, when everything lines up, can show several items from one site in a single swipeable row rather than one blue link.

A host carousel is different from the mixed carousels you see for news or top stories. A host carousel pulls every card from one domain. That is why it looks like such a prize. It takes more space than a normal result and every click goes to you.

Which content types can use a Google carousel?

Four, as of September 2026. Google's carousel documentation states that the feature "must be combined with one of the following features: Recipe, Course list, Restaurant, Movie". Recipe and Movie are the two the docs call out specifically for host carousels.

That is the whole list. It is not a starting point that grows quietly. Google's gallery of supported structured data features runs to more than two dozen types, including Article, Breadcrumb, Product, Organization, Video, Job posting, Discussion forum, Profile page and Loyalty program. Carousel eligibility is not extended to any of them.

So a software company can mark up an Article, a Product, a Video and an Organization correctly and still have no path to a carousel. The types that matter to B2B are simply not in the four.

Why does that list leave most B2B sites out?

Because the four types are all consumer categories with a clear, repeatable shape. A recipe has ingredients and a cook time. A movie has a director and a rating. Google can predict what a card should show and can compare cards fairly.

B2B content does not have that shape. A feature page, a case study and a pricing page are not interchangeable cards. There is no agreed set of fields that would let Google put three of them side by side and have the row make sense to a searcher.

We think that is the real reason, and it also tells you something about where to aim. Google builds rich results where the data is standard. The closer your content sits to a standard shape, the more markup can do for you.

How do the two carousel formats work?

Google documents two. The first is a summary page plus detail pages. The summary page "has a short description of each item in the list, and each description points to a separate detail page that is focused entirely on one item". Each ListItem then carries a position and the canonical URL of its detail page.

The second is an all-in-one page. That is "a single page that contains all list information, including full text of each item". Here each ListItem carries the full item object rather than a pointer, and the URL points to an anchor on the same page.

The summary format is the one most sites would use. It matches how a real index page works: a list of cards, each linking to the full piece. The all-in-one format suits a single long page such as a roundup.

What are the required properties?

Few enough to fit in a paragraph. The ItemList needs itemListElement, and Google says you must "define an ItemList that contains at least two ListItem elements". Each ListItem needs an explicit type of ListItem and a position, which Google describes as "a 1-based number". Summary pages add a url. All-in-one pages add an item object with a name and a url.

Two rules catch people out. All items must be the same type: Google's guidance is that "if a list is about recipes, only include Recipe items. Don't mix different types." And every URL in the list must be unique and on the same domain.

The last rule is the one we see broken most. Google expects the markup to be "complete and contains all the items that are listed on the page". Marking up six cards on a page that shows twelve is a mismatch, and a mismatch is the kind of thing that gets a feature switched off for a site.

What should a B2B site mark up instead?

Start with the types that are open to you and actually change how your result looks. Article markup on blog posts and Breadcrumb markup on deep pages are the two we implement on nearly every build. Organization markup on the homepage helps Google connect your name, logo and social profiles. Video markup earns thumbnails where you have real video.

Product markup applies if you sell something with a price and a defined offer. Job posting markup is worth doing the moment you have open roles. If you run courses or certification, Course list markup is genuinely one of the four carousel types, so that path is open.

Our broader approach to this sits in our guide to schema markup for SEO, and the FAQ question specifically is worth reading before you spend a sprint on it, because that feature narrowed sharply for most sites. We covered that in whether FAQ schema is still worth it.

Does structured data guarantee a rich result?

No, and Google is direct about it. The documentation says including all required properties makes an object "eligible for appearance in Google Search with enhanced display". Eligible is not the same as chosen. Google also notes that "the actual appearance in search results might be different".

That gap matters when you plan work. Markup is a prerequisite, not a lever you pull for traffic. We treat it as table stakes: get it correct, keep it correct, then spend the rest of the time on the content and the page itself.

There is also a limit on what you may describe. Google's guidance is blunt: "don't add structured data about information that is not visible to the user, even if the information is accurate". Marking up a rating or a price that a visitor cannot see on the page is a policy problem, not a clever trick.

How do you test and monitor structured data?

Two tools, in order. The Rich Results Test tells you whether Google can read your markup on a single URL and which feature it maps to. Google recommends JSON-LD for this work because it is "the easiest solution for website owners to implement and maintain at scale", and it keeps the markup separate from your HTML so a content edit cannot break it.

Then Search Console. The enhancement reports there show errors and warnings across your whole site, which is where you catch the case that only appears on old posts or on one CMS template. This is the part teams skip, and it is the part that finds real problems.

Microdata and RDFa are the other two formats Google supports. Both work. Both also live inside your markup, so we avoid them on client sites where marketers edit pages. One stray change in a rich text field and the data is gone.

What happens to markup as AI answers take more of the page?

Structured data becomes more about being understood than about being decorated. A carousel is a visual format on a results page. An AI answer engine does not draw carousels, but it does benefit from clean, machine-readable facts about what a page is and who published it.

That is why we keep recommending Article, Organization, Breadcrumb and Video markup even to teams who only care about AI visibility. The markup states plainly what a human editor would have to infer. Clear tables and clear structure do similar work inside the body, which we wrote about in how comparison tables earn AI citations.

If you want a straight read on which structured data is worth implementing on your site and which is a distraction, we are happy to walk through it. Send us the URL at phoenix.studio and we will tell you what we would do first.