Carousel markup uses ItemList schema to mark a list of items, such as articles, recipes, or products, that Google can show as a swipeable carousel from a single site. It is a host carousel: all items come from your domain. It increases your SERP footprint by displaying multiple entries in one scrollable strip.

Google supports two patterns. In the summary page approach, a list page has an ItemList where each ListItem has a url pointing to a detail page that holds the actual content schema (Recipe, Article, etc.). The detail markup lives on each target page. This generator builds the summary list that ties those pages into a carousel.

Google documents host carousels for specific types including Recipe, Course, Movie, and Restaurant, as well as general article-style lists. The individual detail pages must carry the appropriate type-specific schema; the ItemList simply orders and links them. Always confirm your content type is carousel-eligible in Google's current documentation.

Yes. Each ListItem needs a position starting at 1, and the order should reflect how you want items displayed in the carousel. Google generally preserves your declared order. This generator assigns sequential positions automatically based on the order you enter your URLs, so list your most important items first.

Not for the summary pattern. In the recommended approach the ItemList only contains ListItem entries with position and url; the rich content details live on each linked page. Keep the list lean and accurate. Bloating the ItemList with full nested content can cause validation confusion and is unnecessary.

Common reasons include linked detail pages lacking their own required schema, items pointing to pages on other domains (host carousels must be same-site), too few items, or Google simply choosing not to render it. Validate each detail page separately and confirm all URLs are absolute and on your domain.

No. A host carousel should contain a single content type, for example all recipes or all courses, because Google renders type-specific carousels. Mixing articles with products in one ItemList breaks eligibility. Build separate ItemList carousels per content type if you need multiple kinds of lists.