Best for
- Use when someone wants visibility in AI-generated answers, says 'AI SEO', 'AI search', 'LLM optimization', 'ChatGPT ranking', 'Perplexity citations', 'AI Overviews', or wants their content cited by AI assistants.
MoizIbnYousaf/marketing-cli/skills/ai-seo/SKILL.md
Optimize content for AI search engines — ChatGPT, Perplexity, Claude, Gemini, and AI Overviews. Covers entity optimization, structured data, citation-worthy formatting, and platform-specific strategies. Use when someone wants visibility in AI-generated answers, says 'AI SEO', 'AI search', 'LLM optimization', 'ChatGPT ranking', 'Perplexity citations', 'AI Overviews', or wants their content cited by AI assistants. The new SEO frontier — if you're only optimizing for Google, you're already behind.
Decision brief
You optimize content so AI search engines — ChatGPT, Perplexity, Claude, Gemini, and Google AI Overviews — cite, reference, and recommend it. Traditional SEO gets you on page one of Google. AI SEO gets you into the AI's answer.
Compatibility matrix
| Platform | Status | Evidence | What to check |
|---|---|---|---|
| Codex | Not declared | No explicit evidence | Portability before use |
| Claude Code | Not declared | No explicit evidence | Portability before use |
| Cursor | Not declared | No explicit evidence | Portability before use |
| Gemini CLI | Not declared | No explicit evidence | Portability before use |
Installation
The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.
npx skills add https://github.com/MoizIbnYousaf/marketing-cli --skill "skills/ai-seo"Inspect the Agent Skill "ai-seo" from https://github.com/MoizIbnYousaf/marketing-cli/blob/f12fbcbe4929584697b309b9096c9427b0cfce8e/skills/ai-seo/SKILL.md at commit f12fbcbe4929584697b309b9096c9427b0cfce8e. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.
Workflow
Use available tools to test AI visibility. Not all engines will be testable — audit what you can, note what you can't.
AI engines understand entities (people, brands, products, concepts), not just keywords. You need to establish your entity clearly.
AI engines prefer content structured as clear, authoritative answers. For every target query:
Every page should have at minimum: - Organization schema (site-wide) - Article + Person schema (all content pages) - FAQPage schema (any page with Q&A content) - BreadcrumbList schema (all pages)
Every page should have at minimum: - Organization schema (site-wide) - Article + Person schema (all content pages) - FAQPage schema (any page with Q&A content) - BreadcrumbList schema (all pages)
Permission review
The documentation asks the agent to read local files, directories, or repositories.
Read `brand/` directory: load `voice-profile.md`, `keyword-plan.md`, `positioning.md`, `competitors.md` if present.The documentation includes network, browsing, or remote request actions.
Search for "[brand] + [topic]" to assess web presence that AI engines indexEvidence record
| Signal | Value | Evidence type | Meaning |
|---|---|---|---|
| Quality score | 87/100 | Computed | Documentation, specificity, maintenance, and trust rules |
| Repository stars | 27 | Source | Repository attention, not individual Skill quality |
| Compatibility | 0 platforms | Source | Declared in the catalog source record |
| Usage guide | automated source guide | Editorial | Generated or reviewed according to the visible evidence level |
Pinned source
You optimize content so AI search engines — ChatGPT, Perplexity, Claude, Gemini, and Google AI Overviews — cite, reference, and recommend it. Traditional SEO gets you on page one of Google. AI SEO gets you into the AI's answer.
This is a different game. AI engines don't rank pages — they synthesize answers from sources they trust. Your job is to become a source they trust and cite.
brand/ directory: load voice-profile.md, keyword-plan.md, positioning.md, competitors.md if present.Prefer OpenSEO get_ranked_keywords / get_serp_results (and AI-search MCP tools when exposed) when configured; otherwise crawl/Exa with ranking data unknown. Full contract: skills/openseo/references/backend-contract.md.
Brand context loaded:
├── Voice Profile ✓/✗
├── Keyword Plan ✓/✗
├── Positioning ✓/✗
└── Competitors ✓/✗
Traditional search: User types query → Google ranks pages → user clicks a link AI search: User asks question → AI reads sources → AI synthesizes answer → cites sources inline
What this means for you:
The single highest-leverage page format for AI-citation is the long-form playbook — 2,500+ word pillar content with Article + HowTo JSON-LD, named author, dateModified, and step-based structure. AI engines (ChatGPT search, Perplexity, Claude, Gemini, Google AI Overviews) preferentially cite playbook-pattern pages over short blog posts because:
| Why playbooks win citations | Detail |
|---|---|
| Step-based structure | HowTo schema makes the answer machine-extractable; AI engines lift the steps verbatim |
| Named author + entity | Author bio with sameAs links to social profiles compounds the entity graph |
| Concrete numbers | Specific stats ("73% of B2B SaaS under 50 employees post less than once a week") get cited; vague claims ("most companies struggle") don't |
| Counter-arguments inline | AI engines reward sources that show "thinking" — playbooks with "don't do X because Y" sections demonstrate authority |
| dateModified discipline | Recent modification dates signal freshness; AI engines deprecate stale sources |
Tie-in with seo-machine: if you're running a programmatic sprint, ship playbook pages as Phase 4+ (after alternatives/compare/use-case ship first for conversion). seo-machine Pattern E is the playbook pipeline — pair it with this skill's entity-optimization and FAQ-formatting recipes to maximize citation surface area.
Avoid for AI-citation: generic blog posts with no schema, content without a named author, listicles without a clear "do this not that" stance, pages that hedge every claim with "it depends." These rank but don't get cited.
Use available tools to test AI visibility. Not all engines will be testable — audit what you can, note what you can't.
With browser tool available:
With web search/Exa MCP only:
Without browser or web search:
| Query | ChatGPT | Perplexity | AI Overview | Claude | Status |
|---|---|---|---|---|---|
| [query 1] | Not cited | Source #3 | Not included | Mentioned | Partial |
| [query 2] | Recommended | Source #1 | Featured | Named | Strong |
| [query 3] | Not mentioned | Not found | Not included | Not mentioned | Absent |
For each "Absent" or "Partial" query, create an optimization plan.
AI engines understand entities (people, brands, products, concepts), not just keywords. You need to establish your entity clearly.
Ensure these exist and are consistent across the web:
| Signal | Action |
|---|---|
| Consistent naming | Use the exact same brand name everywhere — no variations |
| Co-occurrence | Get mentioned alongside known entities in your space |
| Structured data | Organization + Person + Product schema on every relevant page |
| Backlinks from authorities | Citations from sites AI engines already trust |
| Cross-platform presence | Same entity info on LinkedIn, Twitter, GitHub, Crunchbase |
AI engines prefer content structured as clear, authoritative answers. For every target query:
## [Question as H2]
[Direct answer in 1-2 sentences — this is what gets cited]
[Supporting detail, evidence, examples in 2-4 paragraphs]
[Data or specific numbers that add credibility]
This pattern works because:
Structure content to match how people ask AI engines questions:
Identify conversational queries:
For each query, create a section that:
Add FAQ sections with structured data to every key page:
## Frequently Asked Questions
### [Exact question someone would ask an AI]
[Direct, authoritative answer. 2-4 sentences. Include a specific fact or number.]
### [Next question]
[Direct answer.]
Add FAQPage schema markup to every FAQ section.
| Schema | Purpose | AI Engine Benefit |
|---|---|---|
| Organization | Establish entity | All engines — entity recognition |
| Person (authors) | Author authority | Perplexity, Google AI — source credibility |
| Article | Content metadata | All engines — content classification |
| FAQPage | Q&A content | Google AI Overviews — direct extraction |
| HowTo | Process content | Google AI Overviews — step extraction |
| Product | Product info | ChatGPT, Perplexity — recommendation queries |
| Review | Credibility signal | All engines — trust signal |
Every page should have at minimum:
Organization schema (site-wide)Article + Person schema (all content pages)FAQPage schema (any page with Q&A content)BreadcrumbList schema (all pages)AI engines are more likely to cite content that is easy to parse and extract from.
| Trust Signal | How to Implement |
|---|---|
| Author expertise | Author page with credentials, experience, publications |
| Original research | Proprietary data, surveys, case studies |
| External citations | Cite reputable sources, link to primary research |
| Freshness | Regular updates, current year stats, "last updated" dates |
| Depth | Comprehensive coverage that other sources lack |
| Specificity | Exact numbers, dates, examples over vague claims |
| Consistency | Same facts across your site, no contradictions |
| Month | Query | Engine | Status | Action Taken | Result |
|-------|-------|--------|--------|-------------|--------|
| Mar 2026 | "best X for Y" | Perplexity | Source #5 | Added comparison table | TBD |
| Mar 2026 | "how to Z" | ChatGPT | Not cited | Created definitive answer | TBD |
| Traditional SEO | AI SEO |
|---|---|
| Optimize for keywords | Optimize for questions and entities |
| Compete for page 1 ranking | Compete to be a cited source |
| Keyword density matters | Answer clarity matters |
| Backlinks drive authority | Being mentioned across trusted sources drives authority |
| Meta tags for CTR | Structured data for extraction |
| Content length signals depth | Answer directness signals usefulness |
| One-time optimization | Continuous monitoring across multiple engines |
marketing/seo/
├── ai-seo-audit.md # AI visibility audit results
├── ai-seo-content-plan.md # Priority queries + optimization plan
└── ai-seo-tracking.md # Monthly tracking sheet
---
title: "AI SEO Visibility Audit"
date_created: "{YYYY-MM-DD}"
last_updated: "{YYYY-MM-DD}"
queries_tested: {number}
engines_tested: ["Perplexity", "ChatGPT", "Google AI Overviews"]
overall_status: "strong / partial / absent"
priority_actions: {number}
---
---
title: "AI SEO Content Optimization Plan"
date_created: "{YYYY-MM-DD}"
priority_queries: {number}
content_to_create: {number}
content_to_optimize: {number}
---
After completing, suggest:
/seo-audit — ensure traditional SEO foundations support AI visibility/seo-content — create new content optimized for AI citation/brand-voice — consistent authoritative voice increases citation likelihood/keyword-research — identify which queries are AI-dominated in your spaceAlternatives
coreyhaines31/marketingskills
When the user wants to optimize content for AI search engines, get cited by LLMs, or appear in AI-generated answers. Also use when the user mentions 'AI SEO,' 'AEO,' 'GEO,' 'LLMO,' 'answer engine optimization,' 'generative engine optimization,' 'LLM optimization,' 'AI Overviews,' 'optimize for ChatGPT,' 'optimize for Perplexity,' 'AI citations,' 'AI visibility,' 'zero-click search,' 'how do I show up in AI answers,' 'LLM mentions,' 'optimize for Claude/Gemini,' 'llms.txt,' 'OKF,' 'Open Knowledge
MoizIbnYousaf/marketing-cli
When the user wants to audit, review, or diagnose SEO issues, plan site architecture, or implement schema markup. Use when someone says 'SEO audit', 'technical SEO', 'site architecture', 'schema markup', 'internal linking', 'why isn't my site ranking', 'site health check', 'crawl issues', 'fix my SEO', 'my traffic dropped', 'rankings fell', or 'site not ranking'. Also trigger when someone wants to plan URL structure, design navigation, add structured data, or review any website for search perfor
coreyhaines31/marketingskills
When the user wants to figure out which marketing actually drives conversions and revenue, choose or interpret an attribution model, or reconcile conflicting numbers across tools. Also use when the user mentions "attribution," "attribution model," "first-touch vs last-touch," "multi-touch," "which channel drives revenue," "what's my real CAC," "my dashboards disagree," "Google/Meta says X but GA says Y," "media mix model," "MMM," "incrementality," "geo lift," "holdout test," "how did you hear ab
coreyhaines31/marketingskills
When the user wants to submit their product to startup, SaaS, AI, agent, MCP, no-code, or review directories for backlinks, domain rating, and discovery. Also use when the user mentions "directory submissions," "submit to directories," "backlinks from directories," "list my product," "submit to Product Hunt," "BetaList," "TAAFT," "Futurepedia," "G2 listing," "Capterra listing," "AlternativeTo," "SaaSHub," "AI directories," "MCP registry," "agent directory," "dofollow backlinks," "launch director