Ten things people actually use SEO Note for

Tool pages usually describe an interface and leave you to guess whether it fixes your Tuesday. This one runs the other way: ten jobs people hand to SEO Note, what they press, what is left at the end. Where the program does not solve something, the case says so instead of sliding past it.

SEO Note is a tree of notes in one file on your own machine - no account, no server of ours, no subscription. The 2.1 desktop build holds it as notes.seonote, the classic 1.3.34 build as .seo. Each case names which build it needs, because those are two different programs; each gives three or four steps with real menu names, then one line on the limit.

Three builds ship from this site. SEO Note 2.1 is the current one: an Electron app (about 121 MB installer) for Windows 10/11 64-bit and Linux x64, with Markdown, the tree editor, AI talking to a model you connect — a local one or any OpenAI-compatible endpoint, a web clipper and git sync of the file. For Android 6.0 and newer there is a release-signed APK (~10 MB) of the same interface; on the phone notes live as a folder of Markdown files on the device, and passwords, sync, the clipper and AI answer there with an explicit refusal. The classic build 1.3.34 (~2.5 MB, Win32) stays on the download page for Windows 7, 8 and 32-bit PCs, where 2.1 does not install; its notes file is .seo. All three work offline with no account: pick your build, or read how 2.1 and 1.3.34 differ.

The ten jobs at a glance

Job	What does the work	Where it stops
Research in forty tabs	Web clipper into Inbox (2.1)	Collects only while the program runs
Telegram favorites	A dated note per capture, tagged	A snapshot, not a live mirror
Notes on two PCs, no cloud	Save as… plus your own git / WebDAV / S3 (2.1)	One editor at a time
An old .seo archive	Import (2.1 on Windows)	Tested on Windows only
One note with a secret	Note or file password, Argon2 (2.1 desktop)	A lost password is unrecoverable
Exams, a thesis, a cert	Subject folders, global search, Markdown export	No flashcards, no drills
A runbook at night	Contour folder with numbered steps	Not a pager, not a vault
What a client agreed	People + Projects, notes linked to notes	No invoices, no reminders
A machine with no internet	All of it except sync and cloud AI	Updates come in by hand
The laptop on Windows 7	Classic 1.3.34, about 2,5 MB, .seo	No AI, no clipper, no sync

1. Research that lives in forty browser tabs

The tab bar is where research dies: you keep forty open because closing one feels like losing it, and two days later the page that mattered is gone with the session. Capture has to be cheaper than a screenshot.

1. Switch on the web clipper in settings - a local receiver on 127.0.0.1 behind a token, plus a clipboard watcher. Since 2.1 the browser extension ships inside the installer.
2. Select the passage, clip it; it lands in Inbox as an ordinary note with the source attached.
3. Once a day, drag clips into the project note they belong to and rename them so the title says what is inside. Delete the rest - an empty Inbox is the working state.

Where it stops: the receiver is your machine, so nothing collects while the program is closed and nothing mirrors to another device. Long version: from browser tabs to a notes tree.

2. Telegram's Saved Messages, unreadable by design

Favorites has no folders and no search that understands what you meant - links, quotes, screenshots of prices, half a recipe, in one stream older than the projects it belongs to.

So stop treating it as storage and start treating it as an inbox: copy the text, paste it into a dated note under Inbox, let a Markdown body keep your lists as lists. One tag per note, because a tag is what you will search by in three weeks. One weekend sitting a week moves those notes into their real folders. Anything you need verbatim - a clause, an address - goes in as text, not as a link you must reopen in the app.

Where it stops: no live bridge, so every capture is a snapshot and edits in the chat do not follow. Telegram favorites into a notes tree.

3. The same notes on the work machine and the home machine

Two PCs and no cloud is the real situation: a work laptop you may not put on a public drive, and a home machine where those notes would help.

1. File → Save as… moves the whole notes file to any folder, including one your git client watches; File → File properties… shows where the open copy lives and copies the path for you.
2. Turn on sync and point it at your own repository, WebDAV share or S3 bucket. Last writer wins, the older copy is kept.
3. Or skip sync: the program with its Data folder next to it is a portable install on a stick.

