In a growing Obsidian vault, structure is everything. As your notes multiply, connections become harder to manage—and that’s where a Map of Content (MOC) becomes invaluable. But manually linking every new note to a related MOC can quickly turn into a chore. Fortunately, Obsidian offers powerful ways to automate this process, saving time while keeping your knowledge base clean and interconnected.
TLDR: You can automatically add a MOC link in Obsidian using templates, the Templater plugin, metadata properties, or automation tools like QuickAdd. The best method depends on how much control and complexity you want. Simple setups use native templates, while advanced workflows combine Templater with folder rules or metadata automation. With the right system, every new note will instantly connect to your broader knowledge structure.
In this guide, we’ll explore why automatic MOC linking matters, how to set it up using several methods, and how to choose the right workflow for your vault.
What Is a MOC (Map of Content)?
A Map of Content (MOC) is a structured note that acts as an index or hub for related topics. Instead of relying purely on folders, MOCs provide contextual navigation through links.
For example, a “Productivity MOC” might contain links to:
- Time Blocking
- Task Management Systems
- Deep Work Strategies
- Goal Setting Frameworks
Whenever you create a new note related to productivity, ideally, it should link back to the Productivity MOC. Over time, these backlinks strengthen your note network.
But doing this manually every time?
That’s inefficient.
Why Automatically Add a MOC Link?
Automation provides several key benefits:
- Consistency – Every note follows the same structural rule.
- Time savings – No need to remember to link manually.
- Stronger backlinks – Your MOCs stay comprehensive.
- Reduced friction – Faster capture of new ideas.
If you’re building a serious knowledge system, automation isn’t just convenient—it’s essential.
Method 1: Using Obsidian’s Built-in Templates (Simple Setup)
If you prefer sticking to native features, you can automatically insert a MOC link using Obsidian’s Core Templates Plugin.
Step-by-Step Setup
- Enable Templates under Settings → Core Plugins.
- Create a “Templates” folder in your vault.
- Create a new template note such as “Default Note Template.”
- Add your MOC link at the top:
Linked MOC: [[Productivity MOC]]
Now, whenever you create a note and insert this template, the MOC link is automatically added.
Pros
- Easy to set up
- No community plugins required
- Stable and simple
Cons
- Manual template insertion required
- No automatic folder-based detection
This works well if most of your notes belong to one central MOC.
Method 2: Using Templater for Dynamic MOC Linking
If you want automation with logic, the Templater plugin is your best friend.
Templater allows you to run JavaScript inside templates. That means you can assign MOCs based on:
- Folder location
- Tags
- File names
- User prompts
Example: Auto-Link Based on Folder
Let’s say your folder structure looks like this:
- Productivity/
- Marketing/
- Programming/
You can create a Templater script like this:
<%*
if (tp.file.folder().includes("Productivity")) {
tR += "Linked MOC: [[Productivity MOC]]";
}
else if (tp.file.folder().includes("Marketing")) {
tR += "Linked MOC: [[Marketing MOC]]";
}
%>
Now, whenever you create a note inside the “Productivity” folder, it automatically inserts the correct MOC link.
Pros
- Powerful and flexible
- Fully automatic
- Scales with complex vaults
Cons
- Slight learning curve
- Requires plugin
This method is ideal for advanced knowledge management systems.
Method 3: Using QuickAdd for Automated Workflows
QuickAdd is another powerful community plugin that enables note creation workflows.
With QuickAdd, you can:
- Create a note in a specific folder
- Apply a template automatically
- Insert predefined MOC links
- Trigger scripts
You can create separate QuickAdd commands such as:
- “New Productivity Note”
- “New Marketing Idea”
- “New Coding Concept”
Each command automatically adds the appropriate MOC link.
Why This Is Powerful
Instead of thinking about structure after writing, your workflow enforces structure at creation.
Comparison Chart: Which Method Should You Use?
| Method | Automation Level | Difficulty | Best For |
|---|---|---|---|
| Core Templates | Low | Easy | Simple vaults or beginners |
| Templater | High | Medium | Advanced structured systems |
| QuickAdd | High | Medium | Workflow-based note creation |
If you want minimal setup, use Templates. If you want intelligent automation, choose Templater. If you want streamlined workflows, QuickAdd is excellent.
Best Practices for MOC Automation
Before automating everything, keep these principles in mind:
1. Avoid Over-Linking
Not every note needs five MOCs. Keep relationships meaningful.
2. Keep MOCs Clean
Your MOC should be structured, not messy. Organize links using:
- Headings
- Categories
- Bullet groups
3. Combine MOCs with Properties
You can reinforce linking using YAML properties:
--- moc: [[Productivity MOC]] ---
This keeps notes queryable using Dataview.
4. Periodically Audit Your System
Even automated systems need maintenance. Review your MOCs monthly to:
- Remove outdated links
- Add missing connections
- Reorganize sections
Advanced Idea: Reverse Automation Using Backlinks
Instead of inserting MOC links into every note, you can sometimes reverse the logic.
Inside your MOC, embed a query like:
```dataview list from "Productivity" ```
This automatically lists notes from a folder—no manual linking required.
This reduces redundancy, but note that explicit links still improve clarity and navigation.
Folder-Based vs Topic-Based MOCs
Some users structure MOCs by folders. Others build them by conceptual themes. Automation works differently depending on your philosophy:
- Folder-based vaults → Use folder detection scripts.
- Tag-based systems → Use metadata rules.
- Zettelkasten-style vaults → Use contextual linking instead of rigid automation.
There is no single “correct” method. The right approach aligns with how your brain organizes ideas.
Final Thoughts
Automatically adding a MOC link in Obsidian transforms your vault from a collection of notes into a living knowledge system. Whether you use built-in templates for simplicity, Templater for logic-driven automation, or QuickAdd for workflow efficiency, the goal remains the same: reduce friction and strengthen connections.
Start simple. Implement a template-based MOC link first. Once your vault grows and patterns emerge, upgrade to smarter automation.
Remember—the true power of Obsidian isn’t just in writing notes. It’s in how those notes connect. And with automatic MOC linking, those connections happen effortlessly.