Local technical SEO audit

Pagination Series Auditor

Check whether category, listing, search, forum, or article-series pages form a complete, internally linked sequence. Review gaps, loops, canonical and indexability conflicts, repeated items, and infinite-scroll fallback evidence.

Browser-only processing No paid API Deterministic checks CSV, JSON, and Markdown exports
Private by default: Processed locally in your browser. Your files are not uploaded. A normal refresh clears the imported data.

Add data

Import pages or crawl evidence

Accepts HTML or HTM files, ZIP archives containing HTML/CSV, crawl CSV, a JSON array of page records, or pasted page URLs. Maximum recommended import: 100,000 pages and 75 MB uncompressed.

ZIP entries are read in memory and never extracted to the server. Processed locally in your browser. Your files are not uploaded.
    For list fields in CSV, separate values with a pipe (|), semicolon, or line break.
    If supplied, the filename is resolved against this URL. Expected URLs are used first when counts match.

    Map and configure

    Identify series, page numbers, and HTML evidence

    Blank uses common pagination landmarks, then conservative link-text detection.

    Expected behavior

    Choose the policy this series should follow

    Analyze

    Run the local series audit

    What this audit cannot prove

    • It does not guarantee that search engines will discover, crawl, index, or rank a page.
    • Saved HTML cannot prove response headers, live status codes, JavaScript interaction, or a changing result count.
    • Cursor sequences and intentionally capped or skipped result sets need human context.
    • Duplicate titles or H1 templates are reported as patterns, not automatic critical errors.
    • rel=next and rel=prev are supplemental evidence, not requirements.

    How the analysis works

    The auditor creates a directed graph for each series. Every supplied page becomes a node with its page number or cursor, response evidence, canonical, indexability, title, H1, item set, depth, sitemap state, and pagination links. It then evaluates named checks against the policy you selected.

    Sequence integrity

    Find missing or duplicate page numbers, skipped edges, self-loops, next-link cycles, cross-series jumps, and orphan pages.

    Directive consistency

    Compare canonicals and indexability with the selected policy, including page-one duplicate forms and unhealthy canonical targets when supplied.

    Content continuity

    Compare adjacent item sets after exclusions, report title/H1 templates, and show overlap evidence without hiding reasoning behind one score.

    Frequently Asked Questions

    Does this auditor crawl my live website?

    No. It analyzes only the HTML, ZIP, crawl CSV, JSON, or expected URL data you add. It does not request live pages or interact with infinite scroll.

    Does the tool require rel=next and rel=prev?

    No. Normal anchor links with href values are the primary crawlability evidence. rel=next and rel=prev are treated only as supplemental signals.

    Which canonical policy is correct for pagination?

    The tool does not enforce one universal policy. Choose the policy your implementation is intended to follow, then review findings that conflict with that selected policy.

    Can saved HTML prove response headers or rendered infinite-scroll behavior?

    No. Saved HTML can show markup, links, directives, and implementation evidence, but it cannot prove response headers, live status codes, or runtime interaction. Add crawl CSV fields when those signals matter.

    How are duplicate and pinned items handled?

    Adjacent item sets are compared after optional pinned or promoted item exclusions. You can adjust warning and critical overlap thresholds before running the audit.

    Does a clean result guarantee indexing?

    No. A clean result is evidence that the supplied sequence is internally coherent under the selected settings. It does not guarantee discovery, crawling, indexing, or rankings.

    Reviewed Jul 2026 · Sources and limitations

    Review details: 2026-07-13 · Marc LaClear · v1.0

    Reference sources:

    Known limits:

    • Checks are based on publicly fetchable HTML, response headers, and browser-side input. They do not use private Google Search Console, analytics, or ranking data.
    • Scores and warnings are diagnostic aids, not guarantees of ranking improvement or Google indexation.
    • Pages blocked by robots.txt, login walls, bot protection, heavy JavaScript, or network timeouts may return incomplete results.
    • Validate critical fixes with official Google tools such as Search Console, Rich Results Test, Lighthouse, and your own crawl data.

    Report an issue with this tool