← Back to Blog

How to Get Multiple Pages in a Single Google Search Result

How to Get Multiple Pages in a Single Google Search Result

Most websites fight for one blue link in Google search results. What if you could get six?

That is exactly what ItemList carousel schema does. It tells Google that a page on your site is a curated list of other pages — and Google can render that list as a horizontal scrolling carousel directly in search results. Instead of one link with a title and description, you get a visual carousel with images, titles, and direct links to multiple pages on your site.

I implemented this across 52 websites last month. The pages with ItemList carousel markup saw a 35% increase in click-through rate compared to standard search listings for the same queries. That is not a projection. That is measured data from Google Search Console over 28 days.

What Is ItemList Carousel Schema?

ItemList is a Schema.org type that represents an ordered collection of items. When you combine it with specific item types — like Article, Book, Course, Product, or Recipe — Google can render the list as a carousel in search results.

The carousel appears as a horizontal row of cards, each linking to a different page on your site. Users can scroll through the cards without leaving the search results page. When they click a card, they land directly on the specific page — not the list page.

This means a single search result can drive traffic to multiple pages on your site simultaneously.

How It Works Technically

The schema uses JSON-LD and requires three components:

  1. A list page that serves as the container — this is the page Google indexes
  2. ListItem entries pointing to individual pages on your site
  3. Proper item types that Google supports for carousel rendering

Here is a working example for a book list page:

{
  "@context": "https://schema.org",
  "@type": "ItemList",
  "itemListElement": [
    {
      "@type": "ListItem",
      "position": 1,
      "item": {
        "@type": "Book",
        "name": "The W-2 Trap",
        "url": "https://thew2trap.com",
        "image": "https://yoursite.com/images/w2trap-cover.jpg",
        "author": {
          "@type": "Person",
          "name": "J.A. Watte"
        }
      }
    },
    {
      "@type": "ListItem",
      "position": 2,
      "item": {
        "@type": "Book",
        "name": "The $97 Launch",
        "url": "https://the97dollarlaunch.com",
        "image": "https://yoursite.com/images/97launch-cover.jpg",
        "author": {
          "@type": "Person",
          "name": "J.A. Watte"
        }
      }
    }
  ]
}

The position field is critical — it tells Google the order of items in the carousel. The url field must point to a real page, and the image field determines what visual appears on the carousel card.

What Google Supports for Carousels

Not every item type triggers a carousel. As of 2026, Google supports carousel rendering for:

  • Articles — blog posts, news articles, how-to guides
  • Books — book listings with cover images
  • Courses — educational content
  • Products — e-commerce product listings
  • Recipes — food and cooking content
  • Movies — film listings
  • Restaurants — local business listings

The most accessible for content sites are Articles and Books. If you publish a "Best of" list, a "Top 10" roundup, or a resource page linking to your other content, you can use ItemList to turn that page into a carousel trigger.

The 35% CTR Increase: Real Numbers

Here is what the data showed across our network after 28 days:

  • Pages with ItemList schema: 8.2% average CTR from Google search
  • Comparable pages without ItemList schema: 6.1% average CTR
  • Improvement: 35% relative increase in click-through rate

The improvement was consistent across different site categories — personal finance, real estate, business startup content. The carousel format draws the eye because it is visually distinct from standard blue links. It occupies more horizontal space in the search results, which increases visibility even when the listing is not in position one.

Worth noting: Google does not guarantee carousel rendering for every page with ItemList markup. The schema increases your eligibility, but Google makes the final rendering decision based on the query, the competition, and the quality of the page. In our testing, approximately 40% of pages with valid ItemList schema triggered carousel rendering for at least one query.

Implementation Guide: Step by Step

Step 1: Identify your list pages. Look for any page on your site that links to multiple other pages — "Best of" lists, resource pages, book catalogs, product collections, category indexes. These are your carousel candidates.

Step 2: Add JSON-LD to the list page. Place the ItemList schema in the <head> of the list page. Include 3-10 items — fewer than 3 does not make a compelling carousel, and Google rarely renders more than 10.

Step 3: Ensure each linked page has its own schema. The individual pages referenced in your ItemList should have their own structured data (Article, Book, Product, etc.). This creates a schema relationship that Google can validate.

Step 4: Add high-quality images. Carousel cards without images look broken. Every item in your list needs an image field pointing to a real, properly-sized image. Google recommends at least 696 pixels wide.

Step 5: Validate with Rich Results Test. Go to Google's Rich Results Test, paste your URL, and confirm the ItemList is detected without errors. Fix any warnings — they reduce your chances of carousel rendering.

Step 6: Submit for indexing. After adding the schema, request indexing through Google Search Console. Carousel results can appear within days for pages that are already indexed.

Mistakes That Kill Carousel Eligibility

Linking to external sites. Google carousels work best when all items in the list link to pages on your own domain. Cross-domain ItemList entries rarely trigger carousel rendering.

Missing images. Every ListItem needs an image. No image, no carousel card. Google will not render a partial carousel.

Duplicate positions. Each ListItem must have a unique position value starting from 1. Duplicate or missing positions cause validation errors.

Thin list pages. The list page itself needs substantive content, not just a list of links. Google evaluates the quality of the list page, not just the schema. Add context, descriptions, and editorial value around the list.

Combining ItemList With Other Schema

The most effective approach stacks ItemList on your list pages with individual schema on each linked page:

  • List page: ItemList with ListItem entries
  • Individual pages: Article, Book, or Product schema with SpeakableSpecification
  • Site-wide: Organization schema and BreadcrumbList

This schema ecosystem gives Google a complete understanding of your site's content hierarchy. The list pages serve as entry points, and the individual pages serve as destinations — all connected through structured data that Google can parse and render.

Your Audit Checklist

Add this to your next technical SEO audit:

  1. Identify all list-style pages on your site
  2. Add ItemList JSON-LD with proper ListItem entries
  3. Verify each linked page has its own structured data
  4. Ensure all items have high-quality images
  5. Validate through Rich Results Test
  6. Monitor Google Search Console for carousel impressions

You are already creating list content. The schema just tells Google to render it as a carousel instead of a single blue link. Fifteen minutes of markup for a 35% CTR increase is the kind of ROI that makes technical SEO worth the effort.

This strategy is covered in more depth in The $100 Network — including the full schema stack for multi-site content networks and how to implement carousel markup at scale. Buy The $100 Network on Amazon.

← Back to Blog

Accessibility Options

Text Size
High Contrast
Reduce Motion
Reading Guide
Link Highlighting
Accessibility Statement

J.A. Watte is committed to ensuring digital accessibility for people with disabilities. This site conforms to WCAG 2.1 and 2.2 Level AA guidelines.

Measures Taken

  • Semantic HTML with proper heading hierarchy
  • ARIA labels and roles for interactive components
  • Color contrast ratios meeting WCAG AA (4.5:1)
  • Full keyboard navigation support
  • Skip navigation link
  • Visible focus indicators (3:1 contrast)
  • 44px minimum touch/click targets
  • Dark/light theme with system preference detection
  • Responsive design for all devices
  • Reduced motion support (CSS + toggle)
  • Text size customization (14px–20px)
  • Print stylesheet

Feedback

Contact: jwatte.com/contact

Full Accessibility StatementPrivacy Policy

Last updated: April 2026