The sitemap is the story. If IA fights positioning, the site loses.
A site architecture template is the information-architecture worksheet: hubs, child pages, and the job of each URL. Use it after the messaging map. The companion sitemap template is the page list; this sheet is the why of each branch. Thought-leadership piece six in this cluster lives here: IA that matches positioning.
Primary job of the site, the three buyer questions, the hub tree, and which promise each hub defends. No page without a job.
Demo, self-serve, or educate — pick one.
The three questions the IA must answer.
Product, use-case, proof, resources.
Pages with no parent and no internal links.
Scribe’s frame is content performance analytics. The site cannot lead with “platform.”
Scribe
| Field | Filled |
|---|---|
| Primary job | Book a demo from VPs who have a content team |
| Hub 1 | /product — the Salesforce join, not a feature grid |
| Hub 2 | /customers — pipeline proof |
| Resources | How-tos that end on the template, not a blog index |
What is it, why you, can I trust it.
If two hubs answer the same question, merge them.
A page with no parent is a leftover campaign.
| Mistake | Fix |
|---|---|
| Nav that lists every feature | Nav lists jobs. Features live under product. |
IA first (this page), then the sitemap list. Same week is fine.