AgentAlley
Connect your AISubmit
Submit

Website Structure Planner

Website structure

by kostja94 · MIT license · ★ 1,006 on GitHub

Website structure cover

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,"…

---
name: website-structure
description: 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.
metadata:
  version: 1.5.0
---

# 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

**Project context:** Read root `contextus.md` when present and load only the modules relevant to this task. Without Contextus, use available project material or user-provided facts and ask for missing information; do not create a parallel context system.

Identify:

Overview

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.

What you get

  • Page listwith priority (Must Have / Great to Have / Optional)
  • URL structure(paths per section)
  • Website-type fit(which pages apply per skills-reference §2)
  • Growth mapping(which paths support which channels)
  • Next stepsurl-structure for URL rules; xml-sitemap for submission; site-crawlability for audit
Manual install (npx, ZIP)
Claude Codenpx skills add kostja94/marketing-skills --skill website-structure -g -a claude-code
Claude Code (degit)npx degit kostja94/marketing-skills/skills/strategies/structure/website-structure#main ~/.claude/skills/website-structure
Claude.ai / desktopZip the folder and upload it under Settings → Capabilities → Skills.
Codex, Cursor, other agentsPoint them at SKILL.md. The other files are plain text.

Connects with Agent Alley MCP · agentalley.io/mcp

Files included

  • SKILL.md8.6 KB
Read SKILL.md here
kostja94/main1 file shown
SKILL.md
Show the full text120 lines
website-structure/SKILL.md120 lines · 8.6 KB
Outline
RawView on GitHub

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

Project context: Read root contextus.md when present and load only the modules relevant to this task. Without Contextus, use available project material or user-provided facts and ask for missing information; do not create a parallel context system.

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 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 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)
  • 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 — 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
  • 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
