Modern Pagination SEO Without rel=next/prev
AI generated
SERP
SEO Technical Guide
Modern Pagination SEO Without rel=next/prev
Getting paginated series right

Since Google dropped support for rel=next/prev, pagination SEO needs a new strategy built on canonical tags, internal linking and smart crawl budget management.

15 min read Canonical Strategy Crawl Budget

1. The End of rel=next/prev and What It Means

Google officially dropped support for the rel=next and rel=prev HTML attributes years ago, after they had long stopped functioning as a meaningful ranking signal anyway. For sites with paginated series such as category pages, product listings or blog archives, that means the old convention of explicitly marking page 1, 2, 3 and so on no longer has any direct effect on how Google evaluates the series.

Even so, the underlying challenge has not gone away, since paginated series still exist and still need to be crawled, indexed and internally linked sensibly. Without rel=next/prev, a deliberate strategy built around canonical tags, internal linking and, where appropriate, view all pages is now required to make sure Google finds the right pages in a series and ranks the most useful ones.

2. How Google Crawls and Evaluates Paginated Series Today

Google treats every page in a paginated series as an independent URL with its own content, its own links and its own indexing status. There is no automatic grouping anymore the way rel=next/prev used to suggest; instead Google relies on content, internal linking and user signals to decide which page in a series is most relevant for a given query.

In practice this means page 1 of a category almost always ranks best, since it usually carries the most internal links and the strongest relevance for the main keyword. Deeper pagination pages, page 4, 5, 6 and beyond, still get crawled, but rarely rank for their own queries and mostly exist to give Google full coverage of the catalog.

3. Canonical Strategy for Page 2 and Beyond

A frequently debated question is whether page 2, 3 and beyond should canonicalize to themselves or to page 1. The now established recommendation is self canonicalization for every pagination page, since each page contains different products or articles and is therefore not actually identical to page 1.

Canonicalizing page 2 to page 1 tells Google the two pages are identical, which is factually wrong and, in the worst case, causes the products on page 2 to stop being indexed at all. This mistaken canonicalization is one of the most common pagination errors in online shops and deserves an explicit check in every technical SEO audit.


<!-- Page 2 canonicalizes to itself, not to page 1 -->
<link rel="canonical" href="https://www.example-shop.com/category/shoes/?page=2" />

4. View All Pages as an Alternative

For series with a manageable total item count, roughly up to 100 to 150 products or articles, an additional view all page that lists every item on a single URL can be worthwhile. That page consolidates the link signals that would otherwise be scattered across multiple pagination pages, letting it outrank any individual pagination page on its own.

Load time is the key constraint here: a view all page with several hundred products can noticeably hurt performance, so lazy loading or a server side cap on the number of images shown is worth building in. For very large series with several thousand items, a view all page stops being practical and classic pagination with clean internal linking remains the better choice.

5. Optimizing Internal Linking for Pagination

With rel=next/prev gone as a semantic signal, plain internal linking between pagination pages matters more than ever. A clearly visible pagination navigation built from real, crawlable links, not buttons that only render via JavaScript, ensures Google can reliably reach every page in the series.

It also helps to show a limited set of visible page numbers, say pages 1 through 5 plus a jump to the last page, rather than only a next button, since that gives both users and crawlers a more efficient way to move through the entire series and cuts click depth for the deepest pages considerably.

6. Pagination on E-Commerce Category Pages

In e-commerce, category page pagination is especially sensitive because revenue potential is directly tied to rankings. Filter combinations, color plus size for example, generate a large number of additional URL variants on top of classic page number pagination, and these need to be clearly separated from actual pagination and governed by their own canonical and indexing rules.

A solid practice is to allow indexing only for page 1 of each category plus any deliberately chosen, high search volume filter combinations, while deeper pagination pages remain crawlable but are deliberately excluded from aggressive internal link building, keeping crawl budget focused on the pages that matter most.

7. Pagination on Blog Archives

Blog archives and content category overviews follow similar rules to product categories, with the added twist that recency plays a role too. As new articles push older ones onto deeper pagination pages, older but still topically relevant articles gradually lose internal link strength unless they are deliberately linked through other paths, such as related articles or topic hubs.

That is why blogs benefit from building topic hub pages alongside plain chronological pagination, bundling evergreen content regardless of publish date and keeping it permanently and prominently linked, rather than letting it sink into deep archive pages over time.

