Explaining the ‘rel=prev/next’ saga of 2019 and how it changed SEO

The history of search engines is a relatively brief one. SEO as a concept has only been around for around two decades or so but in that time there have been some notable moments. One of which is the rel=prev/next saga that got tech SEOs heated up around 2019.

While it wasn’t exactly headline news the story did cause a lot of consternation in the search optimisation community and was emblematic of Google’s lack of communication.

Contact Us

What was ‘rel=prev/next’?

‘rel=prev/next’ was a piece of code that informed Google that a particular web page was part of a series of pages.

For instance, you might have written several pieces of content about search engine optimisation and at the end of each piece of content, you’d include a piece of code to indicate that the next article is related to it.

‘rel=prev/next’ was also a handy thing for eCommerce sites which would use it to group products together into categories.

Why did Google remove it?

For many years, Google had explicit instructions on their site that said to include ‘rel=prev/next’ so that its crawlers could understand the relationship and context from one page to another.

Then, one day, that page just disappeared. This left many confused. Do we all continue to use ‘rel=prev/next’ or not? Should we remove it? Will our rankings be affected if we do or don’t do anything? You can see how this lack of communication caused issues in the SEO community.

The reason Google removed the guidance, and the insistence that it was used if brands wanted to explain the relationship between content clusters, was essentially because they got cleverer.

Through internal linking examination and the content itself, they are better able to identify the relationship between content.

Problem was… they never actually told anyone that!

What is the search engine giant saying now?

Well, it turned out that Google had stopped caring about ‘rel=prev/next’ for several years before they let everyone know.

The only reason that Google went ahead and made a statement about the removal of the ‘rel=prev/next’ guidance was that their webmaster trends team saw that it wasn’t being used anymore by Google search.

Finally, Google said in a Tweet the following:

‘Spring cleaning! 

As we evaluated our indexing signals, we decided to retire rel=prev/next. 

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! #springiscoming’

Nice and clear, right?

While users may well like content all on one page, thousands upon thousands of words on one page covering multiple topics isn’t exactly the most helpful content.

That final sentence – ‘Know and do what’s best for *your* users!’ – is the one we recommend webmasters keep in mind.

Should I remove it from my site?


Thankfully, if you still have ‘rel=prev/next’ dotted around your site you don’t need to do it. Having it on your site won’t cause any harm and, in fact, ‘rel=prev/next’ is still used by search engines such as Bing.

As well as Bing, the World Wide Web Consortium still recommends using it to ensure sites are accessible to everyone.

How to do category optimisation in 2024

So now that ‘rel=prev/next’ is consigned to the history books, what can you do to optimise the categories on your site?

Well, in essence, all you need to do is ensure your content structure and internal linking are logical. Google is smarter than it has ever been and if done right there is no reason it can’t figure out the clusters of content you’ve created. Google wants brands to focus on being helpful, it will do the rest.

As well as focusing on the user here are some other best practices:

  1. Self-canonicalise each page so that Google knows which page is the preferred one on your site.
  2. Creating clear, logical URLs not only helps users but they are preferred by Google now they have retired ‘rel=prev/next’.
  3. Avoid using fragment identifiers (hashtags) in URLs, Google ignores them and might not crawl your paginated content.
  4. Deoptimisie paginated pages so that search engines know to display the main page
  5. Don’t ‘noindex’ paginated pages as this can restrict the level of traffic your site receives

A future without ‘rel=prev/next’ seems fine then?

While Google’s lack of communication about ‘rel=prev/next’ was frustrating, the fact is that the removal of the code had very little impact because Google had the systems in place to categorise content in a better, more natural way.

Consciously linking to relevant pages and ensuring your work is helpful are both things worth consciously doing.

To learn more, get in touch with us today.

Contact Us

Deeper insights