Zettelkasten Tags: When to Use Them Instead of Links

Zettelkasten tags help you retrieve groups of notes; links explain how particular ideas relate. Use a tag when you want to find a set again, and a written link when one note supports, challenges, or extends another. fenbs can keep selected source references and accepted findings with the project that uses them, without becoming your note archive.

How do you start a useful tagging system?

1. Choose a real retrieval question, such as which interview notes still need checking.
2. Create one tag for that group and write a short definition of when to apply it.
3. Apply it to a small sample of notes, then run the search you expect to use later.
4. Add a direct link wherever two notes have a relationship worth explaining.
5. Review the results after a writing session. Keep tags that helped you find material and revise ones that produced a confusing pile.

Start with a few tags rather than designing a classification for every subject you might study. The test is whether you can find something useful without remembering its exact title. A tag that never answers a retrieval question is another label to maintain.

When should you use a tag rather than a link?

Two notes tagged attention may concern unrelated questions. One might discuss classroom concentration and another the visibility of a warning label. The tag makes them candidates for review; it does not establish that evidence from one setting applies in the other.

A relationship sentence does more work: “This observation suggests a possible exception to N014, but the participants differ.” It tells your future self why to follow the link. In his account of working with slip boxes↗ (opens in a new tab), Niklas Luhmann describes both cross-references and a keyword register. Finding a way into the collection and navigating its ideas are complementary jobs.

Which tags are worth keeping?

Keep a distinction between subject tags and process tags. A subject tag says what the note may help you think about. A process tag says what you still need to do with it. That prevents a search for checked findings from returning every rough thought on the same subject.

• Subject: use a familiar term that you would actually search, such as wayfinding or estimation.
• Process: use a clear state such as needs-source or needs-rewrite, and remove it when the work is complete.
• Type: add a tag such as counterexample only if finding that kind of note is useful in your writing.
• Avoid: a different tag for every author, chapter, or temporary project when existing source fields or project links already answer the question.

Give ambiguous terms a definition in a short tag guide. For example, define whether evidence means a source supports the note or simply that a source is attached. Those are different claims. Avoid treating a label such as verified as a guarantee that a note will remain correct in every context.

The AI second brain guide covers the wider role of reusable knowledge; keep this tagging setup focused on retrieval. When a checked note informs a current project, fenbs can preserve its meaning beside the work and source references.

How should tags work in a real note app?

Use the syntax your app supports and test it before applying it everywhere. For example, Obsidian documents tags↗ (opens in a new tab) created with a hash sign, tag searches, and nested tags. Those are app behaviors, rather than rules that every Zettelkasten must follow.

A short hierarchy can help when a parent search is genuinely useful. You might group source-check/pending and source-check/complete if you often need both together. A deep tree with a unique branch for each note usually recreates a filing system that takes more thought to maintain than to search.

Keep links separate from this hierarchy. Obsidian supports internal links↗ (opens in a new tab) to notes and locations within them. Whatever app you choose, open a tagged result, follow its explanatory link, and check that you reach the intended idea rather than merely another note with matching vocabulary.

What does a tagged research note look like?

Say you are researching instructions for a museum exhibit. You notice that a warning appears after the action it is meant to prevent. Write a focused note about the sequence, identify the specific document and page, and distinguish what you observed from what you infer about visitors.

• Title: A warning must appear before the action it changes.
• Source: the exhibit instruction sheet, its revision, and the relevant page or image.
• Tags: instruction-order and needs-source-check, if those match your defined uses.
• Connection: compare with N014 on placing prerequisites before a procedure.
• Boundary: this is a design observation; visitor behavior has not been tested.

Once you check the reference, remove the pending tag. If a project owner chooses to revise the instructions, record that choice separately from your research idea. A useful hypothesis does not become an approved direction just because it has a tidy label.

How do you repair an overgrown tag collection?

Start from a failed search. If attention, focus, and concentration return overlapping results, inspect a sample before merging them. They may be duplicates, or you may have intended a distinction that never made it into the tag guide.

Choose a preferred term, update affected notes, and check saved searches or index entries that depend on the old spelling. For a tag with hundreds of results, create a short index note that introduces the most useful paths. Do not replace one overloaded tag with dozens of categories you will never retrieve.

Keep the project conclusion current when you change the underlying notes. Portable AI memory depends on preserving a useful explanation, not on copying every organizational label. fenbs keeps that explanation with the project’s current work.

How to do this with fenbs

1. Create a free account, free for one person with no credit card, and add the project using your research.
2. Add selected source locations to Links and listings. Include the note identifier and what the source helps establish.
3. Write the checked conclusion and its limits in AI context notes. Keep unanswered research questions as tasks rather than settled rules.
4. Connect a supported assistant through Integrations, ask it to read project context before working, and save Where we left off before stopping.

fenbs is not the right fit for managing your note tags or browsing a linked note graph. Keep those in your note app. Use the distinction in shared AI brains when a personal research finding becomes work that people and connected assistants must continue together. The second-brain topic hub has more ways to organize that knowledge.