A hierarchical diagram of all the pages your new website will have — organized by structure. Think of it as the floor plan of your site. It shows which pages belong under which sections, not how they'll look.
It is not your navigation menu — the menu is a design decision made later. It is also not an XML sitemap submitted to search engines. Those are different things entirely.
Example sitemap
Each box is a page. Lines show which pages belong under which parent. Here's what a typical library sitemap looks like.
This is a simplified example. Your library's sitemap will be tailored to your goals and existing content.
Remember: the sitemap is a map of pages, not a design. "About" being on the left doesn't mean it's the first menu item. The order and naming of your navigation gets decided during the design and build phases.
What feedback to give
Focus your feedback on three areas. Everything else gets addressed in later phases.
Does "Research Help" make sense to your patrons, or do they call it something else? Let us know if any label feels off or unclear.
Is a page missing that your patrons rely on? Is there one in the map that's redundant or no longer relevant? Now's the time to flag it.
Does "Teen Programs" make more sense under "Programs" or at the top level? If a page is in the wrong place, let us know and we'll move it.
Frequently Asked Questions
What's the purpose of the sitemap? +
How did you decide what goes in our sitemap? +
What do the boxes and lines mean? +
Is this the same sitemap we submit to search engines? +
Once you've reviewed the sitemap…
Submit your sitemap feedback along with your design feedback during the Design Feedback Cycle. Your account manager will confirm the due date. Once finalized, the sitemap becomes the blueprint our developers follow when building your site.