seo-aeo-keyword-research
Researches and prioritises SEO keywords with AEO question queries, difficulty tiers, cannibalization checks, and a content map. Activate when the user wants to find keywords, research search terms, or build a keyword strategy.
What this skill does
# SEO-AEO Keyword Research ## Overview Identifies high-value SEO keywords and AEO question-based queries for a topic. Produces keyword tiers (easy wins to long-term goals), search intent classification, cannibalization checks, and a content production map — all from a single topic input. Part of the [SEO-AEO Engine](https://github.com/mrprewsh/seo-aeo-engine) — an open-source AI-powered content growth system. ## When to Use This Skill - Use when you need to build a keyword strategy for a new topic or niche - Use when you want to find AEO question queries for AI engine citation - Use when you need to prioritise which keywords to target first - Use when you want to check for keyword cannibalization before writing content ## How It Works ### Step 1: Extract Seed Keywords Identify 3–5 core terms that anchor the topic's search territory. Go beyond the obvious head term to include adjacent terms the audience actually uses. ### Step 2: Expand Into Tiers Sort all keywords into three tiers: - **Tier 1** — Low-to-moderate difficulty. Target first. - **Tier 2** — Medium difficulty. Build toward after Tier 1 content is live. - **Tier 3** — High difficulty. Long-term goals only. ### Step 3: Generate AEO Keywords Produce question-based keywords that AI engines surface in direct answers and People Also Ask boxes. For each AEO keyword, specify the answer format to use (definition sentence, numbered steps, comparison table, direct number). ### Step 4: Run Cannibalization Check Flag any two keywords similar enough to split traffic if targeted on separate pages. Recommend which page should own which term. ### Step 5: Build Content Map Recommend content type and production order for all Tier 1 and Tier 2 keywords. ## Examples ### Example 1: SaaS Product Input: topic = "remote project management software" audience = "engineering managers and startup founders" goal = "convert" Output: Tier 1 Keywords: "remote project management software" | Medium volume | Difficulty: 38 "project management tool remote teams" | Low volume | Difficulty: 29 AEO Keywords: "What is the best project management software for remote teams?" → Answer format: Comparison table "How does remote project management work?" → Answer format: Numbered steps Content Map: Landing page → "remote project management software" Pillar blog → "complete guide to remote project management" Cluster article → "how to manage remote engineering teams" ### Example 2: Fintech App Input: topic = "automated budgeting app" audience = "millennials managing personal finances" goal = "all" Output: Tier 1 Keywords: "automated budgeting app" | Medium volume | Difficulty: 33 "automatic savings app" | Low volume | Difficulty: 24 AEO Keywords: "What is the best budgeting app for millennials?" → Answer format: Comparison table "How does automated budgeting work?" → Answer format: Numbered steps ## Best Practices - ✅ **Do:** Target Tier 1 keywords first — build authority before going after competitive terms - ✅ **Do:** Use AEO keywords in FAQ sections and definition blocks for AI engine citation - ✅ **Do:** Validate estimated volume and difficulty with a live tool (Ahrefs, SEMrush) before committing - ❌ **Don't:** Target two keywords on the same page if cannibalization is flagged - ❌ **Don't:** Use volume as the only prioritisation signal — difficulty and intent matter more ## Common Pitfalls - **Problem:** High-volume keyword chosen but impossible to rank for early on **Solution:** Always cross-check volume with difficulty. Tier 1 should have difficulty under 45. - **Problem:** AEO keywords ignored in favour of traditional search terms **Solution:** AEO keywords drive AI engine citation — include at least 5 in every research run. ## Related Skills - `@seo-aeo-content-cluster` — uses keyword research output to build topic cluster - `@seo-aeo-landing-page-writer` — consumes primary keyword to generate landing page - `@seo-aeo-blog-writer` — uses secondary keywords for cluster article targeting ## Additional Resources - [SEO-AEO Engine Repository](https://github.com/mrprewsh/seo-aeo-engine) - [Full Keyword Research SKILL.md](https://github.com/mrprewsh/seo-aeo-engine/blob/main/.agent/skills/keyword-research/SKILL.md) ## 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.
Related in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".