Operational article · published

Design Search Paths for Pagination and Infinite Scroll

Keep later collection items reachable with infinite scroll or Load more. Work through three stable page URLs, real links, and a fresh page-three visit.

Reviewed 2026-11-18 · Google Search guidance, fictional collection example
01

The task and the failure mode

Built for: Content strategists, SEO leads, designers, and developers assigning durable ownership to services, markets, resources, and conversion paths. This guide is for the person who must ensure users and crawlers can reach collection items without relying on continuous client interaction and leave a decision trail that implementation, editorial, analytics, or operations can review.

Keep infinite scroll or Load more for people who want it. Give every batch a stable public URL that opens its own items directly, and link each batch to the next with a real anchor. A page-three item should be reachable from page one without a click handler fetching more items or a visitor scrolling. Test that path separately from the enhanced interface.

Frame

Decision brief

Give each batch a durable URL tied to an absolute page number. A fresh request for page three should open page three’s items, even when the visitor arrives from a bookmark with no history or saved state.

Put the next-page link and item links in the initial document for this design. JavaScript can append the next batch to the current view. The normal link remains available to people who open it in a new tab or whose JavaScript fails.

Before approving the release, traverse the expected item path one page at a time. Then check the enhanced path separately so a working Load more button cannot hide a missing document link.

Choose canonicals for paginated and duplicate URLs →

Compare button, router link, and anchor markup →

Ask

Questions to answer before changing the system

  1. 01Which exact item should a visitor find in the final batch, and what is its public detail URL?
  2. 02Can you request page two and page three directly and see the expected items without first opening page one?
  3. 03Does each nonfinal batch contain a real href to the next batch in its initial HTML?
  4. 04After JavaScript appends a batch, can the visitor still use the item link and the normal page URLs?
  5. 05If the visible address follows the current batch, does reloading that address open the same batch?
02

Workflow

  1. 01Pick a small collection with a known order. Record the ordered item IDs in each batch, expected next-page addresses, and the detail URL for one late item. Keep the dataset and sort order fixed while comparing builds.
  2. 02Open the collection’s first URL in a fresh session with JavaScript off. Inspect the initial response and follow its next-page anchor. A Load more button alone supplies no next-page URL.
  3. 03Repeat from the second document. Check its own first and last item and its next link. On page three, find the target’s detail anchor and follow it. Confirm that page three ends the sequence.
  4. 04Paste the second and third URLs into a fresh tab. Their expected item lists should still appear. This catches a route that correctly changes the address bar but returns the first batch on direct entry.
  5. 05With JavaScript on, use the intended Load more or infinite-scroll interface once per remaining batch. Check order, duplicates, the target link, and the unchanged first batch. If the address updates as a batch becomes primary, reload it and check the visible batch.
  6. 06At the end of the enhanced sequence, check that Load more is exhausted and no next link points at a phantom fourth batch. Open the target detail link and confirm the response is for the selected item (C110 in the example), rather than a generic collection page.
  7. 07Keep the initial link and direct document checks as release criteria. If either path loses the target, record where it stops. Review crawl and indexing observations on their own dates after release.
03

Evidence to retain

  • A fixed inventory of item IDs, expected order, batch URLs, and the target’s detail URL.
  • The initial response status, item IDs, and outbound next or detail hrefs for each document.
  • A direct-load observation for pages two and three with no prior collection state.
  • The enhanced flow’s actual batch order and repeated or missing IDs, plus the reload result if it changes the URL.
  • The final response URL and canonical for each direct batch request, so a redirect or a duplicate first page is visible.
  • The last batch’s terminal control state and the detail response for the target item.
  • The first-batch control result and the exact release and test date.
Sample

Worked design: reach item C110 on page three

Collection
A fictional ceramics catalog has ten items in ID order. The first batch has C101–C104, the second C105–C108, and the third C109–C110. The last item links to /catalog/ceramics/c110.
Interaction-only design
The first response has four items and a Load more button. Two button actions can reveal C110, but the initial response exposes no next-page anchor. A reader following document links stops at C104.
Document path
The collection at /catalog/ceramics links to /catalog/ceramics?page=2. Page two serves C105–C108 and links to /catalog/ceramics?page=3. Page three serves C109–C110, links to the C110 detail URL, and ends the sequence.
Direct entry
A fresh visit to /catalog/ceramics?page=3 should open C109 and C110 with their detail links. Reopening it must work without earlier requests, saved scroll state, or a fragment such as #page-3.
Enhanced flow
Load more can append C105–C108 and then C109–C110, preserving order and the ordinary next-page link while another batch remains. If the address updates to page three when that batch becomes primary, reload should show C109–C110.
04

Pagination release checks

  • The first batch remains the same.
  • Pages two and three have durable URLs and return their own items on direct entry.
  • Initial HTML contains both of the sequential links.
  • The final batch contains an ordinary anchor to the target detail page.
  • The final batch does not offer a next page.
  • The enhanced path reaches the same item in order, without repeating earlier items.
  • A direct batch URL does not redirect back to the first page.
  • Each distinct batch declares its own canonical URL.
  • The target detail link opens the intended item.
  • If the enhanced view shows a new batch URL, it opens that batch after reload.
Measure

What to measure—and what it does not prove

  • Count how many of the three expected batch documents are reached by following only the supplied anchors. Record a broken hop by its source and destination.
  • Compare observed IDs with the expected list for each directly loaded batch. A page can have a working next link and still return the wrong items.
  • Keep the enhanced-path result separate. Record the interaction used, the resulting item order and any address change.
  • Use later crawl and indexing evidence as a separate observation. Reachability in a fixture establishes the tested path, while search visibility is an external outcome.
05

Boundaries and caveats

The case is a fictional worked design. Its rows specify expected observations for a release check.

Google documents that it generally follows anchor hrefs and does not click buttons to reveal items. JavaScript can still improve the experience and render content.

Google recommends separate canonicals for distinct paginated pages. Review sorting and faceted variants under their own policies, especially when combinations create an unbounded URL space.

This sample tests how the complete path reaches a late item. The React example covers a single control’s markup and the canonicalization guide covers representative URL selection.

06

Primary sources

  1. Google Search Central: Pagination and incremental page loadingdevelopers.google.com
  2. Google Search Central: Paginated loading for infinite scrolldevelopers.google.com
  3. Google Search Central: Make links crawlabledevelopers.google.com
  4. WHATWG HTML Standard: History interfacehtml.spec.whatwg.org
Next

Start with one bounded case

Choose one real late item in a collection you maintain. Record its expected batch and detail URL, then follow the document path before opening the enhanced view. If it fails, fix the first broken hop and retest the same item.