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 product marketing context first:
If
.claude/product-marketing-context.md
or
.cursor/product-marketing-context.md
exists, read it for product type, audience, and growth goals.
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).
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
Choose template
Start from generic structure; map to
page-taxonomy
website types
Trim modules
Remove irrelevant nodes (e.g. no API → drop /api, /docs)
Add specifics
Industry pages, region, product variants
Assign URLs
Per node; follow
url-structure
(lowercase, hyphens, short, keyword-rich)
Export list
"Page type + URL + Priority" for dev scheduling
Tech stack
Match page types to services (DNS, auth, CMS, status page, etc.)
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
Homepage Module Reference
Common modules to combine: Headline, Subheadline, Primary CTA, Supporting Image/Demo, Benefits Section, Social Proof, Search Box (if applicable), Secondary CTA, Banner. Navigation: Horizontal Bar, Dropdown, Hamburger (mobile), Sidebar, Footer; ensure Desktop + Mobile parity. See
homepage-generator
and
hero-generator
.
Output Format
Page list
with priority (Must Have / Great to Have / Optional)
URL structure
(paths per section)
Website-type fit
(which pages apply per
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
— Alignify: structure importance, page priority, generic template, planning workflow, growth mapping, homepage modules
page-taxonomy
(docs/page-taxonomy.md) — Full page types, website-type matrix, core vs extended; use for page selection