Ecommerce Pagination SEO: How to Handle Page 2, 3... Without Losing Rankings

In 2019, Google quietly deprecated rel=next and rel=prev — the HTML attributes that told Googlebot how paginated series of pages were related. For years, ecommerce SEOs used these tags to handle category pagination. When Google dropped support, it left a gap in best practice guidance that still causes confusion in 2026.

This guide covers what actually works for ecommerce pagination SEO today.

The Problem With Pagination

A category page with 500 products split across 50 pages creates 50 indexable URLs with nearly identical content (same category name, same navigation, different product subset). Without controls, this causes:

• Crawl budget waste — Google crawls page 47 of a low-traffic category instead of your new product pages
• Thin content indexation — Pages 2-50 often rank for nothing useful but consume index quota
• Diluted signals — Links to your category page are split across all 50 URLs instead of consolidating on page 1

What Google Says Today

Google's current guidance is to "think about what's the best user experience" and ensure paginated pages are "crawlable and indexable if useful." They explicitly say there's no special treatment for paginated series — they're just regular pages.

In practice, this means you have to make deliberate choices about which paginated pages deserve to be indexed and which don't.

The Best Approaches for Ecommerce Pagination

Option 1: Infinite Scroll / Load More (Recommended for Most Stores)

Replace paginated pages with infinite scroll or a "Load More" button that loads additional products via JavaScript. All products are accessible to users without creating multiple indexable URLs.

Implementation note: Googlebot can render JavaScript, but only if your products are in the initial HTML or loaded via lazy-loading patterns Google can follow. Test with Google's URL Inspection tool — if products only appear in the JS-rendered view, Google may or may not see them reliably.

Best practice: use intersection observer for load-more, not infinite scroll, as it gives users more control and clearer paging for browser history.

Option 2: Canonical Page 1 for All Pagination

If you keep paginated URLs, add a canonical tag on pages 2-N pointing to page 1. This consolidates link equity to the primary category page and signals to Google that the paginated versions aren't distinct SEO targets.

<!-- On /collections/running-shoes?page=3 -->
<link rel="canonical" href="https://yourstore.com/collections/running-shoes" />

Tradeoff: Products on page 2+ won't be indexed in the paginated context. If you have a lot of inventory, some products may only be discoverable via their own product page URLs, not via category browsing in search results.

Option 3: Noindex on Deeper Pages

Add <meta name="robots" content="noindex, follow"> to pages 2+. This keeps them accessible to users but prevents indexation. The follow is important — Googlebot still crawls and follows links on these pages, indexing the individual product pages they contain.

This is effectively the same signal as the canonical approach but cleaner for cases where you don't want any canonical confusion.

Option 4: Index All Pages With Strong Unique Content

For very large stores where pagination pages naturally differentiate by product (e.g., page 1 has products A-F, page 2 has G-L), allow indexation but ensure each page has:

• A unique title tag: "Running Shoes — Page 2 | YourStore" (though this targets no real search query)
• A unique meta description summarizing what's on that page
• An H1 that doesn't duplicate page 1's H1 exactly

Honestly, this approach rarely works well in practice. Few users search for "running shoes page 3."

View All: Sometimes the Best Option

For categories with fewer than 200-300 products, a "View All" page that shows all products on a single URL is often the cleanest SEO solution. No duplicate pages, full product inventory visible to Googlebot, maximum link equity consolidation.

Performance concerns: lazy-load product images (intersection observer) and defer non-critical resources. A view-all page with 200 products can load fast if images below the fold are deferred.

What Platform Defaults Do

• Shopify — Creates /collections/slug?page=2 URLs. These are indexable by default. Many stores either convert to AJAX-based pagination or add noindex to pages 2+.
• WooCommerce — Creates /product-category/slug/page/2/ URLs. Default Yoast SEO settings typically noindex these.
• BigCommerce — Uses ?page=2 format. Handles pagination reasonably well natively, but review your specific theme's implementation.

Checking Your Current Setup

1. Google Search Console → Coverage — Are paginated pages appearing as "Indexed" in large numbers? That's a signal to add controls.
2. Search: site:yourstore.com inurl:?page= — Shows Google-indexed paginated URLs.
3. Crawl your site — A health scan identifies pages without canonical tags and noindex pages that are still being linked to.

Pagination is often the invisible culprit behind bloated index counts and crawl budget issues. A thorough technical audit with StoreVitals surfaces these patterns before they compound into ranking problems that take months to unwind.