Agent skill · mblode
seo
Audits and fixes technical SEO, researches search demand, creates content briefs, and measures SEO/AEO performance. Use when asked to "audit SEO", "fix indexing", "improve AI visibility", "check keyword volume", "write an SEO brief", or "why did organic traffic drop". For Mintlify Agent Score, AFDocs, or Is Agentic reports use agent-ready. For writing the article use ghostwriter; for visual redesign use ui-design.
What it needs
About 4k tokens when loaded.
What this skill does
SEO IS: one entry point for search visibility: evidence-led audits, implementation, demand research, writer briefs, and performance measurement across search and answer engines. IS NOT: writing the article (ghostwriter), standalone marketing copy (copywriting), visual redesign (ui-design), tenant infrastructure (multi-tenant-architecture), or implementing AFDocs / Is Agentic / Is It Agent Ready scorecards (agent-ready). Fix SEO copy and markup when they are part of the requested implementation. Route the task Request Load Deliverable --- --- --- Audit a site, diagnose indexing, review a migration references/audit.md and references/validation-evidence.md Prioritized findings with URLs, observed evidence, impact, and correction Fix or implement SEO Audit references, then applicable implementation references below Code changes, scoped checks, and served-page evidence for the changed behavior Research demand, choose a target, brief a page references/research-protocol.md; references/brief-template.md for a brief Sourced demand table and decision, or a durable writer brief Explain traffic movement, measure AI visibility, monitor SEO references/monitoring.md Property-scoped diagnosis or configured monitoring with explicit data gaps For a combined request, reuse one property and URL inventory across modes. An audit request produces findings; a request to fix them proceeds through implementation and verification within the user's authorized scope. A research-only request does not require crawling every URL or changing code. Establish the evidence boundary Identify the exact public host, URL-prefix or domain property, production environment, project/subpath, audience, and business outcome. On a shared domain, filter each project's path separately. In analytics, verify hostname, path, conversion event and attribution window before interpreting a number. Discover connected tools and existing project bindings first. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills mblode/seo