rel=prev/next: Does Google Still Use It?

Facts checked: 2 November 2026.

No. Google no longer uses rel="prev" and rel="next" to understand paginated pages. Its pagination guidance says so directly, and adds that other search engines may still use the tags.

You do not need to remove the tags if they are already there. But if your SEO course or an old article told you to add them to make Google understand page 2, 3 and 4 of a blog or shop, that advice is out of date. This guide covers what to do instead.

What was rel=prev/next?

Many websites split a long list across several pages: a blog archive, a shop category, a list of search results. These are called paginated pages. The addresses often look like /blog/page/2/ or /shop/?page=3.

Years ago, site owners added two small tags in the page head, one pointing to the previous page and one to the next. The idea was to tell a search engine that these pages belong together in a series.

Google says it no longer uses them. They are not a setting you need to get right for Google.

What should you do for paginated pages?

Google’s current advice is simple and mostly about how the pages are built. These points come from its pagination guidance.

1. Give each page its own URL

Every page in the series should have its own address, for example a ?page=2 parameter or /page/2/. Google treats each address as a separate page.

2. Link the pages with real links

Link each page to the following page with a normal link (an a tag with an href). Googlebot finds later pages by following those links. Google also suggests linking from each page back to the first page, as a hint that it is the best starting point.

Google does not click buttons or run JavaScript that needs a visitor’s action. If the next page only appears after a "Load more" button or an infinite scroll, check that real links to the later pages also exist.

3. Give each page its own canonical

Do not point the canonical tag of page 2, 3 and 4 at page 1. Google says not to use the first page as the canonical for the whole sequence, and to give each page its own canonical URL. In practice, each page points to itself.

This is a common mistake. A canonical on page 3 that points to page 1 says that page 3 is a copy of page 1, which it is not. Google’s page on consolidating duplicate URLs calls a canonical a strong signal, so a wrong one can cause real confusion.

4. Do not use fragments for page numbers

Do not use a # fragment, such as /blog/#page2, to number pages. Google says it ignores fragments, and Googlebot may skip a next link that only differs by fragment.

5. Keep filters and sort orders out of the index

Filtered or re-sorted lists show the same items in a different order. These create many near-copies of the same list. Google suggests keeping them out of the index with a noindex robots meta tag, or discouraging crawling of those URL patterns with robots.txt.

Note that this advice is for filter and sort variations. It is not advice to noindex page 2, 3 and 4.

What are the noindex pitfalls?

Noindex is a strong tool. Google’s noindex documentation says that when Googlebot sees it, the page is dropped from Search results. Three pitfalls come up often with paginated pages.

  • Noindexing pages 2 and later. It can look tidy to keep only page 1 in search. But those pages are then removed from results, and Google’s documentation does not describe what happens to the links on a noindexed page. If those links are your only route to the products or posts on later pages, do not count on them. Make sure those items are also reachable through other links, such as category links, internal links or a sitemap.
  • Noindex and robots.txt together. For noindex to work, the page must not be blocked by robots.txt. If it is blocked, the crawler never sees the rule, and the page can still appear if other pages link to it.
  • Expecting a quick change. Google notes that it may take months to revisit a page. You can use the URL Inspection tool in Search Console to request a recrawl.

If you are unsure, do not noindex the pages. The pagination guidance describes the default approach as indexing the main paginated pages, each with its own URL and canonical.

Titles and descriptions on page 2 and later

Google’s guidance says pages in a sequence can share titles and descriptions, and Google will still recognise and index them as a series. You do not need to write a unique title for every page number. A pattern such as "Blog, page 2" added by your theme or SEO plugin is acceptable.

What about infinite scroll and Load more?

These patterns are usually built with JavaScript. They are pleasant for visitors, but Google’s crawlers do not click buttons, so content that loads only after a click may not be found. Google’s advice is to make sure links to the later content are standard a href links, to follow its JavaScript SEO practices, and to use a sitemap to help it find all your content.

How does the Arva SEO audit handle page 2 and later?

Arva SEO’s site audit takes pagination into account in one specific way. For checks run since 26 October 2026, page 2 and later of a listing, such as /page/2/ or ?paged=3, no longer count towards the missing-title and duplicate-title checks, or the missing-description and duplicate-description checks. They are expected to share the first page’s text, or have none.

The audit also has canonical checks. One flags a page whose canonical "points to another URL". If a page 2 or page 3 address is flagged, check that its canonical points to itself and not to page 1. The audit shows you where to look. You decide whether it is a mistake.

Checklist: pagination

  • Every page in the series has its own address.
  • Each page links to the next page with a normal link.
  • Each page links back to the first page.
  • Each page has a canonical that points to itself.
  • No page number uses a # fragment.
  • Filter and sort variations are kept out of the index.
  • Pages 2 and later are not noindexed unless I have a clear reason.
  • Content behind "Load more" or infinite scroll also has linked page addresses.
  • Old rel="prev" and rel="next" tags can stay, but I do not rely on them.

Common questions

Should I remove rel=prev/next tags from my site?

You do not have to. Google ignores them. Other search engines may still read them, according to Google’s guidance.

Should every paginated page rank?

Not necessarily. Page 1 usually targets the main search. Later pages mostly help visitors and search engines reach the items on them.

Do I need a different title on every page number?

No. Google says pages in a sequence can share titles and descriptions.

Next step

Run an audit on your website and look at the canonical results for your listing pages. The free SEO site audit tool page explains what the audit checks and how the fix lists work.

Arva SEO runs more than 70 checks and tells you where to look in plain words. It works with public websites on any platform, including WordPress, Shopify, Wix, Squarespace and Webflow. The free plan covers your first website.

Written by

From Arva SEO

Your first website is free.

Create an account in a minute, verify your website and run your first audit. No credit card required.