Claude Skill

geo-ai-search-optimizer

Optimize content to be cited by ChatGPT, Gemini, Perplexity, and AI Overviews (GEO). Use when the user wants visibility in generative answers, not just blue links.

LLM Mart · 0 points · 0 views 0 listing impressions 0 install-command copies
Virus-scanned Reviewed automatically before listing.

Full trust report

Download navinspire-ia-navin-navin_skills_geo-ai-search-optimizer-e9c73a3.zip · 1 KB
Part of navinspire-ia/navin — 182 skills

Install

skills CLI npx skills add https://github.com/Navinspire-ia/navin/tree/main/navin/skills/geo-ai-search-optimizer
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install navinspire-ia-navin@llmmart
Git git clone https://github.com/Navinspire-ia/navin.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole navinspire-ia/navin collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

GEO / AI Search Optimizer

Generative engines cite content that is quotable, structured, and authoritative. Optimize for being the source in an AI answer - stacked on classic SEO, not instead of it.

When to use

  • Brand wants AI Overview / Perplexity / ChatGPT citation presence
  • Refreshing key pages for quotability

When not to use

  • Replacing technical SEO or keyword research entirely
  • Inventing "citation scores" without evidence

What AI engines favor

  • Direct, self-contained answers near the top of sections
  • Clear entity definitions ("X is a ...")
  • Stats, dates, and named sources (fresh + verifiable)
  • Structured data (FAQ, HowTo, Organization)
  • Author/company credibility (about, expertise, sameAs)
  • Consistent brand facts across the web

Workflow

  1. Define target questions the buyer asks (from ICP + PAA-style research).
  2. Fetch current pages; mark which answers are buried or non-quotable.
  3. Rewrite with an answer-first block: 40-80 word direct answer under each H2 question.
  4. Add FAQ schema for real questions; keep answers atomic.
  5. Strengthen entity clarity: who, what, where - same wording on site + profiles.
  6. Publish only citable numbers you can source; never fake stats for GEO.
  7. Note measurement gap: AI citation tracking is manual unless user pastes engine answers.
  8. Save seo/geo-plan-<date>.md.

Quotability check

A paragraph is GEO-ready when it can be lifted verbatim into an answer and still make sense with attribution.

Rules

  • Do not sacrifice classic SEO - GEO stacks on top.
  • Never fake statistics to be "citable".
  • Pair with seo-content-writer and on-page-seo-optimizer.

Anti-patterns

  • Keyword stuffing for LLMs
  • Claiming "you will appear in ChatGPT" as a guarantee
Files (navin)
  • SKILL.md 2 KB
    ---
    name: geo-ai-search-optimizer
    description: Optimize content to be cited by ChatGPT, Gemini, Perplexity, and AI Overviews (GEO). Use when the user wants visibility in generative answers, not just blue links.
    metadata: {"navin":{"emoji":"🤖","category":"seo"}}
    ---
    
    # GEO / AI Search Optimizer
    
    Generative engines cite content that is quotable, structured, and authoritative. Optimize for being *the source* in an AI answer - stacked on classic SEO, not instead of it.
    
    ## When to use
    
    - Brand wants AI Overview / Perplexity / ChatGPT citation presence
    - Refreshing key pages for quotability
    
    ## When not to use
    
    - Replacing technical SEO or keyword research entirely
    - Inventing "citation scores" without evidence
    
    ## What AI engines favor
    
    - Direct, self-contained answers near the top of sections
    - Clear entity definitions ("X is a ...")
    - Stats, dates, and named sources (fresh + verifiable)
    - Structured data (FAQ, HowTo, Organization)
    - Author/company credibility (about, expertise, sameAs)
    - Consistent brand facts across the web
    
    ## Workflow
    
    1. Define target questions the buyer asks (from ICP + PAA-style research).
    2. Fetch current pages; mark which answers are buried or non-quotable.
    3. Rewrite with an **answer-first block**: 40-80 word direct answer under each H2 question.
    4. Add FAQ schema for real questions; keep answers atomic.
    5. Strengthen entity clarity: who, what, where - same wording on site + profiles.
    6. Publish only citable numbers you can source; never fake stats for GEO.
    7. Note measurement gap: AI citation tracking is manual unless user pastes engine answers.
    8. Save `seo/geo-plan-<date>.md`.
    
    ## Quotability check
    
    A paragraph is GEO-ready when it can be lifted verbatim into an answer and still make sense with attribution.
    
    ## Rules
    
    - Do not sacrifice classic SEO - GEO stacks on top.
    - Never fake statistics to be "citable".
    - Pair with `seo-content-writer` and `on-page-seo-optimizer`.
    
    ## Anti-patterns
    
    - Keyword stuffing for LLMs
    - Claiming "you will appear in ChatGPT" as a guarantee
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.

Related