Pagination review
- Stable page URLs
- crawlable next and previous links
- unique item sets
- self-canonical pages when appropriate
- consistent sorting
- handling of invalid page numbers
- links to important items
Infinite scroll
An infinite interface should have accessible paginated URLs or another crawlable fallback so content does not depend only on a user scroll event or transient client state.
Apply Pagination to a real website decision
Use pagination as a decision framework rather than a detached definition. Start with the user or business task, collect discovery paths, response codes, rendering, directives, canonicals, internal links, sitemaps, duplication, and selected URLs, document uncertainty, and decide what action is justified by the evidence.
Evidence
Page-template and url-pattern evidence rather than isolated examples.
Interpretation
Explain how the observed condition affects the intended outcome: make the intended pages discoverable, interpretable, internally connected, and maintainable.
Verification
Recrawl the affected patterns, inspect rendered output and directives, and monitor indexation and search behaviour over time.
Questions to answer about Pagination
- What user, search, commercial, compliance, or operational task does pagination affect?
- Which templates, URLs, entities, environments, or journeys are actually in scope?
- What evidence would distinguish a confirmed problem from the risk of changing directives or canonicals without understanding the intended URL model?
- Who owns the decision, implementation, approval, and follow-up?
- What measurement or retest will prove the change improved the intended outcome?
Turn pagination into an accountable record.
A documented decision or practice for pagination that can be applied to a real website.