Skip to content

Pagination rel=next/prev Checker

Check for rel=next and rel=prev pagination tags and validate their usage for multi-page content.

Pagination rel=next/prev CheckerGratisOn-Page SEOChecks a live URL

Enter a public URL. We fetch the live page and analyse what search engines and AI crawlers see.

Key features of the pagination (rel=next/prev) checker

  • Detects rel=prev and rel=next link tags and their URLs
  • Checks for a canonical tag
  • Warns about relative pagination URLs
  • Explains how Google handles pagination today

How to use the pagination (rel=next/prev) checker

  1. Pick a paginated URL

    Open page 2 of a blog archive or category and copy its address.

  2. Run the check

    Paste the URL and run the tool.

  3. Review the tags

    See whether rel=prev, rel=next and a canonical are present, and whether the URLs are absolute.

  4. Check the canonical target

    View the page source and confirm the canonical points to the page itself, not to page 1.

  5. Check the page links

    Make sure the page has normal <a href> links to the next and previous pages.

What is a pagination (rel=next/prev) checker?

A pagination checker looks at the tags that connect the pages of a series, such as page 2 of a blog archive or a product category. Enter a URL and this tool fetches the page and shows whether it has <link rel="prev">, <link rel="next"> and a canonical tag, with the URLs the pagination tags point to.

It warns when a rel=next or rel=prev link uses a relative path instead of a full URL, and it notes when a page has no pagination tags, which is normal for pages that aren't part of a series. Each page in a series should normally have a self-referencing canonical (page 2 points to page 2, not to page 1), so the posts or products listed on deeper pages stay discoverable.

Google said in 2019 that it no longer uses rel=next and rel=prev as an indexing signal. It finds paginated pages through normal <a href> links instead, so crawlable links to the next and previous pages matter more than the tags. Other search engines may still read the tags, and they do no harm.

Limits: the tool checks one page. It doesn't follow the series or confirm that the linked pages return 200, and it checks that a canonical exists, not where it points. It reads the HTML before JavaScript runs, so for infinite-scroll pages check separately that real page links exist.

Why use a pagination (rel=next/prev) checker?

Pagination mistakes hide content: a canonical from every page back to page 1, page links that only work with JavaScript, or noindex on deeper pages can stop search engines reaching older posts and products. Checking one paginated URL shows whether the basics are in place.

Pagination (rel=next/prev) checker: frequently asked questions

Something else? Ask the team

Does Google still use rel=next and rel=prev?

No. Google said in March 2019 that it had stopped using them for indexing. Bing has said it uses them as hints for discovering pages, so keeping them is harmless.

Should paginated pages canonicalise to page 1?

Usually not. Page 2 lists different items from page 1, so pointing its canonical at page 1 can stop those items being found. Give each page a self-referencing canonical, or, if you have a fast view-all page, canonicalise the series to that.

Should paginated pages be noindex?

Not by default. Indexable paginated pages help search engines reach deeper content. If you do noindex them, keep them linked and crawlable so the items they list are still found.

How should infinite scroll work for SEO?

Back infinite scroll with real paginated URLs (such as ?page=2 or /page/2/) that load directly and are linked with <a href>, and update the URL as the user scrolls. Search engines don't scroll, so content that only appears on scroll may never be crawled.

Is this a PageRank checker?

No. PageRank is Google's internal link-based score. Google stopped showing it publicly in 2016, so no tool can show a real PageRank. This tool checks pagination tags.

Meer AI-vermeldingen winnen?

Pagination rel=next/prev Checker is one piece of the puzzle. See how ChatGPT, Gemini, Perplexity, and Google AI Overviews actually view your brand, and get a prioritised list of fixes, with a free AEO & GEO audit from AI Rank Lab.

One check is a start. The audit checks the whole site.

Voer een gratis AEO- en GEO-audit uit or Bekijk prijzen.

  • Scores SEO, answer-engine (AEO) and generative-engine (GEO) readiness
  • Lists the fixes, page by page
  • Then track whether ChatGPT, Gemini, Perplexity and Google AI Overviews cite you
fieldnote.app4,571 credits

Site audit

fieldnote.app · SEO, AEO and GEO

Illustrative data
SEO
82
+6
AEO
64
+11
GEO
58
+9
Pages
48
Fixesby impact
  • /pricing · Missing H1High
  • /blog/guide · No FAQ schemaMedium
  • /llms.txt · Not foundMedium
  • /about · Meta description too longLow

See where your whole site stands

Paste your site. The free audit scores it for SEO, answer engines and generative engines, with the fixes.