Paginated content uses rel=next/prev or canonicalizes to page 1
Why it matters
Paginated routes without rel=next/rel=prev or canonical consolidation get indexed as disconnected, competing URLs — page 2 of /products ranks against page 1 for the same keywords, splitting link equity and diluting ranking signals. Googlebot treats each paginated URL as a standalone thin page, which suppresses the whole listing's authority and can trigger soft-404 classification on sparse pages.
Severity rationale
High because pagination errors split PageRank across competing URLs and suppress category-level rankings.
Remediation
Emit pagination metadata on every listing route. In app/products/page.tsx, compute the canonical strategy based on the current page:
export async function generateMetadata({ searchParams }) {
const page = Number(searchParams.page) || 1
return { alternates: { canonical: `/products?page=${page}` } }
}
Prefer a single canonicalized view-all page when the listing fits under 100 items.
DetectionPro
The detection method for this pattern is part of AuditBuffet Pro.
The full method (what to look for, pass and fail conditions, and how results get reported) ships inside the Advanced SEO Audit. The pattern definition, severity rationale, and remediation remain openly licensed under CC-BY-4.0.
Taxons
History
- 2026-04-18·v1.0.0·Initial import from seo-advanced·automated