Which listing pages qualify for Google's structured data carousels beta?

The Citead team, updated

In short. Google's beta supports ItemList summary pages for LocalBusiness, Product, and Event entities in documented regions.

Definition: Google's structured data carousel beta is a host carousel rich result: a horizontally scrollable list of entities from a given site. A listing page can qualify when it combines ItemList structured data with a supported LocalBusiness subtype, Product, or Event, and follows Google's summary page and detail page requirements.

Key facts

  • Google supports LocalBusiness and its subtypes, Product, and Event as the list item types for this beta. Google's carousel documentation gives Restaurant, Hotel, and VacationRental as LocalBusiness examples.
  • The regional Search overview describes structured data carousels as list-like results from a given site and lists coverage in the EEA, South Africa, and Türkiye. Google's regional overview provides the query categories for each region.
  • An aggregator unit is for approved Vertical Search Services, such as online travel agencies, comparison shopping services, metasearch engines, and directories. Google's aggregator unit documentation says eligible aggregators must provide the necessary data and meet quality standards.
  • A supplier unit is for direct providers such as individual hotels, airlines, local businesses, and service providers. Google's supplier unit documentation requires the website to serve users in the EEA and the business to be a direct provider.

Which content types are supported?

Google's carousel documentation requires ItemList in combination with at least one supported item type. The supported choices are LocalBusiness and its subtypes, Product, and Event. Google's examples of LocalBusiness subtypes are Restaurant, Hotel, and VacationRental. A generic type is allowed, but the recommended properties for a subtype require that respective type. For example, Google's documentation associates amenityFeature with LodgingBusiness.

The result is a host carousel. Google describes it as a list-like result that lets people scroll horizontally through more entities from one site. The page is therefore a list of entities that the site itself describes, rather than a feed assembled from several providers.

What must the listing page contain?

The marked-up page must be a summary or category page. Google requires information about at least three entities, links from that page to separate detail pages, and the detail page URLs in the ItemList markup. The URLs must be unique and use the same domain, or a subdomain or superdomain, as the summary page. Anchor links within the summary page are not supported.

The required ItemList structure uses itemListElement, an individual item object, and a position. Each item also needs the common image, name, and url properties. Google says image URLs must be crawlable and indexable, and the url must be the canonical URL of the standalone detail page. For a paginated category, add an ItemList to each subsequent page with the entities shown on that page. For infinite scroll, mark up the entities initially loaded in the viewport.

{
  "@context": "https://schema.org",
  "@type": "ItemList",
  "itemListElement": [
    {
      "@type": "ListItem",
      "position": 1,
      "item": {
        "@type": "Restaurant",
        "name": "Trattoria Luigi",
        "url": "https://www.example.com/trattoria-luigi"
      }
    }
  ]
}

Where is the beta available?

As of September 2026, Google's carousel documentation says the feature is in beta and available on desktop and mobile in EEA countries, Türkiye, and South Africa. In the EEA, Google lists hotels, vacation rentals, ground transportation, flights, local businesses, things to do, and products. In Türkiye, it lists hotels, vacation rentals, and local businesses. In South Africa, it lists hotels, vacation rentals, things to do, flights, products, food delivery, car hire, and bus booking.

The regional Search overview presents the same host carousel as a structured-data feature. Its regional table lists vacation rentals among the EEA and South Africa query categories, and lists local businesses among the Türkiye categories. Google warns that beta requirements or guidelines may change as the feature develops.

Do aggregator and supplier pages have extra requirements?

They have requirements for separate Search units. Google's aggregator unit documentation describes the aggregator unit as a multi-provider feature for Vertical Search Services. An eligible aggregator must serve relevant query content, provide data through direct feed integrations or real-time APIs where applicable, and comply with Google's Search content policies. The page gives hotels, flights, long-distance trains, products, and local businesses as query areas for the aggregator unit.

The supplier unit documentation describes a unit for direct providers that appears alongside the aggregator unit and only appears when that unit appears. Eligibility requires a website serving users in the EEA and a direct-provider business. Google says additional data beyond web crawling is not required for the supplier unit, although data feeds can enhance supplier results.

FAQ

Does a list page need markup on every detail page?

No. Google's carousel documentation says the required markup goes on the summary page. The summary page still needs the canonical URLs of the standalone detail pages in its ItemList.

Can a page use more than one supported item type?

Yes. Google says a summary page can mix entity types when the scenario calls for it, such as hotels and vacation rentals or local events and local businesses.

Is an aggregator account required for this beta?

The beta documentation describes ItemList structured data on a summary or category page. Google's separate aggregator unit documentation sets VSS approval and data requirements for that other unit.

Sources

  1. Google Search Central, "Structured data carousels (beta)", 2026-09-11
  2. Google Search Central, "Regional differences in Search experience", 2026-09-18
  3. Google Search Central, "Aggregator unit in Google Search", 2026-09-18
  4. Google Search Central, "Supplier unit in Google Search", 2026-09-18

Check how a page reads to answer engines. Open the GEO score analyzer

Test a page and see what to fix first

The analysis usually takes less than 10 seconds and needs no account.

400,000+ pages scored in the public benchmark