SEO

Pagination

Also called paginated pages, page 2, rel=next and rel=prev

Splitting a long list, such as products or blog posts, across a series of numbered pages linked to each other.

Quick facts: Pagination

Category
SEO
Also called
paginated pages, page 2, rel=next and rel=prev
Level
Intermediate
Affects
Crawling of deep products and posts, duplicate signals, crawl budget
Where to see it
A site crawler, view-source in the browser, Google Search Console URL Inspection
In this article4
  1. How pagination works
  2. Why it matters
  3. Common mistakes
  4. How to act on it

Pagination is the practice of splitting a long list, such as the products in a category or the posts in a blog archive, across a series of numbered pages: page 1, page 2, page 3 and so on. Each page has its own URL and links to the next and previous pages, so both visitors and search engines can work through the whole list.

How pagination works

A typical shop category page might show 24 products, with links to further pages at the bottom. The URLs usually look like /dresses/?page=2 or /dresses/page/2/. Each paginated page shows a different set of items, so to a search engine they are related but distinct pages.

For years sites added rel="next" and rel="prev" tags to tell Google how the series fitted together. In 2019 Google said it had not used those tags for some time, and now works out the relationship from the links themselves. The tags do no harm, and some other search engines may still read them, but they are no longer the main signal for Google.

What Google does rely on is being able to follow plain HTML links from one page to the next. If page 2 only loads when someone clicks a JavaScript button, or appears through infinite scroll with no separate URL, Google may never see the items beyond the first batch.

Why it matters

Paginated pages are often the only route by which crawlers reach older blog posts or products deep in a large category. If pagination is broken, those items can become effectively invisible, even though they are listed in your XML sitemap. For a UK online shop with large ranges, such as a furniture retailer or a parts supplier, that can mean hundreds of product pages getting little or no crawl attention.

Handled badly, pagination also creates confusing signals: duplicate titles across the series, canonical tags that tell Google every page is really page 1, or near-endless combinations when pagination mixes with filters and sorting.

Common mistakes

  • Canonicalising every page to page 1. Page 2 shows different products from page 1, so it is not a duplicate. Pointing its canonical tag at page 1 can stop Google crawling the items on it. Each page should usually have a canonical pointing to itself.
  • Noindexing the whole series beyond page 1. Over time Google may crawl noindexed pages less and follow their links less, which weakens the path to deep items.
  • Load-more buttons without links. A button that fetches more items by script, with no crawlable URL behind it, hides everything after the first batch.
  • Pagination multiplied by filters. Page 5 of “red, size 12, sorted by price” creates crawl waste. See faceted navigation.
  • Identical titles and descriptions. Adding “Page 2” to the title costs nothing and helps people and crawl tools tell the pages apart.

How to act on it

Check how your series renders without JavaScript: view the page source of page 1 and confirm there are real links with href values to page 2 and beyond. Check that each paginated page returns a 200 status, has a self-referencing canonical and adds the page number to its title.

Next, reduce how deep items sit. Show a sensible number of items per page, link to key subcategories from the top of the list, and link to important older content from related pages so it does not depend on pagination alone. If you use infinite scroll or a load-more button, back it with paginated URLs that work on their own.

Finally, crawl the site and look at how many paginated URLs exist compared with how many you expected. A big gap usually means filters or sort orders are generating extra combinations. Untangling that is a regular part of my technical SEO work, particularly on larger shops.

Do and do not

Do

  • Use crawlable HTML links between paginated pages
  • Give each paginated page a self-referencing canonical
  • Back infinite scroll or load-more buttons with real page URLs

Do not

  • Canonicalise every page in the series to page 1
  • Rely on rel=next and rel=prev for Google
  • Let filters and sorting multiply paginated URLs unchecked

Questions people ask about this

Should paginated pages be noindexed?

Usually not. Google recommends letting paginated pages be indexed with a self-referencing canonical, so it keeps crawling them and following links to the items they list. Noindexing the series can gradually reduce how often Google reaches products or posts that are only linked from deeper pages.

Does Google still use rel=next and rel=prev?

No. Google said in 2019 that it no longer uses these tags to understand paginated series and relies on the links between pages instead. Leaving them in place does no harm, and other search engines may still read them, but crawlable links matter far more.

Is a view-all page better than pagination?

It can be, if the view-all page loads quickly with every item on it. For small ranges that is often the simplest option, with paginated pages canonicalised to the view-all version. For large categories a single page becomes too slow, so standard pagination is usually the better choice.

Related terms

Found this useful?

Share it, or ask an AI to summarise it

Back to the glossary

Knowing the term is the easy part

Applying it to your own site and budget is the work. Book a call and I will tell you what actually applies to you.