Information Architecture (IA) is an information site's rod; navigation (UI) are elements that allow visitors to find the information on this site. Practitioners web designers and marketers sometimes make mistakes, identifying the concept of information architecture (IA) and navigation. These concepts are certainly related, but not identical. IA forms navigate web resource certainly, but "information architecture" is a much more global concept that goes far beyond the simple site navigation.
Information architecture of the site includes two main components:
Information Architecture (IA) is not a part of the user interface (UI), which is displayed on the screen, and configures IA rather causes appearance of a set of options and UI. Information Architecture (IA) represented as spreadsheets and charts, and not as a layout: complete layout or prototypes. Despite the fact that the information structure of the site (IA) is invisible, within the user interface (UI), it certainly has a definite impact on the user experience (UX). As is known, the user experience as a whole includes everything that a user meets. Although regular users do not see the site structure, they need to feel that the content is divided and grouped according to their needs and expectations. Unfortunately, most visitors leave even multi-sites and stand-alone Landing Page, despite the fact that the information architecture of last is much simpler. However, they often experience discomfort and frustration due to poor organization structure and/or specification (the nomenclature) site. Actions to determine the information architecture:
Site Navigation is a set of user interface elements. The main purpose of navigation is to help visitors to find the desired information and functionality, and to provoke them to certain actions. The main elements of navigation include:
Some examples of navigation elements: a compact menu, global navigation, "bread crumbs", local navigation, related links (in this case, articles and blog posts), fatty footer. For each element of navigation is required some decisions: Priority use: how users rely on any element of navigation? For example, users can navigate the site using mostly local navigation? Or they rely more on the related links? Accommodation: On what pages should be placed navigation elements? Where they should be, within the grid layout of the page? Scheme of the project: In which circuits (template) project detectability optimal performance and visibility. What is the relationship between information architecture and navigation? Obviously, the navigation does not cover the entire content of the site completely and does not disclose all of the functionality of the web resource, sooner or later will require a total redesign. [bctt tweet="Site Navigation - a set of user interface elements. The main purpose of navigation is to help visitors to find the desired information and functionality, and to provoke them to certain actions."]
There are following types of navigation:
Global navigation is always ready to help answer the question "Where am I?" Local navigation tells, "What is still around?" Contextual navigation contributes finding "What else can be found having regard to the information on the page?"
Auxiliary Navigation (standard icons)
Intertextual navigation (hypertext)
Types Of Internal Navigation:
Faceted navigation is a type of structuring the site in which users can specify a different desired parameters, in order to find the desired product or service.
When you do the audit of using faceted navigation, you should answer the main questions: 1. Does the site use facet navigation? 2. If the site uses faceted navigation, does it create duplicate content issues? When facet structure of the site, the problem of duplicate content arises from the presence of different navigation paths to the same page. And if you carelessly react to this question, you will get the same content on multiple pages. Not important which navigation path is used by a visitor to find a specific product. It is important to be indexed only one way. To do this, use the CMS. Otherwise, the same page will be indexed more than once. Look for query parameters used by faceted navigation (if it's parameter driven) and see if they're listed in Google webmaster tool's URL Parameters report (under Crawl).
3. If it's not using faceted navigation, should it? If a site has a lot of product pages paginated, this could be an indicator that the site should use faceted navigation.
4. What the number of facets is necessary that your site has been indexed qualitatively? Ideally, the facet's "depth" should not exceed 100 items. Such principle will allow search engines to index all the pages of the resource. Most professionals tend to believe that search engine crawlers can recognize more than 100 links on one page. However, it is best to adhere to the following view: since most of the sites in any case have navigation links on every page of links, number of links to products on a separate page should not exceed 100.
Let's say a site has acceptable facet navigation, and relevant pages for each keyword or phrase. But in spite of it all, your site still contains a lot of look-alike pages, content of which is the product lists. Therefore, for each page to be created its unique content, and the most important pages, the better in terms of uniqueness should be its content.