The playbook
Website Architecture: Metrics and Measurement
Measure website architecture by defining successful navigation tasks precisely enough that two people can reproduce the result from the same records. Keep the reporting unit, date basis, and scope visible. Without those definitions, a change in the report may reflect a changed calculation rather than a changed customer outcome.
Put the task in context
Group pages around recognizable tasks such as services, pricing, projects, and contact. Test whether a first-time visitor can find the relevant service from both the homepage and an article. A visitor entering through search may never see the homepage.
Create a metric definition
| Definition field | What it must explain |
|---|---|
| Measure | successful navigation tasks |
| Unit | What one page or interaction record or completed outcome represents |
| Included records | The scope identified by page and parent |
| Date basis | The event date or period used to include a record |
| Exclusions | Tests, duplicates, or other records outside the agreed definition |
| Source owner | site owner |
Separate delivery checks from outcome measures
A delivery check asks whether the team completed a specific task, such as group content around audience tasks. An outcome measure asks what happened for the user or business afterward. Keep both visible. Completing the task is useful evidence of execution, but it does not by itself prove that the broader outcome improved.
Worked arithmetic example
Suppose an illustrative review includes 80 eligible records, and 60 satisfy the explicitly defined completion condition. The completion share is 60 ÷ 80 × 100 = 75%. This is hypothetical arithmetic, not an industry benchmark or a predicted improvement. It describes only the population and condition you defined.
For website architecture, explain the condition before applying that calculation. If the question is whether the team can test paths to important pages from common entry points, a record counts only when the evidence demonstrates that condition. Do not replace missing outcomes with successful ones just to complete a report.
Compare like with like
Keep the scope, date basis, and exclusions consistent between observations. If parent changes meaning between periods, note the change and rebuild a comparable view where possible. A rate can also move because the composition of the underlying group changed, even when individual performance did not.
Investigate an unexpected result
- Check whether the underlying page records are complete.
- Look for this known failure: structuring navigation around internal departments customers do not know.
- Verify that the process still includes: choose category labels people recognize.
- Reconcile a sample with the original record before changing the operating plan.
Use the report to choose an action
If the evidence supports a correction, rename categories around the visitor's needs. Record when the change occurred and what should be checked next. Keep uncertainty visible when the sample is small or the observation period is incomplete. The purpose of measurement is a better decision about successful navigation tasks, not a favorable-looking number.
Keep the page’s main task visible when adding helpful detail. Supporting information should reduce uncertainty at the decision point. If a section introduces a second unrelated offer, decide whether it belongs on another page.
Skip the manual steps. Let AgentixHUB run this for every client.
Start now