Posts Tagged ‘IA’


Information Architecture, Content & SEO

19 December 2008

I was reminded during a discussion this morning of the interplay between information architecture, content and SEO in the success of a Web site. I thought back to a thread on the IA Institute’s mail list from July that touched on one element of this issue, and I figured I might as well extract that conversation and make it available here.

The initial question in the thread came from Jenny Wallace, a candidate for the masters in Interaction Design and Information Architecture at the Univ. of Baltimore. Jenny asked:

“How Search Engine Optimization and Information Architecture can build a reciprocal trust relationship between information providers and information consumers. Any thoughts?”

My response was this:

“The notion of trust in this relationship is primarily one – to my mind – of meeting expectations for the information consumers. The consumer will, frequently, land on a page deep into the site content hierarchy and will immediately begin assessing the page for relevancy based on the high-level content labels presented to them. This is clearly where a partnership is most strongly required between IA and SEO practitioners, so that the visually-dominant labels (headings, titles, sub-headings, bold terms etc) are closely aligned to the original search terms that brought the consumer to the site in the first place.

Trust online is a highly fragile thing, and visitors to a site – particularly when originating within a search engine – will be twitchy to begin, so it is imperative that relevance is established quickly, clearly and unambiguously. It should be the case that the higher-level content labels are the ones most closely tied to the search terms – and it’s here that the semantic structure of the HTML comes to the fore.

It is also important to recognise the conflict inherent in the relationship between SEO and IA. Although the goal of SEO should be to attract pre-qualified potential consumers to site, quite often this is interpreted to mean “attract as many people as possible”. For the IA, this represents a real conflict of interest: they’re being tasked with structuring site content to suit the needs of an audience who – by rights – should never be considered in the information architecture.

And it is here that trust can be destroyed very, very quickly: SEO tactics that are designed to draw in visitors with only a very tenuous interest in the actual product or service on offer; and those visitors being presented with content that has little or no relevance to their needs.

One last point: the information architecture strategy for a site must explicitly accommodate visitor behaviour that does not initiate on the home page. Each and every page must provide the sort of context and relevancy triggers for the visitor so that they can not only decide to continue their journey on the site, but also can see clearly how to commence that journey.”

Regular readers of this blog may have come across another post of mine from July that listed out a bunch a questions that UX practitioners can use as a way to frame the development of a UX strategy for their (web-centric) project. Two of those questions were:

  1. If people arrive at your site somewhere other than the home page, how will you provide them context and communicate both intent and possibilities?
  2. How will people find your site? And how do the activities you undertake to encourage them tie in with your other design consideration?

[Note: they actually appear as questions 13 & 14 in the original post.]

The issue of establishing trust and credibility in the minds of visitors arriving via search engines can be seen to be a sub-component of the overall set of responses one might make to these two questions. Trust and credibility should be two of the considerations when formulating your overall content and SEO strategies, and these should tie in to the information architecture you design for the site.

These three areas: information architecture, content, and SEO, need to be considered together in order to meaningfully address the two questions above; and one is not really complete unless it is being complemented by the other two.


Definition of Information Architecture

18 September 2008

After a very vibrant, and extended (some would say ‘protracted’) discussion on the IA Institute members’ mailing list, the IA community has put forward a range of ideas on what should be adopted as the ‘formal’ – or, at least, the ‘official’ – definition of the phrase “information architecture”.

The one I most like, and the one I’ll be adopting for now, was this one – articulated by Todd Zaki Warfel:

“Information architecture organizes stuff to make it useful, findable, and actionable.
  • For ecommerce sites, we organize products and descriptions to make the shopping experience better
  • For content and news sites, we make finding the stories you’re interested in easier
  • For information systems (e.g. aviation systems) we organize gauges and displays to help reduce error”

I like the way this is constructed with the DIY examples at the end to help contextualise the definition for whatever audience, project, or discussion you may be having at the time. I know there are some holes in this – it doesn’t address the fact that ‘information architecture’ is also a discipline or emerging community of practice. But, to be perfectly honest, I don’t care. In 99% of cases, no-one I discuss IA with will care either. So I’ll stick with this one for now.