Google Enhances Carousels (Beta) Structured Data Guidelines

The Structured Data Carousels (beta) have been updated by Google. The new documentation now provides clearer details on the requirements for displaying rich results for qualifying topics. It is also emphasized that the rich results features are restricted to a single geographic area.

Carousels Structured Data (beta) allows web publishers who focus on travel, local, and shopping content to add structured data to their pages. This helps them qualify for a new carousel rich result in search results. The carousel displays their content in a horizontally scrollable list, making it more visible to users.

This beta feature uses the ItemList structured data and is specifically designed for webpages that feature LocalBusiness, Product, and Event Schema.org properties. Each tile in the carousel showcases important details such as price, rating, dates, and images in a visually appealing and interactive manner.

More Focus on Summary Page

The new documentation emphasizes that the beta carousel structured data should be used on a summary page that directs users to more detailed information. It is important to note that the detailed pages do not require this specific structured data.

To improve the old documentation, follow these instructions:

"Include all list information, such as the full text of each item, on a single page. This type of page is also known as a single, all-in-one-page list. For instance, you can create a list of the best hotels in a specific location all on one page."

The updated guide now clarifies it as follows:

Choose one main page that provides a brief overview of each item on the list. For instance, a category page showcasing the "Top hotels in Paris", with clickable links to individual pages for more detailed information on each hotel.

There is also an addition of an example for clarification:

“For example, if you have a “Things to do in Switzerland” article that lists both local events and local businesses.

Add the required properties to that summary page. You don’t need to add markup to the detail pages in order to be eligible for this beta feature.”

There is also an entirely new paragraph:

Your website should have a summary page and several detail pages. Currently, it is not set up to accommodate other setups, like having all the details on one page with anchor points.

The markup should be on a summary or category page, which is a page that lists information about at least three items and links to other pages for more details. You do not need to add markup to the detail pages, but you must include the URLs of the detail pages in the markup of the summary page.

Lastly, there is an edit to a short paragraph that makes it clearer that the structured data is for a standalone summary page.

This is the previous version:

The item detail page, such as a hotel or vacation listing, should have a unique canonical URL. This URL should be on the same domain as the current page, whether it's the main domain, a subdomain, or a super domain.

Geographic Eligibility Clarification:

When it comes to the canonical URL of the item detail page, such as a standalone page for a single hotel or vacation listing mentioned in the summary page, it is important to note that all URLs in the list should be unique. However, they should still be on the same domain as the summary page, whether it is the same domain, subdomain, or super domain.

Google has updated its changelog documentation to clarify that structured data is meant for use on summary pages. However, the new documentation also includes more information about where the new rich results features are available.

The beta carousel feature is specifically designed for websites that have a summary page linking to other detail pages. The markup should only be added to the summary page, without the need for markup on the detail pages to qualify for this feature.

However, it is important to note that the changelog is inaccurate as it fails to mention that there is a geographical limitation to this rich results feature.

The previous version did not specify which countries are eligible for the beta rich results. This information was only mentioned in the initial announcement of the new feature and not in the documentation.

The new documentation now includes this important detail, addressing the previous omission.

"Feature availability

This feature is currently in beta, which means there may be changes to the requirements or guidelines as we continue to develop it. If your business is located in the EEA or caters to users in the EEA, and you are interested in learning more about these new experiences, you can get started by filling out the relevant form. For flight queries, make sure to use the interest form specifically for flights."

This feature is currently exclusive to countries in the European Economic Area (EEA) and can be accessed on both desktop and mobile devices. It is designed for travel, local, and shopping queries. Initially, the shopping feature is being tested in Germany, France, Czechia, and the UK.

It is strange that Google initially neglected to include crucial details about the availability of this feature in the original Carousels (beta) documentation, and then failed to mention its re-addition in the changelog documentation.

That’s important information and adding it to the newly updated documentation should have been noted in the changelog.

Read the newly updated documentation and guidelines:

Structured data carousels (beta)

Featured Image by Shutterstock/Framalicious

Editor's P/S:

The recent updates to Google's Structured Data Carousels (beta) provide greater clarity and guidance for webmasters. The emphasis on using summary pages for structured data is a welcome improvement, as it ensures that users have a consistent and informative experience when interacting with carousels in search results. Additionally, the clarification regarding geographic eligibility is essential for businesses and content creators who want to optimize their content for specific regions.

However, it is concerning that Google initially omitted crucial information about the feature's availability in its documentation and failed to acknowledge its re-addition in the changelog. This oversight highlights the need for Google to prioritize transparency and accuracy in its communication with developers and content creators. By providing comprehensive and up-to-date documentation, Google can empower webmasters to effectively leverage its features and deliver the best possible user experience.