ai-seo
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,' or 'optimize for Claude/Gemini.' Use this whenever someone wants their content to be cited or surfaced by AI assistants and AI search engines. For traditional techn
npx skills add Infrasity-Labs/dev-gtm-claude-skills --skill ai-seo --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
What it does
The skill positions the agent as an expert in AI search optimization, focusing on getting content cited as a source in AI-generated answers across platforms like Google AI Overviews, ChatGPT, Perplexity, Claude, Gemini, and Copilot. It emphasizes structuring content for extractable passages, adding citations, and improving presence where AI looks.
How it works
- It defines the goal as helping users' content be cited by AI systems rather than solely ranked in traditional search.
- It outlines three pillars: Structure (extractable content blocks), Authority (citation-worthy references), and Presence (be discoverable by AI).
- It prescribes content-pattern blocks: definition blocks, step-by-step blocks, comparison tables, pro/cons blocks, FAQ blocks, and statistic blocks with sources.
- It recommends specific structural rules: direct lead for each section, 40–60 word passages, headings that match queries, tables for comparisons, numbered lists for procedures, and single-idea paragraphs.
- It discusses optimization for multiple AI platforms, noting differences in source selection and the importance of extractable structure for non-Google engines while maintaining standard quality for Google.
- It encourages auditing AI visibility (checking AI answers for key queries, analyzing citation patterns, assessing extractability, and verifying robots.txt access for various AI bots).
- It describes an optimization strategy centered on three pillars (Structure, Authority, Presence) and gives concrete patterns (definition, how-to, comparisons, FAQ, statistics) and best practices for machine-readable files and schema markup to aid AI agents.
When to use it
- Use when content should be cited or surfaced by AI assistants and AI search engines.
- Use when optimizing for AI Overviews, AI mode, and extraction by ChatGPT, Claude, Perplexity, Gemini, Copilot, etc.
- Triggered when the goal is to improve extractability, add authoritative sources, and ensure presence in AI-fed surfaces.
What it can touch
- It references content blocks, headings, and structured data patterns designed to be embedded in content pages.
- It recommends including schema markups: Article, HowTo, FAQPage, Product, ItemList, Review, AggregateRating, Organization.
- It calls for machine-readable files like
/pricing.md,/pricing.txt, and/llms.txt, plus mentions of llms.txt context usage to aid AI agents.
Caveats
- It notes Google’s stance that AI Overviews do not require special markup or files and that content should be written for people first, with normal structure.
- It advises that non-Google engines reward extractable structure and machine-readable files, but keep Google optimization in mind.
- It emphasizes avoiding content that harms AI visibility, such as keyword stuffing, and stresses keeping content up-to-date with freshness signals.
# AI SEO You are an expert in AI search optimization — the practice of making content discoverable, extractable, and citable by AI systems including Google AI Overviews, ChatGPT, Perplexity, Claude, Gemini, and Copilot. Your goal is to help users get their content cited as a source in AI-generated answers. ## Before Starting **Check for product marketing context first:** If `.agents/product-marketing.md` exists (or `.claude/product-marketing.md`, or the legacy `product-marketing-context.md` filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task. Gather this context (ask if not provided): ### 1. Current AI Visibility - Do you know if your brand appears in AI-generated answers today? - Have you checked ChatGPT, Perplexity, or Google AI Overviews for your key queries? - What queries matter most to your business? ### 2. Content & Domain - What type of content do you produce? (Blog, docs, comparisons, product pages) - What's your domain authority / traditional SEO strength? - Do you have existing structured data (schema markup)? ### 3. Goals - Get cited as a source in AI answers? - Appear in
- Before Starting
- 1. Current AI Visibility
- 2. Content & Domain
- 3. Goals
- 4. Competitive Landscape
- How AI Search Works
- The AI Search Landscape
- Key Difference from Traditional SEO
- Google's Official Stance vs. Multi-Platform Reality
- Query Fan-Out (Google AI Search)
- AI Visibility Audit
- Step 1: Check AI Answers for Your Key Queries
- Step 2: Analyze Citation Patterns
- Step 3: Content Extractability Check
What does the ai-seo skill do?
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,' or 'optimize for Claude/Gemini.' Use this whenever someone wants their content to be cited or surfaced by AI assistants and AI search engines. For traditional techn
How do I install it?
Run `npx skills add Infrasity-Labs/dev-gtm-claude-skills --skill ai-seo --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From Infrasity-Labs/dev-gtm-claude-skills, a repository with 97 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.
