Skip to content
Browse all guides

Issue #13 · important

Issue 13

What is this issue?

This issue checks whether paginated pages have proper pagination signals and canonical tags so search engines can understand the relationship between sequence pages.

For paginated pages to pass this check:

  • The page must be correctly identified as paginated (through URL patterns like /page/2/ or pagination navigation elements)
  • The page should have at least one of the following:
    • A canonical tag
    • Rel="next" and/or rel="prev" link tags
  • Pagination URLs should be valid and properly formatted

Example: If you have a blog with multiple pages (/blog/page/1/, /blog/page/2/, etc.), each page should include pagination signals so search engines understand they're part of a sequence.

Why does it matter?

Proper pagination markup is important for:

  • Crawlability: Clear pagination signals help search engines discover and crawl all pages in a sequence
  • Indexability: Canonical tags on paginated pages prevent indexing confusion
  • User experience: Well-structured pagination helps both users and search engines navigate through content

When paginated pages lack proper signals, search engines may:

  • Have difficulty understanding the relationship between pages
  • Index pages inconsistently
  • Miss some pages in the sequence during crawling

Resolving this issue improves your SEO health score by ensuring search engines can properly navigate and understand your paginated content.

How to fix it

  1. Identify paginated pages: Ensure your pagination URL patterns are consistent (e.g., /page/2/, ?page=2, etc.).

  2. Add canonical tags: Include a canonical tag on each paginated page pointing to the preferred URL for that page.

  3. Use rel="next" and rel="prev": Add these link tags in the head section to indicate the relationship between sequential pages:

    <link rel="prev" href="https://example.com/blog/page/1/" />
<link rel="next" href="https://example.com/blog/page/3/" />

  4. Ensure valid URLs: Make sure all pagination URLs are valid and accessible.

  5. Keep navigation crawlable: Ensure pagination links are in standard HTML <a> tags that search engines can follow.

  6. Test implementation: Crawl your paginated pages to verify that canonical tags and pagination signals are properly detected.

Examples

Example 1: Blog with proper pagination signals

Scenario: A blog with multiple pages that has proper pagination markup.

Passes because:

  • Each paginated page has a canonical tag
  • Rel="next" and rel="prev" tags are present
  • Pagination URLs are valid and accessible
<!-- On page /blog/page/2/ -->
<link rel="canonical" href="https://example.com/blog/page/2/" />
<link rel="prev" href="https://example.com/blog/page/1/" />
<link rel="next" href="https://example.com/blog/page/3/" />

Example 2: Paginated page missing signals

Scenario: A paginated page that search engines cannot properly understand.

Fails because:

  • No canonical tag is present
  • No rel="next" or rel="prev" tags are present
  • Search engines may not understand the page relationship
<!-- On page /blog/page/2/ -->
<!-- Missing canonical and pagination signals -->

Example 3: E-commerce category pages

Scenario: An e-commerce site with paginated category pages.

Passes because:

  • Each page has self-referencing canonical tags
  • Clear pagination navigation is present
  • URLs follow a consistent pattern
<!-- On page /shop/category/page/2/ -->
<link rel="canonical" href="https://example.com/shop/category/page/2/" />
<link rel="prev" href="https://example.com/shop/category/" />
<link rel="next" href="https://example.com/shop/category/page/3/" />

How PixyScan detects this

PixyScan identifies pagination issues through these steps:

  1. Fetches the page: PixyScan requests the URL and checks the HTML response.

  2. Detects pagination: The system looks for evidence that the page is paginated:

    • URL patterns (like /page/2/, ?page=2, ?paged=2)
    • Pagination navigation elements in the HTML (next/prev links, numbered page links)

  3. Extracts signals: PixyScan extracts:

    • Canonical URL from <link rel="canonical">
    • Rel="next" and rel="prev" URLs from link tags
    • Pagination navigation links from the body

  4. Evaluates completeness: The system checks if paginated pages have:

    • At least a canonical tag, OR
    • Rel="next" and/or rel="prev" signals

  5. Flags issues: PixyScan triggers warnings when paginated pages lack these essential signals.

The detection uses only raw HTML—no JavaScript rendering is performed.

References