Pagination SEO: Why Page 2 Should Usually Canonicalize to Itself

01

Definition

Pagination splits a larger collection into multiple URLs: page 1, page 2, page 3, and so on. Ecommerce categories, article archives, search listings, forum threads, review lists, and long indexes commonly use this pattern to keep individual responses manageable.

The canonical mistake is treating those later pages as duplicates of page 1. Google's current pagination documentation says URLs in a paginated sequence are treated as separate pages and explicitly advises against using the first page as the canonical for the rest of the sequence. Instead, each page should normally have its own canonical URL. ^[1]

That guidance follows a simple content fact: page 2 usually contains different products, posts, or records than page 1. Canonicalization is for duplicate or very similar content, not for declaring one member of a sequence more important than all the others. ^[2]

02

Mechanism

A canonical annotation tells Google which URL a site prefers as the representative of duplicate or near-duplicate content. Google describes rel="canonical" as a strong canonicalization signal, while also noting that Google ultimately chooses the canonical based on multiple signals. ^[2]

In a paginated sequence, each page exposes unique items. If page 2 points its canonical to page 1, the site is effectively telling Google that page 2 is a duplicate of page 1 even though its primary inventory differs. That can make discovery and indexing of items reachable mainly from deeper pages less reliable.

Google's pagination guidance therefore recommends a unique URL for each page, such as a ?page=n parameter, and a canonical pointing to that page's own URL. ^[1] The first page can still be emphasized through internal linking, navigation, and user-facing design without pretending that every subsequent page is duplicate content.

Crawlable pagination links are the other half of the implementation. Googlebot should be able to follow standard links from page 1 to page 2 and onward. Google's ecommerce URL guidance recommends links that use normal crawlable anchors rather than JavaScript-only navigation and also recommends self-referencing canonicals on indexable pages. ^[3]

03

Examples

An ecommerce category has 240 shoes and displays 24 per page. Page 1 lists products 1 through 24, page 2 lists 25 through 48, and so forth. Canonicalizing every page to page 1 incorrectly collapses distinct inventory into one canonical target. A cleaner implementation gives every page a stable URL and self-canonical, then provides crawlable next-page and page-number links.

A publisher's archive works similarly. Page 1 shows the newest posts, page 2 shows older posts, and each archive page links to individual articles. If later archive pages are canonicalized to page 1, the canonical signal says their unique article lists are duplicates. The better model is to treat the sequence as related but distinct pages.

Infinite scroll can still be indexable if it has a paginated URL structure underneath the interaction. Google's lazy-loading and pagination guidance recommends persistent unique URLs for chunks so crawlers can discover the content without needing to simulate scrolling behavior. ^[1] The interface can feel continuous to users while the crawl architecture remains discrete and linkable.

Sorting and filtering introduce a different problem. A category sorted by price may contain the same products as the default category in a different order. That can be genuinely duplicate or near-duplicate content, depending on the implementation and search value. Canonical decisions for sort parameters should be made separately from page-number decisions. Do not copy a blanket “all parameters canonical to page 1” rule across both cases.

Another common mistake is inconsistent first-page URLs. A site might expose both /shoes and /shoes?page=1, then link to them interchangeably. Google's ecommerce URL guidance recommends choosing a consistent first-page URL pattern. ^[3] Consistency reduces duplicate signals and makes internal linking easier to audit.

04

Boundaries

Self-canonical pagination does not mean every paginated URL must rank or even be strategically important. It means the canonical markup should describe the content truthfully. Google may choose to show the first page more often for broad category queries, and a site can link strongly to page 1 as the preferred user entry point without mislabeling deeper pages as duplicates.

Do not confuse pagination with faceted navigation. Page numbers represent successive chunks of one ordered collection. Filters can create alternate subsets, and sorts can create alternate orderings. Those URL families may need separate crawl, canonical, or indexability policies based on whether they provide distinct search value.

Likewise, do not resurrect obsolete rel="next" and rel="prev" mythology as a requirement for Google. Current Google pagination documentation focuses on crawlable links, unique URLs, and correct canonicalization. The durable architecture is discoverable pages, not legacy markup rituals.

For QA, test page 1, a middle page, and a deep page. Confirm each returns 200, has a stable unique URL, self-canonicalizes when indexable, links to neighboring pages using crawlable anchors, and exposes its unique item links in rendered HTML. Then make sure sitemap and internal-link policies do not contradict the pagination strategy.

The key distinction is sequence versus duplication. Page 2 belongs to the same collection as page 1, but it is not page 1. Canonical markup should preserve that distinction.

References

Sources behind this record

1. Pagination Best Practices for Google — Google Search Central (accessed August 18, 2026)
2. How to Specify a Canonical with rel=canonical and Other Methods — Google Search Central (accessed August 18, 2026)
3. Ecommerce URL Structure Best Practices — Google Search Central (accessed August 18, 2026)

Corrections

Correction history

No corrections recorded.

To report an error, use the public corrections path.