Pagination
Splitting a long list of content, such as products or blog posts, across numbered pages.
The Definition
Pagination breaks a category, archive or search result into a series of pages (page 1, 2, 3 and so on). Google no longer uses rel="next" and rel="prev" as an indexing signal, so each paginated page has to be crawlable through normal links and stand on its own.
Why It Matters
Products and posts deep in a series are only found if crawlers can reach those pages. Canonicalizing every page to page 1, or loading items only through infinite scroll, can hide them from search engines entirely.
Best Practices
Link paginated pages with plain <a href> links crawlers can follow
Give each paginated page a self-referencing canonical
Give each page in a series its own URL (?page=2 or /page/2/)
Back infinite scroll with paginated URLs
Keep important items close to page 1 or link them from elsewhere
Mistakes to Avoid
- 1
Canonicalizing page 2, 3 and onward to page 1
- 2
Noindexing paginated pages and so cutting off the items they link to
- 3
Loading more items only with JavaScript buttons that have no URL
- 4
Relying on rel="next" and rel="prev" for Google
Audit Checks
How Digispot AI identifies and fixes related issues
A "next/previous" pagination link points to a page that redirects or errors instead of loading normally.
Impact: Broken pagination wastes crawl budget and can leave deeper pages undiscovered.
Point rel=next/prev links at live, working pages. • Remove stale pagination links. • Re-crawl to confirm.
The page could not be fetched at all — the request never returned a usable document (redirect loop, timeout, DNS failure, or refused connection).
Impact: Visitors and search engines hit the same dead end: the page can't be read, indexed, or ranked, and any links pointing at it are wasted.
Open the URL in a browser and confirm the failure (e.g. "too many redirects" or a timeout). • Fix the server, DNS, or redirect rule responsible so the URL returns a healthy 200. • Re-run the audit to confirm the page is reachable again.
We could not read this page's content properly — the HTML may be broken or the page returned an error mid-load.
Impact: If our crawler cannot read the page, search engines likely struggle with it too, so it may not rank.
Open the page and confirm it loads fully without errors. • Validate the HTML for unclosed tags or broken markup. • Re-run the audit once the page loads cleanly.
The page shows an "not found"-style error message but still returns a success (200) status code.
Impact: Google keeps crawling and may index these empty pages, wasting crawl budget and cluttering results.
Return a real 404 (or 410) status for pages that no longer exist. • Redirect to a relevant live page if there is one. • Avoid showing error text on a 200 page.
A redirect hop downgrades the connection from HTTPS to HTTP before resolving.
Impact: It exposes users to an insecure hop (MITM/mixed-content) and signals distrust to search engines, bleeding ranking equity.
Rewrite the redirect target to stay on HTTPS. • Make sure no hop drops to http://. • Re-crawl to confirm the chain stays secure.
This URL redirects round in a circle and never lands on a real page.
Impact: A looping URL can't be crawled or indexed, and visitors hit a browser error.
Trace the redirect rules for this URL. • Point it at a single final destination that returns 200. • Re-crawl to confirm the loop is gone.
Related Terms
Canonical Tag
An HTML element that tells search engines which URL is the preferred version of a page.
Crawl Budget
The number of pages search engines will crawl on your site within a given time period.
Internal Linking
Links that connect pages within the same website to distribute authority and help users navigate.