A folder can hold a note in exactly one place. A link can connect it to everything it is actually about. Backlinks — the automatic reverse side of every link between notes — are the feature that turns a pile of notes into a web of thought, and they have quietly become standard across modern note tools. This post covers what they are, why they work, and the practical patterns that make them useful rather than decorative.
Links and backlinks, defined
A link between notes is explicit: while writing note A, you reference note B. In most tools, including Notez, you do this inline — type [[ in the editor and pick the note to link.
A backlink is the automatic reverse view: note B now shows that note A references it, without anyone editing note B. Write "this follows the approach in [[Cursor pagination decision]]" inside a postmortem, and the pagination note gains a backlink to the postmortem, kept in sync by the tool.
That asymmetry is the whole trick. You pay for one deliberate link at writing time; the system maintains the connection from both ends forever. Rename, edit, revisit — the Linked notes section on any note answers the question folders never could: what else refers to this?
Why this beats folders for connected notes
Folders force a note to live in one place, chosen at filing time, when you know the least about what the note will matter for. A note about a caching bug in the billing service — does it go in /bugs, /billing, or /caching? Any answer is wrong for two of the three future searches.
Links sidestep the question. The note simply mentions the bug, the service, and the technique, linking each. Later, standing on your Billing service note, the backlinks show every note that ever touched it — the bug, the design discussion, the postmortem — regardless of where any of them "live".
The practical consequence: hierarchy becomes optional. You still might use sub-notes or tags for coarse grouping (Notez has both), but the load-bearing structure is the link graph, which grows as a side effect of writing rather than as filing work.
Patterns that make links pay off
Link entities, not everything
The highest-value links point at stable entities: projects, systems, people, recurring topics, key decisions. Create a note per entity — even a nearly empty one — and link to it whenever the entity comes up. The entity note becomes a hub whose backlinks are a self-maintaining index of everything related.
Linking every noun, by contrast, produces a graph as noisy as no graph. If you would not ever visit the note to see what references it, it does not need to be a link target.
Write decision notes and link them from both directions
When you make a meaningful decision, give it its own note: the choice, the alternatives, the reason. Then link it from wherever the work happens. Months later, the decision note's backlinks show every place the decision touched — and any note about the work links back to the why. This is the cheapest architecture-decision-record system that actually gets maintained.
Use backlinks as an inbox for hub notes
A hub note does not need constant editing. Because backlinks accrue automatically, the hub stays current by construction: open your Search infrastructure note after a month and its backlink list is the recent activity report. Periodically, promote the important backlinks into the body of the hub as a curated summary.
Create the note from the link
You do not need to leave the note you are writing to declare a new topic. In Notez, the [[ picker can create the target note on the spot: type the name, create the stub, keep writing. The first mention of [[Import pipeline rewrite]] both declares the topic and creates its hub note — and every later mention links to that same note, so backlinks accumulate from day one.
Links and search are complements, not rivals
Semantic search (finding notes by meaning) and link graphs answer different questions. Search answers "what do I have about X?" — probabilistically, across everything. Backlinks answer "what refers to this, exactly?" — deterministically, with human intent behind every edge. Search finds notes that happen to be similar; a link records that you, at writing time, judged two things related.
A vault with both — Notez pairs [[ linking and synced backlinks with embeddings-based search — lets you be lazy in both directions: capture without filing because search will find it, and link only what deserves linking because the graph is for judgment, not coverage.
Getting started without a migration project
You do not need to restructure anything to begin. Three steps:
Pick five entities you touch weekly — current projects, main systems — and create a stub note for each.
Link on mention, starting today. Whenever one of them comes up in a new note, type
[[and link it. Do not backfill old notes; the graph grows forward.Check backlinks before starting work. Opening the hub note before a meeting or a task takes ten seconds and reliably surfaces the context you forgot you had.
Within a few weeks the payoff shows up on its own: you open a note and find, in its backlinks, a connection you made two months ago and had completely forgotten — which is, in the end, exactly what a note system is for.
Continue reading
Beyond folders: how Notez organizes notes — tags, sub-notes, boards and eleven custom property types, and why Notez has no folders.
Links that survive a rename — Notez stores a link as the target note's id, so renaming a note keeps every link and backlink to it.
Every property, one click away — a relation property such as Project gets a sidebar section with its ten most-linked notes.