seoagent

Topics in the source

• SEOAgent
• When to Use This Skill
• Workspace Model
• Workflow (5 phases)
• 1. Technical audit
• 2. Keyword strategy (hub-and-spoke)
• 3. Content briefs (page-type-aware)
• 4. Draft articles

A persistent, repo-local SEO workflow. Unlike one-off SEO prompts that lose their context the moment the conversation ends, every artifact here is written to a .seoagent/ directory in the repo — so audits, strategy, briefs, and drafts accumulate across sessions instead of resetting each time. Use this skill when the user wants to: Run a technical SEO audit of a site (meta tags, headings, internal links, schema, Core Web Vitals readiness, AI-search optimization) Build a keyword strategy with topic clusters and an internal-linking structure Write a content brief for a specific page or article Draft an SEO-optimized article with full metadata and JSON-LD Resume SEO work — read back prior audit findings, strategy, or the roadmap All work persists to .seoagent/ so it survives across sessions: Always read existing .seoagent/ files before acting, and write results back so the next session can build on them. Fetch the site's key pages and check each against the list below. Save findings to .seoagent/audit/latest.md as [ ] checkboxes the user can flip to [x] when fixed, each tagged critical | high | medium | low. Critical / high [ ] Indexability: no accidental noindex, no blocked paths in r

This is an excerpt. Refer to the complete source and its current requirements.