Choose canonicals for a paginated article archive
Give distinct archive pages their own URL and canonical, connect sequential discovery links and test clean versus duplicate pagination variants.
A later archive page contains a different list
Page two of an archive normally introduces articles that are absent from page one. Canonicalizing every list page to the first page describes those distinct lists as duplicates. Decide the intended URL for each real page before adding a generic canonical rule.
Google’s pagination guidance explicitly recommends a unique URL and self-referencing canonical for each paginated page, rather than using the first page as every canonical. It also recommends sequential links that crawlers can follow. [Google Search Central: Pagination and incremental page loading]
A small archive URL policy
This is an illustrative URL family on a reserved example domain. It describes a proposed implementation contract, not a claim about the current pagination architecture of this site.
| Requested URL | Intended meaning | Canonical or response |
|---|---|---|
| /insights | First list page | Self canonical to /insights |
| /insights?page=1 | Duplicate first-page form | Choose a consistent redirect or canonical to /insights |
| /insights?page=2 | Second distinct list page | Self canonical to the intended page-two URL |
| /insights?page=3 | Third distinct list page | Self canonical to the intended page-three URL |
| /insights?page=999 with no such page | Invalid list page | Honest missing-page response under the route policy |
Keep the parameter convention stable. Do not mix /insights/page/2 and ?page=2 as equally promoted addresses without deciding which one is preferred. Internal links, sitemap policy and canonical hints should support the same URL family.
A filtered list may have a different decision from a numbered continuation of the main archive. Review whether it offers a distinct useful collection, repeats the same content in another order or creates an empty combination. A blanket rule for every query parameter will miss those differences.
Verify the archive as a reader and a direct URL request
- Request page one and later pages directly and inspect their actual article sets.
- Inspect the rendered canonical and any redirect chain.
- Follow sequential links with keyboard and mobile navigation.
- Verify that later articles have working contextual links and indexable destinations.
- Test duplicate first-page, invalid page number and empty-list states.
An HTTP 200 and a canonical tag do not guarantee indexing. Record technical delivery separately from Search Console’s later selected canonical and indexing state. If the archive changes while new articles are published, repeat the boundary checks for the first and last valid page.
I would keep the URL matrix with the archive component so that a later routing change preserves the meaning of page two instead of quietly folding it into page one.
Sources
AI-assisted writing and an AI-generated editorial cover. Source links and checked dates are listed below; illustrative examples are labeled in the text.
- Google Search Central: Pagination and incremental page loading — checked 2026-10-18