Field Notes Inside an Integrated Communications Agency

model

  • Sitemaps: what are they good for?

    One thing I continue to struggle with is how relevant sitemaps are--and to whom?1

    Below is an example sitemap, which indicates the basic hierarchy of pages or categories within a site.

    What's wrong with this picture?

    sitemap

    Sitemaps don't represent pages...

    Implicitly, they communicate pages of content. This is not necessarily the case. They are a quasi-system model that blurs the lines between content and page. This leads to misinterpretation.

    Extending this, they are rooted in a page-centric approach that assumes pages have one state. Ajax-y interactions that reload different content into the same page aren't communicated. 

    ...and they don't really represent content.

    They suggest content, but a through the lens of a page. This, I believe, is an artifact left over from the days where sitemaps were closely tied to the physical implementation. As we've evolved the idea of a sitemap away from actual pages, we didn't rethink how it is actually interpreted or used by either developers or clients. 

    ...and they don't reflect true navigation or interaction paths.

    In fact, they indicate a hierarchical flow between pages. Sitemaps suggest that users typically access the site through the home page. Users who arrive via a search or a link from a friend are likely to be entering at a deeper level than the home page. Luke Wroblewski has a great podcast and set of slides on this.

    And sitemaps don't account for related items--hyperlinks that bring together similar content that exist in different categories of the site. Similar information may be "nearer" than sitemaps suggest. The perceived distance is content too and associate navigation can be as important as the categorical navigation. 

    So, what do they do well?

    For me, they are good as a sketch -- not a final product -- for how content may be organized and how navigation may occur. They work well for initial scoping. But having to caveat what sitemaps are feels like a cop out. There's gotta be a better way.

     Any thoughts? Do sitemaps help you or confuse you?

    1I'm talking about the information architecture kind, but many of the points also extend to those junk drawer sitemap pages that many sites have. That's entirely another issue to address.