Where it stops: not collaborative editing - two people typing at once means one loses, and there is no web version to fall back on. Offline notes without the cloud.

4. An old .seo file from the classic program

A decade of notes in a 1.3.34 file is a real archive and a real reason not to switch, so the switch has to be about reading what you already wrote.

Install 2.1 beside the old program - import does not rewrite the source - bring the .seo tree across, then check what historically breaks: attachments, dates, nesting depth, sealed notes. Evernote .enex, Google Keep's JSON export and TreePad / KeyNote .knt take the same route. Leave the original file exactly where it was until you have read your own notes in the new one a few times.

Where it stops: .seo import is implemented and tested on Windows, and the phone build does not read it. What arrives whole and what does not: moving an old .seo file.

5. One note that has to hold something secret

A passport number, a lease, a diagnosis, the router's admin login. You want those shut while the rest of the file stays searchable and ordinary.

1. Copy the file for backup first - before any password exists.
2. Seal the single note with its own password, or encrypt the whole file; both derive the key with Argon2, which is deliberately slow.
3. Know what sealing does to search: the sealed note's text leaves the file's index entirely - it is not hidden from search, it is not in it. Keep the passphrase outside this file.

A forgotten password cannot be recovered by anyone: no reset link, no master key, no back door, and the author does not have your file. Back up before you encrypt, not after.

Where it stops: the Android build answers passwords and encryption with a refusal, so a sealed note is a desktop note. What not to paste anywhere.

6. Exams, a thesis, a certification

Study material fails the same way every year: the notes exist, and the answer is on page forty of a different file.

1. One folder per subject, tickets as notes under it, one checkbox per open question, so the unresolved ones are a countable number rather than a feeling.
2. Ctrl+Shift+F searches the whole file, Ctrl+F the open note. Naming earns its keep here: search finds the words you actually wrote.
3. Ask questions against your own notes - 2.1 talks to any OpenAI-compatible endpoint, LM Studio and Ollama included, so the corpus stays home.
4. Before the exam, export a folder to Markdown; links between notes survive, and a study partner can read the same tree in any editor.

Where it stops: no flashcards, no spaced-repetition schedule - an outliner, not a memoriser. Exam tickets in a tree, study notes with a local model.

7. The runbook that has to work at three in the morning

Incidents reward whatever opens fastest. If the runbook lives in a wiki that died with the service, you are reading chat scrollback written by whoever typed last.

1. Ops → one contour you are on call for → folders for inventory, runbooks, escalation, postmortems.
2. Write the first fifteen minutes as a checklist you could follow half-asleep: one action per step, one check after it.
3. Keep secrets out of the tree - where a step needs a credential, the note gives the vault path and entry name and stops.
4. After an incident, log the timeline in the same contour, with actions that have owners and dates.

Where it stops: not a pager, not a secrets manager, not multiplayer Confluence. Full pattern: sysadmin runbooks in a tree.

8. What each client actually agreed to

Freelance work is lost in agreements, not tasks: the scope discussed in March sits in a chat with a client whose name you no longer type correctly.

1. People - one note per client; Projects - one note per job; link the project from the client note. Links are note-to-note, nothing to learn.
2. In each project note, three headings: what was agreed, what changed, what was never decided.
3. The bank of diary questions hands you one question a day and counts the streak, and a line about a scope change written tonight beats four reconstructions in May. When a job ends, move it under Archive.

Where it stops: no invoices, deadlines, reminders or client portal - this is memory, not a CRM. Freelancer notes tree, PARA in a notes tree.

9. A machine that never touches the internet

Labs, plant floors, offices with a no-outbound policy: anything that phones home is a problem there, and so is anything needing a license server.

Carry the installer in from a connected machine after checking its SHA-256 against the table on the download page. On first start the program creates its own notes file, and a demo vault of fifteen notes shows the shape instead of an empty pane. Trees, search, sealing, Markdown export and import all work with the cable unplugged. If you want AI, point it at a model on the local network and text goes only to the address you named; the key lives in the system keychain, not in settings.

Where it stops: there is no update channel by design - a new version is a new installer you carry in. And 2.1 needs Windows 10/11 64-bit or Linux x64. Installing SEO Note 2.1 on Linux.

