Pagination is the practice of dividing a long list of content — blog posts, products, or search results — into multiple discrete pages, each with its own URL. Page 1 lives at /category/, page 2 at /category/page/2/, and so on. Each page contains a subset of the full content list, keeping individual pages lightweight for users and manageable for search engine crawlers.
Pagination shows up on nearly every content-heavy site — e-commerce category pages, blog archives, forum threads, photo galleries, comment sections. Most sites implement it without much thought and pay for it through crawl waste, thin content flags, and orphaned product pages that Google never finds.
What is pagination?
Pagination splits a large content set into separate pages, each containing a fixed subset of items. When a blog category has 200 posts or an e-commerce section has 500 products, showing them all on one page creates an unusably long page and a file that's slow to load and difficult for crawlers to process efficiently.
The core pattern looks like this:
/blog/ ← Page 1 (canonical: itself)
/blog/page/2/ ← Page 2
/blog/page/3/ ← Page 3
# Each page links to: previous page, numbered pages, next page
Common use cases: e-commerce category pages, blog archives and category listings, search result pages, forum threads, photo galleries, and comment sections.
Google treats paginated pages as ordinary pages. In 2019, Google deprecated rel=next/prev support — clear HTML links between pages are sufficient. Googlebot discovers paginated pages by following the sequential navigation links present in the HTML.
Why pagination matters for SEO
Pagination affects four distinct SEO dimensions, each of which can either help or hurt depending on implementation quality:
- Crawl budget efficiency. Googlebot allocates a crawl budget per site. Well-structured pagination helps crawlers process large content catalogs systematically. Poorly structured pagination wastes crawl budget on near-duplicate pages that deliver little indexable value.
- Content discoverability. Products and posts linked only from paginated pages rely entirely on those pages being crawled. If Google skips page 8 of a category, all products only listed on page 8 are invisible to the crawler.
- Duplicate content risk. Inconsistent URL structures for the same paginated view (?page=2 and /page/2/ returning identical content) create duplication that dilutes ranking signals across multiple URLs.
- Internal link distribution. Pagination creates a chain of internal links that distributes authority through the category hierarchy, providing crawl attention and some ranking signal to deeper content.
How pagination works technically
The browser requests a category or archive URL. The server returns a fixed subset of items (e.g. products 1-24) and renders numbered navigation links at the bottom of the page pointing to adjacent pages. Each page is a distinct URL with distinct content.
Self-referencing canonical tags
Each paginated page should include a canonical tag pointing to itself — not to page 1. This tells Google "this page is the canonical version of itself" and prevents confusion with duplicate-looking content:
<link rel="canonical" href="https://example.com/blog/page/2/">
<!-- NOT pointing to page 1, which would de-index this page -->
<!-- NOT: <link rel="canonical" href="/blog/"> -->
Clear HTML navigation
Since Google deprecated rel=next/prev in 2019, crawlers discover paginated pages through standard HTML links. Every paginated page must include working anchor tags linking to the previous page, numbered page range, and next page.
Pagination vs infinite scroll — which is better for SEO?
| Factor | Pagination | Infinite scroll |
|---|---|---|
| SEO crawlability | Each page has a unique URL — crawlable by default | JavaScript-loaded content often not crawled without extra setup |
| User control | Users can jump to specific pages, bookmark positions | No position control, back button often loses scroll position |
| Analytics tracking | Page views per URL — clean attribution | Requires virtual pageview events to track depth |
| Footer accessibility | Footer always reachable | Footer often buried below infinite content |
| Best fit | E-commerce, blogs, forums | Social feeds, image galleries |
Real pagination examples
1. E-commerce category — 500 products, 21 pages
A furniture retailer had 500 products in a "sofas" category. Implementing 24 items per page created 21 paginated URLs. Each page has a unique title ("Sofas — Page 2 of 21"), a self-referencing canonical, and clear next/previous HTML links. Googlebot crawls all 21 pages in each crawl cycle, ensuring all 500 products are discoverable.
2. Blog archive — orphaned posts through bad implementation
A blog with 300 posts implemented pagination with 10 posts per page but noindexed pages 2-30 to "avoid thin content". Result: the 270 posts only appearing on pages 2-30 became orphaned — no other internal links existed pointing to them. Google's coverage report showed 270 pages as "Crawled, not indexed." The fix: remove noindex, add proper canonical tags.
3. Search results — faceted navigation creating thousands of duplicates
An e-commerce site combined pagination with faceted navigation (colour, size, price filters). Each filter combination created new paginated URLs — the same 24 products appeared across hundreds of URL variations. Solution: canonical tags on all filter URLs pointing to the unfiltered category page, reducing duplicate URLs from 4,000 to 21.
Pagination vs canonical URL — when to use each
Use pagination when
- Content genuinely divides into distinct subsets
- Each paginated page has enough unique items to be useful
- Users benefit from jumping to specific page numbers
- The full list would be too long to render on one page
- You want all items in the set to be discoverable and indexable
Use canonical (to page 1) when
- Paginated pages are almost identical to page 1 content
- Sorting or filtering creates near-duplicate paginated views
- The paginated pages have no unique content worth indexing
- Crawl budget is limited and deeper pages add no ranking value
- Items only appear on a single canonical page anyway
7 pagination best practices for SEO
- Use clean, consistent URL structures. Stick to one pattern:
/category/page/2/. Never mix?page=2,?p=2, and/page/2/for the same content set. - Add unique page titles. Each paginated page must have a distinct title tag: "Sofas — Page 2 of 21 | BrandName". Identical titles across all pages signal duplicate content to crawlers.
- Use self-referencing canonicals. Every paginated page should canonical to itself — not to page 1. Canonicaling page 2 to page 1 tells Google to de-index page 2 and lose all products only listed there.
- Never noindex paginated pages that contain unique content. If products or posts are only accessible from paginated URLs, noindexing those pages makes the content unreachable to Google.
- Include clear HTML links to previous and next pages. Googlebot discovers paginated pages by following links. Missing next/previous links breaks crawl chains and orphans deeper pages.
- Set an appropriate items-per-page count. 12-24 items for e-commerce, 10-20 posts for blogs. Fewer items creates thin pages; more items creates slow pages and fewer indexable URLs for your content set.
- Monitor with Google Search Console. The Coverage report shows discovered paginated pages, indexing status, and any crawl errors specific to pagination patterns.
It seems like a neat solution: canonical all paginated pages to page 1 to avoid "thin content". In practice, it de-indexes pages 2+ and orphans all products or posts that only appear there. Google then cannot discover that content at all. Use self-referencing canonicals (each page points to itself), not page-1 canonicals, across your paginated series.
Common pagination mistakes to avoid
- Orphaned paginated pages — pages 5+ not linked from any page except the sequential chain. If Google skips a crawl of page 4, it may never reach page 5.
- Inconsistent URL parameters —
?page=2and/page/2/returning identical content creates duplication. - Noindexing pagination without alternative discovery path — if items are only listed on noindexed pages, they become invisible to Google.
- Excessive pagination depth — hundreds of paginated pages exhaust crawl budget. Use faceted search, filters, and sub-categories to reduce depth.
- Thin single-item pagination — pages with 1-2 items each are treated as thin content. Set a minimum items-per-page threshold.
- Missing or wrong canonical tags — canonicaling to the wrong URL tells Google to ignore the correct one.
Frequently asked questions
Yes, generally. Google handles pagination like normal pages. Noindexing paginated pages can orphan products or posts that are only linked from those pages, making them invisible to Google. Leave paginated pages indexed unless you have a specific reason not to.
No. Google deprecated support for rel=next and rel=prev in 2019. Clear HTML pagination links between pages are sufficient. Google can understand pagination through standard sequential HTML anchor links without the rel attributes.
There is no fixed rule. Common choices: 12, 24, or 48 products for e-commerce; 10-20 posts for blogs. Balance user experience, page weight, and crawl efficiency. Too few items creates thin content; too many makes pages slow and reduces the total count of crawlable URLs for your content set.
Poor implementation creates crawl inefficiency, duplicate content issues, and orphaned pages that Google cannot discover. Proper pagination — clean URLs, unique titles, self-referencing canonicals, and clear next/previous links — is neutral to positive for SEO.
Pagination loads a fixed set of items per page with numbered navigation. Infinite scroll loads more content as the user scrolls down, typically via JavaScript. Pagination is more SEO-friendly because each page has a unique URL that Googlebot can crawl independently. Infinite scroll requires extra implementation to be crawlable.
Related glossary terms
Sources
