Should you really avoid canonicals pointing to page 1 on paginated pages?

Why does this statement challenge established practices?

Pagination has long been an SEO headache. For years, Google itself has recommended different approaches: rel="next"/"prev" tags (abandoned in 2019), canonical to page 1, or self-referential canonical on each paginated page.

Mueller now decisively states: pointing all paginated pages to the first one via canonical equates to telling Google to ignore pages 2-10. The engine interprets this directive literally and deindexes these URLs. The issue? Their unique content goes with them.

What exactly do we mean by "unique content" on a paginated page?

In a product listing pagination, each page displays different items. A product present only on page 7 will never be indexed if that page has a canonical pointing to page 1.

The same logic applies to a paginated blog: articles that only appear on page 3 or 4 disappear from the index. Google indexes the structure of page 1, but ignores any elements exclusive to the following pages. This is particularly problematic for sites with deep inventory or extensive archives.

How does Google actually handle these pages with centralized canonical?

Google considers canonical as a strong directive. When all paginated pages point to page 1, the engine consolidates signals on this single URL and disregards the others.

Deindexation is not immediate but progressive. Pages 2-10 remain technically crawled (as long as they are linked), but their content is no longer eligible for ranking. In Search Console, they often appear as "Excluded by canonical tag" or "Detected, currently not indexed".

• The canonical to page 1 on all paginated pages causes the deindexation of pages 2-10
• The unique content of these pages disappears from Google's index
• Products or articles present only on these pages become invisible in the SERPs
• This directive is treated as a strong instruction by Google, not as a suggestion
• The deindexation is progressive but systematic on sites applying this configuration

Is this statement consistent with real-world observations?

Absolutely. For years, SEOs have noticed that sites with centralized canonical on pagination lose indexing of deep pages. Before this clarification from Mueller, many attributed it to a crawl budget issue or perceived "quality" of paginated pages.

The reality is harsher: Google does exactly what it is told. The canonical is not a suggestion; it is a consolidation directive. SEO tools like Screaming Frog or Oncrawl have long reported these pages as "canonicalized elsewhere", but few practitioners realized the extent of the loss of indexable content.

In what cases might this rule seem counterintuitive?

On sites where pagination is mainly used to split identical content into several pages (e.g., a long article artificially divided), a canonical to the complete page or to page 1 might make sense. But this is not pagination in the strict sense — it is split content.

The real trap is when this schema is applied to listings with unique content per page. Many CMSs or "SEO-friendly" templates default to a canonical pointing to page 1 across all pagination. [To be verified]: some still recommend this approach to "avoid duplication", even though it sabotages the indexing of the full catalog.

What nuances should be added to this statement?

Mueller does not say that all pagination must be indexed. He states that if you want to index the unique content of pages 2-10, do not set a canonical to page 1. This is a critical nuance.

In some cases (site with very limited crawl budget, pagination generating massive near-duplicate content), voluntary deindexation of paginated pages may be a strategic choice. But it must be a conscious choice, not a configuration accident. If your goal is to index all your products or articles, this approach is toxic.

What should be done concretely to preserve the indexing of paginated pages?

The safest solution: each paginated page should have a self-referential canonical. Page 2 points to itself, page 3 points to itself, etc. This configuration ensures that Google indexes each page and its specific content.

Another viable approach: completely remove the canonical tag on paginated pages. In the absence of an explicit directive, Google indexes the page normally. This is less clean theoretically, but it works if the internal structure (links, sitemap) is clear.

What mistakes should be absolutely avoided?

Never configure a centralized canonical to page 1 if you want to index deep content. This guarantees the loss of 90% of your inventory in the index. Another common mistake: mixing approaches. For example, self-referential canonical on pages 2-5, then canonical to page 1 on pages 6-10.

Be consistent. If you opt for self-referencing, apply it throughout all pagination. And be wary of plugins or modules that add "automatic" canonicals without your knowledge — regularly audit your source code, not just your admin settings.

How do I check that my site is correctly configured?

Crawl your site with Screaming Frog or a similar tool. Filter for paginated URLs (often identifiable via a pattern /page/2/, ?page=3, etc.). Check the "Canonical Link Element" column: each paginated page should point to itself or have no canonical.

In Search Console, go to Coverage > Excluded. If you see hundreds of URLs as "Excluded by canonical tag" corresponding to your paginated pages, it’s a warning sign. Cross-check with an export of your indexed URLs: if only page 1 of your listings show up, you have a problem.

• Set a self-referential canonical on each paginated page (page 2 points to itself, etc.)
• Audit the actual source code of your paginated pages, not just the CMS settings
• Crawl the site and check the "Canonical" column on all pagination URLs
• Analyze Search Console > Coverage for mass exclusions by canonical
• Compare the number of crawlable paginated URLs vs. those actually indexed
• Document the configuration applied to avoid regressions during CMS updates or theme changes