All of the online tools let you name your tree test, so you (or a colleague) can find it later. There’s no special magic here, but we do recommend that you identify:

• The site you’re testing
  
  
• Which variation of the tree you’re testing (if you’re testing more than one)
  
  
• Which revision of the test you’re working on
  
  

For example, suppose we’re helping the Acme Supply company reorganize their website. We’re testing their current site structure (to get a baseline score to compare against) and two new trees – one grouped by topic, and the other by audience. So we create 3 tree tests with the following names:

• Acme current
• Acme topic
• Acme audience
  
  

In Chapter ~, we’ll see that it’s a good idea to pilot each test, revise it, and launch the second (or third) version. So really, the list of tests will eventually look something like this:

• Acme current – draft 1
• Acme current – final
• Acme topic – draft 1
• Acme topic – draft 2
• Acme topic – final
• Acme audience – draft 1
• Acme audience – final
  
  

Any name will work, of course, but if you do more tests over time, it does pay to be systematic now so you can make sense of your tests later.

Next: Disguising the test address