You're looking for the rel next, rel previous HTML attributes: https://support.google.com/webmasters/answer/1663744?hl=en
From the source link above, here is the generic example:
In the section of the first page (http://www.example.com/article-part1.html), add a link tag pointing to the next page in the sequence, like this:
<link rel="next" href="http://www.example.com/article-part2.html">
Because this is the first URL in the sequence, there’s no need to add markup for rel="prev".
On the second and third pages, add links pointing to the previous and next URLs in the sequence. For example, you could add the following to the second page of the sequence:
<link rel="prev" href="http://www.example.com/article-part1.html">
<link rel="next" href="http://www.example.com/article-part3.html">
When developing, one of the most common development mistakes is to not end the rel next attribute on the final item in the cluster. For example, if your 5 part article ends at /article-part5, ensure you do not include a rel next to /article-part6. Seems obvious, but it's a common oversight - the real problem occurs when the server /article-part6 returns "something' with a 200 response code, which also contains a rel next directive. That means these rel next links to "fake" pages get crawled, indexed and bloat your site, add overhead for crawlers and create unnecessary duplication.