INTRODUCTION
Every product with a long list eventually has the same meeting. Someone says pagination feels dated. Someone else says infinite scroll is what people expect. A third person suggests a “load more” button as a compromise, and the meeting ends with a choice made on taste.
This piece argues for a different starting point. The right pattern depends less on how the list looks than on what people do once they find something in it. Founders and product leads can settle the question with that one observation, and then deal with the mechanics each pattern brings: position, keyboard access, screen readers and search engines.
Three patterns, three different promises
Google's Search Central documentation, last updated on 10 December 2025, gives a fair summary of the trade-offs.
Pagination gives people a sense of how big the result set is and where they are in it. In return, it needs more controls, splits content across pages and requires a new page load to see more.
Load more keeps everything on one page and can tell people the total size, on or near the button. It cannot handle very large result sets, because everything ends up on a single page.
Infinite scroll also uses one page and feels effortless: you just keep scrolling. It can cause what Google calls scrolling fatigue, because the size of the set is unclear, and it cannot handle very large result sets either.
Read those as promises. Pagination promises a place. Load more promises control. Infinite scroll promises flow.
The question that decides it
Ask what a person does after finding an item in your list.
If they compare and come back, as in product categories, property listings or search results, they need a place. They open an item, return, and expect to find their position. They may want to send the list to someone. Pagination, or a load-more button that records how far you have loaded in the URL, serves that behaviour.
If they finish a task, such as finding one order in a history or one document in an archive, they need to know when they have seen everything. A visible end and a visible count matter more than flow.
If they browse with no destination, as in a social feed or an inspiration board, a place matters less. That is the case where continuous loading can be the right answer.
The mechanics that come with each choice
Whatever you pick, a few consequences follow, and they are not cosmetic.
Keyboard users. The GOV.UK Design System tells teams to avoid infinite scroll that loads content as people approach the bottom of the page, because it causes problems for keyboard users. Anything placed after the list, a footer, a filter summary or a contact link, keeps moving away.
Screen readers. If you do load content as people scroll, the WAI-ARIA feed pattern describes the contract that makes it workable with assistive technology. It recommends Page Down and Page Up to move between articles, and Control+End and Control+Home to jump to the first focusable element after or before the feed. That exit only exists if you build it.
Search engines. Google says its crawler generally follows links in the href of
<a>elements, and does not click buttons or trigger scrolling. Paginated pages should each have their own URL, for example with a?page=nparameter, their own canonical URL rather than pointing to page one, and no page numbers in the fragment after a#, which Google ignores.
The serious counterargument
Infinite scroll is not a mistake by definition. For open-ended browsing, a next-page link is friction with no payoff, and the feed pattern exists in WAI-ARIA precisely because continuous loading is legitimate when it is built properly. That is the intent of the pattern: nothing stands between one item and the next.
That is a fair point, but it is about flow, not about finding something. If your product's value depends on people finding, comparing and returning to specific items, more scrolling is not the goal. And even a genuine feed still needs real URLs behind it if you want its content found in search, plus the keyboard exits above. Choosing infinite scroll does not remove the work; it moves it.
A worked example
A hypothetical marketplace, not a client case. It has 2,400 listings across twelve categories, a product page with “similar items” and a personal activity feed.
Category pages use pagination with
?page=n, 40 items per page and a visible count. People compare and come back, and every page can be crawled.Similar items on a product page use a load-more button that adds eight at a time. Nobody needs to share position eight of a recommendation strip, and the button keeps the footer reachable.
The activity feed loads continuously, built on the feed pattern, with a visible “skip to the end of the feed” link and no SEO ambition at all.
Three lists, three patterns, one rule: decide by the next action.
Before your next meeting
Write one sentence for each long list in your product: “After finding an item, people usually…”. If the sentence ends in compare, return or share, choose pagination or a load-more button that keeps its place in the URL. If it ends in finish, show the count and the end. If it ends in keep browsing, a well-built feed can be right. And whatever you choose, design what happens when the list is empty, as we discuss in empty states by cause.
Sources checked on 18 November 2026: Google Search Central on pagination and incremental page loading, the GOV.UK Design System pagination component and the WAI-ARIA Authoring Practices feed pattern.