To be useful to my audience, the diagrams must communicate the “big picture” of the website to stakeholders, while providing enough detail to be useful for the development team. A final goal was to avoid unnecessary abstraction in the diagrams; the diagram content should map closely to what will later be observed on the website (or what is currently on the website, if the diagram is part of a redesign). Jason Withrow

• Verbal site map: Urban Libraries Council (each category is listed in sidebar & on site map. Sub-categories are listed on map)
• Heirarchical verbal site map: Apple Support Site Map
• University of Texas Site redesign
• Site map by Glen Doss of a large and complex site. Note: dotted oval indicates navigation locations & pages 8-10 are all one related map

Requirements

• Must be at least 3 levels deep (homepage + 2 sublevels)
• Must include all major categories (you should have somewhere between 5-12 of these)
• Each page must be labelled on the page
• Include a key of symbols
• Include a sidebar of notes for any unusual pages or relationships
• Use the standard diagramming symbols (as shown on right), as described by Withrow. Jesse James Garrett has a downloadable stencil of these shapes.
• Number your page shapes, as per standards: "The home page is 1.0 and second-level pages are 1.1, 1.2, 1.3, etc. Third-level pages under 1.1 would be 1.1.1, 1.1.2, 1.1.3," Withrow
• You can use a horizontal or vertical tree, as seems most appropraite for your site.
• If you have a single page repeated in two locations, show it in both places, but use the convention of cross-linking:
  "Cross link relationships are represented by dotted lines, generally ending in a rectangle containing the numbers of the cross-linked pages (see figure below)." Withrow