AI Summary
Pagination splits a long series such as category listings, blog archives, or search results across numbered pages. For SEO the goal is simple: let Googlebot crawl every page and index the deep items, which means giving each page its own crawlable URL and a self-referencing canonical, never collapsing them onto page 1.
- Google stopped using
rel=nextandrel=previn 2019 and treats each page individually; Bing still uses them. - Never canonicalize pages 2 and beyond to page 1: that hides deep content from the index.
- Avoid
noindexon paginated pages when they are the only path to deep items. - Infinite scroll needs real paginated URLs via
history.pushState, or crawlers cannot reach page 2.
Pagination is how a website breaks a long list into a numbered series of pages: a category with hundreds of products, a blog archive, a forum thread, or a set of search results. It looks trivial, but it is one of the most common places where large sites quietly lose deep content from the index. Get it wrong and the products or posts that only appear on page 5 never get crawled or indexed; get it right and every item in the series stays discoverable. This guide covers the modern, post rel=next/prev model that Google actually uses today.
This SEO case study documents a successful optimization initiative, providing actionable insights for practitioners. The documented approach demonstrates how strategic SEO implementation drives measurable results.
What pagination is and why it is an SEO problem
A paginated series is any single logical list spread across multiple URLs. The SEO risk is always the same: content that lives only on page 2 and beyond can become unreachable or be treated as a duplicate of page 1, so it never earns a place in the index. The job is to make sure Googlebot can crawl the whole series and understand that each page is a distinct step, not a copy. There are several ways to build pagination, and each has its own crawl handling.
| Method | How it works | SEO handling |
|---|---|---|
| Numbered pagination | Links to /page/2/ or ?page=2 | Crawlable anchor links, self-referencing canonical on each page |
| Load more button | A button fetches the next batch with JavaScript | Back it with real paginated URLs and provide link fallbacks |
| Infinite scroll | New items load automatically on scroll | Use history.pushState to map each batch to a crawlable URL |
| View-all page | The whole list on one URL | Fine when it loads fast; component pages can canonical to it |
One piece of history matters here. For years, sites used rel="next" and rel="prev" to tell Google how a series fit together. In 2019 Google stated it had not used those signals for indexing in a long time and had stopped supporting them. Bing still honors them and they help assistive technology, so there is no harm in keeping the markup, but they are not what makes pagination work for Google today. Crawlable links and correct canonicals are.
Initial Situation
Understanding the starting point is essential context for evaluating any case study. This documentation covers the initial challenges, competitive position, and business objectives that shaped the SEO strategy.
Start by classifying your pagination: is it a category listing, a blog or archive, on-site search, or a forum thread, and how deep does it go? Then check whether the deep pages are actually indexed. In Google Search Console, open the Pages report and look for later paginated URLs sitting in "Crawled, currently not indexed" or "Discovered, currently not indexed," and inspect a page 3 or page 4 URL to see the canonical Google selected. If Google reports the user-declared canonical as page 1 while you expected self-canonical, you have found the leak. This same discovery-versus-indexing tension is what makes crawl budget and pagination two sides of the same coin on large sites.
Strategy and Approach
The strategic approach combined multiple SEO disciplines to address identified opportunities. Key decisions around prioritization and resource allocation provide a template for similar initiatives.
The modern strategy is to treat every page in the series as a first-class, indexable URL. Give each one a unique address, a self-referencing canonical, and real anchor links in the HTML so both users and crawlers can walk the series. Decide early whether a View-all page is viable: if the full list is light enough to load quickly, it can simplify everything, but for long catalogs the numbered approach is safer. Above all, resist the two instincts that feel tidy but quietly remove content from Google: canonicalizing everything to page 1, and adding noindex to the later pages.
Implementation
Moving from strategy to execution required specific technical implementations, content development, and process changes. This case study documents the practical steps that translated strategy into action.
Implementation comes down to a short, strict checklist. Use one consistent URL scheme (a query parameter or a path segment) and make sure the pagination controls are crawlable anchors, not JavaScript-only buttons. Put a self-referencing canonical on every page. Do not block the paginated URLs in robots.txt if you need the deep items indexed. If you use infinite scroll or a load-more button, wire it to real paginated URLs with history.pushState and keep standard links as a fallback. The table below catalogs the mistakes that most often break a paginated series, and what to do instead.
| Common mistake | Why it hurts | Better approach |
|---|---|---|
| Canonical every page to page 1 | Deep items on later pages drop out of the index | Self-referencing canonical on each page |
| noindex on paginated pages | The crawl path to deep items decays over time | Keep them crawlable and indexable |
| Infinite scroll with no URLs | Crawlers cannot request page 2 at all | Paginated fallback URLs via pushState |
| Relying on rel=next/prev for Google | Google has ignored it since 2019 | Crawlable links plus self canonical; keep next/prev for Bing |
| Same content at /blog/ and /blog/?page=1 | Duplicate first page | Pick one canonical first-page URL |
| Blocking parameter pages in robots.txt | Google never reaches the deep items | Allow the crawl; control indexing with meta if needed |
Results and Learnings
The outcomes demonstrate effectiveness through measurable improvements in rankings, traffic, and business metrics. Analysis of successes and challenges provides learning value for practitioners.
Judge the fix by whether deep content becomes reachable and indexed, not by a vanity metric. After the changes, re-inspect several later paginated URLs in Search Console and confirm the reported canonical is now the page itself, then watch the "Crawled, currently not indexed" bucket for those templates shrink over the following weeks as Googlebot re-evaluates them. Track impressions and clicks for the deep products or posts that previously had none. The detailed technical reference at the source below documents the crawl behavior in depth; the numbers any individual site sees depend on how much deep content was previously hidden. Pagination is one thread in a wider fabric of technical SEO fundamentals that decide whether good pages ever get seen.
Case studies like this contribute to the SEO knowledge base, helping practitioners learn from documented real-world experiences.
FAQ
No. Google confirmed in 2019 that it had not used rel=next and rel=prev as an indexing signal for years and stopped supporting them. It now treats each paginated page individually. Bing still uses them and they help accessibility, so keeping the markup is fine, but it is not a Google ranking or indexing signal.
No. Each page should carry a self-referencing canonical that points to itself. Canonicalizing pages 2, 3, and beyond to page 1 tells Google those pages are duplicates of page 1, so the deep items listed only on later pages may never be indexed.
Usually not. If those pages are the only crawl path to deep products or posts, a long-standing noindex,follow eventually behaves like noindex,nofollow, so the path to your deep content decays. Keep paginated pages crawlable and indexable unless another strong internal path exists.
A clean, crawlable format such as a query parameter (/blog/?page=2) or a path segment (/blog/page/2/). The format matters less than making the links real crawlable anchors in the HTML and using one consistent scheme. Avoid serving the same content at both /blog/ and /blog/?page=1.
Back the experience with real paginated URLs. Use history.pushState so each batch maps to a crawlable URL like /blog/?page=2, and provide standard paginated links as a fallback. Without crawlable URLs, search engines cannot request anything past the first screen of results.
If the View-all page loads quickly it can be a strong user and crawl experience, and Google has historically favored it when performance allows. For very long lists a single page becomes too heavy, so numbered pages with self-referencing canonicals are the safer default.
Source: https://audisto.com/guides/pagination/
Is your deep catalog content actually getting indexed?
Paginated series are a classic place where products and posts silently vanish from Google. An audit checks whether every page in the series is crawlable and indexable.
Claude Vincent is a technical SEO consultant focused on crawlability, rendering, and AI-search visibility. He writes the field guides and case studies at SEO ProCheck, with a bias toward the durable, unglamorous work that decides whether search engines and AI answer engines can actually read and cite a site.
About SEO ProCheck
Technical SEO consulting and GEO strategy with 20 years of enterprise experience. Case studies, resources, and tools for search and AI visibility.
Work With Me
Technical SEO audits, GEO strategy, site migrations, and international SEO. Hourly consulting for teams who need hands-on support, not just reports.
Subscribe to our newsletter!
