seo-structure-architect
Analyzes and optimizes content structure including header hierarchy, suggests schema markup, and internal linking opportunities. Creates search-friendly content organization.
- License 许可
- MIT
- 最近更新
- 2026-11-10
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- seo-structure-architect
- risk
- unknown
- source
- community
- date_added
- 2026-02-27
- description
- Analyzes and optimizes content structure including header hierarchy, suggests schema markup, and internal linking opportunities. Creates search-friendly content organization.
03 SKILL.md 正文
Use 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.
- If detailed examples are required, open
resources/implementation-playbook.md.
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
High-Impact Schemas:
- 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.
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.
04 同仓库更多 Skills
vercel-sandbox
Run agent-browser + Chrome inside Vercel Sandbox microVMs for browser automation from any Vercel-deployed app. Use when the user needs browser automation in a Vercel app (Next.js, SvelteKit, Nuxt, Remix, Astro, etc.), wants to run headless Chrome without binary size limits, needs persistent browser sessions across commands, or wants ephemeral isolated browser environments. Triggers include "Vercel Sandbox browser", "microVM Chrome", "agent-browser in sandbox", "browser automation on Vercel", or any task requiring Chrome in a Vercel Sandbox.
slack
Interact with Slack workspaces using browser automation. Use when the user needs to check unread channels, navigate Slack, send messages, extract data, find information, search conversations, or automate any Slack task. Triggers include "check my Slack", "what channels have unreads", "send a message to", "search Slack for", "extract from Slack", "find who said", or any task requiring programmatic Slack interaction.
electron
Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include "automate Slack app", "control VS Code", "interact with Discord app", "test this Electron app", "connect to desktop app", or any task requiring automation of a native Electron application.
dogfood
Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to "dogfood", "QA", "exploratory test", "find issues", "bug hunt", "test this app/site/platform", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.
agent-browser
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.
shadcn
Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for "shadcn init", "create an app with --preset", "switch to --preset", and for building a design system or applying a DESIGN.md or brand spec to shadcn/ui.