Pagination SEO: Best Practices for Numbered Pages and Infinite Scroll

Pagination seems simple on the surface — just break content into pages, right? In practice, pagination is one of the most technically nuanced challenges in SEO. Done wrong, it siloes link equity, wastes crawl budget, creates duplicate content issues, and leaves valuable content invisible to search engines. Done right, it distributes authority efficiently, maximizes indexation, and keeps both users and bots happy.

This complete guide covers everything you need to know about pagination SEO for numbered pages, infinite scroll implementations, load-more patterns, and the technical decisions that determine whether your paginated content helps or hurts your rankings.

Why Pagination SEO Matters More Than Most People Think

For many sites, pagination is an afterthought — a feature added to manage content volume without much thought about SEO implications. But for e-commerce sites with thousands of products, news sites with decades of archives, or blog sites with hundreds of posts, pagination is a foundational technical SEO issue that directly affects crawl efficiency, indexation rates, and link equity distribution.

Consider a typical e-commerce category page with 2,400 products, showing 24 per page — that’s 100 paginated pages. Each of those pages needs to be discovered, crawled, and evaluated by Googlebot. If your pagination implementation is poor, Googlebot may never reach products on pages 50-100, those products never get indexed, and they never rank. That’s a direct revenue impact.

The stakes are even higher for sites that combine pagination with faceted navigation (filtering by color, size, price range, etc.), where the combinatorial explosion of URLs can create millions of low-value, near-duplicate pages that drain crawl budget while producing zero SEO value.

Numbered Pagination: The SEO Fundamentals

Numbered pagination — the classic page 1, page 2, page 3 structure — remains the most SEO-compatible pagination pattern when implemented correctly. Here’s what “correctly” means in practice.

URL Structure for Paginated Pages

Your paginated URLs need to be clean, consistent, and crawlable. The best practice is path-based pagination:

https://example.com/category/shoes/
https://example.com/category/shoes/page/2/
https://example.com/category/shoes/page/3/

Avoid parameter-based pagination like ?page=2 or ?p=2 where possible. Parameter-based URLs complicate crawl management, can create duplicate issues, and are harder to canonicalize cleanly. If you must use parameters (common in legacy systems), ensure Google Search Console’s URL parameter handling is configured correctly and robots.txt is tuned appropriately.

Canonical Tags for Paginated Pages

This is where many sites make a critical mistake: adding a canonical tag on paginated pages pointing to page 1. This is wrong. If page 2 canonicalizes to page 1, Googlebot treats page 2 as a duplicate and stops crawling it — which means products, posts, or content on page 2 and beyond get ignored entirely.

The correct approach: each paginated page should self-canonicalize. Page 2’s canonical points to page 2. Page 3’s canonical points to page 3. The canonical tag should reflect the page’s own URL, signaling to Google that each page is a distinct, indexable entity.

What Happened to rel=prev/next?

In March 2019, Google announced it had deprecated support for rel="prev" and rel="next" link attributes, stating it had not used these signals “for a while.” Despite this, many SEO guides still recommend implementing these attributes. While Google ignores them, Bing still uses rel=prev/next signals. If you’re optimizing for Bing visibility, implementation is worthwhile — just don’t expect Google ranking benefits from it.

For Google, the relevant signals for pagination handling are canonical tags, internal linking structure, and the overall content value of each paginated page.

Unique Value on Every Paginated Page

A common thin content issue on paginated pages: every page has the same meta title, meta description, and H1, with only the product/content grid changing. This creates a near-duplicate signals problem. Each paginated page should have:

• A unique meta title that signals the page number: “Shoes – Page 2 | Brand Name”
• A unique meta description that reinforces distinct content
• Content that genuinely differs from adjacent pages

Page 1 of a category is often more valuable than deeper pages because it’s more likely to earn links and gets most of the internal link equity. But pages 2-N shouldn’t be treated as throwaway content — they contain products or posts that deserve to rank and convert.

Infinite Scroll: The SEO Minefield

Infinite scroll became popular for its smooth user experience — content loads seamlessly as users scroll, eliminating the friction of clicking “next page.” But from an SEO perspective, naive infinite scroll implementations are catastrophic: Googlebot cannot simulate scroll events, so all content below the initial viewport is effectively invisible to crawlers.

