---
title: "Pagination signals · Sitebulb Labs"
description: "rel=\"next\" and rel=\"prev\" links let an agent work through a paginated archive instead of stopping at page one."
url: https://labs.sitebulb.com/docs/checks/agent-experience/content-crawl-depth/
---
# Pagination signals
rel="next" and rel="prev" links let an agent work through a paginated archive instead of stopping at page one.
- Category
[Agent experience](https://labs.sitebulb.com/docs/checks/agent-experience)
- Standard
- Emerging checkEmerging
- Off by default, turn on in settings
## What it checks
The extension reads the rendered page’s `` elements for `rel="next"` or `rel="prev"`.
When neither is present, it checks whether the page is paginated at all before offering advice. It counts the page as paginated if it links to URLs such as `?page=2`, `/page/2` or `/p/2`, has links whose text is a page number above 1, or has links reading “Next”, “Previous”, “Older posts”, “Newer entries” and similar.
## Results
| Status | When |
| -------------- | ---------------------------------------------------------------------------------------------------------------- |
| **Pass** | The page declares `rel="next"`, `rel="prev"`, or both |
| **N/A** | The page is not paginated, or it is paginated but declares neither link (a recommendation is shown in that case) |
| **Unmeasured** | The extension could not read the page (open it in the active tab) |
Because this is a bonus check, a paginated page without the links is not marked down; it is reported as N/A with the pagination links that were found.
## How to fix
On each page of a paginated archive, add links to the neighbouring pages in the ``:
```html
```
Leave out `prev` on the first page and `next` on the last.