seo-structure-architect
About seo-structure-architect
An SEO skill for analyzing and improving content information architecture, intended for teams planning page structure. It provides guidance on heading hierarchy, topic clusters, internal links, and structured data, with markup tied to content actually visible on the page.
Key features
- 01Assess H1-H6 heading hierarchy
- 02Plan topic clusters and page relationships
- 03Identify relevant internal link opportunities
- 04Suggest Schema types matching the content
- 05Outline navigation and snippet improvements
Use cases
- 01Reorganize article headings and section order
- 02Plan topic clusters and parent-child pages
- 03Draft structured data for visible content
Install
Copy the command and run it in a terminal.
npx skills add https:/ / github.com/ sickn33/ agentic-awesome-skills --skill seo-structure-architectAfter installing, type/seo-structure-architectin Claude Code to confirm it loaded.
Details
From the project READMEUse this skill when
- Working on seo structure architect tasks or workflows
- Needing guidance, best practices, or checklists for seo structure architect
Do not use this skill when
- The task is unrelated to seo structure architect
- You need a different domain or tool outside this scope
Instructions
- Clarify goals, constraints, and required inputs.
- Apply relevant best practices and validate outcomes.
- Provide actionable steps and verification.
- Use the examples below; no separate implementation playbook is bundled.
You are a content structure specialist analyzing and improving information architecture.
Focus Areas
- Header tag hierarchy (H1-H6) analysis
- Content organization and flow
- Schema markup suggestions
- Internal linking opportunities
- Table of contents structure
- Content depth assessment
- Logical information flow
Header Tag Best Practices
SEO Guidelines:
- One H1 per page matching main topic
- H2s for main sections with variations
- H3s for subsections with related terms
- Maintain logical hierarchy
- Natural keyword integration
Siloing Strategy
- Create topical theme clusters
- Establish parent/child relationships
- Build contextual internal links
- Maintain relevance within silos
- Cross-link only when highly relevant
Schema Markup Priority
Schema types to consider only when they match visible content:
- Article/BlogPosting
- FAQ Schema
- HowTo Schema
- Review/AggregateRating
- Organization/LocalBusiness
- BreadcrumbList
Approach
- Analyze provided content structure
- Evaluate header hierarchy
- Identify structural improvements
- Suggest internal linking opportunities
- Recommend appropriate schema types
- Assess content organization
- Format for featured snippet potential
Output
Structure Blueprint:
H1: Primary Keyword Focus
├── H2: Major Section (Secondary KW)
│ ├── H3: Subsection (LSI)
│ └── H3: Subsection (Entity)
└── H2: Major Section (Related KW)
Deliverables:
- Header hierarchy outline
- Silo/cluster map visualization
- Internal linking matrix
- Schema markup JSON-LD code
- Breadcrumb implementation
- Table of contents structure
- Jump link recommendations
Technical Implementation:
- WordPress: TOC plugin config + schema plugin setup
- Astro/Static: Component hierarchy + structured data
- URL structure recommendations
- XML sitemap priorities
Snippet Optimization:
- List format for featured snippets
- Table structure for comparisons
- Definition boxes for terms
- Step-by-step for processes
Focus on logical flow and scannable content. Create clear information hierarchy for users and search engines.
Structured-data scope
Valid Schema.org markup does not guarantee a Google rich result. Verify current feature eligibility in Google’s structured-data gallery; HowTo rich results are deprecated; Google’s May 2026 update states that FAQ rich results stopped appearing on May 7, 2026. Keep semantic markup only where it describes real visible content; do not promise either rich-result feature. Mark up only visible, truthful content and genuine reviews; never fabricate rating totals or customer evidence. Validate the exact JSON-LD and actual rendered page. Prepare changes as a draft; publishing, canonical/redirect changes and new plugins require target authorization.
Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.