10. The old laptop that still works

Windows 7, a 32-bit netbook, an XP box in the workshop. Those machines are not badly designed; they are simply outside what 2.1 supports.

For them the answer is the classic build: 1.3.34, an installer of about 2,5 MB, running XP through 11, 32-bit included. Its notes file is .seo - same tree, same offline behaviour, still no account. Copying that file to a second disk or a stick is the entire backup strategy, which makes it a habit rather than a project. When the machine is finally replaced, import the .seo into 2.1 (case 4) instead of retyping a decade.

Where it stops: no AI, no sync, no clipper, no Markdown bodies in the classic build. 2.1 versus 1.3.34, portable notes on Windows 7.

The tree all ten cases share

None of this needs a new filing system: one Inbox and four folders carry every case above. The only judgment call is which folder you trust enough to drop a note into without thinking twice.

Inbox — clips, forwards, dated scratch
Projects
  Client A — agreed / changed / undecided
  Thesis — sources, chapters
People — one note per client, teacher, doctor
Ops
  Contour — payments-api
    Runbooks — first fifteen min, rollback
    Postmortems — dated, with owners
Reference
  Prompts, commands, links worth keeping
  Archive — dated, no longer touched

The loop that keeps it alive

1 Capture into Inbox

2 File under a named folder

3 Link it to what it belongs to

4 Empty Inbox weekly

5 Copy the file off that disk

Where SEO Note is the wrong tool

• Two editors in one file at once. No shared session, no live cursors, no conflict merge; sync hands one copy over and someone loses.
• A phone as the main device. The Android build is the same renderer over a folder of Markdown notes, and answers note history, passwords, sync, the clipper and AI with a named refusal; moving a desktop .seonote onto the phone is not finished.
• Databases, relations and views in the Notion sense, or anything needing a link a stranger can open - there is no web version and nothing is hosted.
• People who want no structure: folders and nesting are the product, and the filing discipline stays yours. Environments needing signed binaries too - desktop installers are unsigned, so SmartScreen warns once.

Next steps

1. Pick the one case above that is yours today, not the three that might be next year.
2. Install that build, create four folders: Inbox, Projects, Reference, Archive.
3. Run capture-file-link for a week, then make the first copy of the file off that disk - and only then choose which optional feature to switch on.

Download SEO Note free; if you are unsure which of the two builds is yours, this page decides it in one screen.

Keep going

• Tree templates and PDF guide — role and method skeletons you can copy straight into your own tree.
• If this guide helped, you can say hello or grab ready-made trees on the templates page.

Adjacent tools (VPS for local models, courses, VPN) are not stuffed into every paragraph. If an affiliate link appears, it will be labeled and is never required to use SEO Note.

Mini FAQ

Do these cases need the internet? No. Writing, searching and exporting notes work with the cable unplugged; there is no account and no server of ours. The network is used only by what you switch on: an AI endpoint you name, sync to your own repository, and the clipper, which listens on 127.0.0.1. No build asks a server about new versions.

Which build do the cases above need? Cases 1, 3, 4, 5, 6, 8 and 9 are 2.1 desktop: Windows 10/11 64-bit or Linux x64, since the clipper, sealing, sync and import live there. Case 10 is the classic 1.3.34, because Windows 7, 8 and 32-bit machines are out of 2.1's range. Cases 2 and 7 work in either file.

Is one file for everything a risk? It is the same risk as one folder of documents, and the same advantage: one copy is one thing to back up. 2.1 keeps the last ten versions of the file it saves, which covers a bad edit, not a dead disk - so the answer is a copy on another drive, made as routine.

Can two people work in the same notes file? Not at the same time. Sync moves one copy between machines and the last writer wins, with the older copy kept, so one person edits a file at a time. Writing together, live, is a different kind of tool.

What does any of this cost? Nothing. The program is freeware: no account, no subscription, no ads, no locked features, and the tree templates on the site are free too. Desktop installers are unsigned, which is why Windows warns once; the APK is signed with our own release key.

Related: Using SEO Note every day · Tree outliner for notes · Second brain without the cloud · Templates · FAQ