Choose the journeys the structure must support
A sensible hierarchy starts with the visitor’s task, not a list of keywords.
Use this for: Public pages within the agreed audit scope.
List the main things visitors need to accomplish and the pages that support them. Separate buying, comparing, learning and support journeys when they need different destinations. Use business priorities and observed customer questions rather than inventing traffic estimates.
Hypothetical example: A repair business separates booking a repair from reading a troubleshooting guide.
- Name three to five representative visitor tasks.
- Assign an existing destination to each task.
- Flag tasks with no useful destination.
More help and optional notes
If it fails: Agree on the missing destinations before changing menus.
Retest: Repeat the same check on the published site and record whether the original failure is resolved.
Not applicable: No pages in the stated scope.
Keep in mind: This is a manual audit workflow, not an automatic site scan or a guarantee of search performance.
Optional: URLs checked, finding, decision, owner and retest result. Keep confidential data out of shared exports.
Changing this result updates your checkmark and progress immediately. Notes are optional.

