Free tool · works now

Tag Taxonomy Auditor

Audit nested tag hierarchies, identify case collisions (#Project vs #project), unify delimiters, and eliminate tag sprawl across your Markdown notes.

14 occurrences·12 unique tags·1 Casing Collisions
Markdown Notes Input (Frontmatter & Body)Paste one or multiple notes
Taxonomy Audit & Anomalies
Casing Collisions (1)Tags differing only by capitalization
Recommended: #project/alpha5 uses
#project/alpha (2)#Project/Alpha (1)#Project/alpha (1)#Project/ALPHA (1)
Synonym & Delimiter Near-Matches (5)Singular/plural and hyphen/underscore variants
#architecture⇄#Architecturesplural
#meeting-notes⇄#meeting_notesdelimiter
#meeting-notes⇄#meetingnotesdelimiter
#bench-mark⇄#benchmarkdelimiter
#meeting_notes⇄#meetingnotesdelimiter
All Tags (12)Sorted by usage frequency
TagUsesDepthParent
#project/alpha22#project
#architecture21—
#Project/Alpha12#Project
#meeting-notes11—
#Architectures11—
#bench-mark11—
#benchmark11—
#Project/alpha12#Project
#meeting_notes11—
#database/sqlite/fts5/benchmarks14#database/sqlite/fts5
#Project/ALPHA12#Project
#meetingnotes11—

The Inevitable Decay of Uncurated Knowledge Graph Taxonomies

In the early weeks of adopting a local Markdown knowledge system like Obsidian, tags feel like an effortless, lightweight classification mechanism. You type #idea or #project/alpha, and documents instantaneously cluster into navigable lists. Over months of active research, meeting capture, and project documentation, an uncurated tag collection experiences entropy:

  • Casing Divergence: Mobile virtual keyboards auto-capitalize first words, while desktop workflows favor lowercase or kebab-case. A single concept splinters into #Project/Alpha, #project/alpha, and #PROJECT/ALPHA. In case-sensitive graph queries, these fragments conceal related notes from one another.
  • Delimiter Fragmentation: Notes taken across different projects oscillate between hyphens (#meeting-notes), underscores (#meeting_notes), and collapsed compound words (#meetingnotes).
  • Singular and Plural Duplication: Authors arbitrarily alternate between singular concepts (#architecture) and plural inventories (#architectures), creating parallel taxonomic silos.
  • Runaway Nesting Depths: Hierarchies that extend four or five levels deep (such as #engineering/platform/storage/sqlite/indexes) introduce severe cognitive friction during capture and are almost invariably better structured as dedicated folders or bidirectional wikilinks.

Frontmatter Arrays vs. Inline Body Tags: A Unified Audit

Markdown systems support two competing paradigms for tag declaration. Standardized YAML frontmatter permits machine-readable lists (tags: [research, architecture]) at the apex of documents, while inline body tags allow contextual tagging mid-sentence.

The Tag Taxonomy Auditor parses both sources in a single pass. It decodes YAML arrays, extracts bulleted frontmatter lists, and traverses prose for inline tags. Crucially, the parser implements defense-in-depth immunity: hash signs inside fenced code blocks (such as Python comments or CSS selectors), inline backtick snippets, and URL anchor fragments (https://domain.com/page#section) are strictly excluded from tag counts.

Non-Destructive Normalization: Reversible Rename Mapping

Automated batch refactoring scripts that execute unvetted search-and-replace substitutions across a note vault carry substantial risk of unintended data corruption. A naive replacement of #art might inadvertently mangle #article or #smart.

The auditor adopts a non-destructive workflow. Rather than altering your files directly, it calculates the dominant canonical representation for every collision cluster and outputs an explicit, reviewable rename mapping plan. You can download a formula-guarded CSV inventory to verify all affected notes before executing migrations.

Air-Gapped Confidentiality for Internal Project Taxonomies

Tag lists frequently reveal an organization's most confidential initiatives, unreleased product codenames, and proprietary technical stacks. Uploading note dumps to cloud analyzers or AI chatbots exposes internal organizational structure.

The Tag Taxonomy Auditor runs 100% locally within your browser client. No text or metadata is dispatched across the network, no tracking tokens are recorded, and closing the browser tab purges all document memory instantly.

Questions

Why do casing collisions in tags cause search fragmentation in Markdown vaults?

While some operating systems ignore case in filenames, Obsidian and standard search engines treat tags like #Project and #project as distinct taxonomic entities. When different team members or notes use disparate casings, search queries and graph filter views fail to retrieve complete sets of documents, fragmenting your knowledge graph.

How does the tool distinguish between valid tags and heading markers or URLs?

Markdown headings begin with # followed by a space, whereas tags have no space after the hash. Furthermore, the parser immunizes fenced code blocks, inline backtick code snippets, and URL anchor fragments (such as https://example.com/doc#section), preventing false positive tag detections.

What is the recommended limit for nested tag hierarchy depth?

In personal knowledge management, taxonomies that exceed three levels (e.g. #topic/subtopic/detail) typically introduce excessive cognitive overhead and friction during capture. Deep hierarchies often indicate that sub-categories should be modeled as dedicated MOC (Map of Content) notes or bidirectional wikilinks rather than rigid tag trees.

Does the auditor make destructive changes to my files?

No. The auditor operates entirely non-destructively. It analyzes your notes and outputs an actionable rename mapping matrix (e.g., #Project/Alpha -> #project/alpha) along with a formula-guarded CSV audit log that you can review before executing changes in your editor.

Are my private tags, company codenames, or note contents sent to the cloud?

Never. The entire parsing, hierarchy traversal, Levenshtein distance calculation, and CSV generation pipeline executes 100% locally in your browser memory. No network requests are dispatched.

Maintain a pristine, responsive personal knowledge base

Index your Markdown notes and wikilinks 100% locally on your Mac. Experience sub-millisecond full-text search and complete data sovereignty without remote cloud dependencies.

tools tag taxonomy auditor downloadDownload for Mac

No account needed. Intel Mac build