Wikilinks and Backlinks: Build a Useful Note Graph

Can your notes point at each other without turning into a wall of blue links?

That question sits behind wikilinks and backlinks. Linking notes feels useful for the first week. Then the graph fills with dots, the backlinks panel grows noisy, and you still cannot find the decision you made last Tuesday.

Glyph treats linked notes as a working tool. You write [[wikilinks]], review backlinks, and use local graph view when a visual map helps. Your notes stay as Markdown files on your Mac, so the link system supports the notebook instead of owning it.

What are wikilinks and backlinks?

Wikilinks and backlinks connect Markdown notes in two directions. A wikilink, such as [[Project Atlas]], points from one note to another note. A backlink shows the reverse path: every note that links back to the current note. Together, they help you move through projects, research, people, and daily notes.

Obsidian’s official docs describe internal links with both wikilink syntax, such as [[Three laws of motion]], and standard Markdown links. Bear’s docs support wiki links, note heading links, aliases, and backlinks. The pattern has become common because it lets a note act like part of a small private web.

Glyph uses the same mental model for Mac users who want local Markdown files with built-in links, backlinks, and graph view.

Why wikilinks beat folder decisions

Folders ask you to choose one home. Links let a note belong in more than one conversation.

A meeting note might touch:

Met [[Maya]] about [[Glyph Launch]].
Decision: keep the homepage focused on [[Local Markdown]].
Follow-up: test [[Git Sync]] conflict copy.

That note belongs to a person, a project, a positioning theme, and a technical workflow. A folder can hold only one of those meanings. Wikilinks can hold all of them.

You still need folders for broad shape. Keep daily notes together. Keep attachments sane. Keep imported archives away from active writing. But do not ask folders to explain the thought. Links do that better.

This is why local-first Markdown notes on Mac benefit from links. Plain files give you ownership. Links give those files memory.

Backlinks show context you did not plan

A backlink answers a simple question: “Which notes already mention this?”

Open [[Glyph Launch]], and backlinks might show:

1. A daily note from Monday.
2. A pricing draft.
3. A customer interview.
4. A task list.
5. A comparison post outline.

That context helps because you did not have to build a dashboard first. You wrote links during normal work. The app collected the reverse paths.

Bear’s backlink docs separate linked mentions from unlinked mentions. Linked mentions come from direct wiki links to the current note. Unlinked mentions come from plain text that matches the current note title. That distinction matters. Direct links show intent. Unlinked mentions can reveal missed connections, but they can also create noise.

Glyph keeps backlinks close to the editor so you can use them while writing. A backlink is most useful when it answers the next question, not when it becomes another inbox.

Use graph view as a map, not a scoreboard

Graph view can become decorative. A large network of dots looks impressive, but it may not help you write, plan, or decide.

Use graph view for specific checks:

1. Does this project connect to the right research?
2. Which daily notes mention this person?
3. Which topics sit isolated after import?
4. Did a migration preserve important links?
5. Which notes cluster around a launch, class, book, or client?

Obsidian’s graph docs distinguish a global graph from a local graph. A global graph shows the vault. A local graph shows notes connected to the active note. For day-to-day work, the local graph often gives better signal because it starts from the note in front of you.

Glyph’s local graph should serve the same practical job. Open a note, inspect nearby relationships, follow the useful one, then return to writing.

A useful note graph starts with better link names

Bad link names make bad graphs.

Use names you would search for:

[[Glyph Launch]]
[[Markdown Daily Notes]]
[[Private AI Notes]]
[[Customer Research]]

Avoid vague notes:

[[Ideas]]
[[Stuff]]
[[Misc]]
[[Thoughts]]

Generic notes become link dumps. If a topic matters, give it a name with a noun that can survive outside today’s mood.

Aliases help when a note has a formal title but the sentence needs a shorter phrase. Bear supports wiki link aliases with a pipe character, such as [[note title|alias]]. Many Markdown tools understand or approximate that syntax. Use aliases when they improve reading, but keep the target title clear.

