September 4, 2026 · LinkBoard team
Connecting related lists so people stop asking where the file is
How to point people between related resource lists without making them hunt through chat history.
Your homepage is not the only door
People arrive from an email, a calendar invite, or a teammate’s memory of “that folder with the vendor stuff.” If each directory is an island, they ping you. Put a short “related” note in the description: “Brand kit is in Northwind — brand. This folder is only the website references.”
That is internal linking in the only sense that matters: a human can walk from one collection to the other without asking.
Name the destination
“See other folder” is useless. “Client delivery checklists (password required)” tells people whether to bother. Use the same words the team already uses in conversation. Clever names are how things get lost.
If two directories overlap, say which one is canonical. Overlap without a note produces duplicate saves and arguments.
Two-way pointers
If A points to B, B should mention A. Otherwise you strand people. This is not architecture for crawlers. It is how you stop the “I thought this lived in the other place” loop.
Keep the pointers in descriptions or in a dedicated link titled “Related: …” with a note. Do not rely on everyone remembering the graph.
If they click and bounce
The destination is confusing or the first screen is a dump. Fix the summary. Put the three most important links at the top via favorites or ordering. If they stay but still email you, the next step is missing — add a note that says who to ask or what to do after reading.
Navigation problems are usually writing problems. More folders will not fix a vague sentence.