Pagination SEO Guide: How to Handle Paginated Pages the Way Google Recommends

Pagination SEO covers how search engines discover, crawl and index content that is split across several pages: product categories, blog archives, forum threads, search results on your site. Mistakes here are common and costly, because they can hide hundreds of products or articles from Google without any visible error. This guide follows Google's own documentation on pagination and incremental page loading, with practical examples for e-commerce sites and blogs.

What is pagination in SEO?

Pagination is the practice of splitting a long list of items into a sequence of pages, usually with numbered links at the bottom: 1, 2, 3, next. Sites use it to keep pages fast and readable. For search engines, the question is simple: can a crawler reach every item in the list, and which pages of the sequence deserve to appear in results?

Google treats each URL in a paginated sequence as a separate page. That matters because page 5 of a category is often the only place where Googlebot finds links to older products or articles. If page 5 is unreachable, those items depend entirely on your XML sitemap or on other internal links to be found.

Why does pagination matter for SEO?

Pagination affects three things search engines care about:

• Discovery: deep pages in a series pass links to items that have no other entry point. Broken or JavaScript-only pagination cuts those items off.
• Crawl efficiency: on large sites, pagination combined with filters and sort options can create thousands of near-identical URLs that waste crawl budget.
• Signal consolidation: the wrong canonical setup can tell Google to ignore every page except the first, which removes the links on pages 2 and beyond from its view.

What does Google recommend for pagination in 2026?

Google's guidance fits in a short list. The table below summarizes what to do and what to avoid, based on its pagination documentation.

Should paginated pages canonicalize to page 1?

No. This is the most frequent pagination error. Google's documentation states plainly that you should not use the first page of a sequence as the canonical page. Page 2 contains different items from page 1, so declaring page 1 as its canonical tells Google that page 2 is a duplicate. Over time, Google may stop crawling the deeper pages, and the products or posts linked only from them become harder to discover.

The correct setup is a self-referencing canonical tag on each page: page 2 points to page 2, page 3 to page 3. One related detail: make sure page 1 has a single URL. If both /shoes/ and /shoes/?page=1 exist, link to the clean version everywhere and redirect or canonicalize the ?page=1 variant to it.

Is rel="next" and rel="prev" still useful?

Google confirmed in 2019 that it had stopped using these link attributes for indexing, and its current documentation repeats that it no longer uses them, while noting that other search engines may still read them. They do no harm, so you can keep them if your CMS adds them automatically. What you cannot do is rely on them: Google connects the pages of a series through the visible links between them, which is why crawlable <a href> links matter more than any markup.

Google also suggests linking from every page of a collection back to the first page. This gives the first page more internal links, which may hint that it is the best landing page for the series. Good internal linking on category pages, such as links to subcategories and best sellers on page 1, does the rest.

Should you index or noindex paginated pages?

In most cases, leave paginated pages indexable. A noindex on page 2 and beyond does not stop Google from seeing the page at first, but Google has said that pages kept in noindex for a long time are eventually crawled less and their links followed less. That brings back the discovery problem the pagination was supposed to solve.

Deep pages rarely rank for competitive queries anyway, because page 1 collects most internal links and relevance signals. Their main SEO job is to pass crawlers to the items they list. Keep them indexable, give them a clear title such as "Running shoes, page 3", and avoid copying the long introductory text of page 1 onto every page of the series.

What about view-all pages?

A view-all page displays the whole list on a single URL. In a 2011 Search Central post, Google said users often prefer a view-all page and suggested pointing paginated pages to it with a canonical tag when it loads quickly. Google's current pagination documentation no longer mentions this option. In practice, a view-all page only makes sense for short lists, a few dozen items at most, where the full page stays fast. For large catalogs, a single page with hundreds of products hurts loading time and Core Web Vitals, so classic pagination is the safer choice.

How do infinite scroll and "load more" affect SEO?

Infinite scroll

Infinite scroll loads new items as the visitor scrolls down. Google's crawlers do not scroll or trigger actions that require a user, so items loaded this way can stay invisible. The fix is to back the infinite scroll with paginated URLs: each batch of items has its own address (for example ?page=3), the browser address updates as the user scrolls, and the pages are linked with crawlable links that work without JavaScript.

Load more buttons

A "load more" button has the same limitation: Googlebot does not click buttons. The button can stay for users, as long as it is a real link to the next paginated URL, or as long as the same items are reachable through a standard pagination block or the XML sitemap. Test it by disabling JavaScript in your browser: if you cannot reach page 2, neither can most crawlers.

How does pagination interact with faceted navigation?

Faceted navigation (filters by size, color, price, brand) multiplies URLs fast. A category with 10 pages, 5 sort orders and 20 filters can generate thousands of combinations, each one paginated. Google's guide to managing faceted navigation recommends deciding which versions deserve to be crawled at all:

• Block what you do not need: if filtered URLs have no search value, disallow their parameters in robots.txt, which Google describes as more effective long term than canonical tags for this purpose.
• Keep valuable filters indexable: a filter that matches real demand, such as "black running shoes", can deserve its own optimized, paginated page.
• Use consistent parameters: the standard "&" separator, a fixed filter order, and no duplicate filters in the same URL.
• Return 404 for empty results: filter combinations with no products, and pagination pages that do not exist, should not answer with a 200 status.

How should an e-commerce category handle pagination?

Take a category of 480 running shoes, 24 per page, so 20 pages. A sound setup looks like this:

1. Page 1 lives at /running-shoes/ with the full category text, links to subcategories and a self-referencing canonical.
2. Pages 2 to 20 live at /running-shoes/?page=2 to ?page=20, each with its own canonical, a title that includes the page number and no copy of the introduction.
3. Every page shows numbered links (first, previous, a few page numbers, next, last) as plain HTML links.
4. Sort options use a parameter blocked in robots.txt or carry a noindex, so only the default order is indexed.
5. All product URLs are listed in the XML sitemap, as a second discovery path.
6. Requests for ?page=21 and beyond return a 404.

The same logic applies to a blog archive: one URL per archive page, self-referencing canonicals, numbered links, and every article also reachable from category pages or related posts.

How do you audit pagination on your site?

A pagination audit takes less than an hour on most sites:

• Open a deep page (page 5 or more) and check its canonical tag in the source code.
• Disable JavaScript and confirm that the pagination links still exist and point to real URLs.
• Use the URL Inspection tool in Google Search Console on a deep page to see whether Google indexed it and which canonical it selected.
• Check the indexing report for large numbers of filter, sort or session parameter URLs.
• Request a page number beyond the last page and confirm the 404 status.

Conclusion

Pagination SEO comes down to a few rules from Google's own guidance: one unique URL per page, crawlable links between pages, a self-referencing canonical instead of a canonical to page 1, no reliance on rel="next" and rel="prev", and paginated URLs behind any infinite scroll or "load more" button. Control filters and sort orders so they do not flood the index, and give every item a second discovery path through the sitemap. To check the canonical, indexing tags and links of any paginated URL in seconds, run Sorank's free on-page SEO audit.