Logseq beginner's course (4/8) - Adding structure with bi-directional links

Bi-directional links are Logseq’s core mechanism for turning scattered notes into navigable structure—so a single reference can be followed in either direction without losing context. In the example about planning a birthday gift for “mom,” the user highlights a word and inserts a double-square-bracket link. Clicking “mom” jumps to the referenced page, and the link works both ways: returning to the “mom” page shows where the reference was created (including the date, like “29th of November”). Logseq also surfaces context automatically—hover tooltips reveal what’s inside the linked page, and a list of linked references appears at the bottom—making it easier to resurface relevant material later.

The lesson then shifts from simple linking to building a personal knowledge structure using backlinks and lightweight “association” links embedded directly in journal writing. While drafting a chocolate cake recipe in the daily journal, the user notes that the recipe can be found later either by creating a dedicated page or by relying on backlinks: once the journal entry links to “recipe,” the “recipe” page aggregates all linked occurrences. The same pattern scales to multiple related pages. A “carrot cake recipe” page can be created with its own ingredient blocks, and Logseq will show both the dedicated recipe page and the journal entry as linked references—so the user can jump to either quickly.

For organizing content like birthday planning and card-worthy quotes, Logseq supports both square-bracket links and hashtag links, which behave similarly but are used with different intent. Square brackets are treated as inline links to a concept/page (e.g., linking “mom” within a sentence). Hashtags create links too, but the workflow emphasizes association at the end of a block (e.g., “#quote” to collect quotes under a “quotes” page). The transcript highlights that multiple tags can be attached to a single block, and that this tagging strategy helps with “resurfacing” information—finding notes later even when the user hasn’t created every target page yet. The user demonstrates that a “yesterday” page can be created implicitly by linking/tagging, and even if the page is deleted, the journal entry remains on the canvas for infinite scrolling.

A key practical takeaway is that Logseq’s retrieval depends on consistent linking behavior. Compared with Obsidian, where brackets and hashtags are treated differently (brackets as direct links and hashtags as tags), Logseq treats them similarly, but the user stresses best practice: when writing in the journal, use backlinks and tag blocks so entries don’t fall through the cracks. Search can find unlinked references, but the recommended habit is to add some kind of link to every meaningful journal block. The session closes by previewing more advanced linking patterns—especially task-management links—and ways to structure them for easier retrieval.