One Taxonomy To Rule Them All: Developing a Taxonomy

A shared taxonomy (across your sites, your AMS, your meetings, etc.) is the key to better content and a better user experience. In this series of blog posts, we’ll define taxonomy, tell you why it’s important and show you how to develop and implement one.

Hand drawing chart in whiteboard isolated on whiteDeveloping a Taxonomy

The hardest part of developing a common taxonomy is deciding what belongs where. How do you choose your topics and issues? Here are some tips to help you decide.

Look at:

  • Government affairs issues
    • What are the top 10 issues for your association/organization? What are ongoing issues that are always discussed?
  • Topic areas
    • What topic areas do you currently have? Look at your navigation & how your site is divided now. Can any of these be topics? What is each item about?
  • Conference tracks
    • Your conference tracks and sessions are often great indicators of what’s important to your members. Take a look at the two or three most recent and/or upcoming events. What are the session topics?
  • Committees
    • Committees are often formed around important topics/issues to an organization. What committees do you have? Can these topics translate to the taxonomy?
  • Look at search referrals
    • Check your usage analytics? How do people find your site?  These referrals are often a great way to see what users are looking for.
  • Look at site search keywords and phrases
    • On your own site search, what keywords and phrases are your own members/site users typing in to find content? You’ll often find clear patterns.

 

How to Integrate your CMS and AMS

Joanna Pineda

About Joanna Pineda

Joanna’s business card reads CEO/Chief Troublemaker for a reason. She relishes a challenge and introduces change wherever she goes. She knows anything is possible and that clients come to Matrix to hear "Yes", not "No." Matrix is purple because of Joanna. Staff like to call her JP.

Leave a Reply

Your email address will not be published. Required fields are marked *