Most advice about organizing notes is about structure: tags versus folders, PARA versus Zettelkasten, how big a note should be. Almost none of it is about titles, even though the title is the one piece of metadata that gets read more often than anything else in the note. Content only gets read when a note is opened. A title gets read every time a note is listed — in a sidebar, a search result, a link autocomplete, a backlinks panel — which is far more often than it gets opened.

That asymmetry is the whole argument for taking titles seriously. A note with weak content but a precise title is still findable and still linkable. A note with excellent content but a title like "Notes" or "Untitled 3" is functionally lost the moment it scrolls out of view, because nothing about its listing tells you what's inside.

The five places a title does all the work

A title shows up, alone, with no surrounding content, in more places than most people notice:

The sidebar or note list. Scanning for a specific note means reading titles top to bottom, not opening candidates one by one.
Wiki-link autocomplete. Typing [[ and a few letters shows a list of titles to pick from. If three notes are all titled some variant of "Project Notes," autocomplete stops being useful and starts being a guessing game.
The Quick Switcher or any fuzzy-jump command — it matches against titles, so a vague title is invisible to a tool built specifically to find notes fast.
Search results. A results list shows titles first and a content snippet second. A title that describes the note lets you pick the right result without reading every snippet.
The backlinks panel. Every note that links to this one shows this note's title as the destination. A vague title makes every inbound link vague too, no matter how precise the linking note was.

Five surfaces, and every one of them shows the title with none of the content behind it. If the title doesn't carry the information, nothing else in that moment does either.

What a title that isn't pulling weight looks like

None of these are dramatic mistakes — they're just titles that were an afterthought, written to satisfy the "notes need a title" requirement rather than to be useful later:

Generic nouns. "Meeting," "Ideas," "Notes" — accurate in the moment, indistinguishable from every other note with the same generic title a month later.
First-line-as-title. Whatever sentence you typed first becomes the title verbatim, even when that sentence was a throwaway opener ("ok so thinking about this more") rather than a summary of what the note is about.
Dates on non-daily notes. A date tells you when, not what. That's exactly right for a daily note, where the date is the whole point of the title — but a project note or a reference note titled "2026-08-14" forces you to remember what happened that day just to recognize it.
Never revisited. A title written on the first sentence and never touched again, even after the note's actual subject drifted somewhere else entirely over the following weeks.

None of these fail immediately. They fail three weeks later, in a search result list or a wiki-link autocomplete, when the title is the only information available and it says nothing.

Titles are the addressing system for links

This matters more in a note app with wiki-links than in one without, because a title isn't just a label there — it's an address. Typing [[Q3 Budget Review]] only works, and only autocompletes usefully, if a note with that title (or something close enough to recognize) actually exists. A vague title doesn't just make the note hard to find in a list; it makes every future link to that note harder to write, because the person writing the link has to remember or guess the exact vague phrase instead of a distinctive one.

This is also the case for renaming freely early on. A note's title should describe what's actually in it now, not what you expected when you created it — and since a link by title updates automatically when the title changes, renaming costs nothing structurally. The real cost of a stale title isn't broken links; it's the accumulating gap between what the note says and what its address claims, which is exactly the gap that makes titles useless for scanning.

A rule that actually works

The test that cuts through most title indecision: could you decide whether to open this note without opening it? A title passes that test when it's specific enough to disambiguate from every other similarly-themed note, and it fails when two or three notes in the same list could plausibly share it.

In practice, that means:

Lead with the distinguishing word, not the category. "Q3 Budget Review," not "Meeting: Q3 Budget Review" — the word "Meeting" describes ten other notes; "Q3 Budget" describes one.
Three to seven words, roughly. Long enough to be specific, short enough to read at a glance in a sidebar without wrapping onto two lines.
Skip the date unless the note is a date. Daily notes should be dated. Almost nothing else should be, because the date competes with the actual subject for the few words a title has room for.
Rewrite the title after the note settles, not before. A note started under one title and evolved into something else keeps the old title only out of inertia — updating it once, when the subject is clear, is a one-time cost that pays off every time the note is searched or linked afterward.
Don't reuse near-identical titles. Two notes called "Onboarding Notes" and "Onboarding Notes (2)" are a search result list's worst case — neither one is distinguishable from the other without opening both.

None of this requires a system, a convention doc, or buy-in from anyone else — it's a habit applied at the moment a note is created or, better, revisited once its subject is clear. The payoff shows up immediately, not eventually: the next wiki-link autocomplete, the next Quick Switcher jump, the next search result list that's actually legible instead of a wall of "Notes" and "Untitled."

Try it in practice: Indenta is a free, offline-first outliner — nested notes, backlinks, tags, and peer-to-peer sync, with no account required. Start writing in your browser, or read the User Guide first.

← All articles