New researchTechnical SEO & AI Search · 2027Explore the framework

Pagination SEO: how to paginate category pages so Google finds every product

How Google handles paginated category pages, load more buttons and infinite scroll, the canonical mistake to avoid, and how to check every product is reachable.

Part of the E-commerce SEO series. For the full picture, start with E-commerce technical SEO: the complete guide for online stores.

Pagination looks like a solved problem until you check how deep the products go. A category with 2,000 products at 24 per page has 84 pages; the products on page 70 are 70 clicks from the category if pages only link to their neighbours, and invisible if the pages are hidden behind a “Load more” button.

This guide covers what Google recommends for paginated pages, the canonical mistake that hides products, how to handle load more and infinite scroll, and how to check that every product is reachable.

How does Google treat paginated pages?

As separate pages. Google’s pagination guide for e-commerce recommends:

Do Don’t
“Give each page a unique URL”, for example with a ?page=n parameter Use fragment identifiers (#page=2) for page numbers: Google ignores them
“Include links from each page to the following page using <a href> tags” Rely on buttons or JavaScript events for navigation
Give “each page its own canonical URL” Use the first page as the canonical for every page
Keep alternate sort orders out of the index, with noindex or robots.txt Let every sort order become an indexable copy

Google no longer uses rel="next" and rel="prev". They do no harm, and other search engines may use them, but plain links are what Google follows.

Why not canonicalise everything to page one?

Because page two isn’t a duplicate of page one: it lists different products. A canonical from page five to page one tells Google page five is a copy and the page one URL should be indexed instead, and the products linked only from page five lose their main path for discovery. Each paginated page should canonicalise to itself.

The same logic applies to noindex: noindexing page two onwards removes those pages from the index, and with them a route from indexed pages to the products they list.

What should be consolidated are alternate sort orders and views of the same page (?sort=price, ?view=grid): those really are the same products in a different order. Google recommends keeping them out of the index with noindex or out of the crawl with robots.txt. See faceted navigation.

What about load more and infinite scroll?

Google’s crawlers don’t “click buttons” or trigger JavaScript that needs user interaction. A “Load more” button or infinite scroll that fetches products with JavaScript and no URL change leaves everything after the first batch invisible to crawling.

To make incremental loading crawlable:

  • Back it with real pages. Give each chunk its own URL (?page=2) and include plain links to them, even if users mostly see the button.
  • Update the URL as the user scrolls into the next chunk, so each state is shareable and reloadable.
  • Make products reachable elsewhere too: from subcategories, related products and an XML sitemap. Google’s e-commerce structure guide notes that if category pages don’t link to every product, “Googlebot might not find all of your products by crawling alone.”

See JavaScript SEO for how to check what’s in the HTML versus only after rendering.

How do you reduce pagination depth?

Long chains of pages put products many clicks deep. Options, roughly in order of impact:

  1. More, smaller subcategories. Twenty subcategories of 100 products are easier to crawl and better for shoppers than one category of 2,000.
  2. Link to more than the next page. Page number links (1, 2, 3 … 10, 20, 40, 84) cut the number of hops dramatically.
  3. More products per page, within what page speed allows.
  4. Link popular products directly from the category’s first page, the homepage and content.

How do you check pagination across a store?

Crawl from the homepage with robots.txt respected, and with Render JavaScript on if the store uses load more or infinite scroll. In Crawlens:

Search the URLs table for page= to see how deep each category goes, and sort by Depth to find the deepest products. See internal linking for the wider picture.

Checklist

  • Each paginated page has a unique URL (?page=n), not a fragment
  • Plain <a href> links between pages, including page-number links
  • Each page has a self-referencing canonical; none point at page one
  • Paginated pages are indexable
  • Alternate sort orders and views are noindexed or kept out of the crawl
  • Load more and infinite scroll are backed by linked, crawlable page URLs
  • Products also reachable from subcategories and an XML sitemap
  • No products more than a few clicks deep, or linked from a single page

Frequently asked questions

Should paginated pages canonicalise to page one?

No. Google recommends giving each page in a paginated sequence its own canonical URL. Pointing every page at page one tells Google the later pages are duplicates, so the products only linked from them can be missed.

Does Google still use rel=next and rel=prev?

No. Google no longer uses rel=next and rel=prev as an indexing signal, though other search engines may. Plain links between the pages are what matter for Google.

Should paginated pages be noindexed?

Generally not. Google recommends giving each paginated page its own canonical, which treats them as normal indexable pages. Noindexing page two onwards removes them from the index, so the products they list lose a route from indexed pages. Exclude alternate sort orders instead.

Is infinite scroll bad for SEO?

It can be, because Google's crawlers don't scroll or click to load more. Make sure each chunk of results also exists at its own URL with links between them, or that every product is reachable some other way, such as from subcategories and an XML sitemap.

How many products should be on each page?

There's no SEO rule for it. More products per page means fewer pages for crawlers to walk through and fewer clicks to reach each product, but heavier pages. Choose what works for shoppers and page speed, then make sure every page is linked.

· Founder, Crawlens

Dien builds Crawlens, a desktop crawler for technical SEO audits, and writes about the checks it runs: crawling, indexing, rendering and Search Console data.

Audit your own site with Crawlens

Crawl, run 70 checks, and see them next to Search Console and Core Web Vitals data.

Download free for Windows