For migration, test aliases with care. Standard Markdown links travel better across tools than app-specific wikilink features. Obsidian’s docs note that users can disable wikilinks and use Markdown links for interoperability. That choice matters if you expect to move between apps.

Glyph supports wikilinks because they make note-to-note writing fast. The files remain plain Markdown, so you can still inspect the syntax.

Link daily notes without cluttering everything

Daily notes can make a graph useful or unbearable. If you link every stray word, daily notes create noise. If you link only durable terms, they create a timeline.

Use this rule: link the thing you expect to open later.

Good daily note links:

## 2026-05-07
- Talked with [[Maya]] about [[Glyph Launch]] trial copy.
- Found a useful source for [[Markdown Web Clipper]].
- Need to test board status in [[Markdown Task Management]].

Less useful links:

- Had [[coffee]] before [[meeting]] and read [[article]].

The first example helps you navigate people, projects, and posts. The second turns common words into fake structure.

The guide to Markdown daily notes shows how a daily note can hold capture, meetings, tasks, and review without becoming a page of stray links.

Use links for decisions, not only topics

Topic links help. Decision links often help more.

Create decision notes when a choice will matter later:

# Use Git sync for notes

## Decision
Glyph will use Git sync for versioned file sync.

## Reason
Users who want local Markdown notes often want readable history and diffs.

## Links
- [[Git Sync]]
- [[Local Markdown]]
- [[Conflict Handling]]

Then link to that decision from project notes and daily notes:

See [[Use Git sync for notes]] before changing sync copy.

Backlinks now tell you where the decision affected work. That gives you a better trail than a paragraph buried in a meeting note.

Git pairs well with this pattern. If you change the decision note later, Git shows the diff. The post on Git sync for Markdown notes explains why text history works well for notes.

Keep backlinks clean during migration

If you move from another Markdown app, test links before you trust the archive.

Check:

1. Do [[Note Title]] links open the right note?
2. Do links with aliases still read well?
3. Do heading links work or need adjustment?
4. Do attachment links point to real files?
5. Do renamed notes keep backlinks intact?
6. Does graph view show expected clusters?

Obsidian can update internal links when you rename a file if the setting stays enabled. Other apps handle renames differently. Before a migration, make a copy of the vault and test common link patterns on real notes.

The move from Obsidian to Glyph checklist covers wikilinks, backlinks, attachments, frontmatter, and plugin habits in more detail.

Avoid performative linking

A link should earn its brackets. Do not link every noun because the graph looks sparse. Do not create empty notes for concepts you will never revisit. Do not use backlinks as a substitute for writing a clear summary.

Use links when they answer one of these questions:

1. Where does this belong?
2. Which project does this affect?
3. Who is connected to this?
4. Which decision explains this?
5. Which source supports this?

If a link cannot answer one of those questions, plain text may serve better.

Backlinks also need pruning. Rename vague notes. Merge duplicates. Delete empty stubs. Move long daily note material into topic notes. Your graph gets better when the notes get clearer.

A simple linked-note workflow

Use this daily loop:

1. Capture in today’s note.
2. Link only projects, people, sources, and decisions you expect to revisit.
3. Open backlinks from one active project note.
4. Move useful daily-note fragments into durable notes.
5. Use local graph view to check nearby context.
6. Commit changes if you use Git.

That loop works because it starts with writing. The graph follows the work.

For project planning, combine this with Markdown task management. A task can link to the note that explains it. A board can group tasks without stripping away context.

Should you build a note graph?

Use wikilinks and backlinks if your notes contain projects, research, people, daily logs, or decisions that cross folder boundaries. Links help your notebook remember relationships you would otherwise rebuild by search.

Skip graph-heavy habits if they make writing slower. A local graph should help you find context, audit a migration, or notice missing relationships. It should not become the product you maintain instead of the work you meant to do.

Glyph gives you the linked-note loop without asking you to turn your notebook into a plugin stack: Markdown files, wikilinks, backlinks, local graph view, daily notes, tasks, boards, Git sync, and optional AI. Use the graph when it helps. Close it when the sentence needs your attention.