Home SEO Google hasn’t supported rel=next/prev for a while (thanks for telling us)

Google hasn’t supported rel=next/prev for a while (thanks for telling us)

Google has stopped supporting the rel=next/prev markup it launched back in 2011. The interesting part is, Google has not supported it for the past few years and didn’t tell anyone!

What is rel=next/prev? Rel=next/prev was markup you were able to add to your web pages to communicate to Google that these pages are all part of a larger set of pages. So if you have an article split into several pages, you were able to tell Google that those pages were all part of the same set. Google would then combine all the signals and content from all the pages in the set.

Google stopped supporting it. Google’s John Mueller confirmed today on Twitter that Google stopped supporting it completely.

We don't use link-rel-next/prev at all.

— 🍌 John 🍌 (@JohnMu) March 21, 2019

When did Google stop supporting it? It is unclear as to when Google stopped supporting it. John Mueller said it was a “number of years ago.”

We noticed that we weren't using rel-next/prev in indexing for a number of years now, so we thought we might as well remove the docs :).

— 🍌 John 🍌 (@JohnMu) March 21, 2019

Why did Google stop supporting it? Google said it saw sites approach pagination differently since it stopped supporting it, so the company feels that people are building great sites without the markup.

Since it hasn't been used for a while, it seems like most sites are doing pagination in reasonable ways that work regardsless of these links. People make good sites, for a large part :).

— 🍌 John 🍌 (@JohnMu) March 21, 2019

For the most part, we just index the pages as we find them, so as we've recommended for a long time, it's good to make sure that all pages can stand on their own.

— 🍌 John 🍌 (@JohnMu) March 21, 2019

What does Google recommend now? Google is now recommending to try to make sure they put their content on a single page and not break them into multiple pages for the same piece of content. Google said on Twitter “Studies show that users love single-page content, aim for that when possible, but multi-part is also fine for Google Search. Know and do what’s best for *your* users!”

Communication breakdown. The crazy part about this is that Google has been recommending the use of the rel=next/prev throughout the years. In fact, Google just recommended that we use it in the latest Google webmaster hangout from two days ago!

So webmasters, SEOs, developers and companies have been putting resources into implementing this markup and maintaining it without any benefit at all.

It makes you wonder what else is in Google’s help documentation that Google currently do not support?

Update 3/22/19: Google has apologized for the rel=next/prev mixup.

Must Read

SEOs must focus on intent research practices in 2020

SMX speaker, Frédéric Dubut of Bing, explains why 2020 is the year SEOs need to evaluate their intent research practices to keep up with...

Businesses need to think differently about customer feedback data in 2020

Contributor and SMX speaker, Adam Dorfman, thinks the customer feedback ecosystem is going to play an even more important role in the coming year...

How verticalization and zero-click will impact local search in 2020

In a recent post on the SparkToro blog, Moz founder and search guru Rand Fishkin predicted that 2020 will be the year Google is...

Make it easy for search engines to rank your website in 2020

Contributor and SMX speaker, Fili Wiese, explains why it’s important to audit your website in 2020 to help search engine algorithms better understand your...

Microsoft Advertising launches sweepstakes for advertisers

To kick off a new year, Microsoft Advertising has launched an incentive sweepstakes for advertisers. How to enter. To enter the Microsoft Advertising Sweepstakes,...