website-structure

Solid

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.

Web & Frontend 553 stars 82 forks Updated 3 weeks ago MIT

Install

View on GitHub

Quality Score: 92/100

Stars 20%
91
Recency 20%
90
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# 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 conversi...

Details

Author
kostja94
Repository
kostja94/marketing-skills
Created
3 months ago
Last Updated
3 weeks ago
Language
N/A
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

Data & Documents Listed

site-architecture

When the user wants to plan, map, or restructure their website's page hierarchy, navigation, URL structure, or internal linking. Also use when the user mentions "sitemap," "site map," "visual sitemap," "site structure," "page hierarchy," "information architecture," "IA," "navigation design," "URL structure," "breadcrumbs," "internal linking strategy," "website planning," "what pages do I need," "how should I organize my site," or "site navigation." Use this whenever someone is planning what pages a website should have and how they connect. NOT for XML sitemaps (that's technical SEO — see seo-audit). For SEO audits, see seo-audit. For structured data, see schema-markup.

335 Updated today
aiskillstore
Data & Documents Listed

site-architecture

When the user wants to plan, map, or restructure their website's page hierarchy, navigation, URL structure, or internal linking. Also use when the user mentions "sitemap," "site map," "visual sitemap," "site structure," "page hierarchy," "information architecture," "IA," "navigation design," "URL structure," "breadcrumbs," "internal linking strategy," "website planning," "what pages do I need," "how should I organize my site," or "site navigation." Use this whenever someone is planning what pages a website should have and how they connect. NOT for XML sitemaps (that's technical SEO, see seo-audit). For SEO audits, see seo-audit. For structured data, see schema-markup.

0 Updated 4 days ago
evgeniiakruglova
Data & Documents Listed

30x-seo-architecture

Website architecture planning: page hierarchy, navigation, URL structure, internal linking strategy. Use when user says "site structure", "page hierarchy", "URL structure", "navigation design", or "information architecture". NOT for XML sitemaps (use seo-sitemap).

0 Updated today
square-lupus579
AI & Automation Featured

site-architecture

Plan or restructure website hierarchy, navigation, URL patterns, breadcrumbs, and internal linking. Use when mapping pages, sections, and site structure, but not for XML sitemap auditing or schema markup.

39,227 Updated today
sickn33
AI & Automation Solid

site-architecture

When the user wants to audit, redesign, or plan their website's structure, URL hierarchy, navigation design, or internal linking strategy. Use when the user mentions 'site architecture,' 'URL structure,' 'internal links,' 'site navigation,' 'breadcrumbs,' 'topic clusters,' 'hub pages,' 'orphan pages,' 'silo structure,' 'information architecture,' or 'website reorganization.' Also use when someone has SEO problems and the root cause is structural (not content or schema). NOT for content strategy decisions about what to write (use content-strategy) or for schema markup (use schema-markup).

16,642 Updated yesterday
alirezarezvani