Agent skill

AI SEO

by Nexus-JPF in Nexus-JPF/note-companion

When the user wants to optimize content for AI search engines, get cited by LLMs, or appear in AI-generated answers.

MITAuto-check passedMarketing & SEO

Install AI SEO

skills CLI
$ npx skills add Nexus-JPF/note-companion --skill ai-seo -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install Nexus-JPF/note-companion ai-seo --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/Nexus-JPF/note-companion.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/ai-seo .claude/skills/ai-seo && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
ai-seo
GitHub stars
870
Used in
5 other repos
Token cost
~6.7k tokens
SKILL.md length
3,291 words
Files
7 (incl. references)
Skills in repo
18
Repo updated
First seen
Licence
MIT

At a glance

When the user wants to optimize content for AI search engines, get cited by LLMs, or appear in AI-generated answers.

  • Works in 8 steps: Current AI Visibility → Content & Domain → Goals → …
  • Wants to optimize content for AI search engines
  • SKILL.md covers Before Starting, How AI Search Works, AI Visibility Audit and Optimization Strategy, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

AI SEO is an agent skill from Nexus-JPF/note-companion. 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 Format,'…

Its SKILL.md is about 6.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 8 other files, including reference files (for example `evals/evals.json`, `references/citations-vs-recommendations.md` and `references/content-patterns.md`).

It sits in Marketing & SEO, covering AI search optimization. It works with OpenAI and Perplexity. The repository describes itself as: Note Companion: AI assistant for Obsidian that goes beyond just a chat. (prev File Organizer 2000). The licence is MIT.

When your agent uses it

  • Wants to optimize content for AI search engines
  • Get cited by LLMs
  • Appear in AI-generated answers
  • The user mentions AI SEO

Example prompts

  • “AI SEO,”
  • “answer engine optimization,”
  • “generative engine optimization,”
  • “/ai-seo”

Workflow steps

8 steps, taken from the step headings in SKILL.md.

  1. Current AI Visibility
  2. Content & Domain
  3. Goals
  4. Competitive Landscape
  5. Check AI Answers for Your Key Queries
  6. Analyze Citation Patterns
  7. Content Extractability Check
  8. AI Bot Access Check

What it can do on your machine

Read from SKILL.md and the folder at commit 9cad635. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • developers.google.com
    • llmstxt.org
    • cloud.google.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

AI SEO loads about 6.7k tokens when it runs, and up to ~17k if it reads all its reference files. Until then it costs about 196 tokens; SKILL.md has 3,291 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~196
When it runs · the whole SKILL.md, loaded when a task matches
~6.7k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~17k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Nexus-JPF/note-companion at commit 9cad635, republished under its MIT licence (© Nexus-JPF). 3,291 words, ~6,729 tokens.

