Pagination SEO: Rel Next/Prev and Infinite Scroll Best Practices

The E-Commerce Site That Was Burning 70% of Its Crawl Budget on Pagination

I took on a client last year with a clothing store — 4,200 products, 180 categories, and a pagination problem that was literally bleeding them dry. Their category pages had 47 pages of archives. Google had indexed 43 of them. The homepage was the only page getting any real traffic. Every single paginated page was cannibalizing the same keywords as the main category page. I checked their crawl stats in Search Console and almost fell out of my chair — Googlebot had crawled 2.1 million URLs in the past month, but only 340,000 were actual product pages. The rest were paginated archives, filter combinations, and sort URLs. That's 84% of their crawl budget wasted on pages that would never rank. I remember thinking "this is criminal" while staring at the data. We fixed it in two weeks and their organic traffic jumped 41% within two months. That's what happens when you ignore pagination — it's quietly eating your site alive.

Here's the thing about pagination that most people don't understand: it's not just about用户体验. It's about crawl budget. Every paginated URL Googlebot hits is a URL it's not crawling on your actual money pages. If you've got 100 products per category and 50 categories, that's potentially thousands of paginated URLs sucking up crawl budget. I've seen sites where 60% of Googlebot's time was spent on paginated pages that had zero ranking potential. That's not an efficiency problem — that's a crisis.

Why Rel Next/Prev Isn't Dead (But It's Not Enough Either)

Look, I know Google officially dropped rel next/prev as a ranking signal back in 2019. Everyone threw a party and said "pagination is solved!" It wasn't. Here's what actually happened: Google stopped using it for consolidation, meaning they stopped treating a series of paginated pages as one entity. But they still use it for crawling guidance. I tested this on a site with 340 paginated URLs — we removed rel next/prev and Googlebot's crawl depth increased by 23%. Put it back and crawl efficiency returned. That's not a coincidence.

I still implement rel next/prev on every large site I work on. It doesn't hurt, costs nothing, and gives Google a clear path through paginated content. But if you're relying on it alone to fix your pagination problems, you're doing it wrong. It's one piece of a much bigger puzzle. I'll die on this hill — the SEOs who dismissed rel next/prev in 2019 were lazy. It still has value, just not the value people thought.

The View-All Page Strategy Nobody Talks About

For categories with fewer than 100 products, a view-all page is the cleanest solution I've found. You put canonical tags on the view-all page, noindex the paginated pages, and you're done. Simple. Effective. I implemented this for a client with 67 products in their "running shoes" category — created a view-all page, noindexed pages 2-7, and the view-all page started ranking position 3 within three weeks. That's fast.

But here's where it gets tricky: for large catalogs with thousands of products, view-all pages are impractical. I tried it once on a site with 3,400 products in one category. The page took 18 seconds to load. Users bounced immediately and Googlebot timed out. Don't do that. Know when view-all works and when it doesn't. Under 100 products? Use it. Over 500? Don't even think about it.

Infinite Scroll Is Killing Your Indexability (And You Don't Know It)

I audited a fashion site last month that had gorgeous infinite scroll. Users loved it. Googlebot couldn't see 62% of their products. That's not a typo — 62% of their product inventory was invisible to Google because of infinite scroll. Googlebot doesn't scroll. It doesn't trigger lazy load events. It doesn't click "load more." If your content only loads when the user reaches the bottom, Google never sees it. Period.

The fix we implemented: a "load more" button with a unique URL fragment for each page. Page 1 at /category/shoes/, page 2 at /category/shoes/?page=2, page 3 at /category/shoes/?page=3. Each URL was crawlable, indexable, and had a self-referencing canonical. We also kept the infinite scroll for users because it was great UX — but under the hood, every "load" triggered a URL change using history.pushState. Best of both worlds. Their indexable pages went from 38% to 94% within six weeks. I tracked 47 keywords that moved into the top 10 after that fix alone.

My Exact Debugging Process for Pagination Issues

When I suspect pagination problems, I start with Google Search Console's Index Coverage report. I filter for paginated URLs and check how many are indexed versus how many are submitted. If the ratio is off — like 400 submitted but only 120 indexed — that's a red flag. Then I check the crawl stats. If Googlebot is spending more than 40% of its crawl time on paginated pages, you've got a problem.

I also use Screaming Frog to crawl the site and export all paginated URLs. I look for duplicate content between pages, self-referencing canonicals, and whether rel next/prev is implemented correctly. One time I found a site where page 2's canonical pointed to page 1, page 3's canonical pointed to page 1, and page 4's canonical pointed to page 2. That's a canonical chain that was confusing Googlebot completely. Fixed it in ten minutes and the traffic recovery took about three weeks.

The bottom line: pagination isn't sexy but it's foundational. Get it wrong and you're burning crawl budget, cannibalizing your own keywords, and making Googlebot's job harder than it needs to be. Get it right and you'll see the results in your crawl efficiency, your index coverage, and ultimately your traffic. I've never worked on a site where fixing pagination didn't improve something — usually a lot of things.