Does it crawl every paginated page?

No. It audits only the single HTML snapshot you fetch.

Why warn on numbered text matches?

The heuristic counts plain-text cues—verify visually when numbers might come from unrelated content.

rel prev missing on first page?

Fetch later pages; some templates only emit `rel=prev` when a prior page exists.

If critical signals exist only after hydration, compare with a static render or inspect the served HTML source.

Technical SEO

Live

Pagination Analyzer

Audit pagination signals (rel=next/prev, canonicals, JS).

X / Twitter LinkedIn Facebook

Source

Fetch a paginated URL (e.g. /blog?page=2).

Fetch a paginated page

Start here · What this pagination audit checks

Pagination affects crawl paths, duplicate signals, and how Google consolidates series pages. Start from a mid-series URL such as /blog?page=2 using Fetch a paginated page.

The DOM checks look for rel="next" and rel="prev" link tags, href patterns that resemble pagination parameters, visible numeric cues, canonical tags relative to your fetched URL, noindex robots tags, infinite-scroll keywords, and awkward page=1 URL forms.

Severity icons summarize each signal. Treat warnings as prompts to align with Google pagination guidance—not automatic failures.

When to use this tool

E-commerce category series
Verify canonical policy on filtered sorts before rolling out faceted navigation changes.
Blog archive rollouts
Catch missing rel tags when legacy blogs move from /page/N to query parameters.
Infinite-scroll blogs
See whether HTML still exposes crawlable pagination or load-more endpoints.
Vendor QA
Send developers a single fetched URL that shows the conflicting canonical note text.

Examples

Walk through these with the form above — they are practice scenarios, not live data.

View-all canonical

Try this

Fetch ?page=2 where canonical points to the non-paginated view-all URL.

What to look for

Shows warn severity reminding you that content must live on the canonical target.

Self canonical

Try this

Page canonical equals the fetched paginated URL.

What to look for

Marks canonical strategy ok with a self-referencing explanation.

Short tutorial

Follow in order the first time you use the tool; later you can skip to the step you need.

Step 1 — Pick a representative page
Use page two or three where rel tags should appear.
Step 2 — Fetch HTML
Let UrlFetcher pull the document into the analyzer.
Step 3 — Walk each audit row
Resolve warnings in priority order: canonical, indexability, crawl discovery.
Step 4 — Cross-check server headers
When duplicates persist, pair with http header auditor for status and caching anomalies.
Step 5 — Update sitemaps if needed
Regenerate pagination URLs in xml sitemap generator after fixing paths.

More detail

New here? Skim Start here first, then run one Examples scenario in the form above.

Pagination Analyzer does one job: audit pagination signals (rel=next/prev, canonicals, JS). It lives under Technical SEO on SEOToolkits, where the beginner idea is simple: Technical SEO keeps pages crawlable, indexable, fast enough, and understandable to search engines.

FAQ

Does it crawl every paginated page?: No. It audits only the single HTML snapshot you fetch.
Why warn on numbered text matches?: The heuristic counts plain-text cues—verify visually when numbers might come from unrelated content.
rel prev missing on first page?: Fetch later pages; some templates only emit rel=prev when a prior page exists.
SPA pagination?: If critical signals exist only after hydration, compare with a static render or inspect the served HTML source.