Zettelkasten in an outliner: atomic notes as a tree

Zettelkasten in an outliner: one idea per leaf

Classic Zettelkasten promises a web of atomic notes that surprise you years later. Many apps lean on dense backlinks, graph views, and block references. An outliner is different: the tree is the map. That is not a failure — it is a choice. If you want one idea per leaf, a clear parent, and a file that opens offline on Windows without an account, a tree beats a graph you never maintain.

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.

SEO Note is a free Windows tree outliner (one local file; the classic 1.3.34 installer is ~2.5 MB, SEO Note 2.1 is a ~121 MB Electron build). Use it for atomic notes: short leaves under thematic parents, optional Folgezettel-style numbering in titles if you like ritual. AI can cluster or rephrase after you wrote the takeaway yourself — on a model you connect, with no embeddings behind it — same spine as source of truth for AI, applied to PKM.

Atomic archive vs chat helpers

In SEO Note

One claim per leaf

Parents as maps

Literature stubs

Your wording only

In the AI chat

Rephrase for clarity

Suggest sibling links (titles)

Quiz from a handful of zettels

Disposable outlines

A model that “writes your zettel for you” from a PDF dump is not Zettelkasten — it is outsourcing the thinking the method exists to force.

Tree skeleton (atomic under maps)
ZK
  Maps of content
    Writing craft
    Attention / focus
  Literature
    Book — Title (year)
      Bib stub
      Quotes → own words (child leaves)
  Zettels
    20260304a — Deadlines create fake urgency
    20260304b — Outline before prose speed
    20260305a — Local file beats chat memory
  Hub — Active essay
    Pointers to zettel titles
  AI scratch (dated)
Maps of content are indexes, not essays. Literature holds sources; each quote becomes a child you rewrite — the rewrite is the zettel candidate. IDs in titles are optional glue when you lack a graph.

When the method is working (and when it is cosplay)

Working: you can open a Map and see five leaves that still surprise you into a paragraph. Cosplay: hundreds of imported highlights with no rewrite, a graph screenshot you never use, and AI “atoms” you would not defend in conversation. The outliner rewards the boring middle path — fewer notes, each one yours.

What to paste into AI

Paste three to seven finished zettel leaves (your words) when you want clustering ideas or a quiz. Do not paste an unread PDF “to extract atoms.”
Prompt:
These are atomic notes I already wrote. Do not invent new claims.
Suggest: (1) which leaves belong under one Map parent,
(2) two missing questions I should answer next,
(3) a 5-question quiz from these notes only.
---
[paste 3–7 zettel bodies]
Do not paste: whole books, paywalled PDFs you may not upload, private journals with third-party secrets, or a dump of every leaf “just in case.” Curate a slice; keep the vault local.

How-to in one sitting

Create ZK → Maps of content / Literature / Zettels / Hub / AI scratch.

Add one Map parent for a theme you actually write about this month.

Capture one Literature stub (title, author, why you opened it).

Write two atomic leaves from that source — one idea each, in your words, under Zettels.

Link by structure: nest or list their titles under the Map (and under Hub if an essay is live).

Optional: paste those two leaves plus one older zettel into AI for cluster/quiz suggestions; write any new claim yourself as a new leaf.

Stop when you have atoms you trust — not when the graph looks pretty (there is no graph here).

From source to atom

1 Literature stub

2 Quote → own words

3 One idea → one leaf

4 Place under a Map

5 Optional AI on owned leaves

Link-heavy ZK app Outliner ZK

Primary map Graph / backlinks Parent / child tree

Surprise discovery Strong if maintained Weaker; Maps do the work

Ops cost Plugins, sync, schemas One file, boring structure

AI “ask my vault” Sometimes built-in “Ask over my notes” in 2.1 — up to six notes from the local full-text search, no embeddings

Offline / USB Depends Copy the file

Honest limits (read before converting your life)

SEO Note will not give you a force-directed graph, unlinked mention detection, or block references across notes

Folgezettel sequencing is manual (title IDs or ordered siblings) — no Luhmann robot

If your practice depends on dense lateral links as the main interface, pick a tool built for that; keep SEO Note for projects and runbooks instead

No mobile-first capture app parity: the 2.1 APK writes into its own Markdown folder with no sync, and you process the quick inbox node at the desk

No embeddings search — clustering is a button in 2.1, but it groups the notes you picked, not a semantic index of the vault

People who already think in Areas/Projects can park Maps near Areas and essays near Projects — see PARA in a notes tree. Writers shipping client copy should not mix brand Claims with personal zettels without a boundary; copywriter notes tree keeps that split clean. Templates: templates.

Next steps

Create Maps / Literature / Zettels / Hub

Write two atomic leaves from one source today

Place both under one Map by title list or nesting

Run one optional AI quiz on leaves you already own

Back up the file; resist importing your entire old graph in one night

Download SEO Note free — atomic notes in a tree you control, with AI as a late helper, not the author.

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

How big is the installer for this Zettelkasten outliner? The classic 1.3.34 installer is around 2.5 MB; SEO Note 2.1 is a ~121 MB Electron build. The notes live in one local file, sync stays something you configure rather than a service you are signed up to, and no model ships in the box: the AI in 2.1 calls an endpoint you connect.

Does it give me a graph or backlinks between notes? It will not give you a force-directed graph, unlinked mention detection or block references across notes - the parent and child tree is the map.

How many zettel should I paste into AI at once? Three to seven finished leaves written in your own words, when you want clustering ideas or a quiz from those notes only.

Can AI write the atomic notes straight from a PDF? A model that writes your zettel from a PDF dump is not Zettelkasten - it is outsourcing the thinking the method exists to force.

Do I have to number my notes like Folgezettel? The IDs in titles are optional glue when you lack a graph; the sequencing stays manual, with no Luhmann robot doing it for you.

Related: Source of truth for AI · PARA method tree · Second brain offline · Copywriter notes tree · Templates · FAQ

	Link-heavy ZK app	Outliner ZK
Primary map	Graph / backlinks	Parent / child tree
Surprise discovery	Strong if maintained	Weaker; Maps do the work
Ops cost	Plugins, sync, schemas	One file, boring structure
AI “ask my vault”	Sometimes built-in	“Ask over my notes” in 2.1 — up to six notes from the local full-text search, no embeddings
Offline / USB	Depends	Copy the file