How Googlebot Handles JavaScript and Infinite Scroll

Googlebot renders JavaScript, but it does so on a delayed, resource-constrained basis. Even with JavaScript rendering, Googlebot does not simulate user interactions like scrolling. It renders what’s available in the initial page load — and with infinite scroll, that’s typically only the first batch of content.

This means that if your category page shows 12 products on initial load and loads more as users scroll, Googlebot may only see and index those 12 products. The remaining thousands of products are effectively hidden from Google.

The Correct Infinite Scroll Implementation for SEO

The solution, recommended by Google’s developer documentation, is to implement paginated fallback URLs alongside your infinite scroll experience. The pattern works like this:

1. Users on the site see a seamless infinite scroll experience (handled by JavaScript)
2. Underlying, each “batch” of loaded content corresponds to a distinct, crawlable URL (page/2/, page/3/, etc.)
3. When JavaScript is disabled or Googlebot renders the page, these paginated URLs are navigable via standard HTML links
4. Each paginated URL is indexable and contains unique content

This approach gives users the scroll experience they prefer while giving search engines the structured, crawlable content they need. It’s more implementation work — but it’s the only reliable way to maintain full indexation with infinite scroll.

The History API for Infinite Scroll

If you implement the fallback paginated URLs, you can use the History API (pushState) to update the URL in the browser bar as users scroll. This improves user experience (users can bookmark or share their position) and can help search engines understand content segmentation. However, History API implementation adds complexity and must be done carefully to avoid confusing crawlers.

Load More Buttons: The Middle Ground

“Load More” buttons — where users click a button to load additional content rather than scrolling infinitely — sit between numbered pagination and infinite scroll in terms of SEO friendliness.

Like infinite scroll, content loaded via AJAX in response to a Load More click may not be crawled by Googlebot. The same solution applies: implement paginated fallback URLs for each batch of content, with standard HTML links between pages that are visible even when JavaScript is disabled.

An alternative approach for Load More implementations is to make the “Load More” button a standard link to the next paginated URL (/page/2/) that triggers an AJAX load for JavaScript-enabled users while functioning as a normal page navigation for bots. This progressive enhancement approach is both SEO-friendly and user-friendly.

Crawl Budget Optimization for Paginated Sites

For large sites with extensive pagination, crawl budget management is critical. Googlebot allocates a finite crawl budget to each site — the number of pages it will crawl in a given time period. If paginated pages consume too much of that budget, important content goes uncrawled and unranked.

Identifying Crawl Budget Problems

Check Google Search Console’s crawl stats report to understand how Googlebot is spending its crawl budget on your site. Warning signs include:

• A high percentage of crawl activity concentrated on paginated or parameter URLs
• Important product or content pages showing as “Discovered – currently not indexed”
• A large gap between URLs submitted in sitemaps and URLs actually indexed

Log file analysis provides the most granular view of crawl budget allocation. Analyzing server logs to see exactly which URLs Googlebot is visiting, how often, and in what order reveals patterns that Search Console data alone can’t show. Our technical SEO audit services include comprehensive crawl budget analysis for sites with complex pagination.

robots.txt and Parameter Handling for Pagination

For sites with faceted navigation, using robots.txt to disallow crawling of low-value parameter combinations is often necessary. Be strategic: you want to block parameters that create near-duplicate pages (e.g., sort order variations, color filter combinations with minimal product overlap) while allowing crawling of parameters that create genuinely distinct, valuable pages.

Google Search Console’s URL Parameters tool (now deprecated in favor of guidance via Search Console and crawl stats) previously allowed explicit parameter handling instructions. Today, the best approach is combining robots.txt directives with careful internal link architecture — don’t link to low-value parameter variations from important pages.

XML Sitemaps for Paginated Content

Include your key paginated pages in XML sitemaps — but be selective. Don’t include pages 50-100 of a category with minimal unique content. Do include page 1 of every category, and pages 2-5 or so for your most important, highest-traffic categories where deep content has real value.

