A search that returns sixty results and shows all of them is not a result list, it is a wall.
Numbered pagination gives the visitor a fixed number per page and a way to move between them, without the page reloading.
For every Search Bar setting in one place, see the Search Bar guide.
Before You Start
- Edition: Free. Measured with Nexter Blocks Pro deactivated, the Search Bar renders identically — form, input, dropdowns, suggestions and results all work without Pro.
- Block to enable: Search Bar, switched on under Nexter > Blocks in your WordPress dashboard.
- Published content to find. The block searches your real posts, so a site with nothing published returns nothing.
- Enough content to paginate. With fewer matches than your page size there is nothing to page through.
Steps
- Select your Search Bar block and set the number of results per page.

- Set the loading behaviour to pagination.

- Set the previous and next labels, and how many page numbers to show at once.

- Publish and run a search that returns more than one page.

How It Behaves
Measured with a page size of 3 against a term matching 14 items: the block reported 14 total and returned 3, which is pagination working exactly as it should.
- The full navigation configuration is written onto the block — the page size, whether the counter shows, how many numbers appear at once, and the previous and next labels — so the script can render the controls without another request.
- Page numbers beyond the visible window are rendered but hidden, then revealed as the visitor moves through. This keeps the control a fixed width on long result sets.
- Previous and next can carry text, an icon, or both.
- The total count is available separately, so a results total can be shown above the list.
- AJAX search has to be switched on for results to appear as you type. With it off the bar behaves as a plain form that submits to WordPress’s own search page.
Limitations
- Each page is a fresh request. Nothing is prefetched, so a visitor clicking through several pages makes several round trips.
- Pagination state is not in the URL. A visitor cannot link to page three of a search, and going back in the browser will not return them to it.
- A page size too small makes the control the main feature. Three per page on a wide layout leaves a lot of empty space under a lot of buttons.
- Only one loading behaviour at a time. Pagination, load more and lazy loading are alternatives, not a set you combine.
Troubleshooting
No pagination appears
The search returned fewer results than your page size, so there is only one page. Try a broader term or a smaller page size.
Clicking a page number does nothing
AJAX search has to be on. Without it the block has no way to fetch the next page in place.
The numbers run off the edge on mobile
Reduce how many page numbers are shown at once. The rest stay hidden until they are needed.
I would rather have a button than numbers
Use the load more behaviour instead. See the load more doc.










