Marketing ArchitectureURLsNavigation

Site Architecture

Audit and redesign website structure, URL hierarchy, and navigation.

$skillfish add ~skills/site-architecture

Real Examples Get Started Models & Context

Real Conversations

See how the Site Architecture skill responds to actual requests. These are representative examples of what your AI agent will produce.

You

We're rebuilding the Nucleus PM website and I want to fix the URL structure before we migrate. Currently we have: /blog/, /resources/, /guides/, /documentation/, /changelog/ — and content is scattered inconsistently across /blog/ and /resources/. What's the right structure?

Agent

Consolidating content sections before migration is exactly the right call — fixing it after costs you rankings. Here's a clean architecture for a B2B SaaS:

Recommended URL structure:

nucleuspm.com/
├── /blog/                 # Thought leadership, company news, product updates
├── /learn/                # All educational content (replaces /resources/ + /guides/)
│   ├── /learn/sprint-planning-guide
│   └── /learn/[topic]/    # Topic hubs linking to related posts
├── /integrations/         # Integration pages (programmatic SEO)
├── /compare/              # Competitor comparison pages
├── /customers/            # Case studies
├── /changelog/            # Keep as-is
├── /docs/                 # Documentation
└── /pricing/

Key decisions:

1. Merge /resources/ and /guides/ into /learn/ Two sections with overlapping intent confuse users and Google. /learn/ is a clear, crawlable signal about content type.

2. Keep /changelog/ Changelogs earn organic traffic for "[product] updates" queries and build trust signals. Don't fold them into /blog/.

3. Separate /docs/ from the marketing site docs.nucleuspm.com or /docs/ with its own navigation — mixed marketing + docs confuses crawlers about page intent.

4. Add /compare/ and /integrations/ now These are your highest-intent programmatic pages and need a clean URL namespace from day one.

Migration checklist:

Map every existing URL to its new destination
301 every old URL — no exceptions, even pages with zero traffic
Submit new sitemap to GSC within 24 hours of launch
Monitor GSC Coverage report daily for 2 weeks post-launch

Want a full URL mapping spreadsheet template?

You

Our website has 47 pages but users rarely get past the homepage and pricing page. Heatmaps show almost no clicks on our main nav. The nav currently has: Product, Solutions, Resources, Pricing, Company, Blog. How do we restructure navigation to better guide buyers?

Agent

47 pages with a 2-page user journey is a navigation problem, not a content problem. The current nav is organized by internal company structure, not by what buyers need to do. Here's the fix:

Current nav problem:

"Solutions" — too vague; what does it link to?
"Resources" — internal category name, not buyer language
"Company" — low priority, sitting next to Pricing

Restructured nav for buyer journey:

[Nucleus PM logo]  |  How It Works  |  Integrations  |  Compare  |  Pricing  |  [Start Free Trial]

What changed and why:

"How It Works" replaces "Product" — buyer language. "Product" is inside-out thinking.
"Integrations" replaces "Solutions" — engineering managers immediately ask "does it connect to GitHub/Slack?" Answer that question in the nav.
"Compare" replaces "Resources" — buyers in evaluation mode want comparisons. Give them a direct path.
Remove "Company" and "Blog" from top nav — move to footer. These are not buyer-journey pages.
"Start Free Trial" as a CTA button, not a text link — most SaaS sites with low nav engagement have their primary CTA styled as a plain link. Make it a button with contrast.

Mega-menu for "How It Works":

Sprint Planning → link to sprint planning feature page
AI Estimation → link to AI features page
Velocity Tracking → link to velocity feature page
Watch Demo → link to demo page

Expected impact: Nav click-through typically increases 30–60% when restructured from company taxonomy to buyer task language. Validate with a 2-week heatmap comparison after launch.

Get Started

How to install and use this skill in your preferred environment.

Skills are designed for AI coding agents (Claude Code, Cursor, Windsurf) and IDE-based workflows where the agent can read files, run scripts, and act on your codebase. Web-based AI can use the knowledge and frameworks, but won't have tool access.

Models & Context

Which AI models and context windows work best with this skill.

Recommended Models

Best

Claude Opus 4 Claude Sonnet 4 GPT-4.1 Gemini 2.5 Pro Grok 3 Kimi K2

Good

Claude Haiku 4.5 GPT-4.1 mini Gemini 2.5 Flash Grok 3 mini

Larger models produce more detailed, production-ready outputs.

Context Window

This skill's SKILL.md is typically 3–10 KB — fits in any modern context window.

8K Skill only

32K+ Skill + conversation

100K+ Skill + references + codebase

All current frontier models (Claude, GPT, Gemini) support 100K+ context. Use the full window for complex multi-service work.

Pro tips for best results

1

Be specific

Include numbers — users, budget, RPS — so the skill can size the architecture.

2

Share constraints

Compliance needs, team size, and existing stack all improve the output.

3

Iterate

Start with a high-level design, then ask follow-ups for IaC, cost analysis, or security review.

4

Combine skills

Pair with companion skills below for end-to-end coverage.

Ready to try Site Architecture?

Install the skill and start getting expert-level guidance in your workflow — any agent, any IDE.

$skillfish add ~skills/site-architecture

← Browse all 169 skills