My Tool Studio
Schema

ItemList Schema Generator

This itemlist schema generator turns a top-10 list, a roundup or a set of steps into ItemList JSON-LD with numbered positions. Import the items from a list article's headings, or add them by hand with a name, URL, description and image, and reorder them with the arrows. For lists of recipes, courses, movies or restaurants, choose the item type and a layout, summary page or all-in-one page, to get the structure Google uses for carousels. You can also paste a list as Name | URL lines, load existing ItemList JSON-LD, set the list order, and the tool counts the items. A preview shows the list as readers see it. Food bloggers use it on recipe roundups, and review sites use it on ranked lists.

Always freeNo sign upRuns in your browser

Import items from a list article (reads its H2 headings, or H3 if there are fewer than three, with any link, anchor, first image and first paragraph)

Import existing JSON-LD(paste code or read it from a URL)

Paste existing ItemList JSON-LD to load its items, order and carousel type.

List details

List items· auto-numbered (0 valid)

Item 1
  • Add at least one item.
Output
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "ItemList"
}
</script>
Test in Google Rich Results TestValidate at validator.schema.orgThe test links copy your code first. Paste it into the tester's Code tab.

How to use

01

Import or add items

Paste a list article URL and press Import items to read its headings, or press Add item and fill name, URL, description and image. Reorder with the up and down arrows.

02

Set type, layout and order

Give the list a title and page URL. For a carousel, choose the item type and Summary page or All-in-one page, and pick the list order if it matters.

03

Preview and copy

Check the numbered preview against your page, clear the warnings in the Validation panel, then press Copy script and test the block with Test in Google Rich Results Test.

Why ItemList Schema Generator

Summary page or all-in-one page: which layout

Google's carousel documentation describes two ways to mark up a list, and the choice depends on where the details of each item live.

Use Summary page when the list links out. A roundup of ten recipes where each recipe has its own page is a summary page: the ItemList on the roundup holds ten ListItems with a position and url, and each recipe page carries its own full Recipe markup.

Use All-in-one page when everything is on one URL. A single article that shows all ten recipes in full is an all-in-one page: each ListItem holds the complete Recipe, and each item's url is an anchor to its section on that page.

Summary pageAll-in-one page
Where item details liveOn separate detail pagesOn this page
ListItem containsposition, urlposition, item with @type, name, url, image
Item urlThe detail pageAn anchor on this page
Detail pages need their own markupYesNo

Example: a ranked list of hiking boots

A review site publishes Top 5 hiking boots, with a full review page for each boot. Import items from the article to get five headings with links, keep the plain item type (Product is not a carousel type), set List order to Ascending and the page URL.

The output is an ItemList with name, url, itemListOrder ItemListOrderAscending, numberOfItems 5 and five ListItems holding position, name, url, description and image. Reorder with the arrows if the published ranking changes, and the positions renumber themselves.

If the boots were described in full on the list page instead, with no separate reviews, each item URL would be an anchor such as #boot-3 on the same page. Because Product is not a carousel type, the plain item type stays the right choice either way.

Common questions

Does ItemList schema get my page into a Google carousel?
It can make the page eligible when the items are a type Google supports for carousels: Course, Movie, Recipe and Restaurant. Choose that item type and a layout here. For other lists, the markup describes order and contents but has no carousel.
What is the difference between a summary page and an all-in-one page?
A summary page lists items that each have their own detail page, so each ListItem holds only a position and the item's URL. An all-in-one page describes every item on the same page, so each ListItem holds the full item with its name, URL (usually an anchor) and image.
How does the ItemList generator import items from a URL?
It reads the H2 headings in the article or main content, or the H3 headings if there are fewer than three H2s. Each heading becomes an item with its link or anchor, the first image after it and the first paragraph as a description, up to 50 items.
What is itemListOrder in ItemList schema?
A property that says how the list is sorted: ascending, descending or unordered. A countdown from 10 to 1 is descending. Leave it unset if the order has no meaning.
Should ItemList positions match the order on my page?
Yes. Positions start at 1 in the order shown in the editor, so arrange items exactly as they appear on the published page.
What should the URL be for each ItemList item?
On a summary page, the item's own detail page. On an all-in-one page, an anchor to the item's section, such as example.com/top-boots#item-2. Every item in a carousel list needs a URL, and the warnings will say if one is missing.
How many items does ItemList markup need?
Schema.org sets no minimum. Google's course list needs at least three courses, and the tool warns about that. Very long lists are fine as long as every item is on the page.
Can I still use HowToSection for step lists?
Yes, HowToSection is a valid Schema.org type and the tool can output it. Google stopped showing HowTo rich results in 2023, so it has no effect on how the page looks in Google. For a full guide with supplies and tools, the HowTo Schema Generator covers more.
Can I paste a list into the ItemList generator?
Yes. Paste one item per line as Name | URL, or a bare URL, and press Add pasted items. Leading numbers such as 1. are removed, so a copied ranked list works as is.

More Schema tools

View all