Claude Skill

ai-search-optimization

Optimizes for AI assistants and AI-generated answers — being retrievable, being cited, and being represented accurately when a model answers on your behalf. Use this when traffic is shifting from links to AI answers, when a brand is misrepresented or absent in AI responses, when

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

Full trust report

Download cbrock84-headcount-plugins_demand-generation_skills_ai-search-optimization-98d1c17.zip · 2 KB
Part of cbrock84/headcount — 160 skills

Install

skills CLI npx skills add https://github.com/cbrock84/headcount/tree/main/plugins/demand-generation/skills/ai-search-optimization
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install cbrock84-headcount@llmmart
Git git clone https://github.com/cbrock84/headcount.git

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

Skill manifest

AI search optimization

Classical SEO optimizes to be clicked. This optimizes to be quoted — often with no click at all. That changes what a good page looks like.

What gets cited

  • Self-contained passages. A retrieved chunk arrives without the surrounding page. Each section must make sense alone, with its subject named rather than pronominalized.
  • Direct answers near the question. Bury the answer under three paragraphs of context and the passage retrieved will be the context.
  • Specific, checkable facts — numbers, dates, named methods, stated conditions. Vague claims are neither retrievable nor quotable.
  • Attributable expertise. Named authors, stated credentials, dated content, and cited sources. Anonymous undated content is weakly weighted.
  • Structure that survives extraction — real headings, real lists, real tables. Layout implied by styling disappears.

Practical moves

  • Answer the question in the first sentence under each heading, then elaborate.
  • Write headings as the questions people actually ask.
  • Define your own terms on your own pages, so the model's definition traces to you.
  • Keep facts consistent across your site. Contradictions get resolved against you.
  • Maintain the boring canonical pages — pricing, comparisons, specifications, FAQ. These are heavily retrieved and usually neglected.

Being represented accurately

Assistants assemble an answer about you from whatever is available, weighted toward third-party and structured sources. Where those are thin or stale, the answer will be wrong.

Audit periodically: ask several assistants what your company does, who it is for, what it costs, and how it compares. Note the errors and trace them to a source. The fix is almost always publishing or correcting the source, not the assistant.

Measuring

Click-through will fall on informational queries even as influence rises. Track citation and mention frequency, and downstream branded search and direct traffic, rather than judging this program on organic sessions — that metric will say you are losing while you are winning.

Sources

references/sources.md in this skill lists the outside authorities that settle the questions here — what each one is authoritative for, and what you may do with it. Check them before answering on anything they cover, and cite what you used. Most are free to read and not free to reproduce; the use note on each is binding.

Never

  • Optimize for one assistant's current behavior. Retrieval and citation rules change without notice and without a changelog.
  • Assume being crawlable means being citable. Models cite sources that answer a question cleanly, not sources that merely exist.
  • Leave an inaccurate representation uncorrected because it is not on your site. The claim propagates whether or not you own the page it came from.
Files (headcount)
  • references
    • sources.md 1.7 KB
      # Sources — `demand-generation:ai-search-optimization`
      
      <!-- Generated by scripts/build-sources.py from sources/*.toml. Do not edit. -->
      
      Check these before answering on anything they cover, and cite what you used. The use note on each one is binding: most of what a professional cites is free to read and not free to reproduce.
      
      ## Google crawlers and user-triggered fetchers
      
      Google · global · CC BY — quote with attribution
      
      <https://developers.google.com/search/docs/crawling-indexing/overview-google-crawlers>
      
      Machine-readable: <https://developers.google.com/search/docs/crawling-indexing/robots/intro>
      
      **Authoritative for:** Which user agents Google operates and what each one is for, including the separate control over training and AI surfaces — the question behind every robots.txt argument about blocking AI.
      
      ## RFC 9309: Robots Exclusion Protocol
      
      IETF · global · **read and cite only — copyrighted, do not reproduce**
      
      <https://www.rfc-editor.org/rfc/rfc9309.html>
      
      **Authoritative for:** The formal parsing rules for robots.txt — precedence, wildcards, size limits, and what a crawler is obliged to do. Settles at the protocol level whether disallow prevents indexing, which it does not.
      
      ## Spam policies for Google web search
      
      Google · global · CC BY — quote with attribution
      
      <https://developers.google.com/search/docs/essentials/spam-policies>
      
      **Authoritative for:** Whether a tactic is sanctionable — scaled content abuse, site reputation abuse, expired-domain abuse, cloaking, doorway pages. The only authoritative answer to whether a programmatic build will be penalized.
      
      ---
      
      Sources are maintained in `sources/` upstream, not here. If one is wrong, out of date, or missing, fix it there — this file is regenerated and an edit to it is lost.
      
  • SKILL.md 3.3 KB
    ---
    name: ai-search-optimization
    description: Optimizes for AI assistants and AI-generated answers — being retrievable, being cited, and being represented accurately when a model answers on your behalf. Use this when traffic is shifting from links to AI answers, when a brand is misrepresented or absent in AI responses, when planning content for retrieval rather than ranking, or when deciding how AI search changes an existing SEO program.
    ---
    
    # AI search optimization
    
    Classical SEO optimizes to be *clicked*. This optimizes to be *quoted* — often with no click at all.
    That changes what a good page looks like.
    
    ## What gets cited
    
    - **Self-contained passages.** A retrieved chunk arrives without the surrounding page. Each section
      must make sense alone, with its subject named rather than pronominalized.
    - **Direct answers near the question.** Bury the answer under three paragraphs of context and the
      passage retrieved will be the context.
    - **Specific, checkable facts** — numbers, dates, named methods, stated conditions. Vague claims are
      neither retrievable nor quotable.
    - **Attributable expertise.** Named authors, stated credentials, dated content, and cited sources.
      Anonymous undated content is weakly weighted.
    - **Structure that survives extraction** — real headings, real lists, real tables. Layout implied by
      styling disappears.
    
    ## Practical moves
    
    - Answer the question in the first sentence under each heading, then elaborate.
    - Write headings as the questions people actually ask.
    - Define your own terms on your own pages, so the model's definition traces to you.
    - Keep facts consistent across your site. Contradictions get resolved against you.
    - Maintain the boring canonical pages — pricing, comparisons, specifications, FAQ. These are heavily
      retrieved and usually neglected.
    
    ## Being represented accurately
    
    Assistants assemble an answer about you from whatever is available, weighted toward third-party and
    structured sources. Where those are thin or stale, the answer will be wrong.
    
    Audit periodically: ask several assistants what your company does, who it is for, what it costs, and
    how it compares. Note the errors and trace them to a source. The fix is almost always publishing or
    correcting the source, not the assistant.
    
    ## Measuring
    
    Click-through will fall on informational queries even as influence rises. Track citation and mention
    frequency, and downstream branded search and direct traffic, rather than judging this program on
    organic sessions — that metric will say you are losing while you are winning.
    
    ## Sources
    
    `references/sources.md` in this skill lists the outside authorities that settle the questions
    here — what each one is authoritative for, and what you may do with it. Check them before
    answering on anything they cover, and cite what you used. Most are free to read and not free
    to reproduce; the use note on each is binding.
    
    ## Never
    
    - Optimize for one assistant's current behavior. Retrieval and citation rules change without notice and without a changelog.
    - Assume being crawlable means being citable. Models cite sources that answer a question cleanly, not sources that merely exist.
    - Leave an inaccurate representation uncorrected because it is not on your site. The claim propagates whether or not you own the page it came from.
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.

Related