8. Crawling Efficiency With Very Deep Pagination

On sites with hundreds or thousands of pagination pages, crawl efficiency becomes a topic in its own right. Every extra pagination page consumes crawl budget that might otherwise go toward new products or articles, so excessively deep pagination, more than 20 to 30 pages per series say, deserves a critical look.

Practical fixes include showing more items per page, 48 instead of 24 products for instance, applying a deliberate noindex to very deep, rarely visited pagination pages, or structural changes such as additional subcategories that reduce overall pagination depth without losing any content.

9. Monitoring and Measuring Pagination Success

The success of a pagination strategy can be checked through several metrics: the indexing rate of pagination pages in Search Console, how often deeper pages get crawled according to server logs, and whether important products on deep pages still receive any organic traffic at all.

If the analysis shows deep pagination pages are barely crawled or indexed, that is not automatically a problem as long as the products they contain remain discoverable through other paths such as search, filters or related products. Only when genuinely important, high revenue products become effectively undiscoverable should the structure be adjusted, for example through additional subcategories or stronger internal linking.

Strategy Use Case Benefit Limitation
Self canonical per page Standard pagination Correct indexing of every item Requires clean internal linking
View all page Up to about 150 items Consolidates link signals, often ranks better Can hurt load time
More items per page Large catalogs Reduces total pagination page count Longer initial load per page
Noindex on deep pages Very deep series (20+ pages) Protects crawl budget Requires careful threshold selection
Topic hubs (blog) Content archives Keeps relevant older content visible Extra maintenance effort

Mironsoft

Technical SEO, content strategy, and sustainable ranking

Visibility that doesn't disappear with the next Google update?

We review existing websites for technical SEO issues, weak content structure, and missing structured data, then build a foundation that supports sustainable, not just short-term, organic growth.

Technical SEO Audit

Systematically checking crawling, indexing, Core Web Vitals, and structured data.

Content Strategy

Building search-intent-based content instead of keyword stuffing for real relevance.

Onpage Optimization

Shaping meta data, internal linking, and page structure consistently and scalably.

10. Summary

Pagination SEO

rel=next/prev

No longer supported by Google, safe to remove from code but not required either.

Canonical

Every pagination page self canonicalizes, never canonicalizes to page 1.

View All

Worthwhile up to roughly 150 items, consolidates link signals, needs performance tuning.

Crawl Budget

For very deep series, show more items per page or apply noindex to deep pages deliberately.

11. FAQ: Pagination SEO

1Do I need to remove rel=next/prev from my code entirely now?
No, that is not strictly necessary, since Google simply ignores the attributes and they cause no harm. It makes more sense to invest that effort into a clean canonical and internal linking strategy instead.
2Should page 2 of a category get a noindex tag?
Usually not, as long as the page contains its own products that are relevant to users. Noindex fits better for very deep, rarely visited pagination pages toward the end of a very long series.
3What is the difference between pagination and filter pages from an SEO standpoint?
Pagination shows the same product set in slices, while filter pages show a different, usually smaller subset of that inventory. Both should be treated separately with their own indexing rules.
4How many products per page is ideal for SEO?
There is no universal ideal number; common practice sits between 24 and 48 products per page as a reasonable balance between load time and the number of pagination pages required.
5Is infinite scroll a good alternative to classic pagination?
Only if it is implemented cleanly with real, crawlable URLs per section, typically through History API changes. Pure JavaScript loading without dedicated URLs makes crawling significantly harder for Google.
6How do I check whether my pagination pages are actually indexed?
The URL inspection tool or the index coverage report in Google Search Console lets you check the current indexing status for a sample of deeper pagination pages.
7Should a view all page replace normal pagination or run alongside it?
Usually it makes sense to offer both, since some users appreciate the faster overview while others prefer the smaller, faster loading individual pages.
8Does pagination affect crawl budget on small sites too?
On small sites with only a few thousand URLs, crawl budget is rarely a limiting factor, so heavily granular pagination optimization is usually not worth the effort there.
9What should I do with old rel=next/prev markup still in my code?
It can safely stay as is since it causes no harm, or be removed during routine code cleanup to keep the codebase leaner.
10How quickly do pagination strategy changes affect rankings?
Early effects on crawling and indexing usually show up within two to four weeks, while noticeable ranking changes can take another four to eight weeks depending on site size.