Pagination: Non-200 Pagination URLs

URLs contained in the rel=”next” and rel=”prev” attributes do not respond with a 200 ‘OK’ status code.

This can include URLs blocked by robots.txt, no responses, 3XX (redirects), 4XX (client errors) or 5XX (server errors).

Pagination URLs must be crawlable and indexable and therefore non-200 URLs are treated as errors, and ignored by the search engines.

How to Analyse in the SEO Spider

View URLs with this issue in the ‘Pagination’ tab and ‘Non-200 Pagination URLs’ filter.

The non-200 pagination URLs can be exported in bulk via the ‘Reports > Pagination > Non-200 Pagination URLs’ export.

Read our tutorial on ‘How To Audit rel=”next” and rel=”prev” Pagination Attributes‘.

What Triggers This Issue

This issue is triggered when URLs in the rel=”next” and rel=”prev” attributes do not respond with a 200 ‘OK’ status code.

For example:

https://www.screamingfrog.co.uk/

Has the tag:

<link rel="next" href="https://www.screamingfrog.co.uk/page2/">

But https://www.screamingfrog.co.uk/page2/ returns a 404 ‘Page Not Found’ response code.

How To Fix

Ensure paginated URLs are to canonical, indexable pages – so they can be crawled and indexed.