1.8Step 2 — Inspect the Site Map, if one exists

If the application has a visible Site Map page, start there. This is often the fastest way to capture the product’s real information architecture.

A Site Map page may appear as:

• Site Map
• All Pages
• Browse All
• Documentation Index
• Footer link directory
• Admin navigation tree
• Help center directory

What to extract from the Site Map

Capture:

• page titles
• hierarchy
• grouping by section
• naming conventions
• likely user-facing vs admin-facing areas
• repeated patterns such as /account/*, /settings/*, /orders/*

Copy-paste prompt for Claude Code

Traverse the Site Map page and extract the real application structure.

Capture:
- all visible pages
- page hierarchy
- section names
- naming conventions
- route patterns if visible

Group the pages into logical product domains.

Write findings into:
- docs/discovery/site-map-notes.md
- docs/specs/product-under-test.md

Do not scaffold code yet.

What to do manually if Claude Code misses context

Review the generated notes and correct:

• duplicate pages
• public vs authenticated distinctions
• pages that are present but not test-worthy
• pages that exist only as support/legal content
• internal/admin areas that should be isolated into separate domains