SEO
Pagination SEO: getting paginated series indexed correctly
Copy for AI
Pagination is the way you split a long list, think of a blog overview, a product catalogue or a news archive, across multiple numbered pages. The short answer to the SEO question: treat every page in such a series as a fully fledged, crawlable page with ordinary links, because Google has not used the old rel="prev" and rel="next" signals for indexing in years. If you skip that, part of your content stays undiscoverable. In this article you will read how to handle pagination, infinite scroll and view-all pages correctly on a B2B site.
What is pagination and why does it affect your SEO?
As soon as you have more items than fit on one page, pagination appears. Your overview splits into /blog/, /blog/page/2/, /blog/page/3/, and so on. For the visitor that is convenient. For Google it is a crawling question: every item on page two and beyond is only reachable through those deeper pages. If that chain does not load or link cleanly, the crawler simply never sees your newest or deepest content.
This belongs in every technical SEO approach and ties directly into how Google indexes your website. A product or article that is not in the index cannot generate a single enquiry, no matter how strong the content is. That is why pagination is not a side detail but part of your acquisition: it helps decide which share of your offering even gets a chance to rank.
What happened to rel=prev/next?
For years the advice was: link the pages in a series with rel="prev" and rel="next" in the <head>, so Google understands they form a whole. That advice is outdated. Google has confirmed that it no longer uses these tags as an indexing signal and has not supported them for a long time. The tags do no harm if they are still there, but they also do nothing for your rankings anymore.
So what should you do instead? Google’s own guideline is clear: treat every page in the series as a standalone page. Concretely, that means:
- Every paginated page has its own unique URL that opens directly in the browser.
- That URL is indexable. Do not put a
noindexon it to avoid “duplicate content”; that is exactly what keeps Google away from the items on that page. - The canonical of page two points to page two itself, not back to page one. A self-referencing canonical is the right choice here.
- The pages link to each other with ordinary
<a href>links. No buttons that only work through JavaScript.
That way the crawler can follow the chain from page to page and discover every item along the way, exactly what you need to get your full catalogue or archive into the index.
How do you handle infinite scroll?
Infinite scroll, where new items load automatically as you scroll down, feels modern and smooth. The problem: a crawler does not scroll. Whatever only appears after a scroll action or a mouse click often stays invisible to Google. If you build your entire overview on infinite scroll without underlying URLs, in practice you will see that only the first batch of items gets indexed and the rest disappears into a black hole.
The solution is not “no infinite scroll”, but infinite scroll on top of real pagination. That pattern is often called progressive enhancement:
- Underneath the visual scrolling experience sit ordinary paginated URLs (
?page=2,?page=3). - Every batch of content that scrolls in matches such a URL and updates the address bar accordingly.
- Without JavaScript, everything falls back on clickable “next” links that guide the visitor and the crawler through the series.
That way your visitor gets the fluid experience and Google keeps a crawlable path to every page. Test it by switching JavaScript off in your browser: if you can still click through to page two, you are fine. If you cannot, you are hiding content from search engines.
When do you choose a view-all page?
A view-all page shows the entire series in one go, without splitting. For smaller series that can be a strong choice: users do not have to click through, and all items sit on one crawlable URL. Google has indicated in the past that it often prefers such a consolidated page, provided it loads quickly.
That “provided” is the crux. A view-all with hundreds of products and heavy images becomes slow, and speed is a ranking factor that also undermines your conversion. A few rules of thumb:
- Limited series? A view-all can make pagination unnecessary and simplify your internal link structure.
- Large catalogue? Stick to real pagination; a view-all would become too heavy to load smoothly.
- Need both? Offer pagination for the user and optionally let a view-all exist as a crawlable source, but consciously choose which version you treat as the main one.
Which variant pays off most depends on your item count, your load time and your audience. There is no universally correct answer, only the choice that fits your site.
Which mistakes do you see most often?
In practice the same pagination blunders keep coming back. Avoid these:
noindexon everything except page one. You think you are solving duplicate content, but you are shutting your deeper items out of the index.- Canonical from every page to page one. Same effect: Google ignores page two onwards, including the items on it.
- Parameters that create endless variants. Filters and sorting options that generate new URLs can swallow your crawl budget. Keep this under control with a well thought out SEO friendly URL structure.
- “Next” buttons without a real link. If navigation only works through JavaScript, the crawler stops at page one.
- Slow view-all pages. Too many items on one URL makes the page unusably slow.
Every one of these is a self-inflicted blockage. A thorough SEO audit exposes them quickly, because they are measurably visible in a crawl of your site.
Frequently asked questions about pagination and SEO
Should I still use rel=prev/next?
For Google it has no effect anymore; the company no longer uses these tags as an indexing signal. Leaving them in place does no harm, but do not expect any ranking benefit from them. Put your energy into real, crawlable links between your pages instead.
Does pagination cause duplicate content?
Not if you handle it correctly. Every page shows different items, so the content is unique. Keep a self-referencing canonical on every page and do not put a noindex on it, and no problem arises.
Is infinite scroll bad for SEO?
Not necessarily, but only if you build it on top of real paginated URLs that are reachable without JavaScript. If the scroll hides the content from crawlers, only your first batch of items gets indexed.
Does this apply to a small B2B site too?
Yes. As soon as your blog or services overview runs across multiple pages, it counts. For a limited series, a view-all is often the simplest solution that makes everything crawlable in one go.
Make your whole catalogue count, not just page one
Pagination looks like a technical detail, but it decides whether the deeper part of your content gets a chance at all. Treating every page as a standalone, crawlable URL is not a luxury; it is the basis for getting your full offering into the index. We are a small team that moves fast, says honestly what does and does not pay off, and approaches SEO as the acquisition layer of a growth engine that steers on pipeline, not on numbers that merely look good. Want this handled professionally? That is exactly what our SEO specialist does. All of this fits within the bigger picture of what SEO is and how it feeds your growth.
Do you suspect part of your content stays undiscoverable because of poor pagination? Schedule your free intake
Free website scan
Enter your website and get an automatic scan within minutes, with concrete technical and SEO improvements. No sales pitch.
We only use your details for your scan. No spam, unsubscribe anytime.