Resources · 87
Paginated lists: make catalogs accessible and crawlable
Coordinate URLs, links and incremental loading so items deeper in a collection remain discoverable.
· 3 min
What this guide helps achieve
- Inventory list states
- Give each page an address
- Choose canonical URLs appropriately
- Test incremental loading
- Handle endings and changes
Quick check
- Should the whole series canonicalize to page one?
- Does a sitemap replace pagination links?
- Does Google use rel next and prev for pagination?
Step-by-step method
- 01
Inventory list states
Separate pagination, filters, ordering and internal search. Define useful reader states and pages intended for indexing. Record item count, order and behavior when the collection changes. A single policy for every parameter can hide useful pages.
Deliverable: states and intentions map.
- 02
Give each page an address
Google recommends distinct URLs and accessible links for paginated pages. A fragment alone is insufficient to represent a separate page for this purpose. Provide links to subsequent pages and navigation that helps restore position. Do not rely solely on a load-more click.
Deliverable: URLs and discovery paths.
- 03
Choose canonical URLs appropriately
Pages displaying different items are not copies of page one. Google recommends a self-canonical URL for each page in the series. Examine sorting and filters that duplicate content separately. A sitemap can signal URLs but does not fix navigation that leaves them unreachable.
Deliverable: state-specific canonical policy.
- 04
Test incremental loading
Compare the initial response and the interactive interface. Check access to deeper items when scripts fail and understandable state after back navigation, reload and URL sharing. Measure accumulated resource weight when many cards are appended.
Deliverable: reader and discovery tests without mandatory interaction.
- 05
Handle endings and changes
A nonexistent page should not silently appear as a successful empty list without a status decision. Test the final page, empty categories and withdrawn products. After changing page size or order, check links, canonical URLs and saved addresses; avoid redirecting the entire series to its beginning.
Deliverable: edge cases and handling map.
Reusable worksheet
Complete with your authorised observations. These fields are a working template, not observed results.
| Field | Information to record |
|---|---|
| States | Pagination, filters, order and search; purpose of each URL |
| Discovery | Links to pages and deeper items without mandatory interaction |
| Indexing | Canonical URLs, directives and relevant sitemap inclusion |
| Journey | Back navigation, shared state, list ending and script failure |
Worked example
Illustrative situation
Fictional example: a library displays twenty records and reveals the rest only after a JavaScript click.
Decision and expected evidence
It retains the button for reading convenience while adding addressable pages, continuation links and a self-canonical URL for each page.
Distinguish the mechanisms
| Mechanism | Purpose | Check or limitation |
|---|---|---|
| Classic pagination | Reach distinct pages | Check links and position restoration |
| Load more | Append items to one view | Also provide reachable URLs and links |
| Infinite scrolling | Continue reading without an obvious page change | Test memory, keyboard and shareable state |
Management indicators
| Indicator | What it measures | First action |
|---|---|---|
| Reachable depth | Final pages reachable through links | Fix navigation breaks |
| URL coherence | Distinct states with justified canonical URLs | Address inappropriate consolidation |
| List weight | Resources and memory after additional cards | Limit accumulation and test mobile |
Common pitfalls
- Check links and position restoration
- Also provide reachable URLs and links
- Test memory, keyboard and shareable state
Frequently asked questions
Should the whole series canonicalize to page one?
No when each page shows different items. Examine pagination guidance and the actual content of each state.
Does a sitemap replace pagination links?
No. They serve complementary needs; test links that people and search engines can follow.
Does Google use rel next and prev for pagination?
Google no longer uses them for this purpose. Prioritize distinct URLs and crawlable links over markup without the expected effect.
Official references
References consulted: . The method and worksheet propose checks to adapt to your context; they do not constitute certification.
Continue exploring
Related analysis
