Pagination Canonical Wrong
Paginated lists need consistent canonical and indexing logic.
Paginated lists need consistent canonical and indexing logic; canonical signals help consolidate URL variants. It will be problematic if canonical, status code, robots and internal links suggest different goals.
Subsequent pages are not automatically duplicates of page one
The second page of a product list often contains products other than the first. A blanket canonical on page one therefore does not describe this content appropriately. Check the actual displayed entries and the independent URL of each subsequent page.
Example: Recognizing the Result
Illustrative example: /Category/? page=2 shows other products as page one, but refers to /category/ via canonical. The content is not identical.
Limit cause and implement correction
For the paginated sequence, use consistent canonical addresses of your own and directly trackable links between pages. In particular, test products that only appear further back. A pure “load more” button without corresponding reachable URLs can make it difficult to find them.
What makes you recognize a suitable correction
Treat each independent following page with a suitable canonical URL and keep it accessible via retrievable links. Check product distribution and link path.
Classification and boundaries
When is this indication not a clear error?
A true full view-all page requires a separate decision. Not every page-two URL has to get the same rule without looking at the content.
Further documentation
Pagination Canonical Wrongly Set After CMS and Cause
Many audit messages can be resolved faster if they are grouped by system, page type and technical cause. CMS indentations are only linked where Pagination Canonical incorrectly set has a clearly own cause or fixed route in the respective system.
Frequent causes of this error
Related SEO Errors
Appropriate Seitenreport checks
This error should not be checked in isolation. The following tools and clusters help to narrow down the cause faster and to cleanly prioritize the affected URL groups.