Pagination signals

rel="next" and rel="prev" links let an agent work through a paginated archive instead of stopping at page one.

Standard
Emerging checkEmerging
Off by default, turn on in settings

Who supports it

No agent or browser has announced support yet.

27 others: no evidence yet. See every agent and browser

What it checks

The extension reads the rendered page’s <link> 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 <head>:

<!-- On /blog/page/2 -->
<link rel="prev" href="https://example.com/blog/" />
<link rel="next" href="https://example.com/blog/page/3" />

Leave out prev on the first page and next on the last.

Support by agent and browser

Announced means the vendor’s own docs or announcement say so. Published is the date on the vendor’s own page, where it has one. Checked is the last time our weekly research found that page still saying so.

No agent or browser has announced anything about this yet.

No evidence yet27
  • ChatGPT
  • Claude
  • Gemini
  • Perplexity
  • Copilot
  • Meta AI
  • ChatGPT Atlas
  • Comet
  • Dia
  • Gemini in Chrome
  • Edge Copilot Mode
  • Claude Code
  • Cursor
  • Codex
  • GitHub Copilot
  • Windsurf
  • CCBot
  • Applebot
  • Amazonbot
  • Bytespider
  • Cohere
  • Mistral
  • DuckAssist
  • Chrome
  • Edge
  • Firefox
  • Safari

Adoption on the top 100 sites

0 of 99 measured sites implement it

Scanned 23 Oct 2026 with the Sitebulb Labs extension, against the Tranco list (tranco-56Z8N). 1 sites couldn’t be measured (bot challenge or timeout) and are left out of the share.

9 Oct 2026: 0%12 Oct 2026: 0%23 Oct 2026: 0%
9 Oct 2026 0% → 23 Oct 2026 0%

Overview

3/9

Speculative

Specified, but little evidence anything uses it yet.

How this rating is worked out3 of 9 points
FactorPointsWhy
Vendor support0 / 30 vendors supporting, 0 partly or planned
Top-100 adoption0 / 30% of measured sites
Spec maturity3 / 3Published standard

8 or more points is Established, 5 to 7 is Gaining traction, 2 to 4 is Speculative and under 2 is Stalled. A feature is also Stalled when more vendors have said no than yes. Read the spec.

Community insights

No community insights for this feature yet.

Quotes are from public posts, checked against the original before they appear here. Suggest an insight, or ask for yours to be removed.