seo-brain

Decompose a compound request (multiple deliverables, skills, pillars, or approval gates) into spec + plan + result-check before any downstream skill runs.

Runs SEO Brain Autoresearch experiment loops for skills, fixtures, regressions, and keep/reject decisions.

Analyzes backlinks and referring domains using configured providers, with freshness and confidence notes.

Produces public SEO content briefings, drafts, reviews, and promotion checks with hard approval gates.

Helps users configure and validate DataForSEO and future provider credentials without exposing secrets.

Documents EEAT evidence, gaps, authorship, proof, and trust signals for SEO Brain project.

Finds verified contextual internal link opportunities with websearch and approval-ready paragraph edits.

Runs keyword research with DataForSEO when enabled and produces normalized keyword evidence for clusters and content.

Creates SEO-ready Next.js SSG website for SEO Brain project with default page types and Vercel-first conventions.

Sets up Payload CMS structures for SEO Brain project, including editorial collections, authors, media, redirects, and SEO fields.

Initializes SEO Brain project with the required folder layout, Wiki templates, status frontmatter, and log entry. Use when creating a new project.

Orchestrates SERP evidence, top-result comparison, heading/meta extraction, UX observations, and SEO improvement hypotheses.

Extracts and normalizes SERP snapshots with provider metadata, organic results, and SERP features.

Runs deterministic technical SEO audits by page type and reports evidence-backed findings.

Builds topic clusters from keyword evidence, user intent, business value, and information-completeness gaps.

Maintains SEO Brain project Wikis with source provenance, logs, linting, approval status, and Obsidian-compatible links.

When the user wants a rigorous iteration loop for an artifact, prompt, briefing, content structure, or SEO Brain skill. Also use for Karpathy-style experiment runs that need baseline scoring, explicit metrics, stop rules, and keep/reject decisions.

When the user wants backlink, referring-domain, anchor, link-quality, or competitor link-profile analysis for one target domain or URL.

When the user wants to brief, write, review, optimize, or publish public SEO content. Also use for article outlines, blog posts, landing-page copy, refreshes, and ranking-oriented editorial drafts.

When the user wants to configure, validate, or troubleshoot DataForSEO or another SEO data provider securely. Also use when provider credentials are missing before keyword, SERP, or SEO analysis work.

When the user wants to audit, strengthen, or prepare evidence for Experience, Expertise, Authoritativeness, and Trust. Also use before updating strategic E-E-A-T context in `project/wiki/eeat.md`.

When the user wants internal link opportunities, contextual link recommendations, anchor text improvements, or validation before applying internal links.

When the user wants keyword research, keyword expansion, search volume, CPC, competition, long-tail opportunities, or clustering inputs for a market. Also use before topic-cluster or content planning work that needs keyword evidence.

When the user wants to create, scaffold, or validate a Next.js static website for an SEO Brain project with SEO-ready pages and local preview.

When the user wants to decide whether to add Payload CMS to an SEO Brain site, or to configure Payload CMS after the fit decision is justified.

When the user wants to create, initialize, or prepare one SEO Brain project with the standard local project structure, initial Wiki, project metadata, and draft strategic pages.

When the user wants a keyword SERP analysis with competitor comparison, target page gaps, or player-score interpretation. Also use before topic cluster or content brief work that needs SERP evidence.

Load SEO Brain's canonical runtime context and route broad, ambiguous, or compound Agentic SEO requests through the right gates and downstream skills.

When the user wants to create, rewrite, evaluate, or improve an SEO Brain skill. Also use when planning a skill-loop run or converting a formal contract skill into a narrative self-sufficient skill.

When the user wants to create, port, fork, or review deterministic provider tools for SEO Brain. Also use when adding tool attribution, registry entries, or provider integration docs.

When the user wants to capture SERP evidence, search result snapshots, competitor URLs, or SERP features for specific keywords without doing SEO analysis.

MUST USE PROACTIVELY before executing a user request with two or more distinct deliverables, downstream skills, SEO Brain pillars, dependencies, or approval gates. Use for compound requests such as research plus Wiki, Wiki plus website, technical audit plus content plan, content plus site, or any bulleted/numbered request with separate outcomes. Do not use for a single clear task.

Friendly first-run alias that routes new SEO Brain users to the canonical seo-brain and project-init workflow without duplicating process rules.

When the user wants a deterministic technical SEO audit, page-template validation, JSON audit interpretation, or repair-priority report for a rendered page or site URL.

When the user wants an SEO topic cluster, topical authority map, pillar/support architecture, or content roadmap structure backed by keyword and SERP evidence. Also use when they ask to rerender or update an existing topic cluster while preserving human curation.

When the user wants to ingest sources, update the SEO Brain LLM Wiki, catalog evidence, reconcile project knowledge, or lint wiki pages for provenance and approval safety.

1 hook across 1 event