# Structured data carousels (beta) Google uses [structured data](https://developers.google.com/search/docs/appearance/structured-data/intro-structured-data) to understand the content on the page and show that content in a richer appearance in search results, which is called a *rich result*. This guide focuses on a [new carousel rich result that's in beta](https://developers.google.com/search/blog/2024/02/search-experiences-in-eea), which is a list-like rich result that people can scroll horizontally to see more entities from a given site (also known as a host carousel). Each tile in the carousel may have information from your site about the price, rating, and images for entities on the page. To be eligible for this beta rich result, add `ItemList` structured data in combination with at least one one of the following supported structured data items: - [`LocalBusiness`](https://developers.google.com/search/docs/appearance/structured-data/carousels-beta#localbusiness) and its subtypes, for example: - [`Restaurant`](https://schema.org/Restaurant) - [`Hotel`](https://schema.org/Hotel) - [`VacationRental`](https://schema.org/VacationRental) - [`Product`](https://developers.google.com/search/docs/appearance/structured-data/carousels-beta#product) - [`Event`](https://developers.google.com/search/docs/appearance/structured-data/carousels-beta#event) Here's how carousels can look in Google Search when you add `ItemList` markup in combination with a supported content type: ![New carousel rich result](https://developers.google.com/static/search/blog/images/new-carousel-rich-result.png) ## Feature availability This feature is in beta and you may see changes in requirements or guidelines, as we develop this feature. This feature is also only available in [European Economic Area](https://ec.europa.eu/eurostat/statistics-explained/index.php?title=Glossary:European_Economic_Area_(EEA)) (EEA) countries, Türkiye, and South Africa, on both desktop and mobile devices. In EEA countries, this experience is available for queries related to hotels, vacation rentals, ground transportation, flights, local businesses, things to do (events, tours, and activities), and products. In Türkiye, this experience is only available for queries related to hotels, vacation rentals, and local businesses. In South Africa, this experience is available for queries related to hotels, vacation rentals, things to do (events, tours, and activities), flights, products, food delivery, car hire, and bus booking. If your business serves users in the EEA or Türkiye, fill out the applicable form: - For ground transportation, hotel, vacation rental, local business, and things to do (for example, events, tours, and activities) queries, use this [Google Search aggregator features interest form](https://support.google.com/websearch/contact/search_aggregator_features). - For flight features, use this [flight queries interest form](https://support.google.com/travel/contact/flight_queries_interest). - For products queries in [CSS Program countries](https://support.google.com/css-center/answer/7524491#Supported_countries), get started with the [Comparison Shopping Services (CSS) program](https://support.google.com/css-center/answer/7524491). If your business is based in South Africa, fill out the [Google Search South African Badging and Refinement Chips Interest Form](https://docs.google.com/forms/d/e/1FAIpQLSeio2rTpaGNFohJQNKRDLQENyfK5avJFGJSx1nguoRwqsocIQ/viewform). ## Add structured data Structured data is a standardized format for providing information about a page and classifying the page content. If you're new to structured data, you can learn more about [how structured data works](https://developers.google.com/search/docs/appearance/structured-data/intro-structured-data). Here's an overview of how to add structured data to your site. 1. Pick a single summary page that contains some information about every entity in the list. For example, a category page that lists the "Top hotels in Paris", with links out to specific detail pages on your site for more information about each hotel. You can mix and match different types of entities (for example, hotels, restaurants), if needed for your scenario. For example, if you have a "Things to do in Switzerland" article that lists both local events and local businesses. 2. Add the [required properties](https://developers.google.com/search/docs/appearance/structured-data/carousels-beta#structured-data-type-definitions) to that summary page. You don't need to add markup to the detail pages in order to be eligible for this beta feature. Based on the format you're using, learn where to [insert structured data on the page](https://developers.google.com/search/docs/appearance/structured-data/intro-structured-data#format-placement). > [!NOTE] > **Using a CMS?** It may be easier to use a plugin that's integrated into your CMS. > **Using JavaScript?** Learn how to [generate structured data with JavaScript](https://developers.google.com/search/docs/appearance/structured-data/generate-structured-data-with-javascript). 3. Add the required and recommended properties for the specific content type that the carousel is about: - [`LocalBusiness`](https://developers.google.com/search/docs/appearance/structured-data/carousels-beta#localbusiness) and its subtypes, for example: - [`Restaurant`](https://schema.org/Restaurant) - [`Hotel`](https://schema.org/Hotel) - [`VacationRental`](https://schema.org/VacationRental) - [`Product`](https://developers.google.com/search/docs/appearance/structured-data/carousels-beta#product) - [`Event`](https://developers.google.com/search/docs/appearance/structured-data/carousels-beta#event) Depending on your scenario, you may choose the best type to use. For example, if you have a list of hotels and vacation rentals on your page, use both `Hotel` and `VacationRental` types. While it's ideal to use the type that's closest to your scenario, you can choose to use a more generic type (for example, `LocalBusiness`). 4. Follow the [guidelines](https://developers.google.com/search/docs/appearance/structured-data/carousels-beta#guidelines). 5. Validate your code using the [Rich Results Test](https://search.google.com/test/rich-results). 6. Deploy a few pages that include your structured data and use the [URL Inspection tool](https://support.google.com/webmasters/answer/9012289) to test how Google sees the page. Be sure that your page is accessible to Google and not blocked by a robots.txt file, the `noindex` tag, or login requirements. If the page looks okay, you can [ask Google to recrawl your URLs](https://developers.google.com/search/docs/crawling-indexing/ask-google-to-recrawl). > [!NOTE] > **Note**: Allow time for re-crawling and re-indexing. Remember that it may take several days after publishing a page for Google to find and crawl it. 7. To keep Google informed of future changes, we recommend that you [submit a sitemap](https://developers.google.com/search/docs/crawling-indexing/sitemaps/build-sitemap). You can automate this with the [Search Console Sitemap API](https://developers.google.com/webmaster-tools/search-console-api-original/v3/sitemaps). ## Guidelines For your page to be eligible for carousel rich results (beta), you must follow the [Search Essentials](https://developers.google.com/search/docs/essentials) and [general structured data guidelines](https://developers.google.com/search/docs/guides/sd-policies). In addition, the following guidelines apply to carousel rich results (beta): - Use of generic types is allowed. However, to use recommended properties, you must use the respective types. For example, to use `amenityFeature`, use the `LodgingBusiness` type. - Use of additional or extra fields is allowed, but may not appear in the rich result. - Your site must have a summary page and multiple detail pages. Currently, this feature isn't designed to support other scenarios, such as an all-in-one page where the "details" are anchor points within the same page. - The markup must be on a summary or category page, which is a list-like page that contains information about at least three entities and then links out to other pages on your site for more information on those entities. While you don't need to add markup to the detail pages, you must include the detail page URLs in your summary page's markup. - Mark up all items that are on the summary or category page. For paginated categories, add an `ItemList` to each subsequent page and include the entities that are listed on that page. For infinite scroll, focus on marking up the entities that are initially loaded in the viewport. ## Examples The following is a high level structure of the carousel. The order specified in the markup is the order that will be used to order the tiles in the carousel rich result. \ \ \Top 5 Restaurants in Italy\ \ ``` ## Structured data type definitions You must include the required properties for your content to be eligible for display as a rich result. You can also include the recommended properties to add more information about your content, which could provide a better user experience. ### `ItemList` `ItemList` is the container item that holds all elements in the list. All URLs of the elements in the list must point to different pages on the same domain. The full definition of `ItemList` is available at [schema.org/ItemList](https://schema.org/ItemList). | Required properties || |---|---| | `itemListElement` | [`ListItem`](https://schema.org/ListItem) List of items. To specify a list, define an `ItemList` that contains at least three `itemListElement.item` elements. | | `itemListElement.item` | Subtype of `LocalBusiness`, `Product`, or `Event` An individual item in a list. Populate this object with: - The [general properties](https://developers.google.com/search/docs/appearance/structured-data/carousels-beta#common) that all carousels must have (`image`, `url`, `name`) - Any other properties required for this data type, as described for your content type: - [`LocalBusiness` and its subtypes](https://developers.google.com/search/docs/appearance/structured-data/carousels-beta#localbusiness) - [`Product`](https://developers.google.com/search/docs/appearance/structured-data/carousels-beta#product) - [`Event`](https://developers.google.com/search/docs/appearance/structured-data/carousels-beta#event) **Example** : For a hotel, provide `priceRange` and `amenityFeature` properties. | | `itemListElement.position` | [`Integer`](https://schema.org/Integer) The item's position in the carousel. This is a 1-based number. | ### Common list item properties (`LocalBusiness`, `Product,` or `Event`) All of the carousel item types have the following properties in common. | Required properties || |---|---| | `image` | Repeated `https://schema.org/URL` or `https://schema.org/ImageObject` One or more images of the entity or item (for example, an image of the hotel). Don't include logos in this image property. Additional image guidelines: - Image URLs must be crawlable and indexable. To check if Google can access your URLs, use the [URL Inspection tool](https://support.google.com/webmasters/answer/9012289). - Images must represent the marked up content. - Images must be in a file format that's [supported by Google Images](https://developers.google.com/search/docs/appearance/google-images#supported-image-formats). - For best results, we recommend providing multiple high-resolution images (minimum of 50K pixels when multiplying width and height) with the following aspect ratios: 16x9, 4x3, and 1x1. For example: ``` "image": [ "https://example.com/photos/1x1/photo.jpg", "https://example.com/photos/4x3/photo.jpg", "https://example.com/photos/16x9/photo.jpg" ] ``` | | `name` | [`Text`](https://schema.org/Text) The string name of the entity or item. For example, the name of a hotel or a vacation listing. The `item.name` is displayed as the title of an individual item in the carousel. HTML formatting is ignored. | | `url` | [`URL`](https://schema.org/URL) The canonical URL of the item detail page (for example, the standalone page for a single hotel or vacation listing that was referenced in the summary page). All URLs in the list must be unique, but live on the same domain (the same domain, or sub or super domain as the summary page). > [!NOTE] > Anchor links within a summary or category page aren't supported; your site must have standalone detail pages for each item in the list. | | Recommended properties || |---|---| | `aggregateRating.bestRating` | [`Number`](https://schema.org/Number) The highest value allowed in this rating system (for example, `5 / 10`). If `bestRating` is omitted, `5` is assumed. | | `aggregateRating.ratingCount` | [`Number`](https://schema.org/Number) The total number of ratings for the item on your site. | | `aggregateRating.ratingValue` | `https://schema.org/Number` or `https://schema.org/Text` A numerical quality rating for the item, either a number, fraction, or percentage (for example, `4`, `60%`, or `6 / 10`). Google understands the scale for fractions and percentages, since the scale is implied in the fraction itself or the percentage. The default scale for numbers is a 5-point scale, where 1 is the lowest value and 5 is the highest value. If another scale is intended, use `bestRating` and `worstRating`. For decimal numbers, use a dot instead of a comma to specify the value (for example `4.4` instead of `4,4`). In Microdata and RDFa, you can use `content` attributes to override the visible content. That way, you can show the user whatever style convention you want, while also satisfying the dot requirement for structured data. For example: ``` 4,4 stars ``` | ### Additional type-specific properties definitions #### `LocalBusiness` (and subtypes) In addition to the [`ListItem` properties](https://developers.google.com/search/docs/appearance/structured-data/carousels-beta#listitem), Google supports the following `LocalBusiness` properties (including its subtypes) for carousel rich results. Nest these properties under `itemListElement.item`. | Recommended properties || |---|---| | `amenityFeature` | [`LocationFeatureSpecification`](https://schema.org/LocationFeatureSpecification) **For `LodgingBusiness` only**: An amenity feature (for example, a characteristic or service) of the accommodation. ``` "amenityFeature": { "@type": "LocationFeatureSpecification", "name" : "beachAccess", "value": true } ``` | | `priceRange` | [`Text`](https://schema.org/Text) The relative price range of a business, commonly specified by a normalized number of currency signs. Provide the price range in either of the following formats: - **Price level:** for example, "$", "$$", "$$$" - **Range:** for example, "$-$$" This field must be shorter than 12 characters. If it's longer than 12 characters, Google won't show a price range for the business. | | `servesCuisine` | [`Text`](https://schema.org/Text) **For restaurants only**: The type of cuisine the restaurant serves. | #### `Product` In addition to the [`ListItem` properties](https://developers.google.com/search/docs/appearance/structured-data/carousels-beta#listitem), Google supports the following `Product` properties for carousel rich results. Nest these properties under `itemListElement.item`. | Recommended properties || |---|---| | `offers` | [`Offer`](https://schema.org/Offer) or [`AggregateOffer`](https://schema.org/AggregateOffer) A nested `Offer` or `AggregateOffer` to sell the product. Include the recommended properties for either `Offer` or `AggregateOffer` (whichever is applicable to your content). If you're using `Offer`, including the following properties: - `offers.price` - `offers.priceCurrency` If you're using `AggregateOffer`, including the following properties: - `offers.highPrice` - `offers.lowPrice` - `offers.priceCurrency` | | `offers.highPrice` | [`Number`](https://schema.org/Number) The highest price of all offers available. If you're specifying a single price with `price`, don't need to include the `highPrice` and `lowPrice` properties. | | `offers.lowPrice` | [`Number`](https://schema.org/Number) The lowest price of all offers available. If you're specifying a single price with `price`, don't need to include the `highPrice` and `lowPrice` properties. | | `offers.price` | [`Number`](https://schema.org/Number) The offer price of a product, or of a price component when attached to `PriceSpecification` and its subtypes. If you're specifying a price range with `lowPrice` and `highPrice`, don't include the `price` property. | | `offers.priceCurrency` | [`Text`](https://schema.org/Text) The currency used to describe the product price, in three-letter [ISO 4217](https://en.wikipedia.org/wiki/ISO_4217) format. If a currency is not provided, Google defaults to `USD`. | #### `Event` In addition to the [`ListItem` properties](https://developers.google.com/search/docs/appearance/structured-data/carousels-beta#listitem), Google supports the following `Event` properties for carousel rich results. Nest these properties under `itemListElement.item`. | Recommended properties || |---|---| | `offers` | `Offer` or `AggregateOffer` A nested `Offer` or `AggregateOffer` to sell the event. Include the recommended propeties for either `Offer` or `AggregateOffer` (whichever is applicable to your content). If you're using `Offer`, including the following properties: - `offers.price` - `offers.priceCurrency` If you're using `AggregateOffer`, including the following properties: - `offers.highPrice` - `offers.lowPrice` - `offers.priceCurrency` | | `offers.highPrice` | [`Number`](https://schema.org/Number) The highest price of all offers available. If you're specifying a single price with `price`, don't need to include the `highPrice` and `lowPrice` properties. | | `offers.lowPrice` | [`Number`](https://schema.org/Number) The lowest price of all offers available. If you're specifying a single price with `price`, don't need to include the `highPrice` and `lowPrice` properties. | | `offers.price` | [`Number`](https://schema.org/Number) The price for your tickets, including service charges and fees. Don't forget to update it as prices change or tickets sell out. If you're specifying a price range with `lowPrice` and `highPrice`, don't include the `price` property. If the event is available without payment, fees, or service charges, set the `price` to `0`. ``` "offers": { "@type": "Offer", "price": 0 } ``` | | `offers.priceCurrency` | [`Text`](https://schema.org/Text) The currency used to describe the event price, in three-letter [ISO 4217](https://en.wikipedia.org/wiki/ISO_4217) format. If a currency is not provided, Google defaults to `USD`. | ## Examples for common scenarios ### `Restaurant` example Here is an example of a restaurant carousel in JSON-LD. \ \ \Top 5 Restaurants in Paris\ \ ``` ### Lodging (`Hotels` and `VacationRental`) example Here is an example of a lodging carousel in JSON-LD. \ \ \Top 5 Hotels in Paris\ \ ``` ### Things to do example example Here is an example of a things to do carousel in JSON-LD. \ \ \Top 5 Things To Do in Paris\ \ ``` ### `Product` example Here is an example of a product carousel in JSON-LD. \ \ \Top coats of the season\ \ ``` ## Troubleshooting If you're having trouble implementing or debugging structured data, here are some resources that may help you. - If you're using a content management system (CMS) or someone else is taking care of your site, ask them to help you. Make sure to forward any Search Console message that details the issue to them. - Google does not guarantee that features that consume structured data will show up in search results. For a list of common reasons why Google may not show your content in a rich result, see the [General Structured Data Guidelines](https://developers.google.com/search/docs/appearance/structured-data/sd-policies). - You might have an error in your structured data. Check the [list of structured data errors](https://support.google.com/webmasters/answer/13300873) and the [Unparsable structured data report](https://support.google.com/webmasters/answer/9166415). - If you received a structured data manual action against your page, the structured data on the page will be ignored (although the page can still appear in Google Search results). To fix [structured data issues](https://support.google.com/webmasters/answer/9044175#zippy=%2Cstructured-data-issue), use the [Manual Actions report](https://support.google.com/webmasters/answer/9044175). - Review the [guidelines](https://developers.google.com/search/docs/appearance/structured-data/carousels-beta#guidelines) again to identify if your content isn't compliant with the guidelines. The problem can be caused by either spammy content or spammy markup usage. However, the issue may not be a syntax issue, and so the Rich Results Test won't be able to identify these issues. - Structured data issues can affect how your site's content appears in search results. Use this [Troubleshoot missing rich results / drop in total rich results](https://support.google.com/webmasters/answer/13300208) guide to review a step-by-step approach to identify, fix, and validate these issues in Search Console. - Allow time for re-crawling and re-indexing. Remember that it may take several days after publishing a page for Google to find and crawl it. For general questions about crawling and indexing, check the [Google Search crawling and indexing FAQ](https://developers.google.com/search/help/crawling-index-faq). - Post a question in the [Google Search Central forum](https://support.google.com/webmasters/community).