Backlinks vs. Tags (and when to use each)

TL;DR

Use backlinks to create bidirectional associations between notes and rely on incoming backlinks to surface related content.

Briefing Cornell Notes

Briefing

Backlinks and tags solve different problems in note-taking: backlinks connect related notes so associations become searchable over time, while tags group notes into lists for quick retrieval. The practical takeaway is to stop overthinking the choice—use backlinks for “entities” (people, places, companies, meetings) and use tags when you want a curated collection of notes (like all recipes or all article drafts).

A backlink is a bidirectional link between two notes. In Reflect-style systems, it shows up under an “incoming backlinks” section, making it easy to see what other notes reference a given note. That visibility matters because it turns scattered notes into a navigable web: when a note is linked from other places, the relationships become explicit and can be reused later. The recommended structure inside a backlink note is also specific: keep evergreen or contextual “legacy” information in the backlink note itself (for example, background on a person, a topic, or why a recurring meeting happens), then store the actual event details underneath as bullet points. Over time, those bullets accumulate and remain tied to the entity note through the backlink.

Tags, by contrast, are labels that add a note to a collection. Clicking a tag surfaces a list of all notes carrying that label—effectively a personal library. This is especially useful when the goal isn’t to express relationships between items, but to retrieve a set. The transcript gives examples like a “book” tag to browse all books, a “recipe” tag to access a digital cookbook, a “city” tag to pull up all city-related notes, and an “article draft” tag to review unpublished writing. Tags can also support personal workflows such as listing “daily reflections,” though the choice depends on whether the user prefers to manage daily entries inside a daily note (where backlinks can still show an organized list in incoming backlinks).

A simple rule of thumb ties everything together: backlink anything that starts with a capital letter—typically names of people, places, companies, and similar entities. For everything else, ask whether the need is association (backlinks) or collection (tags). When uncertain, the guidance leans toward backlinks, with an option to convert later by adding a tag inside the note if a list view becomes more important. Finally, the workflow can be accelerated with an AI prompt for backlinks (e.g., “decorate my writing with backlinks”), while tags still require manual setup because they depend on personal categorization preferences. The overall message is to start using both methods immediately, because repetition makes the decision feel obvious.

Cornell Notes

Backlinks and tags in Reflect-style note systems serve different roles. Backlinks create bidirectional connections between notes and surface related notes under incoming backlinks, making relationships easy to find and reuse. A practical rule is to backlink “entities” (capitalized items like people, places, companies, and meetings) and store evergreen context in the entity note, with specific instances (like meeting details) as bullets underneath. Tags are for building lists—clicking a tag shows all notes in that category, such as recipes, book notes, city notes, or article drafts. Tags usually require manual decisions, while backlinks can be partially automated with an AI prompt.

What makes a backlink different from a tag in day-to-day use?

A backlink is a bidirectional link between two notes and appears in an “incoming backlinks” area, so it highlights which notes reference a given note. That makes associations visible and searchable over time. A tag, instead, labels a note so it joins a collection; clicking the tag produces a list of all notes with that label, without necessarily expressing relationships between the items.

Why does the transcript recommend putting evergreen context in the backlink note and event details underneath?

The entity note (the backlink target) is where stable background information belongs—such as who someone is, context about a topic, or why a recurring meeting happens. The specific instance details (like the actual meeting notes) go underneath as bullet points. Because those bullets live in the linked note, they remain tied to the entity and show up through incoming backlinks.

When should a user backlink something like “San Francisco” or “Alex Macau”?

Backlink entities—especially anything that starts with a capital letter. “San Francisco” (a city) and “Alex Macau” (a person) are treated as entity notes. The backlink captures the association (e.g., San Francisco is in California) and keeps the network of relationships organized.

When does a tag make more sense than a backlink?

Use tags when the goal is to retrieve a set of notes as a list rather than to express relationships between notes. Examples include “recipe” for a cookbook-style list, “book” for a library of book notes, and “article draft” for all unpublished writing. The transcript contrasts this with backlinks, which are better for linking related entities.

How can a daily reflection be handled using backlinks or tags?

One approach is to keep daily reflections inside a daily note and backlink the daily reflection note so it still appears in incoming backlinks, giving an organized list by date. Another approach is to add a tag to daily reflections so clicking the tag shows all daily reflections. The choice is presented as personal preference.

What role does AI automation play in the workflow?

Backlinks can be accelerated with an AI prompt such as “decorate my writing with backlinks,” which can add backlinks automatically. Tags are described as trickier because they depend on individual categorization choices, so they generally require manual setup.

Review Questions

If you want to quickly browse all notes about recipes, which mechanism fits best—backlinks or tags—and why?
How would you structure an entity note that receives multiple backlinks over time (what goes in the main note vs. what goes underneath)?
What decision rule helps determine whether something should be a backlink or a tag when you’re taking notes quickly?

Key Points

1
Use backlinks to create bidirectional associations between notes and rely on incoming backlinks to surface related content.
2
Backlink capitalized “entities” such as people, places, companies, and meetings to keep relationships explicit.
3
Store evergreen context in the backlink target note, then add specific instances (like meeting details) as bullet points underneath.
4
Use tags to build lists for quick retrieval when the goal is collection rather than relationship mapping.
5
Tags work best for categories like recipes, books, cities, and article drafts where a single click should show all matching notes.
6
When uncertain, default to backlinks; add tags later if you need a dedicated list view.
7
Automate backlink creation with an AI prompt, but expect to set up tags manually due to personal categorization preferences.

Highlights

Backlinks turn relationships into something you can browse via incoming backlinks, while tags turn labels into clickable lists.

A clean pattern emerges: evergreen context lives in the entity note; week-to-week specifics go underneath as bullets.

Backlink “entities” (capitalized items) and tag collections (recipes, books, article drafts) to avoid cognitive overload.

Daily reflections can be managed either through backlinks (organized by date) or tags (click-to-list), depending on preference.