Pagination and SEO

Pagination creates multiple URLs from a single body of content: a blog archive split across 20 pages, a product category divided into pages of 24 items each, or a comment thread spread across 10 pages. Each paginated URL is technically distinct, and Google must decide what to do with them. The decisions you make about pagination structure affect crawl efficiency, indexation, and where ranking signals consolidate.

The end of rel=prev/next

Many technical SEO guides still recommend rel=prev and rel=next link attributes to signal paginated sequences to search engines. Google announced in March 2019 that it had never used these attributes for indexation and had dropped support for them entirely.¹ They have no effect on how Google handles paginated content.

The announcement surprised many SEOs because Google had previously implied these attributes were useful. The clarification confirmed what Google actually does: it analyses paginated content individually, makes independent indexation decisions for each URL, and does not use prev/next relationships to consolidate signals. Implementing rel=prev/next does no harm, but it also does no good.

How does Google handle paginated URLs?

Google’s approach to paginated content is largely pragmatic:

• It crawls paginated URLs if they are linked to (typically through “next page” links)
• It makes independent indexation decisions for each URL
• It rarely indexes deep paginated pages (beyond page 3 or 4) unless those pages have strong internal or external links pointing to them
• It does not automatically consolidate signals from paginated URLs to the first page

The practical result is that page 1 of a category typically ranks; pages 2 and beyond rarely do. Users searching for a product category will see the first page in results. They will not search for “page 14 of your shoes category.”

URL structure for paginated content

Paginated URLs can use path-based or parameter-based formats:

Path-based: /blog/page/2/, /category/shoes/2/ Parameter-based: /blog/?page=2, /category/shoes/?paged=2

Path-based URLs are preferable. They are more readable, less likely to be excluded by parameter-handling rules, and less likely to be treated as crawl noise. Parameter-based pagination URLs are more likely to be confused with other parameter types (tracking parameters, filter parameters) and harder to manage consistently.

Strategies for paginated content

Give each page its own canonical (Google’s documented approach): each paginated URL points its canonical at itself, and each can be crawled and indexed. Google’s ecommerce pagination guidance is explicit: “Don’t use the first page of a paginated sequence as the canonical page. Instead, give each page its own canonical URL.”² This suits a long-running blog where older posts have no other access path, or a product catalogue where pages 2+ list entirely different products.

Do not canonical deep pages to page 1. An older recommendation was to add <link rel="canonical" href="/category/shoes/"> to pages 2, 3, 4 and so on, to consolidate signals onto the first page. Google advises against it: because each paginated page shows different content, Google treats a page-2-to-page-1 canonical as a mis-canonicalisation and generally ignores it.² The signal consolidation this was meant to deliver does not reliably happen. If you do not want deep pages indexed, use noindex instead.

noindex on deep pages: prevents later pages from being indexed while still allowing Googlebot to crawl them (and follow links to individual product or post pages). Use when you are certain that users will never land on page 5 of a category from search, but you still want Googlebot to discover the content on those pages. The page must be crawlable for noindex to work; do not also block it in robots.txt.

Infinite scroll: presents an SEO challenge because paginated content only loads as users scroll. If implemented purely in JavaScript with no server-side HTML, Googlebot will only see the initial page load content. The correct implementation uses the History API to update the URL as users scroll (/category/shoes/, then /category/shoes/2/ as page 2 loads), and ensures each URL is accessible as a standalone page with its own server-rendered HTML.

Why is page 2 ranking instead of page 1?

A paginated URL outranking the page it belongs to is a common and frequently misdiagnosed problem. The instinct is to reach for a canonical pointing at page 1, which is the one fix guaranteed not to work. Work through the causes in this order.

Check whether it is a problem at all. Filter the Search Console Performance report by the paginated URL and read the queries it wins. If the query matches items that genuinely sit on page 2, Google has made a reasonable choice and page 1 has nothing better to offer it. The click still arrives. The only real cost is a reader landing halfway through a list, and that is a content problem rather than a canonical one.

Redirect ?page=1 to the bare URL. This is the one true duplicate in a paginated set, and it is the most common reason the parent URL loses to a numbered one. The same applies to any other parameter that renders the first page, such as ?start=0 or ?offset=0. Unlike page 2, these URLs are identical to the parent, so a 301 is correct here in a way it never is further into the sequence.

Give page 1 content the later pages cannot have. Most first pages are a bare listing, identical in template and wording to page 2, which leaves Google choosing between them on link signals alone. Put the descriptive introduction, the query-matching copy and any supporting sections on page 1 only, and let pages 2 and beyond carry the listing and nothing else. This is the durable fix, because it makes page 1 the only page in the set that matches the query.

Audit the internal links into the set. The parent URL should be what navigation, breadcrumbs and hub pages link to. Google’s pagination guidance also suggests linking back to the first page from every page in the collection, as a hint that page 1 is the better landing page.² Check external links too: a single decent link pointing at the ?page=2 URL can outweigh everything else you do.

Treat noindex on pages 2+ as a last resort. It works, but Google eventually treats links on a long-term noindexed page as nofollowed, so the items on those pages lose a discovery path. Only use it when every item is reachable another way, through the XML sitemap or other internal links. If the paginated page ranks for a genuinely distinct query, the better answer is usually that the query deserves its own filtered or sub-category URL rather than being suppressed.

URL Inspection on the paginated URL is the fastest first diagnostic: the Google-selected canonical and the referring page data usually separate a genuine duplicate from a differentiation problem in seconds.

Crawl waste from deep pagination

Deep pagination is one of the most common sources of crawl budget waste. A large e-commerce site with 500 category pages, each paginated to 50+ pages, can generate tens of thousands of paginated URLs. Most contain thin content and have no realistic search demand. Googlebot crawling them consumes budget that could be spent on product pages with actual ranking potential.

The fix is either to noindex deep paginated URLs, reduce the number of items shown per page (fewer pages total), or block deep pagination from crawling in robots.txt if the content on those pages is accessible through other means (individual product pages, sitemap links, internal category links).

Parameter-based pagination and Search Console

If your site uses parameter-based pagination (e.g. ?page=2), Google now handles parameter detection automatically. The Search Console URL Parameters tool was removed in April 2022.³ The reliable fixes are noindex on deep pages, or switching to path-based pagination. Do not reach for a canonical pointing at the first page: that is the mis-canonicalisation described above, and it is ignored whether the pagination is path-based or parameter-based.

Frequently asked questions

Does Google index paginated pages?
Sometimes, but rarely beyond the first few pages. The first page almost always has the strongest signals and is the version that ranks.

Should I noindex all pages after page 1?
Not necessarily. If deeper pages contain content users might search for directly, allow indexation. If they are thin or near-duplicate, noindex them.

Should I canonical pages 2+ to page 1?
No. Google advises against it and generally ignores such canonicals because the pages differ. Give each page a self-referencing canonical, and use noindex if you want to keep deep pages out of the index.

Footnotes

1. Pagination with rel=“next” and rel=“prev” — Google Search Central Blog (updated to note the attributes are no longer an indexing signal) ↩

2. Ecommerce pagination and incremental page loading — Google Search Central ↩ ↩² ↩³

3. Spring cleaning: the URL Parameters tool — Google Search Central Blog ↩