"Just search for it" is the standard answer to every question about organising notes, and it is half right. Search removes the need for most folder structures. It does not remove the need to think about findability, it relocates it.
A search box can only find words that are in your notes. If the note you need describes an idea using words you would never think to type, it is invisible, and no amount of indexing fixes that. Almost every failed search is a writing problem wearing a search costume.
Why search fails
You search for the concept and wrote the example. You remember "that thing about pricing psychology" and the note says "anchoring in the enterprise deal". Both correct, no shared words.
You wrote in shorthand. Notes taken quickly are full of pronouns and context that made sense at the time. "The approach he suggested worked better" is unfindable by any query.
Too many hits. Searching a five-year archive for meeting returns eight hundred results, which is functionally the same as zero. This is the failure mode that grows with you and the one people are least prepared for.
The words are in an image or a PDF. Scanned pages, screenshots of slides, photographed whiteboards. Some apps run OCR over these and some do not, and this is worth checking, because a screenshot-heavy archive can be substantially unsearchable without anyone noticing.
You are searching for a feeling. "That note where I finally understood the thing" has no keywords. This is the one search genuinely cannot solve, and it is what links and structure exist for.
Learn your app's operators
Most people use search as a single keyword box for years without discovering that their app supports far more. The vocabulary differs but the capabilities are nearly universal:
- Exact phrase, usually
"quoted text". The single most useful one, and the fix for high-noise queries. - Scope by location, such as
path:or a folder filter. Turns eight hundred results into twelve. - Scope by field, such as searching titles only. Extremely effective if you name notes well.
- Tag filters, such as
tag:#reading. See tags vs folders. - Date filters, created or modified. Underrated: you often remember roughly when far better than what.
- Boolean and negation, such as
-invoiceto exclude a category that dominates results.
Spend twenty minutes with your app's search documentation once. It is the highest-return twenty minutes available to anyone with more than a few hundred notes, and almost nobody spends it.
Two habits on top of the syntax:
Search titles before you search everything. If your notes are named as claims or as things, a title search is dramatically higher precision. See how to name notes.
Search by date when the topic is vague. Sorting by modified date and scanning the week you think it happened often beats any keyword you could invent.
Write so it can be found
This is where the actual improvement is. Five habits, in order of return.
1. Put the conclusion in the title. A note called Meeting 12 March is findable only by date. A note called Why we dropped the Postgres migration is findable by six different queries you might plausibly type. Titles are weighted heavily by every search engine ever built, including your app's.
2. Write the synonyms in, once. If a note is about what you call "onboarding" and the industry calls "activation", put both words in it. One clause is enough: naming the alternative terms once makes the note reachable from whichever word arrives in your head in three years. This is the cheapest findability habit there is and the least practised.
3. Never use a pronoun for the subject. "It", "he", "the approach" are unsearchable. Write the actual name at least once in every note, even when it feels redundant. Redundancy is what makes text findable.
4. Record why, not just what. Searches are usually motivated by a problem, not a topic. A note that says "we chose X because Y was too slow under Z" is reachable from all three. A note that says "decided: X" is reachable from one.
5. Add the words you would search for, deliberately. If while writing you think "I will want this when I am dealing with pricing again", write the word pricing into the note. Tags are the formal version of this and a sentence works nearly as well.
All five reduce to the same instruction: write for the person who has forgotten the context. That is the standard behind atomic notes and evergreen notes, and findability is one of its main dividends.
When search is the wrong tool
Search answers "where is the note about X". It cannot answer "what do I know about X", because that requires knowing what exists, and you cannot search for something you have forgotten you wrote.
That is what structure is for, and it is the honest limit of the search-only position:
- Backlinks show you what else referenced this note, including things you had forgotten.
- Maps of content are hand-made index notes for a topic. One per active area is usually enough, and it is the single most effective structure most people are missing.
- The weekly review is the only reliable way to keep an archive present in your head rather than merely stored.
- A knowledge graph surfaces adjacency, which is what you want when you do not yet know what you are looking for.
Search is retrieval when you know what you want. Links are discovery when you do not. An archive with only one of them is half a system.
Two things to check today
Does your app search inside attachments and images? Test it: search for a word you know is only in a screenshot. If it comes back empty, either stop storing knowledge in images or start writing a caption line under each one.
Does search cover everything? Some apps exclude archived, encrypted, or shared content from the default scope, silently. Search for something you know is in an archived note. A surprising number of "I lost that note" incidents are actually this.
More in how to organize your notes, how to review your notes, and how to take notes.