A common mistake is including all paginated pages in sitemaps, hoping Google will crawl them. This often backfires, as Google may discover but choose not to index thin paginated pages, wasting crawl budget on low-value URLs while signaling poor site quality.

Pagination and E-Commerce: Special Considerations

E-commerce sites face unique pagination challenges due to the combination of category pagination and faceted navigation. Here’s how to handle the most common scenarios.

Category Pages with Filters

When users filter a category (e.g., “shoes” filtered by “red” and “size 10”), the resulting URLs often look like /shoes/?color=red&size=10 or similar parameter combinations. Left unmanaged, these create thousands of near-duplicate pages that dilute crawl budget and can trigger duplicate content issues.

The recommended approach: allow filtering for user experience, but use noindex on filtered pages that don’t represent significant distinct content, and ensure they’re not linked from the main navigation or linked internally in ways that signal high importance to Google.

Product Listing Depth

Not all paginated pages deserve equal crawl priority. Page 1 of a major category is much more valuable than page 47. Structure your internal linking to reflect this: link to page 1 and page 2 from navigation and sitemaps, but don’t force Googlebot to crawl page 47 if it’s thin content.

Consider whether very deep paginated pages warrant their own indexation at all, or whether a flat product catalog approach (with search/filter functionality) would better serve both users and SEO. For very large catalogs, an indexed product search page may outperform deep pagination.

Measuring Pagination SEO Performance

After implementing pagination SEO improvements, track these metrics to measure impact:

Indexation Rate of Paginated Pages

In Google Search Console, use the Coverage report to track how many of your paginated pages are indexed versus excluded. After improvements, you should see fewer “Discovered – currently not indexed” pages and more successful indexation of deep pages containing valuable content.

Crawl Frequency of Priority Pages

Monitor crawl stats to verify that Googlebot is spending more of its budget on your high-value pages (key categories, top products) and less on low-value parameter variations and deep paginated pages with thin content.

Ranking and Traffic from Deep Pages

Products or posts that previously lived on page 5+ of category lists and were uncrawled may begin ranking for long-tail queries once they’re properly indexed. Track this through Search Console’s performance data, filtered to URL paths corresponding to deeper paginated content.

According to SEMrush’s technical SEO research, sites that resolve pagination issues see an average 12-25% increase in indexed page counts and corresponding improvements in organic traffic within 3 to 6 months of implementing fixes.

Working with an expert team on complex pagination issues can accelerate these results significantly. See how our SEO case studies demonstrate pagination optimization results for e-commerce clients.

Frequently Asked Questions

Should I use rel=prev/next for pagination?

Google officially deprecated rel=prev/next support in 2019, stating they had not used it for years. However, Bing still supports it. You can implement it for Bing compatibility, but do not rely on it for Google. Focus instead on canonical tags and internal link architecture for Google pagination management.

Is infinite scroll bad for SEO?

Infinite scroll is bad for SEO if implemented without a parallel paginated URL structure. Googlebot cannot execute JavaScript scroll events, so content loaded via infinite scroll is often invisible to crawlers. The solution is to implement paginated fallback URLs alongside infinite scroll for human users, ensuring all content has a crawlable, indexable URL.

Should paginated pages be noindexed?

Blanket noindexing of paginated pages is generally discouraged. Pages 2 and beyond may rank for specific long-tail queries and can pass link equity. However, very thin paginated pages with near-duplicate content may benefit from noindex. Evaluate on a case-by-case basis based on content value and competitive landscape for deep paginated pages.

How does pagination affect crawl budget?

Pagination can significantly consume crawl budget, especially on large e-commerce or news sites with thousands of paginated pages. Faceted navigation combined with pagination is particularly problematic. Use robots.txt to limit crawling of low-value paginated variations and ensure your most important pages are crawled first by strengthening their internal link profile.

What is the best pagination pattern for SEO?

Numbered pagination with clean, consistent path-based URLs is generally the most SEO-friendly pattern. Each page should have unique, valuable content, a canonical pointing to itself (not page 1), unique meta titles and descriptions indicating the page number, and clear internal linking between pages. Avoid blanket parameter-based pagination and faceted navigation URL proliferation where possible.