seo-structure-architect — Claude Code subagent
Analyzes header hierarchy, suggests Schema markup, and maps internal linking opportunities. Organizes content structure so search engines and readers both understand it.
/plugin marketplace add wshobson/agents
/plugin install seo-technical-optimization@claude-code-workflowsWhat seo-structure-architect does
The subagent audits your page structure: checks for a single H1, verifies H2–H6 placement, and flags logical flow issues. It recommends Schema.org markup (Article, FAQ, HowTo, BreadcrumbList) and builds an internal linking matrix to connect related content. Uses siloing strategy—creating topical clusters where pages link contextually, not arbitrarily.
Delivers a checklist: where to add subheadings, how to convert a list into a table for featured snippet potential, which paragraphs need splitting. Shows structure as a tree (H1 → H2 → H3) and outputs JSON-LD for search engines. Suggests plugin configs for WordPress (TOC and schema tools) or component setups for Astro and static generators.
Run it before publishing or restructuring: the subagent catches hierarchy issues that could bury your content in search results.
What it helps with
- build a header hierarchy that search engines understand
- identify internal linking opportunities across pages
- design a topical cluster structure (siloing strategy)
- choose and implement the right Schema markup
- optimize content layout for featured snippets
Example prompts for the agent
- Audit this section's structure and recommend a header hierarchy for SEO
- Where should I add internal links between these three pages?
- Generate Schema markup for our FAQ and suggest the header order for this page
How to install seo-structure-architect
1Plugin marketplace
/plugin marketplace add wshobson/agents/plugin install seo-technical-optimization@claude-code-workflows2Manually: put the files in place
.claude/agents/seo-structure-architect.mdFor all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention
Manually: put the files in place
.codex/agents/seo-structure-architect.tomlCodex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/
Manually: put the files in place
.cursor/agents/seo-structure-architect.mdCursor also reads .claude/agents/
Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean
Questions about seo-structure-architect
How do I install seo-structure-architect in Claude Code?
Run /plugin marketplace add wshobson/agents, then /plugin install seo-technical-optimization@claude-code-workflows, then load the config from .claude/agents/seo-structure-architect.md.
What does seo-structure-architect do?
It audits header hierarchy (H1–H6), recommends Schema markup, maps internal linking opportunities, and suggests how to organize content so search engines index it correctly.
Which platforms support this subagent?
Works with Claude Code, Codex, and Cursor. Each platform uses its own config location: .claude/agents/, .codex/agents/, or .cursor/agents/.
Source text
seo-structure-architect.md · MIT
--- 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. model: haiku --- 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 **High-Impact Schemas:** - 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.
© Seth Hobson · MIT · wshobson/agents