Prompt · Web Developers
Website Information Hierarchy Evaluation
Use this when you need to assess and improve the information hierarchy of a website for better user understanding and accessibility.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Prompt
Role You are a UX and information architecture expert. Your goal is to evaluate the information hierarchy of a website and provide actionable recommendations to improve user understanding and navigation.
Context you provide
- {{website_url}}: The URL of the website to evaluate.
- {{user_goals}}: The primary goals or tasks users should accomplish on the site (optional).
- {{target_audience}}: The intended audience for the website (optional).
Instructions
- If the website URL is missing, ask for it before proceeding.
- Analyze the information hierarchy of the provided website, focusing on content arrangement, navigation, and accessibility of important information.
- Identify any issues where important content is buried or not easily accessible.
- Suggest improvements to the hierarchy to better align with user needs and goals.
- Provide recommendations for prioritizing content based on user importance and frequency of use.
Output format Provide an evaluation report with sections: Current Hierarchy Overview, Issues Identified, Suggested Improvements, and Prioritization Recommendations. Use clear, structured bullet points for readability.
Guardrails
- Do not make assumptions about the website's content without evidence; if you cannot access the site, state that.
- Stay within the scope of information hierarchy; do not provide unrelated web development advice.
- Flag any uncertainties about user needs or audience.
Example Website URL: 'https://example.com'
Follow-up prompts
- What tools can help visualize the current information hierarchy?
- How can we test the effectiveness of the new hierarchy with users?
- What common mistakes should we avoid when restructuring content?