rel next and rel prev: The Complete 2026 Guide

The rel="next" and rel="prev" link attributes tell search engines about paginated sequences. They connect page 1 to page 2, page 2 to page 3, and so on. Google announced in 2019 that these tags would no longer be a ranking signal. This guide covers what works in 2026.

What rel next and rel prev do

These attributes sit in the <head> section of HTML pages. Page 2 of a category lists <link rel="prev" href="/category/" /> and <link rel="next" href="/category/page/3/" />. The tags create a linked list of pages. Search engines use this chain to understand pagination structure.

Google dropped official support

Google confirmed in September 2019 they stopped using rel next/prev for pagination detection. John Mueller stated Google now relies on sitemaps, canonical tags, and internal links. The tags are ignored for indexing decisions. This change happened as Google's index system moved to a modern framework.

Bing and Yandex still use them

Not every search engine followed Google. Bing still references rel next/prev in their webmaster docs. Yandex also supports the tags. If your site targets multiple search engines, keep the markup in place. It costs minimal development time.

Canonical tags replace rel next/prev

The modern pagination strategy uses canonical URLs. Page 2 through page N point their canonical back to page 1. Google's Mueller recommended this approach in 2023. The canonical consolidates ranking signals. Page 1 collects the authority.

How to implement rel next and rel prev in 2026

Place the link tags in the <head> element. Use absolute URLs. Include a self-referencing link on each page. Page 3 should list both prev (page 2) and next (page 4). Moz has a reference implementation showing the correct markup structure.

<!-- Page 2 -->
<link rel="prev" href="https://example.com/category/" />
<link rel="next" href="https://example.com/category/page/3/" />

Common implementation mistakes

Developers often forget the self-referencing canonical. They also mix relative and absolute URLs. Another mistake is omitting the tags on the first and last pages. Page 1 must have rel="next" only. The last page must have rel="prev" only. Validate with a crawler after deployment.

Sitemap pagination is the priority

XML sitemaps carry more weight than link tags. Include only the canonical page 1 in your sitemap. Leave paginated pages out. Google's sitemap guidelines say you should list canonical URLs only. This approach directs crawlers to the right page.

Testing your pagination setup

Use the URL Inspection Tool in Search Console. Check that Google sees the canonical you intend. Run a crawl with Screaming Frog or Sitebulb. Screaming Frog supports pagination checks out of the box. Confirm each page in the chain links correctly.

Validating rel next/prev markup

Use the browser developer tools to inspect the <head> element on each paginated page. Verify the link tags exist and contain absolute URLs. Check that rel="next" points to the correct subsequent page. Check that rel="prev" points to the correct previous page. The first page in the series must omit rel="prev". The last page must omit rel="next". This validation step catches coding errors during deployment.

The rel next/prev audit

Review all paginated series on your site. Check for broken chains. Remove rel next/prev if you rely solely on canonicals. Add them back if Bing or Yandex traffic matters. Note the gap between your current pagination setup and search engine requirements. Audit quarterly.

Ready to Build Your Dream Website?

Let's discuss your project and create something amazing together.