Pagination

Pagination is the practice of splitting a long list of items across multiple pages — /blog?page=2, /products/category/page/3/, /news/2026/01/. This is best practice on blog archives, e-commerce category pages, and any large catalogue.

Done well, pagination makes content more navigable and accessible. Done wrong, pagination can significantly weaken a website's primary content, as well as create indexing problems.

Why paginate content

Loading 1,000 products on a single category page would be painfully slow and ultimately unusable. Pagination breaks this list into manageable chunks, e.g., 10, 20, or 30 items per page (or whatever number is appropriate for the content). The trade-off is that pagination creates many new category URLs with similar datasets; if not managed correctly, these can cause significant SEO issues.

How Google treats pagination

Google evaluates each paginated URL independently, deciding:

• Whether to index it (based on uniqueness, quality, and value).
• Which URL ranks for which queries (typically page 1 for category-level queries, deeper pages for specific item queries).
• How much crawl budget to allocate to these sub-pages.

For most sites, page 1 (www.example.com/category/) will function as the primary category page — it has the strongest internal links and the most visited content. Deeper pages usually function more for navigation and UX, but these sub-pages are capable of ranking in SERPs and generating traffic.

Pagination approaches

1. Standard numbered pagination

The two most common patterns are URL parameters (?page=2) or path segments (/page/2/).

SEO recommendations that are often missed: - Self-referencing canonicals on each page (/category?page=2 canonicals to itself, not to page 1). - Allow indexing by default. Pages 2+ still hold valuable items that deserve to rank. - Internal links that provide navigation through the pagination, e.g., page number links, first page, previous, next, last.

An old recommendation that still sometimes surfaces is to canonicalize pages 2+ to page 1. This is wrong in most cases — it tells Google that pages 2+ are duplicates of page 1, which leads to deindexing of all the items those deeper pages contain.

2. View-all page

Some sites offer a single "view all" URL alongside paginated versions, with the paginated pages canonicalizing to the view-all version. This somewhat defeats the purpose of pagination.

If a single page works well for users and search engines, why paginate it in the first place? Pick the appropriate approach for the volume of content, and stick to it.

3. Infinite scroll

Items load dynamically as the user scrolls, with no pagination buttons. Without backing URLs*, this is invisible to many crawlers — items beyond the first page render may not be crawled.

*The fix: implement infinite scroll with paginated URL fallbacks. Each "page" of items has a real URL (/category?page=2) that loads when accessed directly, even if the in-browser experience is infinite scroll. This is sometimes called "progressive enhancement" or "history-aware infinite scroll" — it provides the user experience of infinite scrolling while still providing content in a crawler-accessible way.

4. "Load more" buttons

Similar to infinite scroll but click-triggered. This poses the same issues as above: subsequent items must be reachable via crawlable URLs.

Common pagination mistakes

Canonicalizing paginated pages to page 1

Tells Google "these are duplicates of page 1." Deeper items get dropped from the index. The right canonical is the page itself.

Noindexing paginated pages

Sometimes appropriate (e.g., for thin tag archives) but detrimental for primary category pages, where you want products on pages 2+ discoverable. Use noindex selectively in pagination, not as a default.

Adding paginated URLs to the sitemap

Not technically "wrong", but largely unnecessary. Having page 1 of each category in the sitemap is sufficient to ensure sub-pages are crawled as long as appropriate navigation is implemented.

Inconsistent URL patterns

Mixing ?page=2 and /page/2/ for different category structures within the same site. Pick one pattern and use it everywhere.

No links to deep pages

If pagination only shows "1, 2, ... last", users can navigate, but search engines may not crawl middle pages efficiently. Show a reasonable number of page links to make subpages reachable in as few clicks as practical.

Page 1 specifically

Page 1 of any series is the most important page — it gets the brand backlinks, the navigation links, and the main keyword traffic. For the first page:

• Use the parameter-free URL (/category, not /category?page=1).
• Canonical to itself.
• Include in the sitemap.
• Optimise for the head category keyword.

A pagination policy checklist

For each paginated series on the site:

1. One URL pattern — ?page=2 or /page/2/, not both.
2. Page 1 has no ?page=1 parameter — and any URL with ?page=1 redirects to the parameter-free version.
3. Self-referencing canonicals on every page.
4. Allow indexing unless there's a specific reason not to.
5. Real, crawlable links between pages (not JavaScript-only navigation).
6. Page 1 only in the sitemap.
7. Infinite scroll backed by paginated URLs if used.

Bots, crawlers, and linking

Disclaimer: All information contained herein is for informational purposes only. It is not advice or instructional.