Learn about HTML site maps, why they're useful, and how to make one. Plenty of real-world examples included.
Site maps have been around for almost as long as the Web itself. They're a great way to improve your website's navigation and usability.
Although site maps aren't used that often by visitors — around 7% of the time, according to Jakob Nielsen — a site map can really save a visitor if they can't find what they're looking for using your site's regular navigation menu.
In this article you'll explore the concept of site maps, look at some examples, and learn how to design and create a site map for your own website.
A site map is a single page of your website that contains links to all the important pages and sections of your site. Usually you link to your site map from every page of your site — typically in the navigation menu or page footer — so that it's easy to find.
This article covers HTML site maps, which are designed for people to use. Another type of site map is an XML sitemap, often called a Sitemap (with a capital 'S'). These are designed for search engines to read, and are a handy way to submit your site to search engines. I'll cover Sitemaps in a later tutorial.
Here's a simple site map. This site is for a fictional company that sells widgets:
This site map contains 3 topics: Products, Support, and About. Under those topics are links to the various main sections and pages of the site.
A site map for a bigger site will have many more topics and links. If the site is very large then it may make sense to group the topics under several broader topics, creating a 3-level hierarchy. You'll look at some examples of this approach in a moment.
There are 3 main reasons to create a site map for your website:
Here are some good example site maps on major corporate sites:
Another recent trend — particularly amongst Web 2.0 sites — is to have a mini site map in the footer of every page on the site. This mini site map often doubles up as the main site navigation. Common examples of this approach include:
A mini site map has the advantage that it's easily accessible from every page, which means it gets used more than a site map hidden away on its own page. On the minus side, mini site maps can add to general page clutter and load times, especially if they contain a large number of links. Try to keep your links to a minimum if you go this route.
Apple takes an interesting hybrid approach here, combining its global site map page (described above) with section-specific mini site maps in the page footers (for example, see the iPhone section).
You can see from the above examples that there's quite a range of site map styles out there. Your choice of site map format will depend partly on the way your site is structured, and partly on personal preference. You might need to do a bit of experimenting to find a format that you're happy with.
Here are some dos and don'ts for designing your site map:
Do:
Don't:
So how do you actually create a site map for your site? There are 3 main approaches that you can take. You can:
If you have the time to devote to the task, then hand-building your site map is a good option. This approach has a number of advantages:
You can code the HTML for the site map page yourself, or if you prefer, you can use a WYSIWYG editor such as Dreamweaver.
Make sure you use semantic markup for your site map. For example, use the ul
and li
list elements for lists of links, rather than just <p>
or <br/>
tags. This makes your site map easy for search engines to work with. It also makes it easier to style your site map using CSS.
There are many tools — both browser-based and desktop-based — that you can use to create your site map automatically. Popular tools include:
The advantage of using a site map tool is that it's quicker than building a site map by hand. Unfortunately, the quality of automatically-generated site maps is generally pretty poor, since the tools aren't very good at guessing the important topics and sections of your site. Typically this results in site maps that link to every page of your site rather than just the main sections, or that don't properly represent your site structure.
However, site map tools can be useful for big sites. They're a quick way to get a site map up and running, and you can always go through the site map afterwards and clean it up manually.
If your site uses a content management system or blogging system then you may find that it can automatically generate a site map for you. If not then a plugin may be available to do the job.
A CMS generally creates a higher quality site map than a stand-along site map tool, since it has a better understanding of the site's structure. Also, many CMS can update the site map automatically whenever your site content changes.
Here's some info for specific content management systems and blogging platforms:
In this article you've learned about site maps, and why they're useful. You've seen plenty of real-world site map examples, you've picked up some tips for good site map design, and you've looked at different ways to create a site map. Have fun!