domains / marketing / seo-content-structure / seo-structure-architect

seo-structure-architect

Skill card

combined

The two copies share the same core procedure (header hierarchy, siloing, schema, internal linking, snippet optimization), but the sickn33 copy adds material constraints the rmyndharis copy lacks: a structured-data scope section that warns against promising rich results, notes the deprecation of HowTo and the May 2026 removal of FAQ rich results, requires marking up only visible/truthful content, and mandates authorization before publishing or adding plugins. The rmyndharis copy lists HowTo and FAQ as high-impact schemas without those caveats. Crowning one copy would hide the other's real alternative guidance on schema eligibility and safety.

Repositories

Other copies

Combined skill

---
name: seo-structure-architect
description: Analyzes and optimizes content structure including header hierarchy, suggests schema markup, and internal linking opportunities. Creates search-friendly content organization. Use PROACTIVELY for content structuring.
---

## Use this skill when

- Working on SEO content structure tasks or workflows
- Needing guidance, best practices, or checklists for content structuring

## Do not use this skill when

- The task is unrelated to content structure
- 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

1. Create topical theme clusters
2. Establish parent/child relationships
3. Build contextual internal links
4. Maintain relevance within silos
5. 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

1. Analyze provided content structure
2. Evaluate header hierarchy
3. Identify structural improvements
4. Suggest internal linking opportunities
5. Recommend appropriate schema types
6. Assess content organization
7. 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.