agentic-seo

Routes ambiguous SEO requests through gated downstream skill chains.

49|7|Updated May 4, 2026
One-click install
npx skills add https://github.com/agencia-conversion/agentic-seo-skills --skill agentic-seo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agentic-seo
Source: https://github.com/agencia-conversion/agentic-seo-skills/tree/main/skills/agentic-seo
Command: npx skills add https://github.com/agencia-conversion/agentic-seo-skills --skill agentic-seo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents ambiguous SEO requests from turning into unfocused or unsupported work by routing them through evidence-aware gates and the correct downstream Agentic SEO skills.

Core Features & Use Cases

  • Request routing with explicit gates: classifies the request into the right pillars and stops when required prerequisites (e.g., DataForSEO evidence, voice/brain rules, review/content checks, or source separation) are missing.
  • Evidence-first execution planning: enforces separation of raw evidence, synthesis, drafts, artifacts, and report pages while recording decisions and bypasses with consequences.
  • User-appropriate output delivery: prioritizes the Web Companion report flow for substantive deliverables and uses local browser handoffs for decisions, approvals, previews, or sensitive inputs.

Quick Start

Use the agentic-seo skill at session start and ask for a complete SEO workflow, such as “Analyze our current SEO situation, plan content for the next cluster, and identify technical fixes for the site in Brazil,” and it will route you through the appropriate gated steps.

Frequently Asked Questions about agentic-seo

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I handle complex SEO requests that span multiple workflows?

Complex SEO requests are routed through evidence-aware gates that classify work into strategy, brain, technology, technical SEO, content, and data pillars, stopping execution when required prerequisites are missing. This gate-first routing prevents unfocused or unsupported work.

How do I separate raw SEO evidence from synthesized drafts?

You separate raw SEO evidence from synthesis by enforcing evidence-first execution planning, which strictly divides raw evidence, synthesis, drafts, artifacts, and report pages while recording decisions and bypasses with their consequences.

What happens when my technical SEO workflow is missing DataForSEO evidence?

When DataForSEO evidence or other prerequisites are missing, the agentic routing stops execution at the explicit gate to prevent unsupported work, requiring you to provide the necessary evidence before proceeding.

When should I use Web Companion reports instead of local browser handoffs?

Use the Web Companion report flow for substantive SEO deliverables and local browser handoffs for decisions, approvals, previews, or sensitive inputs, ensuring user-appropriate output delivery across the workflow.

How do I plan content strategy and technical fixes in a single session?

Start a session with a compound SEO request like analyzing current SEO, planning content clusters, and identifying technical fixes, and the workflow routing will classify and route you through the appropriate gated steps sequentially.