The playbook
Website Architecture: Checklist
Use this website architecture checklist before a new release, a handoff, or a scheduled review. Its purpose is to verify the decisions that affect successful navigation tasks. Check an actual page or interaction record; a box marked complete without evidence does not show that the customer journey works.
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.
Before you use the checklist
Name the exact item being checked and its purpose. Gather page, parent, audience task, navigation label. If one of those details is unknown, mark it as unknown and assign a way to resolve it. An invented value makes the checklist look complete while weakening every later decision.
Working checklist
| Check | Evidence to keep | Responsible role |
|---|---|---|
| Group content around audience tasks | A dated observation showing how page was verified | website lead |
| Choose category labels people recognize | A dated observation showing how parent was verified | designer or developer |
| Test paths to important pages from common entry points | A dated observation showing how audience task was verified | site owner |
Check the failure path
- Look specifically for this failure: structuring navigation around internal departments customers do not know.
- Rename categories around the visitor's needs. Record the actual correction, not just the intention to make it.
- Repeat the affected task after the correction and check navigation label.
- Make sure the next owner can find the decision and supporting evidence.
Use three outcomes for each check
Mark an item as complete only when the expected behavior or information has been observed. Mark it as incomplete when a required condition is absent. Use not applicable when the condition genuinely does not belong to the chosen scope, and write a short reason. These states keep a review useful without forcing every process into an identical mold.
For example, if the check is “Group content around audience tasks,” a meeting about the subject is not the evidence itself. Retain the relevant page and parent, the decision made from them, and the result of checking that decision. The record should allow someone who missed the meeting to understand what changed.
Decide what must be resolved first
An incomplete item that prevents organize pages so visitors can find information and understand relationships deserves attention before a cosmetic improvement. Assign an owner and a next action to that issue. Keep optional refinements visible, but do not let them obscure a failure in the core process.
Close the review
Recheck corrected items and note anything still uncertain. The checklist is finished when the next owner understands what was verified and what remains open. Follow successful navigation tasks using a consistent definition so later reviews can connect execution quality with useful results.
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