website-structure
When the user wants to plan website structure, decide which pages to build, or prioritize pages for a new or existing site. Also use when the user mentions "website structure," "site structure," "which pages do I need," "page planning," "sitemap planning," "Must Have pages," "website architecture," or "site hierarchy." For a specific page template (e.g. homepage), use homepage-generator or landing-page-generator as appropriate. Not for organic SEO roadmap alone; use seo-strategy.
Best use case
website-structure is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
When the user wants to plan website structure, decide which pages to build, or prioritize pages for a new or existing site. Also use when the user mentions "website structure," "site structure," "which pages do I need," "page planning," "sitemap planning," "Must Have pages," "website architecture," or "site hierarchy." For a specific page template (e.g. homepage), use homepage-generator or landing-page-generator as appropriate. Not for organic SEO roadmap alone; use seo-strategy.
Teams using website-structure should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/website-structure/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How website-structure Compares
| Feature / Agent | website-structure | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
When the user wants to plan website structure, decide which pages to build, or prioritize pages for a new or existing site. Also use when the user mentions "website structure," "site structure," "which pages do I need," "page planning," "sitemap planning," "Must Have pages," "website architecture," or "site hierarchy." For a specific page template (e.g. homepage), use homepage-generator or landing-page-generator as appropriate. Not for organic SEO roadmap alone; use seo-strategy.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# 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 | /education, /startups, /student-discount | education-program, startups-page-generator | | Multi-language | /zh-CN, /ja | localization-strategy | | Community | /ambassadors, /showcase | creator-program, landing-page-generator | | B2B / Enterprise | Solutions (industry-first), Use cases (scenario-first; can be sub-pages), Customer stories | solutions-page-generator, use-cases-page-generator, customer-stories-page-generator | | Developer product | /api, /docs, /status | api-page-generator, docs-page-generator, status-page-generator | | User feedback | Feedback, Roadmap | feedback-page-generator; External (Canny, FeatureBase) | | Plugins/Integrations | /integrations, /plugins | integrations-page-generator, category-page-generator | | Giveaway/Contest | /giveaway | contest-page-generator | ## Domain Structure (Multiple Products) When planning for multiple products or brands, see **domain-architecture** for subfolder vs subdomain vs independent domain. This skill covers page structure within a single domain. For initial domain choice (Brand vs PMD vs EMD, TLD), see **domain-selection**. ## Planning Workflow 1. **Choose template**: Start from generic structure; map to [skills-reference §2](../../../docs/skills-reference.md#2-page-taxonomy) website types 2. **Trim modules**: Remove irrelevant nodes (e.g. no API → drop /api, /docs) 3. **Add specifics**: Industry pages, region, product variants 4. **Assign URLs**: Per node; follow **url-structure** (lowercase, hyphens, short, keyword-rich) 5. **Export list**: "Page type + URL + Priority" for dev scheduling 6. **Tech stack**: Match page types to services (DNS, auth, CMS, status page, etc.) 7. **Iterate**: Expand with new features, markets; keep structure clear ## Structure Principles | Principle | Guideline | |-----------|-----------| | **Flat structure** | Max 4 clicks from homepage to any page; improves crawlability and weight distribution | | **Early planning** | Plan structure before growth; can start right after domain purchase | | **Sitelinks** | Good structure + TOC + authoritative internal links → natural sitelinks in SERP (cannot be forced via schema); see **serp-features** | | **Orphan prevention** | Every page needs internal links; see **site-crawlability** and **internal-links** | | **Features vs Use cases** | /features = capability-first; /use-cases = scenario-first; differentiate content angle, link between, avoid overlap; see **features-page-generator**, **use-cases-page-generator** | | **Clear navigation** | Clear hierarchy and nav improve task completion; users find what they need faster; see **navigation-menu-generator** | | **Pricing placement** | Marketing site: /pricing in main nav for prospects; in-app: Settings → Billing in sidebar for logged-in users (subscription management). Enterprise-only: "Contact sales" may replace public pricing page; see **pricing-page-generator** | ## Homepage Module Reference See **homepage-generator** for common modules (Headline, Subheadline, CTA, Benefits, Social Proof, etc.), navigation options, and **hero-generator** for hero design. ## Output Format - **Page list** with priority (Must Have / Great to Have / Optional) - **URL structure** (paths per section) - **Website-type fit** (which pages apply per [skills-reference §2](../../../docs/skills-reference.md#2-page-taxonomy)) - **Growth mapping** (which paths support which channels) - **Next steps**: url-structure for URL rules; xml-sitemap for submission; site-crawlability for audit ## References - [Website structure SEO guide](https://alignify.co/zh/seo/website-structure) — Alignify: structure importance, page priority, generic template, planning workflow, growth mapping, homepage modules - **skills-reference §2** (docs/skills-reference.md#2-page-taxonomy) — Full page types, website-type matrix, core vs extended; use for page selection ## Related Skills - **seo-strategy**: SEO workflow order; structure planning fits before Technical phase - **domain-selection**: Initial domain choice; do before structure when choosing domain - **domain-architecture**: Subfolder vs subdomain vs independent; do before structure if domain decision pending - **url-structure**: URL optimization, hierarchy, slugs; apply after structure is defined - **site-crawlability**: Crawlability, orphan pages, redirects; audit existing structure - **internal-links**: Link strategy, hub-spoke; implement after pages exist - **xml-sitemap**: Sitemap creation; include planned URLs - **breadcrumb-generator**: Breadcrumb for hierarchy; large sites, e-commerce - **navigation-menu-generator**: Nav design; primary, footer, mobile - **content-strategy**: Content clusters, pillar pages; complements structure planning
Related Skills
url-structure
When the user wants to optimize URL structure, fix URL issues, or plan URL hierarchy. Also use when the user mentions "URL structure," "URL optimization," "slug," "clean URLs," "URL hierarchy," "URL path," "permalink structure," "URL best practices," "dynamic URLs," or "URL parameters." For per-page slug wording, use url-slug-generator. For canonical consolidation, use canonical-tag.
heading-structure
When the user wants to optimize heading structure (H1-H6), fix heading hierarchy, or improve content structure. Also use when the user mentions "H1," "heading," "heading hierarchy," "content structure," "H2," "H3," "heading tags," "heading SEO," "multiple H1," or "heading structure." For SEO workflow, use seo-strategy.
seo-strategy
When the user wants to plan SEO strategy, prioritize SEO work, or understand the SEO workflow. Also use when the user mentions "SEO strategy," "SEO plan," "SEO roadmap," "SEO priority," "SEO audit," "SEO workflow," "where to start SEO," "SEO approach," "organic growth strategy," "why SEO," "SEO value," or "search strategy." For technical/crawl audit execution, use seo-audit. For keyword research, use keyword-research. For AI search visibility, use generative-engine-optimization.
seo-audit
When the user wants to run an SEO audit, technical SEO audit, or site health check. Also use when the user mentions "SEO audit," "technical audit," "site audit," "crawl audit," "indexing audit," "SEO health," or "fix SEO issues." For prioritization and organic strategy, use seo-strategy. For GSC data analysis, use google-search-console.
retention-strategy
When the user wants to reduce churn, improve customer retention, or plan lifecycle marketing. Also use when the user mentions "retention," "churn," "customer lifecycle," "churn prevention," "at-risk customers," or "loyalty program." For lifecycle, use growth-funnel.
research-sources
When the user wants to find information sources for content ideation, competitor monitoring, or industry tracking. Also use when the user mentions "research sources," "information sources," "content ideation," "industry monitoring," "competitor monitoring," "market intelligence," "content research," or "topic research." For keywords, use keyword-research.
product-launch
When the user wants to plan a product launch, execute launch channels, or create a launch checklist. Also use when the user mentions "product launch," "launch strategy," "product announcement," "launch channels," or "market launch." For GTM motion and positioning, use gtm-strategy. For cold start and first users, use cold-start-strategy. For Product Hunt day-of, use product-hunt-launch.
pmf-strategy
When the user wants to validate product-market fit, measure PMF, or plan before scaling. Also use when the user mentions "PMF," "product-market fit," "product market fit," "Sean Ellis test," "very disappointed," "vitamin vs painkiller," "PMF validation," "premature scaling," or "validate before scale." For GTM after validation, use gtm-strategy.
indie-hacker-strategy
When the user wants indie hacker or bootstrapping founder strategy—growth, channels, Build in Public, or solo founder tactics. Also use when the user mentions "indie hacker," "indie developer," "bootstrapping," "bootstrapped founder," "solo founder," "Build in Public," "scratch your own itch," "Micro-SaaS," "first 100 users," or "solo company." For cold start, use cold-start-strategy.
gtm-strategy
When the user wants to plan go-to-market strategy, GTM framework, or market entry. Also use when the user mentions "GTM," "go-to-market," "market entry," "new market," "repositioning," "PLG," "sales-led," "product-led," "marketing-led," "ICP," "buyer persona," "GTM motion," or "market expansion." For launch checklist, use product-launch.
growth-funnel
When the user wants to plan growth using the AARRR framework, diagnose growth bottlenecks, or map actions across the customer lifecycle. Also use when the user mentions "growth funnel," "AARRR," "pirate metrics," "acquisition activation retention," "customer lifecycle metrics," or "growth framework." For retention tactics, use retention-strategy.
conversion-optimization
When the user wants to improve conversion rates, run A/B tests, optimize funnels, or reduce friction. Also use when the user mentions "CRO," "conversion rate optimization," "A/B test," "split test," "funnel optimization," "checkout optimization," "form optimization," or "conversion funnel." For pricing psychology, use pricing-strategy.