llm-optimization

Optimize websites for AI assistant recommendations. ChatGPT, Gemini, Perplexity, Claude. Get cited in AI answers.

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "llm-optimization" with this command: npx skills add soborbo/claudeskills/soborbo-claudeskills-llm-optimization

LLM Optimization Skill

Purpose

Make websites appear in AI assistant recommendations and citations. Different from traditional SEO - optimized for how LLMs parse and recommend content.

Core Rules

  1. Structured > Prose — LLMs extract facts from clear structure
  2. Schema.org is Critical — Speakable, FAQPage, HowTo schemas
  3. Answer the Question — First paragraph must directly answer intent
  4. Cite Sources — Links to authoritative sources build trust
  5. Entity Clarity — Clear business name, location, service definitions
  6. Freshness Signals — Last updated dates, recent content
  7. No Walls — Content must be crawlable, no JS-only rendering
  8. Never Override Truth — LLM optimization NEVER overrides factual accuracy or legal compliance

LLM Crawlers to Support

LLMCrawlersNotes
OpenAI/ChatGPTGPTBot, OAI-SearchBot, ChatGPT-UserGPTBot = training, others = real-time
Google GeminiGoogle-Extendedrobots.txt control token, not a distinct UA
PerplexityPerplexityBot, Perplexity-UserBot = indexing, User = real-time fetch
ClaudeClaudeBot, Claude-User, Claude-SearchBotOfficial Anthropic crawlers
Microsoft CopilotBingbotUses Bing's crawler

robots.txt Configuration

# OpenAI crawlers
User-agent: GPTBot
Allow: /

User-agent: OAI-SearchBot
Allow: /

User-agent: ChatGPT-User
Allow: /

# Google AI (control token)
User-agent: Google-Extended
Allow: /

# Perplexity crawlers
User-agent: PerplexityBot
Allow: /

User-agent: Perplexity-User
Allow: /

# Anthropic/Claude crawlers
User-agent: ClaudeBot
Allow: /

User-agent: Claude-User
Allow: /

User-agent: Claude-SearchBot
Allow: /

Content Structure for LLM Extraction

<!-- 1. Direct Answer (first 150 chars) -->
<p class="lead">
  [Business Name] provides [service] in [location].
  [Key differentiator]. [Call to action].
</p>

<!-- 2. Quick Facts Box -->
<aside class="quick-facts" itemscope itemtype="https://schema.org/LocalBusiness">
  <h2>Quick Facts</h2>
  <dl>
    <dt>Service Area</dt><dd itemprop="areaServed">[Areas]</dd>
    <dt>Price Range</dt><dd itemprop="priceRange">[Range]</dd>
  </dl>
</aside>

<!-- 3. FAQ Section (critical for LLM) -->
<section itemscope itemtype="https://schema.org/FAQPage">
  <!-- Each Q&A as schema -->
</section>

Forbidden

  • ❌ Content behind JavaScript-only rendering
  • ❌ Blocking LLM crawlers in robots.txt
  • ❌ Missing Speakable schema
  • ❌ Vague, marketing-speak first paragraphs
  • ❌ No FAQ section on service pages
  • ❌ Missing lastModified dates
  • ❌ No structured data

Definition of Done

  • robots.txt allows all LLM crawlers
  • Speakable schema on all key pages
  • FAQPage schema on service pages
  • First paragraph directly answers search intent
  • Quick Facts box with structured data
  • lastModified meta tag present
  • Content renders without JavaScript
  • Entity names consistent across site

References

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

General

astro-seo

No summary provided by upstream source.

Repository SourceNeeds Review
General

astro-ux

No summary provided by upstream source.

Repository SourceNeeds Review
General

astro-architecture

No summary provided by upstream source.

Repository SourceNeeds Review