Why lists get split
A blog with 400 posts, a store category with 900 products or a directory with thousands of entries cannot sensibly show everything on one page. A single huge page would load slowly, overwhelm the reader and strain a phone’s memory. So lists are divided into smaller pages, a technique called pagination.
Done well, pagination is invisible. Done badly, it hides content, wastes crawling and frustrates visitors. The goal is simple: every item stays reachable, each page of the list is usable, and the list does not generate confusing duplicates.
The main approaches
Numbered pages. The classic pattern: Page 1, 2, 3 with Previous and Next links. Each page has its own address. This is the most predictable approach for both people and crawlers.
Load-more button. A button below the list adds more items to the same page. It is friendly for casual browsing, but you need to be sure that the additional content is also reachable through ordinary links, not only through a script.
Infinite scroll. New items load automatically as the visitor scrolls. It can feel smooth, but it has drawbacks: footer links become unreachable, people lose their place after clicking an item and going back, and crawlers, which generally do not scroll the way people do, may see only the first batch. If you use it, provide a fallback with real paginated addresses that work without scrolling.
View-all page. A single page showing everything. This suits shorter lists, and for longer ones it can create the speed problems that pagination avoids.
Which is best depends on the content. For archives and product listings, numbered pages with real links are usually the safest base, with any smoother layer added on top.
What crawlers need
Search engines follow links. For an item on page 40 of a list to be discovered through the list, there must be a chain of links reaching page 40, and the page must be crawlable. Several habits support that:
- Use plain links. Previous, Next and numbered links should be ordinary links with real addresses, not buttons that only work through scripts.
- Give each page its own address. For example
/blog/page/2/or?page=2, and always the same format. - Link to more than just “next”. If the only way to reach page 40 is to click Next 39 times, items on that page sit extremely deep. Offering links to the first, last and a few surrounding pages shortens the route. This is the same issue described under click depth.
- Keep the sequence stable. If new items are added at the top and shift everything down, addresses of older items change pages. This is normal for chronological lists but is worth remembering.
Canonical tags and pagination
A common mistake is pointing the canonical tag of every paginated page at page 1. This tells search engines that pages 2, 3 and so on are copies of page 1, which they are not, and the items listed on them may then be harder to discover. A more conventional approach is for each page of the list to use a canonical tag that points to itself. The tag is a hint rather than a command, and search engines have changed how they treat pagination signals in the past, so check current official guidance before relying on any detail.
Noindex on deeper pages is another tempting shortcut. Be careful: if pages are kept out of the index for a long time, search engines may eventually stop following the links on them, and the items listed there may lose a route to being found.
Titles, headings and content on paginated pages
Give each page a distinct title so pages are not mistaken for duplicates, for example by adding “Page 2” to the title tags. Keep the main heading the same across the series, but avoid repeating a long introductory block on every page. Put the explanatory text on page 1 only.
The list itself should show enough information to be useful: a clear item title, a short description or image, and a link. Thin entries make a list of 30 items per page look repetitive.
Choosing how many items per page
There is no perfect number. Too few items per page create many pages and a deep list; too many slow the page and overwhelm the reader. Many sites settle somewhere in the range of 10 to 50 items, depending on how heavy each item is. Page speed is often the deciding factor, along with how people actually use the list. Test on a phone, since long pages are slower there.
Reducing the need for deep lists
Pagination is a way to display a list, not a way to organize it. If a category has 900 products, it may need subcategories, filters or topic groups. Visitors rarely want to look through 45 pages. Strengthening the structure, for example by adding clear subcategories, allows people to find things without paging, and makes each smaller list more focused. Be mindful that filters bring their own risks with parameter URLs, as covered separately.
For editorial content, consider hub pages and a “popular” or “start here” block so that older, valuable articles do not exist only on page 15 of the archive.
A quick checklist
- Can you reach every item through ordinary links, without scripts or scrolling?
- Does each list page have its own stable address and a distinct title?
- Do canonical tags point sensibly, usually to the page itself?
- Can a visitor jump several pages at once?
- Does the list work well on a phone and load quickly?
- Are deep pages included in a crawl, and does any important item appear only on a very deep page?
If the answer to any is no, fix the simplest problem first and then check again. Search engines change how they handle pagination from time to time, so avoid clever tricks and favor clear, crawlable links.