site-mapping

Organize web or app pages into a hierarchical site map with typed pages and stable IDs.

1|Updated Nov 29, 2025
One-click install
npx skills add https://github.com/SSiertsema/claude-code-plugins --skill site-mapping
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: site-mapping
Source: https://github.com/SSiertsema/claude-code-plugins/tree/main/site-mapping/skills/site-mapping
Command: npx skills add https://github.com/SSiertsema/claude-code-plugins --skill site-mapping

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Design a hierarchical site map for a web or app product. Produces a structured page inventory with stable IDs, parent-child hierarchy, page types (hub / detail / utility / legal / entry / funnel), URL pattern per page, primary navigation placement, and access level. Surfaces orphan pages, redundant pages, and depth violations.

Core Features & Use Cases

  • Stable IDs (P-001, …) that persist across revisions
  • Every page has a type — no untyped pages
  • Depth ceiling (default 4) — flag violations
  • Orphans and redundancy surfaced — not hidden
  • URL patterns consistent — naming convention declared
  • Access levels explicit — public / authenticated
  • No fabricated pages — work from supplied scope or elicited content
  • Phase-driven inventories, hierarchy, and diagrams for approval

Quick Start

Provide a product name and an initial page inventory, then request an autonomous site-mapping pass to generate the hierarchical, typed pages with IDs and URL patterns.

Frequently Asked Questions about site-mapping

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a hierarchical site map with stable page IDs?

To create a hierarchical site map, provide a product name and initial page inventory to generate a structured hierarchy with stable IDs, typed pages, defined URL patterns, and explicit navigation placements across revisions.

What is the default depth ceiling for a site map hierarchy?

The default depth ceiling for a site map hierarchy is 4. Any pages exceeding this depth limit are automatically flagged as depth violations, ensuring the information architecture remains accessible and properly structured.

How do I identify orphan pages and redundant pages in a web page inventory?

To identify orphan pages and redundancies, run an autonomous site-mapping audit on your existing web pages. This audit surfaces disconnected pages and overlapping content rather than hiding them within the hierarchy.

Can I generate a site map from an existing product scope without fabricating pages?

Yes, you can generate a site map from an existing product scope without fabricating pages. The process works strictly from supplied scope or elicited content to ensure no artificial pages are introduced into the inventory.

What page types are used when building a site map information architecture?

When building a site map, every page is assigned a specific type from the categories: hub, detail, utility, legal, entry, or funnel. No untyped pages are permitted in the final hierarchical structure.