1---
2name: website-structure
3description: 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.
4metadata:
5 version: 1.5.0
6---
7 
8# Strategy: Website Structure
9 
10Guides 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.
11 
12**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.
13 
14## Initial Assessment
15 
16**Project context:** Read root `contextus.md` when present and load only the modules relevant to this task. Without Contextus, use available project material or user-provided facts and ask for missing information; do not create a parallel context system.
17 
18Identify:
191. **Website type**: Product/SaaS, B2B, E-commerce, Portfolio, Forum, Directory
202. **Stage**: New site (plan from scratch) vs. existing (extend or audit)
213. **Growth strategy**: Affiliate, education, multi-language, community, B2B, developer
224. **Constraints**: Team size, budget, tech stack
23 
24## Page Priority Framework
25 
26Plan 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.
27 
28| Priority | Pages | Notes |
29|----------|-------|-------|
30| **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) |
31| **Great to Have** | Testimonials, FAQ, Sitemap (HTML), 404, Refund/Returns | Support UX and SEO |
32| **Optional** | Search Results, News, Careers, Disclosure | Situational |
33| **Traffic-driven** | Category/Collection pages | For content-heavy or e-commerce; needs Category + Tags |
34 
35## Generic Template Structure
36 
37Applicable 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).
38 
39| Section | Typical Paths | Page Skills |
40|---------|---------------|-------------|
41| **Root** | /, /features, /pricing, /demo, /contact | homepage-generator, features-page-generator, pricing-page-generator |
42| **Tools** | /tools, /free-tools; hub + per-tool pages | tools-page-generator; free tools for lead gen; often SPA; programmatic; see **programmatic-seo** |
43| **Resources** | /blog, /changelog, /glossary, /faq, /tutorials | blog-page-generator, changelog-page-generator, glossary-page-generator, faq-page-generator |
44| **Partnership** | /affiliate, /startups, /ambassadors | affiliate-page-generator, landing-page-generator |
45| **Legal** | /terms, /privacy, /careers | terms-page-generator, privacy-page-generator, careers-page-generator |
46| **Competitor** | /alternatives, /compare, /migrate | alternatives-page-generator, migration-page-generator |
47| **Standalone** | /dashboard, /login, /signup, /docs, /api, /status, /support | signup-login-page-generator, docs-page-generator, api-page-generator, status-page-generator |
48 
49## Growth Strategy → Structure Mapping
50 
51Structure reflects growth strategy. Subdirectories signal channels:
52 
53| Goal | Path Example | Page/Channel |
54|------|--------------|--------------|
55| Affiliate conversion | /affiliate | affiliate-page-generator |
56| Education/student plan | /education, /startups, /student-discount | education-program, startups-page-generator |
57| Multi-language | /zh-CN, /ja | localization-strategy |
58| Community | /ambassadors, /showcase | creator-program, landing-page-generator |
59| 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 |
60| Developer product | /api, /docs, /status | api-page-generator, docs-page-generator, status-page-generator |
61| User feedback | Feedback, Roadmap | feedback-page-generator; External (Canny, FeatureBase) |
62| Plugins/Integrations | /integrations, /plugins | integrations-page-generator, category-page-generator |
63| Giveaway/Contest | /giveaway | contest-page-generator |
64 
65## Domain Structure (Multiple Products)
66 
67When 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**.
68 
69## Planning Workflow
70 
711. **Choose template**: Start from generic structure; map to [skills-reference §2](../../../docs/skills-reference.md#2-page-taxonomy) website types
722. **Trim modules**: Remove irrelevant nodes (e.g. no API → drop /api, /docs)
733. **Add specifics**: Industry pages, region, product variants
744. **Assign URLs**: Per node; follow **url-structure** (lowercase, hyphens, short, keyword-rich)
755. **Export list**: "Page type + URL + Priority" for dev scheduling
766. **Tech stack**: Match page types to services (DNS, auth, CMS, status page, etc.)
777. **Iterate**: Expand with new features, markets; keep structure clear
78 
79## Structure Principles
80 
81| Principle | Guideline |
82|-----------|-----------|
83| **Flat structure** | Max 4 clicks from homepage to any page; improves crawlability and weight distribution |
84| **Early planning** | Plan structure before growth; can start right after domain purchase |
85| **Sitelinks** | Good structure + TOC + authoritative internal links → natural sitelinks in SERP (cannot be forced via schema); see **serp-features** |
86| **Orphan prevention** | Every page needs internal links; see **site-crawlability** and **internal-links** |
87| **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** |
88| **Clear navigation** | Clear hierarchy and nav improve task completion; users find what they need faster; see **navigation-menu-generator** |
89| **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** |
90 
91## Homepage Module Reference
92 
93See **homepage-generator** for common modules (Headline, Subheadline, CTA, Benefits, Social Proof, etc.), navigation options, and **hero-generator** for hero design.
94 
95## Output Format
96 
97- **Page list** with priority (Must Have / Great to Have / Optional)
98- **URL structure** (paths per section)
99- **Website-type fit** (which pages apply per [skills-reference §2](../../../docs/skills-reference.md#2-page-taxonomy))
100- **Growth mapping** (which paths support which channels)
101- **Next steps**: url-structure for URL rules; xml-sitemap for submission; site-crawlability for audit
102 
103## References
104 
105- [Website structure SEO guide](https://alignify.co/zh/seo/website-structure) — Alignify: structure importance, page priority, generic template, planning workflow, growth mapping, homepage modules
106- **skills-reference §2** (docs/skills-reference.md#2-page-taxonomy) — Full page types, website-type matrix, core vs extended; use for page selection
107 
108## Related Skills
109 
110- **seo-strategy**: SEO workflow order; structure planning fits before Technical phase
111- **domain-selection**: Initial domain choice; do before structure when choosing domain
112- **domain-architecture**: Subfolder vs subdomain vs independent; do before structure if domain decision pending
113- **url-structure**: URL optimization, hierarchy, slugs; apply after structure is defined
114- **site-crawlability**: Crawlability, orphan pages, redirects; audit existing structure
115- **internal-links**: Link strategy, hub-spoke; implement after pages exist
116- **xml-sitemap**: Sitemap creation; include planned URLs
117- **breadcrumb-generator**: Breadcrumb for hierarchy; large sites, e-commerce
118- **navigation-menu-generator**: Nav design; primary, footer, mobile
119- **content-strategy**: Content clusters, pillar pages; complements structure planning
120 
View all files on GitHub →

Details

License
MIT
Stars on the repo
★ 1,006
Checked
Source
kostja94/marketing-skills ↗
Creator
kostja94 · 106 listings
View creator

Similar skills

See all →
AgentPhase 2: Foundation Scaffoldingmsitarzewski/agency-agents · by msitarzewski> Duration: 3-5 days | Agents: 6 | Gate Keepers: DevOps Automator + Evidence Collector★ 154k GitHub starsAgentNEXUS Network Frameworkmsitarzewski/agency-agents · by msitarzewski> NEXUS transforms The Agency's independent AI specialists into a synchronized intelligence network. This is not a prompt collection — it…★ 154k GitHub starsSkillAnsoff Matrix Generatorphuryn/pm-skills · by phurynGenerate an Ansoff Matrix analysis mapping growth strategies across market penetration, market development, product development, and diversification. Use when considering growth options, planning market expansion, or evaluating strategic growth paths.★ 26.6k GitHub starsSkillArchitecture Advisorshadcn/improve · by shadcnSurvey any codebase as a senior advisor and produce prioritized, self-contained implementation plans for OTHER models/agents to execute. Strictly read-only on source code — never implements, fixes, or refactors anything itself. Use when asked to audit a codebase, find improvement opportunities (bugs, security, performance, test coverage, tech debt, migrations, DX), suggest features or where to take the project next (roadmap, product direction), or generate handoff plans for another agent to implement.★ 9.2k GitHub starsSkillCareer Skills TranslatorParamchoudhary/ResumeSkills · by ParamchoudharyTranslate skills from one industry to another, identify transferable skills★ 2.4k GitHub starsSkillMarketing Skills CollectionLeoYeAI/openclaw-marketing-skills · by LeoYeAIA collection of 37 battle-tested marketing skills for OpenClaw agents. Use when you want to install or reference any marketing skill including: CRO (page-cro, signup-flow-cro, onboarding-cro, form-cro, popup-cro, paywall-upgrade-cro), copywriting, copy-editing, cold-email, email-sequence, social-content, seo-audit, ai-seo, programmatic-seo, site-architecture, schema-markup, content-strategy, paid-ads, ad-creative, ab-test-setup, analytics-tracking, referral-program, free-tool-strategy, churn-prevention, revops, sales-enablement, launch-strategy, pricing-strategy, competitor-alternatives, marketing-ideas, marketing-psychology, lead-magnets, product-marketing-context, and data connectors (google-ads-connect, search-console-connect, meta-ads-connect, x-twitter-connect). Start with product-marketing-context to set up your product context document, then use any other skill naturally. Powered by MyClaw.ai.★ 1k GitHub stars

More from kostja94

SkillAffiliate Marketing Strategykostja94/marketing-skills · by kostja94When 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.★ 1k GitHub starsSkillAI Search Traffic Trackerkostja94/marketing-skills · by kostja94When 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.★ 1k GitHub starsSkillGA4 Analytics Optimizerkostja94/marketing-skills · by kostja94When the user wants to set up, audit, or optimize analytics tracking (GA4, events, conversions). Also use when the user mentions "Google Analytics," "GA4," "event tracking," "conversions," "attribution model," "gtag," "data layer," "GA4 setup," "conversion tracking," "event setup," "User ID tracking," or "CTA attribution." For traffic insights, use traffic-analysis.★ 1k GitHub starsSkillMobile App Campaign Managerkostja94/marketing-skills · by kostja94When 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.★ 1k GitHub starsSkillLong-Form Article Writerkostja94/marketing-skills · by kostja94When 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.★ 1k GitHub starsSkillBacklink Profile Analyzerkostja94/marketing-skills · by kostja94When 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.★ 1k GitHub stars

Browse more free Claude skills or everything in Product.