actualNoteContentPart: A "tag hierarchy" is what we call a tag when its name contains words separated by the /, like personal/friends. Technically a "tag" can be a single word, as is the case with the note you're reading -- [in its notebook, it has two tags](https://images.amplenote.com/b90019ae-0b9e-11ec-b84f-9664627f7969/65698839-31a8-4292-9354-ed820e917ea4.png) , amplenote and blog/draft. 
  
  Many users migrate to Amplenote from apps that use "**directories**" to organize notes. Our "tag hierarchies" are effectively identical to what other apps call "directories" - except that our tag hierarchies do not carry the restriction that a note must exist within a single directory. Being able to catalog a note such that it can be found through multiple hierarchies opens the door to [interesting opportunities that aren't possible with directories alone]() .
  
  # 👩‍🔬 Choosing a tag hierarchy name
  Picking an enduring tag name is really hard! Don't feel bad if it takes you repeated experimentation to end up with something that serves your desired ends. The good news is that we make it [really easy to change your mind about tag names as you go](https://www.amplenote.com/help/tag_renaming_reorganizing) .
  
  Here are a few guidelines we've developed from years of creating tag names.
  
  ## 1. Don't get fancy
  Few have sustained willpower to pursue productivity for its own sake. Any "productivity system" that needs to be learned isn't built for the long-term. 
  
  **Suggestion:** Use **10 or less tags at any level**. This maxes you out at 100 second-level tags. No tag in a two-level hierarchy feels too overwhelming. As far as specific tag names and organizing principles, don't subscribe to any one methodology. 
  
  ## 2. prefer/short/path, non-pluralized, non-abbreviated words to promote consistency
  Tags aren't going to do you any good if you create elaborate hierarchies that are never seen. If the CEO of Amplenote has yet to meet anyone productive who regularly employs 4-level tags, you probably don't need four levels. Nested tags are at their finest in the second level of the hierarchy, but third-level tags make sense in domains where your interest runs deep.
  
  Whenever possible, we recommend using the singular form of words in your tag hierarchy, so you don't end up with a mishmash of arbitrarily pluralized and singular words.
  
  Suggestion**: **Prefer keeping tag hierarchies that are **three or less levels deep. **
  
  Suggestion: Prefer cumulative words in a hierarchy to be **five or less total words **([examples]() )
  
  Suggestion**:** **Use the singular form of words** when naming tags, so your naming remains maximally consistent. I.e., homework/example instead of homework/examples
  
  Suggestion: Prefer **non-abbreviated words **when practical, especially for 2nd and 3rd-level tags. This reduces the likelihood you'll accidentally duplicate tags.
processedNoteContent: ---
  title: Five recommendations for choosing hierarchy/nes...
  tags: 
  ---
  A "tag hierarchy" is what we call a tag when its name contains words separated by the /, like personal/friends. Technically a "tag" can be a single word, as is the case with the note you're reading -- [in its notebook, it has two tags](https://images.amplenote.com)`
   , amplenote and blog/draft. Many users migrate to Amplenote from apps that use " directories
  " to organize notes. Our "tag hierarchies" are effectively identical to what other apps call "directories" - except that our tag hierarchies do not carry the restriction that a note must exist within a single directory. Being able to catalog a note such that it can be found through multiple hierarchies opens the door to [interesting opportunities that aren't possible with directories alone]()
   . 
  👩‍🔬 Choosing a tag hierarchy name
  Picking an enduring tag name is really hard! Don't feel bad if it takes you repeated experimentation to end up with something that serves your desired ends. The good news is that we make it [really easy to change your mind about tag names as you go](https://www.amplenote.com)`
   . Here are a few guidelines we've developed from years of creating tag names. 
  1. Don't get fancy
  Few have sustained willpower to pursue productivity for its own sake. Any "productivity system" that needs to be learned isn't built for the long-term. Suggestion:
   Use 10 or less tags at any level
  . This maxes you out at 100 second-level tags. No tag in a two-level hierarchy feels too overwhelming. As far as specific tag names and organizing principles, don't subscribe to any one methodology. 
  2. prefer/short/path, non-pluralized, non-abbreviated words to promote consistency
  Tags aren't going to do you any good if you create elaborate hierarchies that are never seen. If the CEO of Amplenote has yet to meet anyone productive who regularly employs 4-level tags, you probably don't need four levels. Nested tags are at their finest in the second level of the hierarchy, but third-level tags make sense in domains where your interest runs deep. Whenever possible, we recommend using the singular form of words in your tag hierarchy, so you don't end up with a mishmash of arbitrarily pluralized and singular words. Suggestion**: **Prefer keeping tag hierarchies that are **three or less levels deep. ** Suggestion: Prefer cumulative words in a hierarchy to be **five or less total words **( [examples]()
   ) Suggestion**:** Use the singular form of words
   when naming tags, so your naming remains maximally consistent. I.e., homework/example instead of homework/examples Suggestion: Prefer **non-abbreviated words **when practical, especially for 2nd and 3rd-level tags. This reduces the likelihood you'll accidentally duplicate tags.
noteTitle: Five recommendations for choosing hierarchy/nested tag names