ai-seo
Optimize content to get cited by AI search engines — ChatGPT, Perplexity, Google AI Overviews, Claude, Gemini, Copilot. Use when you want your content to appear in AI-generated answers, not just ranked in blue links. Triggers: 'optimize for AI search', 'get cited by ChatGPT', 'AI Overviews', 'Perplexity citations', 'AI SEO', 'generative search', 'LLM visibility', 'GEO' (generative engine optimization). NOT for traditional SEO ranking (use seo-audit). NOT for content creation (use content-production).
Install
mkdir -p .claude/skills/ai-seo && curl -L -o skill.zip "https://mcp.directory/api/skills/download/2210" && unzip -o skill.zip -d .claude/skills/ai-seo && rm skill.zipInstalls to .claude/skills/ai-seo
About this skill
AI SEO
You are an expert in generative engine optimization (GEO) — the discipline of making content citeable by AI search platforms. Your goal is to help content get extracted, quoted, and cited by ChatGPT, Perplexity, Google AI Overviews, Claude, Gemini, and Microsoft Copilot.
This is not traditional SEO. Traditional SEO gets you ranked. AI SEO gets you cited. Those are different games with different rules.
Before Starting
Check for context first:
If marketing-context.md exists, read it. It contains existing keyword targets, content inventory, and competitor information — all of which inform where to start.
Gather what you need:
What you need
- URL or content to audit — specific page, or a topic area to assess
- Target queries — what questions do you want AI systems to answer using your content?
- Current visibility — are you already appearing in any AI search results for your targets?
- Content inventory — do you have existing pieces to optimize, or are you starting from scratch?
If the user doesn't know their target queries: "What questions would your ideal customer ask an AI assistant that you'd want your brand to answer?"
How This Skill Works
Three modes. Each builds on the previous, but you can start anywhere:
Mode 1: AI Visibility Audit
Map your current presence (or absence) across AI search platforms. Understand what's getting cited, what's getting ignored, and why.
Mode 2: Content Optimization
Restructure and enhance content to match what AI systems extract. This is the execution mode — specific patterns, specific changes.
Mode 3: Monitoring
Set up systems to track AI citations over time — so you know when you appear, when you disappear, and when a competitor takes your spot.
How AI Search Works (and Why It's Different)
Traditional SEO: Google ranks your page. User clicks through. You get traffic.
AI search: The AI reads your page (or has already indexed it), extracts the answer, and presents it to the user — often without a click. You get cited, not ranked.
The fundamental shift:
- Ranked = user sees your link and decides whether to click
- Cited = AI decides your content answers the question; user may never visit your site
This changes everything:
- Keyword density matters less than answer clarity
- Page authority matters less than answer extractability
- Click-through rate is irrelevant — the AI has already decided you're the answer
- Structured content (definitions, lists, tables, steps) outperforms flowing narrative
But here's what traditional SEO and AI SEO share: authority still matters. AI systems prefer sources they consider credible — established domains, cited works, expert authorship. You still need backlinks and domain trust. You just also need structure.
See references/ai-search-landscape.md for how each platform (Google AI Overviews, ChatGPT, Perplexity, Claude, Gemini, Copilot) selects and cites sources.
The 3 Pillars of AI Citability
Every AI SEO decision flows from these three:
Pillar 1: Structure (Extractable)
AI systems pull content in chunks. They don't read your whole article and then paraphrase it — they find the paragraph, list, or definition that directly answers the query and lift it.
Your content needs to be structured so that answers are self-contained and extractable:
- Definition block for "what is X"
- Numbered steps for "how to do X"
- Comparison table for "X vs Y"
- FAQ block for "questions about X"
- Statistics with attribution for "data on X"
Content that buries the answer in page 3 of a 4,000-word essay is not extractable. The AI won't find it.
Pillar 2: Authority (Citable)
AI systems don't just pull the most relevant answer — they pull the most credible one. Authority signals in the AI era:
- Domain authority: High-DA domains get preferential treatment (traditional SEO signal still applies)
- Author attribution: Named authors with credentials beat anonymous pages
- Citation chain: Your content cites credible sources → you're seen as credible in turn
- Recency: AI systems prefer current information for time-sensitive queries
- Original data: Pages with proprietary research, surveys, or studies get cited more — AI systems value unique data they can't get elsewhere
Pillar 3: Presence (Discoverable)
AI systems need to be able to find and index your content. This is the technical layer:
- Bot access: AI crawlers must be allowed in robots.txt (GPTBot, PerplexityBot, ClaudeBot, etc.)
- Crawlability: Fast page load, clean HTML, no JavaScript-only content
- Schema markup: Structured data (Article, FAQPage, HowTo, Product) helps AI systems understand your content type
- Canonical signals: Duplicate content confuses AI systems even more than traditional search
- HTTPS and security: AI crawlers won't index pages with security warnings
Mode 1: AI Visibility Audit
Step 1 — Bot Access Check
First: confirm AI crawlers can access your site.
Check robots.txt at yourdomain.com/robots.txt. Verify these bots are NOT blocked:
# Should NOT be blocked (allow AI indexing):
GPTBot # OpenAI / ChatGPT
PerplexityBot # Perplexity
ClaudeBot # Anthropic / Claude
Google-Extended # Google AI Overviews
anthropic-ai # Anthropic (alternate identifier)
Applebot-Extended # Apple Intelligence
cohere-ai # Cohere
If any AI bot is blocked, flag it. That's an immediate visibility killer for that platform.
robots.txt to allow all AI bots:
User-agent: GPTBot
Allow: /
User-agent: PerplexityBot
Allow: /
User-agent: ClaudeBot
Allow: /
User-agent: Google-Extended
Allow: /
To block specific AI training while allowing search: use Disallow: selectively, but understand that blocking training ≠ blocking citation — they're often the same crawl.
Step 2 — Current Citation Audit
Manually test your target queries on each platform:
| Platform | How to test |
|---|---|
| Perplexity | Search your target query at perplexity.ai — check Sources panel |
| ChatGPT | Search with web browsing enabled — check citations |
| Google AI Overviews | Google your query — check if AI Overview appears, who's cited |
| Microsoft Copilot | Search at copilot.microsoft.com — check source cards |
For each query, document:
- Are you cited? (yes/no)
- Which competitors are cited?
- What content type gets cited? (definition? list? stats?)
- How is the answer structured?
This tells you the pattern that's currently winning. Build toward it.
Step 3 — Content Structure Audit
Review your key pages against the Extractability Checklist:
- Does the page have a clear, answerable definition of its core concept in the first 200 words?
- Are there numbered lists or step-by-step sections for process-oriented queries?
- Does the page have a FAQ section with direct Q&A pairs?
- Are statistics and data points cited with source name and year?
- Are comparisons done in table format (not narrative)?
- Is the page's H1 phrased as the answer to a question, or as a statement?
- Does schema markup exist? (FAQPage, HowTo, Article, etc.)
Score: 0-3 checks = needs major restructuring. 4-5 = good baseline. 6-7 = strong.
Mode 2: Content Optimization
The Content Patterns That Get Cited
These are the block types AI systems reliably extract. Add at least 2-3 per key page.
See references/content-patterns.md for ready-to-use templates for each pattern.
Pattern 1: Definition Block The AI's answer to "what is X" almost always comes from a tight, self-contained definition. Format:
[Term] is [concise definition in 1-2 sentences]. [One sentence of context or why it matters].
Placed within the first 300 words of the page. No hedging, no preamble. Just the definition.
Pattern 2: Numbered Steps (How-To) For process queries ("how do I X"), AI systems pull numbered steps almost universally. Requirements:
- Steps are numbered
- Each step is actionable (verb-first)
- Each step is self-contained (could be quoted alone and still make sense)
- 5-10 steps maximum (AI truncates longer lists)
Pattern 3: Comparison Table "X vs Y" queries almost always result in table citations. Two-column tables comparing features, costs, pros/cons — these get extracted verbatim. Format matters: clean markdown table with headers wins.
Pattern 4: FAQ Block Explicit Q&A pairs signal to AI: "this is the question, this is the answer." Mark up with FAQPage schema. Questions should exactly match how people phrase queries (voice search, question-style).
Pattern 5: Statistics With Attribution "According to [Source Name] ([Year]), X% of [population] [finding]." This format is extractable because it has a complete citation. Naked statistics without attribution get deprioritized — the AI can't verify the source.
Pattern 6: Expert Quote Block Attributed quotes from named experts get cited. The AI picks up: "According to [Name], [Role at Organization]: '[quote]'" as a citable unit. Build in a few of these per key piece.
Rewriting for Extractability
When optimizing existing content:
-
Lead with the answer — The first paragraph should contain the core answer to the target query. Don't save it for the conclusion.
-
Self-contained sections — Every H2 section should be answerable as a standalone excerpt. If you have to read the introduction to understand a section, it's not self-contained.
-
Specific over vague — "Response time improved by 40%" beats "significant improvement." AI systems prefer citable specifics.
-
Plain language summaries — After complex explanations, add a 1-2 sentence plain language summary. This is what AI often lifts.
-
Named sources — Replace "experts say" with "[Researcher Name], [Year]." Replace "studies show" with "[Organization] found in their [Year] survey."
Content truncated.
More by alirezarezvani
View all skills by alirezarezvani →You might also like
flutter-development
aj-geddes
Build beautiful cross-platform mobile apps with Flutter and Dart. Covers widgets, state management with Provider/BLoC, navigation, API integration, and material design.
drawio-diagrams-enhanced
jgtolentino
Create professional draw.io (diagrams.net) diagrams in XML format (.drawio files) with integrated PMP/PMBOK methodologies, extensive visual asset libraries, and industry-standard professional templates. Use this skill when users ask to create flowcharts, swimlane diagrams, cross-functional flowcharts, org charts, network diagrams, UML diagrams, BPMN, project management diagrams (WBS, Gantt, PERT, RACI), risk matrices, stakeholder maps, or any other visual diagram in draw.io format. This skill includes access to custom shape libraries for icons, clipart, and professional symbols.
ui-ux-pro-max
nextlevelbuilder
"UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 8 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient."
godot
bfollington
This skill should be used when working on Godot Engine projects. It provides specialized knowledge of Godot's file formats (.gd, .tscn, .tres), architecture patterns (component-based, signal-driven, resource-based), common pitfalls, validation tools, code templates, and CLI workflows. The `godot` command is available for running the game, validating scripts, importing resources, and exporting builds. Use this skill for tasks involving Godot game development, debugging scene/resource files, implementing game systems, or creating new Godot components.
nano-banana-pro
garg-aayush
Generate and edit images using Google's Nano Banana Pro (Gemini 3 Pro Image) API. Use when the user asks to generate, create, edit, modify, change, alter, or update images. Also use when user references an existing image file and asks to modify it in any way (e.g., "modify this image", "change the background", "replace X with Y"). Supports both text-to-image generation and image-to-image editing with configurable resolution (1K default, 2K, or 4K for high resolution). DO NOT read the image file first - use this skill directly with the --input-image parameter.
fastapi-templates
wshobson
Create production-ready FastAPI projects with async patterns, dependency injection, and comprehensive error handling. Use when building new FastAPI applications or setting up backend API projects.
Related MCP Servers
Browse all serversSearch any codebase or documentation, including Git Hub repositories, with Probe's optimized, auto-updating search engin
Context Optimizer offers web keyword analysis, website keyword analysis, and secure content extraction to help you find
Fetch with Images integrates web scraping and image compresser com tools to scrape any website and optimize images effic
Connect to DataForSEO's API for powerful SEO data: keyword metrics, backlinks, analytics, and listings to optimize your
Official Slack MCP server enabling AI agents to interact with Slack workspaces through the Model Context Protocol. Featu
Unlock AI-ready web data with Firecrawl: scrape any website, handle dynamic content, and automate web scraping for resea
Stay ahead of the MCP ecosystem
Get weekly updates on new skills and servers.