Pagination & Rel-Next/Prev Auditor
Paginated series break in subtle ways — a rel=next that skips a page, a
missing return link, or page 2 canonicalizing to page 1. Instead of checking pages one
by one, paste the whole series and validate the entire chain in a single pass.
Tool interface
Format: URL | canonical | rel-next | rel-prev — pipe or comma separated.
Leave next/prev empty where they don't apply. Lines starting with # are ignored.
Chain Audit Results
Chain Visualization
Per-Page Detail
| # | URL | Canonical | rel-prev | rel-next |
|---|
Introduction
E-commerce categories, blog archives, and search results all use pagination. When the next/prev chain is broken, crawlers can't discover deep pages, and incorrect canonicalization can deindex entire sections. Auditing the whole series at once is the only reliable way to catch these issues.
How It Works
- Each line is parsed into URL, canonical, next, and prev fields.
- A URL index is built; next/prev targets are resolved to positions.
- The chain is walked from page 1 to detect loops and unreachable orphans.
- Canonical targets are checked against each page's own URL and page 1.
Privacy
Your pagination data is analyzed entirely in your browser. No content is transmitted anywhere. No API calls, no tracking, no page fetching.
Limitations
- Cannot crawl live pages; you must paste the series (e.g., from a crawler export).
- URL matching is normalized (trailing slash, case) to reduce false negatives.
- Does not detect query-parameter ordering variations (e.g.,
?page=2&sort=ascvs?sort=asc&page=2).
FAQ
Should paginated pages self-canonicalize?
Yes. Each paginated page is unique content and should canonical to itself. Canonicalizing to page 1 risks deindexing the series.
Does Google still use rel=next/prev?
Google stopped using it as a ranking signal in 2019, but Bing and others still read it, and it helps crawlers discover paginated content.
Is my data uploaded?
No. Everything is analyzed locally in your browser. Nothing is transmitted.