Automatically splits a long list across multiple pages: visitors browse with previous/next buttons and page numbers. As part of a list it works entirely by itself — the total is counted automatically. The technical name is Pagination.
Add Pagination whenever a Records list can grow beyond a handful of items — a blog index, a product catalogue, a knowledge base. Without it, a long list either loads everything at once or gets arbitrarily truncated; Pagination solves both by fetching only the current page's records while still exposing every item through page links.
Set a sensible limit on the surrounding Records block first — small numbers like 10-20 per page work well for text lists, larger numbers for image grids. Pagination then reads that same list context and needs no separate configuration.
Typical use cases
A webshop category page with two or three dozen products commonly sets limit=12 or limit=24 so pages load fast and product grids stay a consistent height regardless of how large the catalogue grows. A blog or knowledge-base index is the classic case: new articles push older ones onto page two, three and beyond, without anyone needing to touch the page template. Even a professional-services site benefits once its case-study or testimonial list grows past a handful of entries — pagination keeps that page from turning into an endless scroll of similar-looking cards.
Common mistakes
The most frequent mistake is not setting a limit on the surrounding Records block at all — without one, the list may render everything on a single page and Pagination has nothing to split. Set the limit deliberately based on content type: smaller numbers (8-12) for text-heavy rows, larger numbers (16-24) for compact image or product grids. Also give the list a stable sort — without one, the underlying order can shift between page loads, which risks showing the same record twice or skipping one as a visitor pages through. See datatypes and records for how sorting and filtering resolve across a data type.
Pair Pagination with Search on a dedicated search-results page once result counts regularly exceed a page or two, so visitors aren't stuck scrolling through everything to find a relevant match.
Because each page link is a real, crawlable URL rather than a client-side-only click handler, search engines can index deeper pages of a long list on their own — useful for a large product catalogue or article archive where later pages still contain content worth ranking.
Example
The prompt for this example
Show the knowledge-base articles with 2 per page and paging buttons below.