Rel Next
rel="next" is an HTML link relation that marks a page as the next page in a sequence, such as a paginated series.
Start here
- Confirm crawlable pagination links exist.
- Include rel=next and rel=prev in the
<head>. - Self-canonical on each paginated page.
- Don't rely on rel=next for SEO signals.
But here's the thing: Google stopped using it for indexing years ago.
What I'd do first
- Confirm your paginated series has crawlable links between pages (like 'Next' and 'Previous' buttons).
- Keep rel=next and rel=prev in the
<head>for completeness. - Set each page's canonical tag to itself.
- Don't rely on rel=next for SEO—focus on user-friendly navigation and unique content.
Plain-English take
Think of rel=next as a signpost telling browsers and search engines which page comes next in a series. It's like saying 'Page 1 leads to Page 2, Page 2 leads to Page 3.' Google used to use these signs to understand [pagination](/pagination/), but now it treats each page as an independent entry. The signpost still works—it just isn't the main navigation for crawlers anymore.
When it actually matters
If you have a paginated series—like product listings, blog archives, or image galleries—rel=next still matters for:
- Clearly documenting page order in your code.
- Supporting search engines that may still use it (legacy systems or smaller crawlers).
- Keeping your HTML semantic and structured for future-proofing. But for today's Google indexing, internal linking and good content are far more important.
What I got wrong
I used to think rel=next was a direct ranking signal or a way to consolidate page authority. The reality is Google deprecated its use years ago. Another mistake: assuming rel=next replaces crawlable pagination links. You still need proper HTML links (Next/Previous buttons) for users and crawlers. And don't point canonical tags to the category root—each paginated page should canonicalize to itself unless you have a deliberate view-all strategy.
Next step
Quick answers
Does Google still use rel=next for indexing?
No. Google's official guidance now says it does not use rel=next or rel=prev for pagination discovery. The markup remains valid HTML and can help with code readability.
Sources
Primary documentation is linked directly. Anything commercial is marked nofollow.
- Google Search Central Blog: Pagination with rel='next' and rel='prev' — Google's original official guidance on how rel='next' and rel='prev' were intended to work.
- MDN Web Docs: rel HTML attribute — Authoritative HTML reference for what the rel attribute means in general.
- Google Search Central / Google announcement referenced in SEO coverage — Google later stated it no longer uses rel='next' and rel='prev' for indexing; use Search Central-era guidance and later Google commentary together.
Notes from Callum Bennett.