Resources · 87

Paginated lists: make catalogs accessible and crawlable

Coordinate URLs, links and incremental loading so items deeper in a collection remain discoverable.

· 4 min

Global network map in an empty intelligence briefing room AI-generated editorial illustration

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

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

Acceptance case to reproduce

Fictional example: these inputs describe no customer or observed result.

View case inputs
{
    "page_2": "/catalog?page=2",
    "canonical": "/catalog",
    "next_link": "<button>More</button>"
}

Expected decision

Page 2 needs its own canonical and crawlable href links to subsequent pages.

Fictional variations to test

Page 3 exists only after clicking a JavaScript button.

Also provide an href link to a directly loadable URL. Verify that this URL exposes the expected items without replaying earlier clicks.

Following pages use only #page=2 and #page=3.

Use distinct URLs for crawlable pages. A fragment alone is not a separate page for Google; check navigation, reload and link sharing.

Sorting changes between pages and a product disappears from the journey.

Define stable ordering with a tie-breaker. Replay the journey during a concurrent addition and record missing or repeated items; crawlability does not guarantee completeness.

Evidence to retain

  • Present href links and content obtained by directly loading each page.
  • URL, canonical and reload results without a click history.
  • Traversed identifiers, sort order and anomalies during an addition.

Additional reference : Google Search Central — Pagination and incremental page loading [EN]

Verification procedure

  1. Record each page’s URL, canonical and links.
  2. Reach subsequent content without a JavaScript button.
  3. Keep crawlable href links and the self-canonical. Open each URL directly and compare displayed items; a different address repeating the first page does not validate continuation.

Google Search Central — Pagination and incremental page loading

Reusable worksheet

Complete with your authorised observations. These fields are a working template, not observed results.

FieldInformation to record
StatesPagination, filters, order and search; purpose of each URL
DiscoveryLinks to pages and deeper items without mandatory interaction
IndexingCanonical URLs, directives and relevant sitemap inclusion
JourneyBack 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

MechanismPurposeCheck or limitation
Classic paginationReach distinct pagesCheck links and position restoration
Load moreAppend items to one viewAlso provide reachable URLs and links
Infinite scrollingContinue reading without an obvious page changeTest memory, keyboard and shareable state

Management indicators

IndicatorWhat it measuresFirst action
Reachable depthFinal pages reachable through linksFix navigation breaks
URL coherenceDistinct states with justified canonical URLsAddress inappropriate consolidation
List weightResources and memory after additional cardsLimit 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.