Download SKILL.mdSave it as .claude/skills/ai-seo/SKILL.md (or your agent's skills folder). This skill also uses 6 other files; get the full folder from GitHub.
name
ai-seo
description
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 Format,' 'knowledge bundle,' or 'agent-readable site.' Use this whenever someone wants their content to be cited or surfaced by AI assistants and AI search engines. For traditional technical and on-page SEO audits, see seo-audit. For structured data implementation, see schema.
metadata.version
2.2.0

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 Google AI Overviews for specific queries?
  • Compete with specific brands already getting cited?
  • Optimize existing content or create new AI-optimized content?
4. Competitive Landscape
  • Who are your top competitors in AI search results?
  • Are they being cited where you're not?

How AI Search Works

The AI Search Landscape
PlatformHow It WorksSource Selection
Google AI OverviewsSummarizes top-ranking pagesStrong correlation with traditional rankings
ChatGPT (with search)Searches web, cites sourcesDraws from wider range, not just top-ranked
PerplexityAlways cites sources with linksFavors authoritative, recent, well-structured content
GeminiGoogle's AI assistantPulls from Google index + Knowledge Graph
CopilotBing-powered AI searchBing index + authoritative sources
ClaudeBrave Search (when enabled)Training data + Brave search results

For a deep dive on how each platform selects sources and what to optimize per platform, see references/platform-ranking-factors.md.

Key Difference from Traditional SEO

Traditional SEO gets you ranked. AI SEO gets you cited.

In traditional search, you need to rank on page 1. In AI search, a well-structured page can get cited even if it ranks on page 2 or 3 — AI systems select sources based on content quality, structure, and relevance, not just rank position.

Critical stats:

  • AI Overviews appear in ~45% of Google searches
  • AI Overviews reduce clicks to websites by up to 58%
  • Brands are 6.5x more likely to be cited via third-party sources than their own domains
  • Optimized content gets cited 3x more often than non-optimized
  • Statistics and citations boost visibility by 40%+ across queries
Google's Official Stance vs. Multi-Platform Reality

This is important to read once before doing anything else.

Google's position (AI features optimization guide):

"The best practices for SEO continue to be relevant because our generative AI features on Google Search are rooted in our core Search ranking and quality systems."

Google explicitly says:

  • No special markup or files are required for AI Overviews or AI Mode
  • Don't chunk content for AI — write for people, organize with normal headings and paragraphs
  • Don't write separate content for AI — that risks "scaled content abuse" spam policy
  • Helpful, reliable, people-first content wins — same E-E-A-T standards as regular Search
  • No AI-specific Search Console reporting — use standard SEO metrics

Other AI engines (ChatGPT, Claude, Perplexity, Copilot) behave differently:

  • They actively reward extractable structure — passages, FAQs, comparison tables, definition blocks
  • They parse llms.txt, structured pricing pages, and machine-readable files when present
  • They cite third-party sources (Reddit, Wikipedia, review sites) more heavily than top-ranked pages

What this means for the work:

  • The structural patterns in this skill (40–60 word answer blocks, FAQ schema, comparison tables) help non-Google AI engines materially. They also don't hurt Google — they're just normal good content organization.
  • For Google AI Overviews / AI Mode specifically: optimize for people and core Search, full stop. Strong E-E-A-T, original information, semantic HTML, clean indexability.
  • For ChatGPT/Claude/Perplexity: layer on the extractable structure + llms.txt + machine-readable files.

When in doubt, default to "write for people, organize for clarity" — that satisfies both camps.

Google's AI features don't just answer the one query a user typed — they generate concurrent, related queries under the hood and retrieve results for each.

Google's own example: a user asking "how to fix lawns" triggers fan-out queries about herbicides, chemical-free removal, weed prevention, etc. The AI synthesizes across all of them.

Implications:

  • Single-page-per-keyword targeting is less effective. Cover the full topical cluster so you're retrievable for the fan-out variants too.
  • Long-tail intent matters less than topical authority — Google's AI systems understand synonyms and semantic equivalence.
  • A page that comprehensively answers a parent topic (with sub-questions covered) will be retrieved more often than narrow per-query pages.

Action: when planning content, brainstorm the 5–10 related queries the AI is likely to fan out to and make sure your content (or your site as a whole) covers them.


AI Visibility Audit

Before optimizing, assess your current AI search presence.

Step 1: Check AI Answers for Your Key Queries

Test 10-20 of your most important queries across platforms:

QueryGoogle AI OverviewChatGPTPerplexityYou Cited?Competitors Cited?
[query 1]Yes/NoYes/NoYes/NoYes/No[who]
[query 2]Yes/NoYes/NoYes/NoYes/No[who]

Query types to test:

  • "What is [your product category]?"
  • "Best [product category] for [use case]"
  • "[Your brand] vs [competitor]"
  • "How to [problem your product solves]"
  • "[Your product category] pricing"
Step 2: Analyze Citation Patterns

When your competitors get cited and you don't, examine:

  • Content structure — Is their content more extractable?
  • Authority signals — Do they have more citations, stats, expert quotes?
  • Freshness — Is their content more recently updated?
  • Schema markup — Do they have structured data you're missing?
  • Third-party presence — Are they cited via Wikipedia, Reddit, review sites?
Step 3: Content Extractability Check

For each priority page, verify:

CheckPass/Fail
Clear definition in first paragraph?
Self-contained answer blocks (work without surrounding context)?
Statistics with sources cited?
Comparison tables for "[X] vs [Y]" queries?
FAQ section with natural-language questions?
Schema markup (FAQ, HowTo, Article, Product)?
Expert attribution (author name, credentials)?
Recently updated (within 6 months)?
Heading structure matches query patterns?
AI bots allowed in robots.txt?
Step 4: AI Bot Access Check

Verify your robots.txt allows AI crawlers. Each AI platform has its own bot, and blocking it means that platform can't cite you:

  • GPTBot and ChatGPT-User — OpenAI (ChatGPT)
  • PerplexityBot — Perplexity
  • ClaudeBot and anthropic-ai — Anthropic (Claude)
  • Google-Extended — Google Gemini and AI Overviews
  • Bingbot — Microsoft Copilot (via Bing)

Check your robots.txt for Disallow rules targeting any of these. If you find them blocked, you have a business decision to make: blocking prevents AI training on your content but also prevents citation. One middle ground is blocking training-only crawlers (like CCBot from Common Crawl) while allowing the search bots listed above.

See references/platform-ranking-factors.md for the full robots.txt configuration.


Optimization Strategy

The Three Pillars
1. Structure (make it extractable)
2. Authority (make it citable)
3. Presence (be where AI looks)
Pillar 1: Structure — Make Content Extractable

AI systems extract passages, not pages. Every key claim should work as a standalone statement.

Content block patterns:

  • Definition blocks for "What is X?" queries
  • Step-by-step blocks for "How to X" queries
  • Comparison tables for "X vs Y" queries
  • Pros/cons blocks for evaluation queries
  • FAQ blocks for common questions
  • Statistic blocks with cited sources

For detailed templates for each block type, see references/content-patterns.md.

Structural rules:

  • Lead every section with a direct answer (don't bury it)
  • Keep key answer passages to 40-60 words (optimal for snippet extraction)
  • Use H2/H3 headings that match how people phrase queries
  • Tables beat prose for comparison content
  • Numbered lists beat paragraphs for process content
  • Each paragraph should convey one clear idea
Pillar 2: Authority — Make Content Citable

AI systems prefer sources they can trust. Build citation-worthiness.

The Princeton GEO research (KDD 2024, studied across Perplexity.ai) ranked 9 optimization methods:

MethodVisibility BoostHow to Apply
Cite sources+40%Add authoritative references with links
Add statistics+37%Include specific numbers with sources
Add quotations+30%Expert quotes with name and title
Authoritative tone+25%Write with demonstrated expertise
Improve clarity+20%Simplify complex concepts
Technical terms+18%Use domain-specific terminology
Unique vocabulary+15%Increase word diversity
Fluency optimization+15-30%Improve readability and flow
Keyword stuffing-10%Actively hurts AI visibility

Best combination: Fluency + Statistics = maximum boost. Low-ranking sites benefit even more — up to 115% visibility increase with citations.

Statistics and data (+37-40% citation boost)

  • Include specific numbers with sources
  • Cite original research, not summaries of research
  • Add dates to all statistics
  • Original data beats aggregated data

Expert attribution (+25-30% citation boost)

  • Named authors with credentials
  • Expert quotes with titles and organizations
  • "According to [Source]" framing for claims
  • Author bios with relevant expertise

Freshness signals

  • "Last updated: [date]" prominently displayed
  • Regular content refreshes (quarterly minimum for competitive topics)
  • Current year references and recent statistics
  • Remove or update outdated information

E-E-A-T alignment

  • First-hand experience demonstrated
  • Specific, detailed information (not generic)
  • Transparent sourcing and methodology
  • Clear author expertise for the topic
Pillar 3: Presence — Be Where AI Looks

AI systems don't just cite your website — they cite where you appear.

Third-party sources matter more than your own site:

  • Wikipedia mentions (7.8% of all ChatGPT citations)
  • Reddit discussions (1.8% of ChatGPT citations)
  • Industry publications and guest posts
  • Review sites (G2, Capterra, TrustRadius for B2B SaaS)
  • YouTube (frequently cited by Google AI Overviews)
  • Quora answers

Actions:

  • Ensure your Wikipedia page is accurate and current
  • Participate authentically in Reddit communities
  • Get featured in industry roundups and comparison articles
  • Maintain updated profiles on relevant review platforms
  • Create YouTube content for key how-to queries
  • Answer relevant Quora questions with depth
Machine-Readable Files for AI Agents

Google's stance: not required for AI Overviews or AI Mode. Their guide explicitly says you don't need new markup, AI files, or markdown to appear in generative AI search.

Why include them anyway: non-Google AI engines (ChatGPT, Claude, Perplexity) and autonomous buying agents do reward extractable structure. The files below help with those engines without harming Google.

AI agents aren't just answering questions — they're becoming buyers. When an AI agent evaluates tools on behalf of a user, it needs structured, parseable information. If your pricing is locked in a JavaScript-rendered page or a "contact sales" wall, agents will skip you and recommend competitors whose information they can actually read.

Add these machine-readable files to your site root:

/pricing.md or /pricing.txt — Structured pricing data for AI agents

markdown
# Pricing — [Your Product Name]

## Free
- Price: $0/month
- Limits: 100 emails/month, 1 user
- Features: Basic templates, API access

## Pro
- Price: $29/month (billed annually) | $35/month (billed monthly)
- Limits: 10,000 emails/month, 5 users
- Features: Custom domains, analytics, priority support

## Enterprise
- Price: Custom — contact sales@example.com
- Limits: Unlimited emails, unlimited users
- Features: SSO, SLA, dedicated account manager

Why this matters now:

  • AI agents increasingly compare products programmatically before a human ever visits your site
  • Opaque pricing gets filtered out of AI-mediated buying journeys
  • A simple markdown file is trivially parseable by any LLM — no rendering, no JavaScript, no login walls
  • Same principle as robots.txt (for crawlers), llms.txt (for AI context), and AGENTS.md (for agent capabilities)

Best practices:

  • Use consistent units (monthly vs. annual, per-seat vs. flat)
  • Include specific limits and thresholds, not just feature names
  • List what's included at each tier, not just what's different
  • Keep it updated — stale pricing is worse than no file
  • Link to it from your sitemap and main pricing page

/llms.txt — Context file for AI systems (see llmstxt.org)

If you don't have one yet, add an llms.txt that gives AI systems a quick overview of what your product does, who it's for, and links to key pages (including your pricing).

/okf/ — Open Knowledge Format bundle (Google-backed, v0.1)

Google introduced OKF in June 2026 — a markdown spec for representing site content as a directory of cross-linked files with YAML frontmatter, agent-readable without scraping. Built primarily for data-team catalog metadata; the site-readable-by-agents repurposing was popularized by Suganthan Mohanadasan. No confirmed AI-search ranking signal today — treat it as protocol-layer registration like early schema.org. For the full breakdown, implementation paths (free generator, WordPress plugin, by-hand), hosting guidance, and when to skip, see references/okf.md.

Schema Markup for AI

Structured data helps AI systems understand your content. Key schemas:

Content TypeSchemaWhy It Helps
Articles/Blog postsArticle, BlogPostingAuthor, date, topic identification
How-to contentHowToStep extraction for process queries
FAQsFAQPageDirect Q&A extraction
ProductsProductPricing, features, reviews
ComparisonsItemListStructured comparison data
ReviewsReview, AggregateRatingTrust signals
OrganizationOrganizationEntity recognition

Content with proper schema shows 30-40% higher AI visibility on non-Google AI engines. Google's note: structured data is "not required for generative AI search" but is recommended for overall SEO strategy. For implementation, use the schema skill.


Show full SKILL.md (1,273 more words)Show less

Agentic Experiences

Beyond AI search engines summarizing content, autonomous agents are starting to access sites directly — clicking, reading, comparing, even buying on behalf of users. Google's guide flags this as an emerging category to plan for.

How agents access your site:

  • Visual rendering — they screenshot/read the page like a user would
  • DOM inspection — they parse the page's HTML structure
  • Accessibility tree — they rely on the same semantic information assistive tech uses (labels, roles, landmarks, headings)

What to do:

  • Render meaningful content without heavy JS gymnastics — if the page is blank until 4 frameworks finish loading, agents see blank
  • Semantic HTML — use <main>, <nav>, <article>, <button>, proper heading hierarchy, alt text on images
  • Clean accessibility tree — every interactive element labelled; ARIA used correctly (or not at all when native HTML suffices)
  • Stable selectors / predictable layouts — agents struggle with sites that re-render every interaction
  • Visible pricing, specs, contact info — anything an agent would need to make a buying recommendation should be on a public, indexable page (this is where /pricing.md and similar files help)

Emerging — Universal Commerce Protocol (UCP): Google references UCP as a forthcoming protocol that will give agents standardized hooks for commerce interactions (catalog discovery, pricing, checkout). Watch for adoption; for now, the structural recommendations above are the precursor.

For ecom and local business specifically, Google highlights:

  • Merchant Center feeds + Google Business Profile for product/service visibility in AI Search
  • Business Agent for conversational customer engagement (where applicable)

Content Types That Get Cited Most

Not all content is equally citable. Prioritize these formats:

Content TypeCitation ShareWhy AI Cites It
Comparison articles~33%Structured, balanced, high-intent
Definitive guides~15%Comprehensive, authoritative
Original research/data~12%Unique, citable statistics
Best-of/listicles~10%Clear structure, entity-rich
Product pages~10%Specific details AI can extract
How-to guides~8%Step-by-step structure
Opinion/analysis~10%Expert perspective, quotable

Underperformers for AI citation:

  • Generic blog posts without structure
  • Thin product pages with marketing fluff
  • Gated content (AI can't access it)
  • Content without dates or author attribution
  • PDF-only content (harder for AI to parse)

Citation ≠ recommendation. Getting cited means your content was useful to consult; getting recommended — onto the buyer's actual shortlist — is governed by web-wide consensus (reviews, forums, analysts, press) and is largely independent of your own content. Self-promotional "best [category]" listicles can even backfire for emerging brands: in one 100-query B2B study, 69% of the AI Overview citations that self-promotional listicles earned came in answers that recommended competitors instead of the publishing brand. See references/citations-vs-recommendations.md for the visibility ladder (retrieved → cited → mentioned → recommended), stage-dependent buyer's-guide strategy, what earns recommendations, and the attribution blind spot.


Monitoring AI Visibility

What to Track
MetricWhat It MeasuresHow to Check
AI Overview presenceDo AI Overviews appear for your queries?Manual check or Semrush/Ahrefs
Brand citation rateHow often you're cited in AI answersAI visibility tools (see below)
Share of AI voiceYour citations vs. competitorsPeec AI, Otterly, ZipTie
Citation sentimentHow AI describes your brandManual review + monitoring tools
Recommendation rateWhether you're on the shortlist, not just cited (see citations-vs-recommendations.md)Prompt tracking + mention framing
Source attributionWhich of your pages get citedTrack referral traffic from AI sources
AI Visibility Monitoring Tools
ToolCoverageBest For
Otterly AIChatGPT, Perplexity, Google AI OverviewsShare of AI voice tracking
Peec AIChatGPT, Gemini, Perplexity, Claude, Copilot+Multi-platform monitoring at scale
ZipTieGoogle AI Overviews, ChatGPT, PerplexityBrand mention + sentiment tracking
LLMrefsChatGPT, Perplexity, AI Overviews, GeminiSEO keyword → AI visibility mapping
DIY Monitoring (No Tools)

Monthly manual check:

  1. Pick your top 20 queries
  2. Run each through ChatGPT, Perplexity, and Google
  3. Record: Are you cited? Who is? What page?
  4. Log in a spreadsheet, track month-over-month
Search Console expectations

Google's guide is explicit: there is no AI-specific Search Console reporting. AI Overviews and AI Mode use core Search ranking, so the standard Search Console reports (Performance, Coverage, Core Web Vitals) are still what you measure with for Google. The third-party tools above are the only way to see cross-platform AI citation behavior.


What NOT to Do

Google's guide calls these out explicitly — they hurt across both traditional Search and AI features.

  1. Write separate content "for AI". Same content should serve people and AI. Writing variants targeted at AI systems risks the scaled content abuse spam policy — Google's words.
  2. Chunk pages into AI-bait fragments. Google's guide is direct: "Don't break your content into tiny pieces for AI to better understand it." Use normal paragraph + heading structure.
  3. Generate at scale for ranking manipulation. AI-generated content is fine if it meets Search Essentials and spam policies. Mass-producing thin variations does not.
  4. Pursue inauthentic mentions. Don't fabricate citations or bulk-spam Reddit/Wikipedia for AI visibility. Real participation only.
  5. Block AI crawlers if you want citation. Blocking GPTBot, PerplexityBot, ClaudeBot, Google-Extended means those engines literally cannot cite you. Block training-only crawlers (CCBot) if you must, not the search-and-cite ones.
  6. Hide your main content behind JS that doesn't render. Both core Search and AI agents need to see your content; JS-only rendering loses both audiences.
  7. Skip E-E-A-T fundamentals. Author identity, first-hand experience, expertise signals, transparent sourcing — Google's guide leans heavily on these for AI features.

AI SEO by Content Type

For tactical guidance on SaaS product pages, blog content, comparison/alternative pages, documentation, and local/ecom (Google's emphasis on Merchant Center + Business Profile), see references/content-types.md.


Common Mistakes

  • Ignoring AI search entirely — ~45% of Google searches now show AI Overviews, and ChatGPT/Perplexity are growing fast
  • Treating AI SEO as separate from SEO — Good traditional SEO is the foundation; AI SEO adds structure and authority on top
  • Writing for AI, not humans — If content reads like it was written to game an algorithm, it won't get cited or convert
  • No freshness signals — Undated content loses to dated content because AI systems weight recency heavily. Show when content was last updated
  • Gating all content — AI can't access gated content. Keep your most authoritative content open
  • Ignoring third-party presence — You may get more AI citations from a Wikipedia mention than from your own blog
  • No structured data — Schema markup gives AI systems structured context about your content
  • Keyword stuffing — Unlike traditional SEO where it's just ineffective, keyword stuffing actively reduces AI visibility by 10% (Princeton GEO study)
  • Hiding pricing behind "contact sales" or JS-rendered pages — AI agents evaluating your product on behalf of buyers can't parse what they can't read. Add a /pricing.md file
  • Blocking AI bots — If GPTBot, PerplexityBot, or ClaudeBot are blocked in robots.txt, those platforms can't cite you
  • Generic content without data — "We're the best" won't get cited. "Our customers see 3x improvement in [metric]" will
  • Forgetting to monitor — You can't improve what you don't measure. Check AI visibility monthly at minimum

Tool Integrations

For implementation, see the tools registry.

ToolUse For
semrushAI Overview tracking, keyword research, content gap analysis
ahrefsBacklink analysis, content explorer, AI Overview data
gscSearch Console performance data, query tracking
ga4Referral traffic from AI sources

Task-Specific Questions

  1. What are your top 10-20 most important queries?
  2. Have you checked if AI answers exist for those queries today?
  3. Do you have structured data (schema markup) on your site?
  4. What content types do you publish? (Blog, docs, comparisons, etc.)
  5. Are competitors being cited by AI where you're not?
  6. Do you have a Wikipedia page or presence on review sites?

  • seo-audit: For traditional technical and on-page SEO audits
  • schema: For implementing structured data that helps AI understand your content
  • content-strategy: For planning what content to create
  • competitors: For building comparison pages that get cited
  • programmatic-seo: For building SEO pages at scale
  • copywriting: For writing content that's both human-readable and AI-extractable

© Nexus-JPF, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 6 other files (references) in .agents/skills/ai-seo of Nexus-JPF/note-companion.

  • SKILL.md
  • evals/evals.json
  • references/citations-vs-recommendations.md
  • references/content-patterns.md
  • references/content-types.md
  • references/okf.md
  • references/platform-ranking-factors.md

Open the folder on GitHubat commit 9cad635

Used in 5 other repositories

We found 7 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 5 other GitHub owners. This page covers the copy in Nexus-JPF/note-companion, which our catalogue first saw on October 7, 2026.

Compare with similar skills

AI SEO next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

AI SEO compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
AI SEO this skillNexus-JPF/note-companion8705 repos~6.7kAutomated safety check: PassMIT
Geo Fundamentalswasp-lang/wasp19k9 repos~861Automated safety check: PassMIT
SEO GeoReScienceLab/opc-skills1.8k4 repos~2.1kAutomated safety check: PassApache-2.0
GEO-First SEO Audit Toolzubair-trabzada/geo-seo-claude11k—~2.8kAutomated safety check: NotesMIT
Fire Your SEO Agencyleopard627/fire-your-seo-agency711—~1.1kAutomated safety check: PassMIT
Marketing OsYuzzyuk/marketing-os540—~2.5kAutomated safety check: PassMIT

Similar skills

  • Geo Fundamentals

    wasp-lang/wasp

    Generative Engine Optimization for AI search engines (ChatGPT, Claude, Perplexity).

    19k GitHub starsUsed in 9 repos~861 tokens
    Marketing & SEOAuto-check passed
  • SEO Geo

    ReScienceLab/opc-skills

    SEO & GEO (Generative Engine Optimization) for websites. An agent skill from ReScienceLab/opc-skills.

    1.8k GitHub starsUsed in 4 repos~2.1k tokens
    Marketing & SEOAuto-check passed
  • GEO-First SEO Audit Tool

    zubair-trabzada/geo-seo-claude

    Audits a website for AI search visibility across ChatGPT, Claude, Perplexity and Google AI Overviews while checking traditional SEO, schema and E-E-A-T content quality.

    11k GitHub stars~2.8k tokensUpdated yesterday
    Marketing & SEOAuto-check: notes
  • Fire Your SEO Agency

    leopard627/fire-your-seo-agency

    SEO·AEO·GEO·LLMO·NEO(네이버) 다섯 레인을 진단하고 직접 구현하며, 인용되는 콘텐츠를 계속 생산하는 서브 블로그·콘텐츠 운영 파이프라인까지 세팅하는 스킬.

    711 GitHub stars~1.1k tokensUpdated 15 days ago
    Marketing & SEOAuto-check passed
  • Marketing Os

    Yuzzyuk/marketing-os

    A complete marketing department in one skill. An agent skill from Yuzzyuk/marketing-os.

    540 GitHub stars~2.5k tokensUpdated 1 mo ago
    Marketing & SEOAuto-check passed
  • AI Visibility

    Ryze-AI-Adgent/open-seo-mcp-skills

    Measure real AI-engine visibility — traffic from ChatGPT, Perplexity, Claude, Gemini and which pages they cite — from actual GA4 referral data, not prompt sampling.

    4.7k GitHub stars~611 tokensUpdated 17 days ago
    Marketing & SEOAuto-check passed

More from Nexus-JPF/note-companion

All 18 skills in this repo
  • Analytics

    Nexus-JPF/note-companion

    When the user wants to set up, improve, or audit analytics tracking and measurement.

    870 GitHub starsUsed in 7 repos~2.2k tokens
    Auto-check passed
  • Customer Research

    Nexus-JPF/note-companion

    When the user wants to conduct, analyze, or synthesize customer research.

    870 GitHub starsUsed in 6 repos~3.2k tokens
    Auto-check passed
  • Marketing Plan

    Nexus-JPF/note-companion

    When the user needs a comprehensive marketing plan for a client, a company they advise, or their own product.

    870 GitHub starsUsed in 5 repos~5.2k tokens
    Auto-check passed
  • Competitor Profiling

    Nexus-JPF/note-companion

    When the user wants to research, profile, or analyze competitors from their URLs.

    870 GitHub starsUsed in 4 repos~3.5k tokens
    Auto-check passed
  • Onboarding

    Nexus-JPF/note-companion

    When the user wants to optimize post-signup onboarding, user activation, first-run experience, or time-to-value.

    870 GitHub starsUsed in 4 repos~1.6k tokens
    Auto-check passed
  • Image

    Nexus-JPF/note-companion

    When the user wants to create, generate, edit, or optimize images for marketing — blog heroes, social graphics, product mockups, profile banners, listing visuals, or brand assets.

    870 GitHub starsUsed in 3 repos~3.9k tokens
    Auto-check passed

Categories

Questions about AI SEO

What does AI SEO do?

When the user wants to optimize content for AI search engines, get cited by LLMs, or appear in AI-generated answers. AI SEO is an agent skill from Nexus-JPF/note-companion. When the user wants to optimize content for AI search engines, get cited by LLMs, or appear in AI-generated answers.

When should I use AI SEO?

AI SEO fits situations like: wants to optimize content for AI search engines; get cited by LLMs; appear in AI-generated answers; the user mentions AI SEO.

How do I install AI SEO in Claude Code?

Run `npx skills add Nexus-JPF/note-companion --skill ai-seo -a claude-code`. Or copy the skill folder (.agents/skills/ai-seo in Nexus-JPF/note-companion) into .claude/skills/ai-seo in your project. Claude Code loads it when a task matches its description.

How do I install AI SEO in Codex?

Run `npx skills add Nexus-JPF/note-companion --skill ai-seo -a codex`. Or copy the skill folder (.agents/skills/ai-seo in Nexus-JPF/note-companion) into .agents/skills/ai-seo in your project. Codex loads it when a task matches its description.

Can I use AI SEO in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Nexus-JPF/note-companion --skill ai-seo -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ai-seo, .gemini/skills/ai-seo, .github/skills/ai-seo and .opencode/skills/ai-seo in your project.

What does AI SEO need to run?

SKILL.md names no scripts, command-line tools or credentials: AI SEO is instructions for the agent only.

Does AI SEO access the network?

SKILL.md names 3 domains. As links in the text: developers.google.com, llmstxt.org and cloud.google.com. This is read from the text; nothing was executed.

Is AI SEO safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does AI SEO use?

AI SEO is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does AI SEO use?

About 6.7k tokens (SKILL.md is roughly 27k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 9.8k tokens, read only when the agent opens those files.

What are the alternatives to AI SEO?

Skills that share tags, products or a category with AI SEO: Geo Fundamentals (wasp-lang/wasp, 19k stars), SEO Geo (ReScienceLab/opc-skills, 1.8k stars), GEO-First SEO Audit Tool (zubair-trabzada/geo-seo-claude, 11k stars) and Fire Your SEO Agency (leopard627/fire-your-seo-agency, 711 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains AI SEO?

Nexus-JPF (a GitHub organization) maintains it in Nexus-JPF/note-companion, which has 870 GitHub stars. The repository holds 18 skills in this directory. The repository was last updated on October 7, 2026.

Source: Nexus-JPF/note-companion on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.