Website Structure
Plan which pages your marketing site needs, in what priority order, before you wire templates or chase rankings alone.
Overview
Website-structure is an agent skill most often used in Validate (also Build, Launch) that plans site hierarchy, page priorities, and Must-have inventory before you build or optimize individual templates.
Install
npx skills add https://github.com/kostja94/marketing-skills --skill website-structureWhat is this skill?
- Classifies site type (Product/SaaS, B2B, E-commerce, Portfolio, Forum, Directory) and new vs existing site stage
- Plans page inventory, priority (Must Have vs later), and hierarchy for UX, crawlability, and sitelinks
- Ties structure to navigation, Google importance signals, and growth—not a standalone organic SEO roadmap
- Reads `.claude/project-context.md` or `.cursor/project-context.md` when present for audience and goals
- Points to homepage-generator, landing-page-generator, or seo-strategy for page templates or SEO-only roadmaps
- skill version 1.5.0 in metadata
Adoption & trust: 921 installs on skills.sh; 586 GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You know you need a website but cannot decide which pages matter first or how they should link without either overbuilding or starving SEO and UX.
Who is it for?
Solo founders scoping a marketing site, B2B service pages, or e-commerce information architecture before copy and dev.
Skip if: Organic keyword roadmaps or content calendars only—use seo-strategy; single-page copy for one URL—use homepage-generator or landing-page-generator instead.
When should I use this skill?
User wants to plan website structure, decide which pages to build, prioritize pages, or mentions website structure, site structure, sitemap planning, Must Have pages, or site hierarchy.
What do I get? / Deliverables
You leave with a prioritized page plan and structure rationale aligned to site type and stage, ready to invoke homepage-generator, landing-page-generator, or implementation work on specific URLs.
- Prioritized page inventory and structure plan
- Rationale tying hierarchy to UX and SEO crawl paths
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Canonical shelf is validate because structure decisions happen before full build—page inventory and hierarchy lock scope for landing, product, and legal pages. Scope subphase fits when you are deciding Must-have vs later pages, site type (SaaS, B2B, e-commerce), and hierarchy for a new or existing site.
Where it fits
List Must-have pages (pricing, docs entry, legal) before committing to a Next.js marketing repo.
Decide whether landing URLs are separate routes or consolidated before running landing-page-generator.
Map planned hierarchy to nav components and footer links without inventing orphan pages.
Align URL depth and hub pages so crawlers and sitelinks reflect the agreed structure.
Add blog or resource sections in the hierarchy without breaking primary conversion paths.
How it compares
Use for site-wide page planning and hierarchy, not as a substitute for a dedicated SEO strategy skill or one-off landing copy generators.
Common Questions / FAQ
Who is website-structure for?
Solo and indie builders launching or restructuring a product, portfolio, or store site who need a clear list of pages and priority before design or SEO deep dives.
When should I use website-structure?
During validate when scoping Must-have pages; during build when aligning docs and routes to planned IA; at launch when ensuring SEO-friendly hierarchy and internal links match the plan.
Is website-structure safe to install?
It is planning guidance with optional reads of local project-context files; review the Security Audits panel on this Prism page before installing any skill from the registry.
SKILL.md
READMESKILL.md - Website Structure
# Strategy: Website Structure Guides website structure planning: which pages to build, page priority, and how structure supports UX, SEO, and growth. Structure is the organization and connection of pages; it affects user navigation, Google's understanding of content importance, crawlability, and sitelinks in SERPs. See **serp-features** for sitelinks and SERP optimization. **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 product type, audience, and growth goals. Identify: 1. **Website type**: Product/SaaS, B2B, E-commerce, Portfolio, Forum, Directory 2. **Stage**: New site (plan from scratch) vs. existing (extend or audit) 3. **Growth strategy**: Affiliate, education, multi-language, community, B2B, developer 4. **Constraints**: Team size, budget, tech stack ## Page Priority Framework Plan pages by priority for development scheduling. See [skills-reference §2 Page Taxonomy](../../../docs/skills-reference.md#2-page-taxonomy) for full page types and website-type mapping. | Priority | Pages | Notes | |----------|-------|-------| | **Must Have** | Home, Product/Features, Pricing, Blog, About, Privacy, Terms, Contact | Essential for trust and conversion; Pricing: public page in nav for self-serve; enterprise-only may use "Contact sales" instead; see **pricing-page-generator** (Visibility & Placement) | | **Great to Have** | Testimonials, FAQ, Sitemap (HTML), 404, Refund/Returns | Support UX and SEO | | **Optional** | Search Results, News, Careers, Disclosure | Situational | | **Traffic-driven** | Category/Collection pages | For content-heavy or e-commerce; needs Category + Tags | ## Generic Template Structure Applicable to SaaS, tools, and content sites. Adapt by removing unused nodes (e.g. no API → drop API) and adding specific modules (e.g. industry, region). | Section | Typical Paths | Page Skills | |---------|---------------|-------------| | **Root** | /, /features, /pricing, /demo, /contact | homepage-generator, features-page-generator, pricing-page-generator | | **Tools** | /tools, /free-tools; hub + per-tool pages | tools-page-generator; free tools for lead gen; often SPA; programmatic; see **programmatic-seo** | | **Resources** | /blog, /changelog, /glossary, /faq, /tutorials | blog-page-generator, changelog-page-generator, glossary-page-generator, faq-page-generator | | **Partnership** | /affiliate, /startups, /ambassadors | affiliate-page-generator, landing-page-generator | | **Legal** | /terms, /privacy, /careers | terms-page-generator, privacy-page-generator, careers-page-generator | | **Competitor** | /alternatives, /compare, /migrate | alternatives-page-generator, migration-page-generator | | **Standalone** | /dashboard, /login, /signup, /docs, /api, /status, /support | signup-login-page-generator, docs-page-generator, api-page-generator, status-page-generator | ## Growth Strategy → Structure Mapping Structure reflects growth strategy. Subdirectories signal channels: | Goal | Path Example | Page/Channel | |------|--------------|--------------| | Affiliate conversion | /affiliate | affiliate-page-generator | | Education/student plan | /