Website Checker - What Is Pagination in SEO? Current Best Practice

What Is Pagination in SEO? Current Best Practice

Aug 09, 2026 · SEO Glossary

In March 2019, Google casually mentioned on Twitter that it hadn't used rel="prev" and rel="next" as indexing signals "for a few years." Thousands of sites had been dutifully maintaining that markup the whole time. It remains one of the better reminders that implementation advice has a shelf life — and pagination advice in particular is full of expired guidance still being repeated.

So, what is pagination? It's splitting a long list — blog archives, product categories, forum threads, search results — across a numbered series of URLs: /category/, /category/page/2/, and so on. The SEO question is how to structure that series so Google can crawl through it, index what matters, and consolidate what doesn't.

How Google Handles Paginated Series Now

Since dropping rel=prev/next, Google treats each page in a series as an independent URL. There's no special consolidation of the series into one entity. Page 3 is just a page that happens to link to pages 2 and 4. That has direct consequences:

  • Each paginated page can be indexed and can rank on its own (usually page 1 does; deep pages rarely).
  • Googlebot discovers items on page 6 only by crawling through pages 2–5 — the chain of links is the discovery mechanism.
  • Anything that breaks the chain (JavaScript-only "load more" buttons, canonicals pointing to page 1) can silently hide most of your catalog from crawling.

You can see this in your logs: on a healthy paginated category, Googlebot walks the numbered pages in sequence, less frequently as depth increases. When pagination breaks, requests for deep pages simply stop, and products linked only from those pages start dropping from the index weeks later.

What Is Pagination Done Right? Five Rules

  1. Give every page a unique, crawlable URL. ?page=2 or /page/2/ both work. What doesn't work is a button that fetches more items via JavaScript without changing the URL — Googlebot doesn't click buttons.
  2. Use real <a href> links between pages. Next/previous links and numbered links must be anchor elements in the rendered HTML. If you use infinite scroll for users, pair it with paginated URLs updated via the History API and matching anchor links as fallback.
  3. Self-canonical every page. Page 2's canonical tag should point to page 2. Canonicalizing all pages to page 1 is the most common pagination mistake I see — it tells Google the deeper pages are duplicates, and the products on them lose their crawl path.
  4. Don't noindex the series casually. A long-term noindexed page eventually gets crawled less and its links weigh less. If deep pages are noindexed, the items linked only from them become harder to discover. If you must keep them out of the index, make sure every item is also reachable elsewhere — an XML sitemap plus category cross-links.
  5. Keep the first page clean. /category/ and /category/?page=1 shouldn't both exist as duplicates; the page-1 parameter version should canonicalize (or redirect) to the base URL.

Sort orders deserve a special mention because they multiply the series invisibly. ?page=3&sort=price_asc and ?page=3&sort=newest contain the same items shuffled — near-duplicates from Google's perspective. Pick one default sort as the canonical, crawlable series and canonicalize the re-sorted variants to their default-sort equivalents. The items don't need to be discoverable through every possible ordering; once is enough.

Pagination and Crawl Budget

Paginated series multiply fast. A faceted category with 12 filters and 40 pages of results can generate tens of thousands of near-duplicate URL combinations, and Googlebot will happily burn its crawl budget wandering through them. The fix isn't to block pagination — it's to block the combinations: paginate the canonical category view, and keep filtered variants out of the crawlable link graph (or robots.txt them) unless a filter has real search demand. Watch Search Console's crawl stats: if parameter URLs dominate your crawled-not-indexed report, this is why.

Design Choices That Help Deep Content

Whatever the markup, depth itself is the enemy — an item on page 23 sits 23+ clicks from the homepage, and its internal PageRank reflects that. You can flatten the series:

  • Larger page sizes. 48 items per page instead of 12 turns a 40-page series into 10.
  • Skip links. Numbered pagination that links to first, last, and a window of nearby pages (1 … 8 9 10 … 40) roughly halves the click depth of the middle pages.
  • Category splits. If a category needs 60 pages, it's usually two or three categories wearing one URL.
  • A "view all" page works for modest lists (Google has long said it's fine) but becomes a performance liability past a few hundred items.

Auditing Your Own Pagination

Three quick checks reveal most problems. Crawl your site and look at click depth: if products sit 15+ clicks deep, your series is too long or your links too sparse. Fetch page 2 with JavaScript disabled and confirm the item links and next-page link exist in the raw HTML. And check the canonicals on pages 2–5 — pointing anywhere but themselves is a red flag. A site crawler surfaces all three in one pass, along with the redirect and duplicate-title issues that paginated templates love to breed. The rel=prev/next era is over; what's left is making sure the humble chain of links actually holds.

Frequently Asked Questions

Should I still add rel=prev/next markup?

Not for Google — it confirmed in 2019 that it no longer uses those hints for indexing. Some accessibility tools and browsers make minor use of them, so keeping the markup does no harm, but adding it purely for SEO is wasted effort.

Should page 2 canonical to page 1?

No. Each paginated page should carry a self-referencing canonical. Pointing deeper pages at page 1 tells Google they're duplicates of it, which can remove them from crawling paths and strand every item that's only linked from those pages.

Is infinite scroll bad for SEO?

Infinite scroll alone is a problem because Googlebot doesn't scroll or click to trigger loading. The fix is pairing it with real paginated URLs: update the address bar with the History API as the user scrolls, and include standard anchor links to those page URLs in the HTML so crawlers can walk the series.

Do paginated pages waste crawl budget?

Ordinary numbered pagination is rarely the issue — Google crawls deep pages less often on its own. The real waste comes from pagination multiplied by filters and sort parameters, which can spawn thousands of near-duplicate URLs. Keep filtered combinations out of the crawlable link graph and the budget takes care of itself.

Try WebsiteChecker.Tech Free

Run a free technical SEO audit on any website. Get a client-ready report in minutes.

Start Free Scan