navigation-menu-generator

$npx mdskill add kostja94/marketing-skills/navigation-menu-generator

Design, optimize, or audit site navigation menus for SEO and UX.

  • Helps users create or improve header, mega, dropdown, and mobile menus.
  • Reads project context files for key pages and audience.
  • Assesses site structure, goals, and platform to recommend menu organization.
  • Outputs structured navigation designs with size, hierarchy, and grouping guidelines.

SKILL.md

.github/skills/navigation-menu-generatorView on GitHub ↗
---
name: navigation-menu-generator
description: When the user wants to design, optimize, or audit site navigation menus. Also use when the user mentions "navigation," "nav menu," "header menu," "site structure," "menu design," "navbar," "main menu," "mega menu," "dropdown menu," "mobile menu," or "hamburger menu." For breadcrumbs, use breadcrumb-generator.
metadata:
  version: 1.0.1
---

# Components: Navigation Menu

Guides navigation menu design for SEO, UX, and accessibility. Navigation helps users find content and signals site structure to search engines.

**When invoking**: On **first use**, if helpful, open with 1-2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output.

## Initial Assessment

**Check for project context first:** If `.claude/project-context.md` or `.cursor/project-context.md` exists, read it for key pages and audience.

Identify:
1. **Site structure**: Main sections, hierarchy
2. **Primary goals**: Conversion paths, key pages
3. **Platform**: Web, mobile, both

## Structure & Organization

### Menu Size

- **Primary nav**: 7-9 items; avoid overwhelming users
- **Sub-navigation**: Up to 2 levels; deeper topics in sub-menus
- **Pattern**: Horizontal top nav or vertical side nav; avoid novel patterns

### Hierarchy

- Reflect sitemap structure; need not match exactly
- Prioritize what visitors need most
- Logical grouping by topic or task

## SEO Best Practices

| Practice | Purpose |
|----------|---------|
| **Semantic HTML** | `<nav>`, `<ul>`, `<li>`; proper landmark roles |
| **Descriptive anchor text** | Target keywords; avoid "Click here" |
| **Text links** | Prefer text over images; crawlers need readable links |
| **Initial render** | All nav HTML in first paint; no JS-only menus for critical links. See **rendering-strategies** |
| **Visible links** | Prefer visible over hidden; helps crawlers understand structure |

### Crawlability

- Sub-menus: Ensure HTML is in DOM (e.g., CSS-hidden, not JS-injected)
- Footer nav: Include secondary links
- Breadcrumbs: See **breadcrumb-generator** for implementation

## UX Guidelines

### Visibility & Location

- **Desktop**: Visible nav; avoid hiding behind hamburger when space allows
- **Expected placement**: Primary nav in header; footer nav at bottom
- **Current location**: Indicate active page/section in menu

### Accessibility

| Requirement | Practice |
|-------------|----------|
| **Labels** | Clear, intuitive wording |
| **Contrast** | 4.5:1 for link text |
| **Touch targets** | >=44x44px; adequate spacing |
| **Keyboard** | Full keyboard navigation; focus visible |
| **Screen readers** | Proper ARIA; skip links for long menus |

### Design

- Simple, clear; avoid covering entire screen with open menus on desktop
- Consistent across pages
- Mobile: Hamburger acceptable; ensure menu is usable when open

## Output Format

- **Structure** (primary items, sub-items)
- **Anchor text** suggestions
- **HTML/ARIA** notes
- **SEO** checklist
- **Accessibility** checklist

## Related Skills

- **website-structure**: Plan structure and nav hierarchy; nav reflects planned sections
- **xml-sitemap**: Nav should reflect discoverable pages
- **internal-links**: Nav is primary internal linking
- **site-crawlability**: Nav affects crawl paths
- **category-page-generator**: Category hierarchy in nav
- **footer-generator**: Footer nav complements header nav
- **logo-generator**: Logo typically sits in header with nav
- **breadcrumb-generator**: Breadcrumb navigation; BreadcrumbList schema
- **rendering-strategies**: Nav in first paint; no JS-only menus

More from kostja94/marketing-skills

SkillDescription
404-page-generatorWhen the user wants to create, optimize, or audit 404 error pages. Also use when the user mentions "404 page," "404 error," "error page," "page not found," "broken link page," "404 design," "custom 404," "404 redirect," "404 page UX," or "404 recovery." For sitewide page planning, use website-structure.
about-page-generatorWhen the user wants to create, optimize, or audit About page content. Also use when the user mentions "about page," "about us," "company story," "our team," "about section," "company overview," "brand story," "team page," or "who we are." For sitewide page planning, use website-structure.
affiliate-marketingWhen the user wants to plan, implement, or optimize affiliate marketing strategy. Also use when the user mentions "affiliate marketing," "affiliate program strategy," "CPS model," "affiliate recruitment," "commission structure," "affiliate partners," "affiliate network," "affiliate tracking," "affiliate commission," or "partner marketing." For affiliate page, use affiliate-page-generator.
affiliate-page-generatorWhen the user wants to create, optimize, or audit affiliate program page content. Also use when the user mentions "affiliate program," "affiliate page," "partner program," "referral program page," "affiliate landing," "partner landing," "commission page," or "affiliate signup." For affiliate program strategy, use affiliate-marketing.
ai-traffic-trackingWhen the user wants to track AI search traffic in GA4 or GSC. Also use when the user mentions "AI traffic," "ChatGPT referral," "Perplexity traffic," "AI Overviews," "GA4 AI sources," "AI search analytics," "track AI referrals," "AI search traffic," "Claude traffic," or "how to track AI traffic." For AI SEO strategy, use generative-engine-optimization.
alternatives-page-generatorWhen the user wants to create, optimize, or audit alternatives or comparison content (page or blog article). Also use when the user mentions "alternatives page," "alternatives listicle," "X alternatives," "competitor comparison," "vs page," "compare page," "best alternatives to X," "switch from X," "competitor brand traffic," "brand keyword ads," or "intercept competitor search." For competitor research, use competitor-research.
api-page-generatorWhen the user wants to create, optimize, or audit the API introduction/overview page. Also use when the user mentions "API page," "API landing page," "/api page," "API overview," "developer landing," "API marketing," or "API for developers." Note: API documentation (endpoint reference) lives in docs; use docs-page-generator.
app-adsWhen the user wants to run app install ads, user acquisition (UA), or promote mobile apps. Also use when the user mentions "app ads," "app install ads," "UA," "user acquisition," "Google App Campaigns," "Apple Search Ads," "ASA," "UAC," "App Store ads," "Play Store ads," "CPI," or "app promotion." For store listings, use distribution-channels.
article-contentWhen the user wants to write, generate, or create article body content—blog post body, long-form content, how-to guide, listicle. Also use when the user mentions "write article," "article content," "blog post content," "article body," "long-form content creation," "generate article," "article draft," "how-to guide content," "listicle content," "information gain," or "content density." For single post page structure, schema, and SEO metadata, use article-page-generator. For blog index/listing page, use blog-page-generator. For short ad, landing, or email copy, use copywriting.
backlink-analysisWhen the user wants to analyze backlinks, audit link profile, or identify link issues. Also use when the user mentions "backlink analysis," "backlink audit," "referring domains," "toxic links," "link profile," or "disavow file." For acquisition, use link-building.