Pagination SEO is the work of making page 2, page 3 and page 30 of a category crawlable, so search engines reach every product listed there. Google's current rules fit in one paragraph: give every page its own URL such as ?page=2, link the pages with ordinary <a href> links, let each page carry a canonical tag that points to itself, and keep sorted and filtered copies of the same list out of the index. Google no longer uses rel="next" and rel="prev" (Google Search Central).
That covers the markup. The harder part in a large catalog is structural: how many clicks a product sits from the first page of its category, what happens to that path when a shopper sorts by price, and whether the product is in a category at all. This guide works through each of those with one running example, a 340-product running shoe category, and ends with an audit checklist you can run on a single category.
Google's rules for paginated category pages
Google covers pagination in its ecommerce documentation on pagination and incremental page loading. Six points from it apply to almost every store:
- One URL per page. A query parameter (/c/running-shoes?page=4) or a path segment (/page/4/) both work. Google treats each URL as a separate page.
- Links Googlebot can follow. Link each page to the next with an <a href> element. Google adds that linking every page back to page 1 helps it treat page 1 as the start of the series.
- A canonical that points to the page itself. Google says explicitly not to use the first page of a paginated sequence as the canonical page.
- No page numbers in fragments. Google ignores everything after a #, so /c/running-shoes#page=3 is the same URL as page 1 to its crawler.
- No reliance on rel=next and rel=prev. Google stopped using them. Other search engines may still read them, so leaving them in place does no harm.
- Sorted and filtered variants kept out of the index, with a noindex robots meta tag or a robots.txt rule for those URL patterns.
The same page also says what you do not need: paginated pages can reuse the category's title and meta description. Google can still group and index the series. Pagination is one item on a longer list of crawl and indexing checks; the ecommerce technical SEO guide covers the rest.
Seven pagination setups and what a crawler can follow
Most pagination problems come from how the next batch of products is loaded, not from tags. Googlebot follows URLs in href attributes. It does not click buttons, and it generally does not run JavaScript that waits for a user action. Here is how the common setups compare.
Pagination setups compared for crawlability
| Numbered pages with ?page=n links | Yes | Yes | All products reachable |
|---|---|---|---|
| Load more button that fetches products with JavaScript only | No | No | Only the first batch is crawled |
| Load more link with href="?page=2", enhanced by JavaScript | Yes | Yes | All products reachable, shoppers keep the growing list |
| Infinite scroll with no paginated URLs | No | No | Only the first batch is crawled |
| Infinite scroll that writes ?page=n to the address bar and keeps page links in the HTML | Yes | Yes | Reachable, if each page URL also loads on its own |
| Page numbers in a fragment (#page=3) | No | No, the fragment is ignored | Pages 2 and later look like page 1 |
| Every page canonical to page 1 | Yes | Yes | Later pages may be treated as duplicates and dropped |
Rows three and five use progressive enhancement. The HTML holds an ordinary link to the next page, and JavaScript intercepts the click to append the products in place. Googlebot follows the href, and the shopper never sees a page reload. To test it, paste /c/running-shoes?page=5 into a private browser window: it must show page 5's products on its own, not page 1 and not an empty grid.
Canonical tags, noindex and titles from page 2 onward
Point each page's canonical at itself: /c/running-shoes?page=3 declares /c/running-shoes?page=3. Page 3 shows different products than page 1, so it is not a duplicate. Declaring it one tells Google to treat page 3 as a copy of page 1, which risks losing the page, and its links are the path to products 49 to 72.
Some SEO plugins and themes offer a setting that puts noindex on page 2 and later. Google's pagination documentation does not address this, so what follows is our editorial advice rather than a Google rule. Deep pages rarely rank for anything, so the loss in search results is small. The risk is discovery: you are relying on Google to keep following links on pages you asked it to drop. If products on deep pages have no other internal links, keep those pages indexable and let the self-referencing canonical do its job.
Titles are a smaller decision. Google does not require unique titles on paginated pages, and adding "Page 3" to the title tag is harmless and helps shoppers with several tabs open. Google sets no rule for category text either, so this one is a practical choice: show the category introduction text on page 1 only, so pages 2 and later are not near-copies of the same text with a different grid underneath.
One more rule comes from Google's faceted navigation guidance: a pagination URL that does not exist should return a 404 status. On the 15-page running shoe category, ?page=99 must not redirect to page 1 or render an empty page with status 200.
Load more, infinite scroll and the shopper's back button
The choice is also a usability question. In Baymard Institute's testing on more than 50 ecommerce sites, published in Smashing Magazine in 2016, participants browsed far more products on sites with infinite scrolling than on sites with pagination or load more buttons, and with pagination they virtually never got past 100 products. Infinite scrolling, in turn, made them skim, and Baymard found it harmful for on-site search results and on mobile.
Baymard's recommendation for category lists is a hybrid: show 10 to 30 products on load, lazy-load further batches of 10 to 30 as the shopper scrolls until 50 to 100 products are on the page, then show a load more button. It suggests the lower end for spec-driven products such as electronics and parts, and the higher end for visual ones such as apparel and furniture.
The crawling rules apply on top of that. Every batch needs an address: when the shopper presses load more and products 49 to 72 appear, the address bar should change to ?page=3 with history.pushState, and that URL must work when opened directly. The back button is where many builds fail. In the same benchmark, Baymard found that over 90% of the sites using load more got it wrong. A shopper who opens product 61 and goes back should land at product 61, not at the top of the list.
Products per page and the number of pages a category needs
Page size decides how deep a category goes. Platforms set the outer limits: Shopify's paginate tag accepts 1 to 250 items per page and paginates only up to the 25,000th item in a list (Shopify). Default themes sit at the low end: Shopify's Dawn theme shows 16 products per page unless you change it (the setting runs from 8 to 36, see the Dawn source on GitHub), and Magento Open Source shows 12 in grid view, with 24 and 36 as options (Magento catalog configuration). The chart shows what that means for categories of different sizes.
Pages needed per category at three page sizes
Illustrative example| Category size | 24 per page | 48 per page | 96 per page |
|---|---|---|---|
| 120 products | 5 | 3 | 2 |
| 340 products | 15 | 8 | 4 |
| 1,100 products | 46 | 23 | 12 |
| 2,400 products | 100 | 50 | 25 |
At 24 per page, the 340-product running shoe category runs to 15 pages, which is manageable. A 2,400-product category runs to 100. The fix for that is rarely a bigger page, because 96 product cards with images make a heavy page. It is subcategories: trail running shoes, road running shoes and spikes as their own categories give shorter lists, better landing pages for the searches people actually make, and a natural place for filters. The category management guide covers how to cut a tree that way.
Pager links that shorten the click path
With only a Next link, product 330 on page 14 is 13 clicks from page 1. A pager that shows the first and last page plus two neighbors on each side of the current page (1 ... 5 6 7 8 9 ... 15) puts page 14 two clicks away, and no page of the 15-page category sits more than four clicks from page 1. Subcategory links at the top of the category and breadcrumbs on every product shorten the path further, because they give crawlers more than one route to the same products.
Sorting, filter parameters and paginated URLs
Every sort option multiplies the paginated series. Fifteen pages with four sort orders (featured, price ascending, price descending, newest) make 60 URLs for one category, before a single filter is applied. Keep one default sort indexable and keep the sorted variants out of the index with noindex, or stop crawlers from fetching them with a robots.txt rule for the sort parameter. Pick one per pattern: a page blocked in robots.txt is never fetched, so a noindex tag on it is never seen.
Filters behave the same way at larger scale; faceted navigation SEO covers which filter pages deserve indexing. Two pagination-specific rules: reset the page parameter to 1 when a shopper changes a filter or sort, and keep parameter order fixed, so ?color=black&page=2 never appears elsewhere on the site as ?page=2&color=black. Google's faceted navigation page asks for the same fixed, logical order when filters sit in the URL path, and the reason carries over to parameters: two spellings of one URL are two URLs to crawl.
Keep the default order stable as well. A featured sort that reshuffles every night shows Google different products on page 3 at every visit. A default based on something that changes slowly, such as weekly bestseller rank with the product ID as the tiebreaker, keeps each page's contents consistent between crawls.
Sold-out and discontinued products in a long category
Hiding sold-out products from listings looks tidy, but it shifts every product after them forward. If 30 of the 340 running shoes sell out and come back in a normal week, the contents of pages 2 to 15 change several times a week. A steadier pattern is to keep sold-out products listed and move them to the end of the default sort, while their product pages stay live.
Discontinued products are different: take them out of the listing and decide what the URL does. A product with a direct successor gets a 301 redirect to it; one without gets a 404 or 410, and it leaves the sitemap in the same release, as the ecommerce sitemap guide explains. Products you still sell on backorder stay listed, with an availability status that says so.
Products that no category page links to
Pagination only helps products that are in a category. In WISEPIM's State of Product Data report, the average catalog arrived in the PIM with 64% of its products in no category, measured at import across about 50 catalogs. Some of those products sit in a category in the shop anyway. The rest are reachable only through site search, the XML sitemap or a stray link from another page, and no pagination setting changes that.
Two checks find them. Export the catalog from your shop platform and filter for products with an empty category or collection field. Then compare the products in your catalog with the product URLs in your sitemap, because a product that is in neither a category nor the sitemap is close to invisible to a crawler.
In WISEPIM, AI categorization assigns uncategorized products to your category tree (AI category classification is 95%+ accurate), and the category tree can be exported to Shopify, WooCommerce, Magento 2, Lightspeed and CCV Shop. Sitemap Coverage reads your shop's own sitemaps and lists products from a connected store whose URLs are missing from them. WISEPIM does not render category pages or pagination: the pager, canonicals and page size stay in your store theme.
Pagination audit for one category

