plugins/skjalden/skills/sitemap-planning/SKILL.md
Information architecture and sitemap planning — page hierarchy, content siloing, header structure, internal linking strategy, schema markup selection, URL conventions, and featured snippet optimization.
npx skillsauth add hjemmesidekongen/ai sitemap-planningInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Key pages within 3 clicks from homepage. Logical parent/child structure. No orphaned pages. URL structure mirrors the hierarchy: /category/subcategory/page. Keep URLs under 60 chars, lowercase, hyphens only.
Group pages into topical clusters. Each silo has a pillar page (broad topic) linking to cluster pages (specific subtopics). Within-silo linking is dense. Cross-silo linking is rare and intentional. Steps: (1) identify 3-7 core topic areas, (2) assign pages to silos, (3) create pillar page per silo, (4) link cluster pages to their pillar, (5) cross-link only when highly relevant.
One H1 per page matching the primary topic. H2s for main sections (use keyword variations). H3s for subsections (use related terms). Maintain strict hierarchy — no skipping levels. Headers reflect content structure, not visual styling.
H1: Primary Keyword Focus
├── H2: Major Section (Secondary KW)
│ ├── H3: Subsection (LSI term)
│ └── H3: Subsection (Entity)
└── H2: Major Section (Related KW)
└── H3: Subsection
2-3 internal links per page minimum. Descriptive anchor text (not "click here"). Link to related content within the same silo first. Pillar pages should receive the most internal links. Distribute link equity intentionally — don't link everything to the homepage.
High-impact schemas: Article/BlogPosting, FAQPage, HowTo, Review/AggregateRating, Organization, BreadcrumbList, Product. Choose schema based on page type. Implement as JSON-LD in the page head.
Lists for step-by-step content. Tables for comparisons. Definition paragraphs (40-60 words) for "what is" queries. FAQ sections with concise answers. Place the snippet-target content immediately after the relevant H2.
See references/process.md for sitemap templates, linking matrices, schema JSON-LD examples, and URL structure patterns.
development
Creates a brand from scratch through market research and interactive sparring. Runs competitive research via Perplexity, then guides the user through positioning, audience, voice, values, and content pillars. Produces the full brand guideline set at .ai/brand/{name}/. Use when building a new brand, defining brand strategy for a product, or when /våbenskjold:create is invoked.
testing
Loads brand guidelines from .ai/brand/{name}/ and makes them available to the current context. Progressive disclosure: L1 confirms brand exists, L2 loads summary, L3 loads specific files on demand. Use when a downstream skill or user needs brand context, or when /våbenskjold:apply is invoked.
documentation
Guided reinvention of an existing brand guideline. Loads current brand from .ai/brand/{name}/, identifies what to keep vs change, and walks the user through targeted evolution. Preserves brand equity while updating positioning, voice, or values. Use when refreshing a brand or when /våbenskjold:evolve is invoked.
development
Codifies an existing brand from materials, samples, and references. Analyzes provided content to extract voice patterns, values, and positioning. Produces the same guideline format as brand-strategy. Use when a brand already exists but isn't documented, or when /våbenskjold:audit is invoked.