Technical SEO
Pagination SEO Auditor
Paste the URLs of a paginated series, in order — page 1 first — and we will fetch every page and check the whole series for duplicate titles, a broken canonical strategy, a bad noindex pattern, a broken rel="next"/"prev" chain, and thin content.
Up to 12 URLs, http(s) only. We fetch each one live and analyze the whole series together — this can take a few seconds.
What this tool checks
A paginated series — category page 2, 3, 4…, a blog archive, a forum thread, a search-results listing — is one of the easiest places to accidentally create duplicate content or hide your own pages from search engines. Checking one page at a time misses all of this; you need the whole series compared side by side, which is what this tool does.
The four things that go wrong most often
Each of these is graded separately and rolled into an overall score, because a series can fail on one dimension while doing fine on the others.
Canonical strategy
Every page should either canonicalize to itself (the modern default) or, less commonly, deliberately consolidate to page 1. We flag it when pages disagree with each other or point somewhere unrelated.
Duplicate titles & descriptions
If every page in the series shares one <title> and meta description, search engines cannot tell your pages apart in results — a classic pagination mistake.
rel="next" / rel="prev" chain
Google has ignored these since 2019, so their absence is never penalized here — but if you do add them, we verify the chain actually links page 1→2→3 correctly, since a broken chain is worse than no chain.
noindex pattern & thin content
We check whether your noindex directives follow a consistent, intentional pattern, and flag any page whose visible text is too thin to look like a real, useful page.
Frequently asked questions
Should page 2, 3, 4… canonicalize to page 1, or to themselves?
Self-referencing canonicals are the current best practice for almost every paginated series, because each page usually shows different items. Canonicalizing everything to page 1 tells Google those items do not need to be indexed on their own — only do this deliberately, for example when you also offer a single "view all" page that already contains everything.
Do I still need rel="next" and rel="prev"?
Google stopped using them for pagination in March 2019, so they are optional for Google. Some other crawlers still read them, so adding a correct chain does no harm — but a missing chain is not flagged as an error here, only a broken one is.
Why would I noindex pages 2, 3, 4…?
It is a valid strategy: keep page 1 indexable (it is what people actually search for and link to) and noindex,follow the rest, so link equity still flows through the site without every thin listing page competing for the same query. It only becomes a problem when it is applied inconsistently.
How is the score calculated?
We weigh five things: how many pages were reachable (30%), title uniqueness (25%), canonical strategy consistency (25%), meta description uniqueness (10%) and the noindex pattern (10%). A broken rel="next"/"prev" chain is reported but does not move the score, since Google does not require it.
Is my page content stored anywhere?
No — each page is fetched, analyzed in memory for this one report, and discarded. We do not store or re-publish the HTML we fetch.