AI Agents Hub: Build menu navigation

[konopkja]

Parent: #17615

Summary

Move /ai-agents/ from Use > Emerging Use Cases to Build menu. Add contextual cross-links from related Use case pages. No duplicate nav entries.

Why Move to Build (Data-Backed)

Matomo analytics (site ID 4, Sep 2025 – Feb 2026) show the current Use menu placement contributes minimal traffic and the page already serves a builder/researcher audience:

Traffic sources (Feb 2026):

• 112+ entries from search engines and direct links (62% of visitors)
• ~20 from internal navigation (homepage, use-case pages)
• Google organic drives 40-60% of all entries
• AI assistants (ChatGPT, Copilot) are a new and growing referral source

The Use menu dropdown is responsible for ~20 visits/month. Search and direct traffic is 5-6x that and growing.

Visitor behavior:

• 75% bounce rate — visitors arrive, read, leave. The page does not convert Use-menu browsers into deeper site engagement.
• 77% exit rate — most visitors leave the site from this page
• 129s average time on page (doubled from 33s in Oct 2025) — people are reading, but not navigating further into the site

Audience profile (Paperform survey, 6 respondents from /ai-agents/):

• All 6 are crypto-native (own wallet, 5/6 own crypto)
• Visit intent: "Learn about Ethereum" (3), "Research/academic" (2), "Technical documentation" (1)
• Ease of finding content rated 4-5/10 (mediocre)

Traffic trajectory:

• Sep 2025: 74 visitors → Feb 2026: 157 visitors (22 days, on pace for 220+)
• Traffic has tripled in 5 months, driven entirely by search, not by menu placement

Conclusion: The page's growth is search-driven, its audience is already technical, and the Use menu entry contributes ~20 visits/month against 112+ from external sources. Restructuring the content for builders and placing it under Build aligns navigation with actual audience behavior. The 75% bounce rate suggests Use-menu browsers who land here expecting an end-user explainer are not well-served by the current content, and the builder restructure will widen this mismatch further.

Changes

1. Remove from Use > Emerging Use Cases

In src/lib/nav/buildNavigation.ts, delete this entry from use > use-cases > nav-emerging-label:

// DELETE:
{
  label: t("ai-agents"),
  description: t("nav-ai-agents-description"),
  href: "/ai-agents/",
},

2. Add to Build menu

Add new "AI Agents" section under build.items:

{
  id: "build/ai-agents",
  label: t("ai-agents"),
  description: t("nav-build-ai-agents-description"),
  items: [
    {
      label: t("nav-ai-agents-overview"),
      description: t("nav-ai-agents-overview-description"),
      href: "/ai-agents/",
    },
    {
      label: t("nav-ai-agents-getting-started"),
      description: t("nav-ai-agents-getting-started-description"),
      href: "/ai-agents/getting-started/",
    },
    {
      label: t("nav-ai-agents-frameworks"),
      description: t("nav-ai-agents-frameworks-description"),
      href: "/ai-agents/frameworks/",
    },
    {
      label: t("nav-ai-agents-wallets"),
      description: t("nav-ai-agents-wallets-description"),
      href: "/ai-agents/wallets/",
    },
  ],
}

3. Remove from use-case dropdown switcher

In src/intl/en/template-usecase.json, remove the template-usecase-dropdown-ai-agents entry so the horizontal use-case page switcher (DeFi/NFT/Gaming/etc.) no longer includes AI Agents.

4. Add cross-links from related Use case pages

Add contextual in-content links on these existing pages:

• /defi/ — "AI agents can automate DeFi strategies. Explore AI agents on Ethereum →"
• /payments/ — "AI agents use x402 for machine-to-machine payments. Learn more →"
• /decentralized-identity/ — "ERC-8004 provides portable identity for AI agents. Read more →"

These in-content links carry more SEO weight than nav dropdown entries because they are topically relevant. They also provide better user experience: a user reading about DeFi who is curious about AI agents gets a contextual bridge, rather than stumbling into a builder hub from a generic dropdown.

5. i18n strings

Add new Build menu translation keys to src/intl/en/common.json. Remove or update old Use menu keys.

Files to Modify

• src/lib/nav/buildNavigation.ts — move nav entry
• src/intl/en/common.json — add/update i18n strings
• src/intl/en/template-usecase.json — remove dropdown entry
• public/content/defi/index.md — add cross-link
• public/content/payments/index.md — add cross-link
• public/content/decentralized-identity/index.md — add cross-link