Website information architecture
Skill the-nam-shub/e5-real-skills/skills/website-information-architecture
Guides Claude to help marketers structure website navigation, CTAs, and page hierarchy to reduce cognitive load and drive conversions. Trigger when a user is auditing or redesigning website IA, navigation menus, or CTA strategy.From its SKILL.md
npx -y skills add the-nam-shub/e5-real-skills --skill website-information-architectureAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 8 stars8 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
4.7 KB, 937 tokens by cl100k_base, as published. Nobody here has run it
Website Information Architecture
Overview
This skill covers best practices for structuring B2B website navigation, calls to action, and visual hierarchy to reduce visitor confusion and improve conversion. All practices are sourced exclusively from Exit Five podcast guests. No general marketing knowledge has been added.
CTA Strategy and Hierarchy
When helping a user design or audit their calls to action, apply the following principles:
Consolidate to one primary CTA per page or section. Do not allow multiple equally-weighted CTA buttons to compete for attention. Identify the single most important conversion action for the page and make it the primary button. If secondary actions are necessary (e.g., "See Features" or "View Pricing"), render them as text links below the primary button — not as additional buttons. This makes the conversion hierarchy immediately legible to visitors. (Source: Talia Wolf, Episode #251)
Ensure each CTA serves a distinct purpose. If multiple CTAs must coexist on a page (e.g., "Book Demo," "Start Trial," "See Features"), verify that each one appeals to a meaningfully different visitor mindset or stage of intent. Remove or demote any CTA that duplicates the goal of another. One CTA should be clearly primary; all others should be visually subordinate. (Source: Talia Wolf, Episode #251)
Reserve your CTA button color exclusively for the primary action. Do not reuse the CTA button color for other UI elements on the page — callouts, highlights, icons, section backgrounds, or secondary elements. Every additional use of that color trains the visitor's eye to ignore it, diluting the visual signal that says "click here." If your primary button is blue, blue should appear nowhere else on the page in a decorative or emphasis role. (Source: Talia Wolf, Episode #251)
Navigation Design
When helping a user audit or redesign their website navigation, apply the following principles:
Remove redundant CTAs from the header that duplicate existing navigation items. If "Pricing" already exists as a menu item, do not also place a "View Pricing" button in the header navigation. Visitors can already find pricing through the menu. Header CTA slots are scarce and high-visibility — reserve them for your primary conversion goal (e.g., "Book Demo" or "Start Free Trial"), not for directing visitors to pages they can already reach through the nav. (Source: Talia Wolf, Episode #251)
Personalize navigation menus by customer segment. Rather than displaying every feature, use case, and integration to all visitors, customize the navigation to surface the paths most relevant to each segment (e.g., agencies vs. enterprise buyers). Highlight the case studies, features, and integrations that matter to that specific customer type. This creates a more focused experience without requiring complex personalization infrastructure. (Source: Talia Wolf, Episode #251)
What NOT To Do
- Do not use your CTA button color for non-CTA elements. Repeating the primary action color throughout the page for decorative or secondary UI purposes reduces its ability to draw the eye to the conversion point. (Source: Talia Wolf, Episode #251)
- Do not place redundant navigation CTAs in the header. A "View Pricing" button next to a "Pricing" menu item adds noise without adding value and wastes a high-visibility conversion slot. (Source: Talia Wolf, Episode #251)
- Do not present multiple CTAs of equal visual weight. When everything is a primary action, nothing is. Visitors faced with competing buttons of equal prominence experience decision paralysis and are less likely to convert. (Source: Talia Wolf, Episode #251)
- Do not offer multiple CTAs that accomplish the same goal. If two buttons lead to the same outcome or serve the same visitor intent, remove one. Every CTA should earn its place by serving a distinct purpose. (Source: Talia Wolf, Episode #251)
- Do not show all features and use cases to all visitors indiscriminately. A navigation menu that tries to serve everyone equally often serves no one well. Segment-specific navigation reduces cognitive load and signals relevance. (Source: Talia Wolf, Episode #251)
Where Experts Disagree
No disagreements were identified among the contributing episodes for this skill.
Sources
| Episode | Guest | Date |
|---|---|---|
| Episode #251 | Talia Wolf | 2025-06-02 |
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 0 of the 12 instructions most architecture codebase skills give in 937 tokens
Counted across 811 of the 1,134 authors here whose files we hold, read 2026-08-07
- Ask the user which candidate to explorein 45 of 811, across 15 files
- Apply the deletion test to suspected shallow modulesin 43 of 811, across 15 files
- Read any relevant architecture decision records firstin 31 of 811, across 8 files
- Use exact glossary terms in every suggestionin 30 of 811, across 10 files
- Accept dependencies instead of creating themin 24 of 811, across 5 files
- Include before and after visualisations for each candidatein 24 of 811, across 5 files
- Read the domain glossary before exploringin 24 of 811, across 6 files
- Return results instead of producing side effectsin 23 of 811, across 4 files
- Explore the codebase for shallow modules and frictionin 23 of 811, across 3 files
- Introduce seams only where things varyin 22 of 811, across 3 files
- Reduce the number of methodsin 21 of 811, across 2 files
- Design deep modules with small interfacesin 21 of 811, across 3 files
Said here and by no other author read
- consolidate to one primary CTA per page
- render secondary actions as text links
- verify each CTA serves a distinct purpose
- reserve CTA button color exclusively for primary actions
- remove redundant CTAs from the header
- personalize navigation menus by customer segment
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.