Here's something I see in almost every technical SEO audit I run: a site that's losing crawl budget — quietly, consistently — because of pagination that nobody set up correctly.
It's not glamorous. Pagination doesn't get the attention that backlinks or Core Web Vitals do. But get it wrong, and you're essentially asking Google to waste its time crawling page 47 of your blog archive while your actual money pages sit unvisited and under-indexed.
So let's fix that. This guide covers every real pagination SEO problem worth knowing about in 2026, the myths you can stop worrying about, and the practical fixes that actually work.
What Is Pagination in SEO — and Why Does It Matter?
Pagination is what happens when a large set of content gets split across multiple pages. Your blog archive, category pages on an e-commerce site, product listings, forum threads — if you're navigating through page 1, page 2, page 3 of any content list, that's pagination.
From an SEO standpoint, pagination matters for three reasons:
- Crawl budget: Every paginated URL takes up a portion of the crawl budget Googlebot allocates to your site. If page 12 and page 13 of a blog archive are getting crawled repeatedly, those resources aren't being spent on product pages or new content that actually drives revenue.
- Indexation: Pages that Googlebot can't reach or doesn't see as valuable won't get indexed — which means any content sitting on page 6 of your category listing might as well not exist.
- Internal link equity: Pagination creates the link pathways that pass authority from your main pages down to individual products, posts, and content. Break those pathways and you're cutting off equity flow to your deepest pages.
The 6 Most Common Pagination SEO Issues
Canonical Tags Pointing Back to Page 1
This one's probably the single most damaging pagination mistake I come across. A developer sets up pagination and adds a canonical tag on page 2, page 3, and beyond — all pointing back to page 1. The intention seems logical: "page 1 is the main page, so it should be canonical."
But here's what actually happens. By canonicalising page 2 through page N back to page 1, you're telling Google those pages are duplicates of page 1. Google then stops crawling them, stops passing link equity through them, and stops indexing the content on those pages. Every product or post that only appears on page 3 and beyond? Effectively invisible.
<link rel="canonical" href="https://yoursite.com/category/shoes/" />Page 2:
<link rel="canonical" href="https://yoursite.com/category/shoes/page/2/" />Page 3:
<link rel="canonical" href="https://yoursite.com/category/shoes/page/3/" />Each page is canonical to itself. That's it. Simple, but it's what Google needs.
JavaScript-Only Pagination Links
Modern frameworks love JavaScript. React, Vue, Angular, Next.js — they all make it easy to build slick, dynamic pagination that feels smooth for users. The problem? Googlebot often can't follow JavaScript-rendered links the same way it follows plain HTML anchor tags.
Two specific patterns break crawlability completely:
- Hash-based URLs: If clicking "next page" changes the URL to
yoursite.com/category#page=2, Google treats that hash as the same URL as page 1. It's not a new URL. It won't be indexed separately. Everything past page 1 is invisible to the crawler. - JavaScript-only buttons: If your "Next" button triggers a JavaScript function that loads new content but doesn't produce a crawlable
<a href>link, Googlebot literally can't follow it. It can see the button, but it can't navigate through it.
<a href="/page/2/"> HTML anchor tags in the server-rendered HTML. The safest approach is progressive enhancement: ship real paginated links as server-rendered HTML first, then layer any JavaScript/AJAX behaviour on top for users. Users get the fancy experience. Crawlers get the clean links.
Noindex Tags on Paginated Pages
Sometimes sites add noindex to all paginated pages beyond page 1 — again, the thinking being that those pages shouldn't rank in search results. And sometimes that's a reasonable choice. But there's a critical consequence most people miss: noindex doesn't mean nofollow.
Here's the nuance. Googlebot will still crawl a noindex page, but over time — as it repeatedly finds those pages marked noindex — it de-prioritises crawling them. Which means the internal links on those pages (to individual products, posts, etc.) stop being followed reliably. You've now blocked the main link pathway to your deepest content.
Crawl Depth Getting Too Deep
Google's crawlers don't crawl infinitely deep. The further a page is from your homepage in terms of click depth, the less frequently it gets crawled — and for large sites with hundreds of paginated pages, important content can end up buried 10, 15, even 20+ clicks from the homepage.
Think about what that means for page 50 of a product category. To get there, Googlebot has to crawl pages 1 through 49 first. That's 49 intermediate crawls just to reach one page. In practice, it often doesn't bother.
Faceted Navigation Creating Infinite URL Variants
This one's particularly common on e-commerce sites. Faceted navigation — filtering by colour, size, price, brand — can generate hundreds of thousands of unique URL combinations. /shoes/red/, /shoes/red/size-8/, /shoes/red/size-8/nike/ — each filter combination becomes a new URL, and most of them are thin variations of the same content.
The result is Googlebot spending an enormous amount of crawl budget on near-duplicate filter combination pages while the pages that actually drive revenue — individual product pages — get crawled far less frequently than they should.
noindex to faceted filter combinations that don't have significant search volume or unique value. Use canonical tags to consolidate near-duplicate filter pages to the root category URL. And use robots.txt or parameter handling in Google Search Console to prevent Googlebot from crawling the most prolific URL combinations entirely.
Infinite Scroll With No Crawlable URLs
Infinite scroll is great for user experience. Products or posts just keep loading as you scroll — no clicking required. But unless it's implemented correctly, Googlebot sees only the initial content that loads on page load. Everything below that? Invisible.
The fix isn't to abandon infinite scroll. It's to build a paginated series underneath it. Real URLs, real anchor links, server-rendered HTML — users get the scroll experience, crawlers get the pages. Both can coexist with progressive enhancement, and plenty of major sites do exactly this.
The Myth That Won't Die — rel=prev/next
If you've seen rel=prev/next in a technical audit recommendation recently, that's an outdated checklist. Skip it and spend that time on self-referencing canonicals, crawlable anchor links, and crawl depth — those are the things that actually move the needle.
How to Audit Your Pagination SEO — Step by Step
/page/, ?page=, or ?p=) and check the canonical tag on each one. Self-referencing? Good. Pointing to page 1? Problem.<a href> tag? Or is it a JavaScript button with no crawlable anchor? This one check alone surfaces a lot of crawlability issues.Pagination Best Practices That Still Hold in 2026
- Self-referencing canonicals on every paginated page. Non-negotiable. Page 3 points to page 3. Not page 1.
- Real HTML anchor links for all pagination controls. No JavaScript-only buttons. No hash-based URLs. Real
<a href>tags in the server-rendered HTML. - Keep each paginated page unique and valuable. If pages 2 through 50 have identical metadata, descriptions, and no unique content beyond the item list, they're contributing very little SEO value. Even small differences in H1, title tag, and meta description help signal distinct value.
- Allow paginated pages to be indexed by default. Unless you have a specific crawl budget reason to noindex them, let them be crawlable. They're the link pathways to your content.
- Include jump links in large pagination blocks. Don't force Googlebot to crawl sequentially through 50 pages. Give it shortcuts to the middle and end of the series.
- For infinite scroll: build a paginated URL structure underneath it. Users see the scroll. Crawlers follow the links. Both work, and neither has to compromise.
- Monitor crawl stats monthly. Pagination issues develop gradually as sites grow. A category that had 5 pages last year might have 30 now — and the crawl budget picture changes with it.
Frequently Asked Questions
Generally, you should let paginated pages be indexed. They're the internal link pathways that connect your category or archive pages to individual content and product pages. Noindexing them can cut off the only crawl route to content on page 3, 5, or 10 of a listing. The exception is when pagination is generating thin, low-value pages (like faceted filter combinations with very few products) that are consuming crawl budget without delivering value.
No. Google confirmed in 2019 that it no longer uses rel=prev/next as an indexing signal — and said it hadn't used them for several years before that. Focus on self-referencing canonicals and crawlable anchor links instead. Those are the signals that actually influence how Google crawls and indexes your pagination.
No — and this is the single most damaging pagination mistake I see in audits. Canonicalising page 2 to page 1 tells Google those pages are duplicates that shouldn't be indexed, which also devalues all the internal links running through them. Use self-referencing canonicals instead. Page 2 is not a duplicate of page 1 — it has different products or posts on it. Treat it as what it is: a distinct page.
Not if it's implemented correctly. The key is to build a paginated URL structure underneath the scroll experience — real URLs, server-rendered HTML anchor links, crawlable pages. Users get the scroll, crawlers get the links. Where infinite scroll causes real SEO problems is when there's no underlying URL structure and Googlebot can only see the first screenful of content.
Significantly on larger sites. Every paginated URL takes up a portion of the crawl budget Google allocates to your site. If you have 200 pagination pages that are getting crawled repeatedly, that's budget not being spent on product pages, blog posts, or new content. The goal is to make your most valuable pages the ones Googlebot prioritises — which means keeping pagination as lean and efficient as possible, with jump links to reduce sequential crawl requirements.
Google's e-commerce documentation suggests 24–48 items per page as a reasonable range. Too few items per page means more pagination pages and more crawl overhead. Too many items per page can slow down page load and hurt Core Web Vitals. 24–48 is a practical sweet spot for most e-commerce and listing pages, but the right number really depends on your content type and page performance.
Check three things in Google Search Console. First, look at your Index Coverage report and see what percentage of indexed URLs are pagination pages. Second, look at your Crawl Stats to see which pages are consuming the most crawl budget. Third, use URL Inspection on a few of your deep paginated pages to confirm they're indexed and that the canonical is set correctly. If pagination pages dominate your indexed URL count and crawl budget while your content pages are barely being crawled, you've got a problem worth fixing.
Pagination issues are genuinely fixable. Most of them come down to three things: the wrong canonical setup, JavaScript links that crawlers can't follow, and crawl depth that's grown out of control as a site has scaled. None of those are complex problems — they just need to be found first, which is why a proper technical SEO audit matters.
At Wevlopers, we run deep technical audits that surface exactly these kinds of structural issues — the ones that are quietly costing sites indexation and traffic without any obvious warning signs. If you think pagination might be one of them, let's take a look.
