TECHNICAL
Pagination SEO: How to Handle Paginated Content Without Losing Rankings
Paginated content — blog archives, category listings, search results, comment threads — creates SEO challenges around content fragmentation, crawl budget waste, and thin page indexing. Here's the complete guide to pagination SEO: what works, what Google recommends, and what to avoid.
Published July 13, 2026 · 8 min read
Pagination is a common pattern on content-heavy websites: instead of loading all content on one page, it's split across /page/2, /page/3, and so on. Blog archives, e-commerce category pages, search result listings, and comment sections are common pagination use cases.
From an SEO perspective, pagination creates several problems: content fragmentation (the most valuable content on page 2 or 3 receives less ranking signal than if it were on a single page), crawl budget consumption (Googlebot must visit many URLs to discover paginated content), and thin page risk (page 15 of a blog archive may have little unique value as a standalone URL).
What happened to rel=prev/next
For years, the recommended approach to paginating content for search engines was the rel="prev" / rel="next" link attribute pair — placed in the <head> of paginated pages to signal to Google that they formed a series. This told Google to consolidate the series for indexing purposes and typically resulted in the first page (page 1) being indexed as the canonical for the series.
Google dropped support for rel=prev/next in 2019. They announced they had not used the signal for indexing purposes for several years before dropping it officially. Bing still supports rel=prev/next. For Google, however, this approach is no longer relevant.
The removal doesn't mean paginated pages are automatically mishandled — it means you need to implement a deliberate strategy rather than relying on this signal.
Current Google recommendations for pagination
Google's current guidance is pragmatic: paginated pages should serve users and should be crawlable. The specific technical implementation depends on the use case.
For paginated content that should be indexed: paginated category pages on e-commerce sites, or blog index pages, may have legitimate indexing value if each page contains unique, valuable content. If the content on page 3 of your product category includes products not on pages 1 or 2, those products need to be discoverable via some indexable path — the paginated category page serves that function.
For paginated content where only page 1 should be indexed: blog archives, where all individual posts are already indexed via their own URLs, are a common case where pages 2–N of the archive provide no unique value as standalone indexed URLs — they're navigation devices, not content destinations. In this case, adding noindex to pages 2–N removes thin, low-value archive pages from the index while keeping the individual post pages indexed.
For search results and filters: paginated search results pages (site search, filtered product listings with URL parameters) are typically best handled with noindex or canonical tags pointing to the unfiltered page, as these pages don't provide standalone value for external searchers.
Pagination implementation strategies
Strategy 1: Let pagination index (for content-value use cases). If each paginated page contains valuable, unique content that users might reach directly from search, allow it to index normally. Ensure each paginated URL is canonical to itself (not to page 1), has a unique and descriptive title tag (not Category | Page 2), and is included in the sitemap. This is appropriate for paginated product listings where each page contains distinct products.
Strategy 2: Noindex pages 2–N (for archive-style pagination). Add <meta name="robots" content="noindex, follow"> (or robots: noindex in Next.js generateMetadata()) to all paginated pages except page 1. The follow directive ensures Googlebot continues crawling the links on those pages (following links to individual posts) — so the posts are still discovered. The paginated archive pages themselves are removed from the index. This is appropriate for blog archives, news archives, and comment paginations.
Strategy 3: Canonical page 1 on all paginated pages. Adding <link rel="canonical" href="/blog/"> on /blog/page/2 tells Google that page 1 is the preferred URL for the series. All ranking signal consolidates to page 1. This is less aggressive than noindex (the pages can still be crawled and followed) but removes their standalone ranking potential. The downside: if Google chooses to honour the canonical (it's a hint, not a directive), pages 2–N are ignored for indexing. If it ignores the canonical, the pages may still be indexed as low-value thin pages.
Strategy 4: View-all page (if feasible). Google has stated that a single-page "view all" version of paginated content (showing all products, all posts) is often preferred to pagination for indexing — it consolidates all content signals on one URL. This is only practical for content volumes small enough to render on a single page without performance degradation. For large catalogues (1,000+ products), a view-all page is typically not feasible.
Strategy 5: Infinite scroll with pushState. Infinite scroll replaces paginated URLs with continuous loading. For SEO, infinite scroll needs careful implementation: use history.pushState() to update the URL as new content loads (so individual "sections" of the infinite scroll have addressable URLs); implement a fallback paginated version for users with JavaScript disabled (and for Googlebot when JavaScript rendering is limited); ensure the progressive loading doesn't prevent Googlebot from discovering content below the initial fold. Google can render some JavaScript infinite scroll implementations, but the reliability depends on the complexity of the implementation.
Crawl budget implications
Every paginated URL consumes crawl budget. A blog with 500 posts paginated 10 per page generates 50 archive URLs — plus tag and category pages, which may also be paginated. For smaller sites, this isn't a practical concern. For large sites (hundreds of thousands of URLs), paginated archive pages competing with important content pages for crawl budget is a real issue.
The noindex approach reduces crawl budget consumption on paginated archives — while noindexed pages are still crawlable (and should be, so Googlebot follows links to individual posts), Google's systems typically reduce crawl frequency on noindexed URLs over time.
What to avoid
Don't block paginated pages with robots.txt. If you Disallow: /page/ in robots.txt, Googlebot cannot crawl the internal links on those pages — meaning content that only appears on page 2+ of an archive may never be discovered. Blocking crawling is more aggressive than blocking indexing. Use noindex (which allows crawling, blocks indexing) instead of robots.txt disallow.
Don't canonicalize page 1 via duplicate content. Some implementations copy page 1's content to /page/1 and /category/, creating duplicate content rather than pagination. Each page in the series should contain distinct content (different set of results); if they overlap, that's a separate canonicalization issue.
Don't use noindex when content isn't indexed elsewhere. If the only way Googlebot can discover a product is via page 3 of the category listing, and you noindex page 3, that product may not be indexed. Ensure every important page has an indexable path to it — either a paginated page that's indexed, a sitemap entry, or an internal link from an indexed page.
Frequently asked questions
Should I noindex paginated archive pages?
For blog archives and news archives where individual posts are the indexable content, yes — noindexing pages 2–N of the archive typically improves crawl efficiency without impacting the indexing of individual posts. The follow attribute on the noindex directive ensures Googlebot continues crawling links on those pages, so post discovery is maintained. For product category pages where the paginated listing is the entry point for products, the decision is more nuanced: if page 3 contains products not indexed through any other path, noindexing page 3 may prevent those products from being indexed.
Does pagination hurt SEO?
Pagination itself doesn't hurt SEO, but poorly implemented pagination does. The specific risks: thin, low-value archive pages competing for crawl budget (fixable with noindex or allowing crawl-but-not-index); content fragmentation where the most valuable product or post is on page 12 and only reachable through 11 previous paginated pages (fixable with XML sitemap entries for all important content); and duplicate title tags across paginated pages ("Category | Page 1", "Category | Page 2" — thin variation, low value). Implementing a deliberate pagination strategy eliminates these issues.
Does Google treat page 2 of a category the same as page 1?
Not quite. Page 1 of a paginated series has advantages: it receives all internal links that point to the category URL without a page parameter, it's typically in the navigation, and it has the most external links (most linkers link to /category/, not /category/page/3). Pages 2–N typically have fewer links pointing to them and less ranking signal for the category query. Whether this is a problem depends on whether you want pages 2–N to rank as standalone results — for archive navigation pages, you probably don't; for product listings, you may want all category pages to rank for the category's keyword.
What replaced rel=prev/next for Google?
Nothing directly replaced it as a signal — Google simply removed reliance on rel=prev/next and now evaluates paginated pages like any other page. The practical implication: if you want page 1 to be the canonical for the series, implement a canonical tag pointing from pages 2–N to page 1. If you want pages 2–N to be excluded from the index entirely, use noindex. If you want all pages indexed, ensure each has unique content and a descriptive title. The prior convenience of a single rel=next/prev pair automatically consolidating the series is gone — explicit canonical or noindex declarations are now required.
MORE FROM THE BLOG
Related articles
11 min read
YouTube SEO: How to Rank Videos on YouTube and Google Search
YouTube SEO covers title optimisation, description keyword placement, chapters, thumbnails, closed captions, and the watch signals that drive YouTube and Google ranking.
Read →7 min read
Voice Search SEO: How to Optimise for Voice Queries and AI Assistants
How voice search queries differ from typed queries, what technical signals (FAQ schema, speakable schema, featured snippet eligibility) matter for voice results, and why optimising for voice search overlaps heavily with AI visibility.
Read →10 min read
TikTok SEO: How to Rank in TikTok Search and Get Discovered in Google
TikTok SEO covers how to optimise videos for TikTok's internal search algorithm, how TikTok content ranks in Google Search, and how TikTok presence feeds into AI answer systems.
Read →Run DeepSEOAnalysis on your own site.
Free, no signup. Technical SEO, Core Web Vitals, structured data, and AI visibility in one report.
Run a free audit →