ai-bot-log-audit

AI Bot Log Audit

Analyze server logs to understand how AI crawlers retrieve your content, then optimize placement and structure for maximum citation probability. Based on Metehan Yeşilyurt's log file analysis framework.

When to Use This Skill

Use this skill when you need to:

• Audit AI bot crawl patterns on your site (what they fetch, how often, what they skip)
• Diagnose citation gaps — your content exists but AI search doesn't cite it
• Optimize content placement for LLM retrieval mechanics (lost-in-the-middle, embedding similarity)
• Compare AI bot behavior across different products (Google, OpenAI, Anthropic, Perplexity)
• Build a GEO strategy grounded in actual crawl data, not assumptions
• Identify which pages AI bots prioritize and which they ignore

This skill is particularly valuable for:

• SEO professionals adding AI search to their optimization scope
• Publishers monitoring AI traffic and content extraction
• Technical SEOs conducting log file analysis
• Content strategists deciding what to optimize for AI visibility

Methodology Foundation

Source Expert: Metehan Yeşilyurt (SEO Consultant, speaker at BrightonSEO, The Search Session)

Core Thesis: Log file analysis reveals the real mechanics of AI search retrieval. Different AI products (AI Overviews, AI Mode, Perplexity) use fundamentally different retrieval pipelines, so optimizing for "AI search" requires understanding each product's specific crawl and retrieval behavior.

"AI Overviews, AI Mode, and Web Guide are three completely different products with different retrieval behaviors. You can't optimize for 'AI search' as if it's one thing." — Metehan Yeşilyurt, The Search Session

Key Insight: The shift from traditional SEO to AI search optimization is from chasing clicks in deterministic SERPs to chasing citations in machine-generated text. Log files reveal the mechanics behind citation selection.

What Claude Does vs What You Decide

| Claude Does | You Decide | |-------------|------------| | Guides log analysis methodology | Which log data to provide | | Identifies patterns in crawl behavior | Strategic priority of AI products | | Recommends content placement optimizations | Content creation/modification scope | | Maps retrieval behavior to optimization actions | Resource allocation for changes | | Creates audit templates and checklists | Which recommendations to implement |

What This Skill Does

When invoked, I will guide you through:

1. Log Collection — Identify and extract AI bot activity from server logs
2. Bot Identification — Map user agents to AI products
3. Crawl Pattern Analysis — Understand what AI bots fetch and ignore
4. Retrieval Mechanics — Learn how each AI product processes your content
5. Optimization Actions — Specific changes to improve AI citation probability

Instructions

Phase 1: AI Bot Identification

Known AI Crawlers (2026)

| Bot User Agent | Operator | Purpose | Respects robots.txt? | |---------------|----------|---------|---------------------| | GPTBot | OpenAI | Training data + ChatGPT Browse | Yes | | ChatGPT-User | OpenAI | Real-time browsing in ChatGPT | Yes | | OAI-SearchBot | OpenAI | SearchGPT / ChatGPT Search | Yes | | ClaudeBot | Anthropic | Training data collection | Yes | | PerplexityBot | Perplexity | Real-time search + answer generation | Yes (mostly) | | Google-Extended | Google | Gemini/AI training (deprecated — now part of Googlebot) | N/A | | Googlebot | Google | Traditional crawl + AI Overviews + AI Mode | Yes | | Bytespider | ByteDance | Training for TikTok AI features | Yes | | CCBot | Common Crawl | Open dataset used by many AI models | Yes | | Applebot-Extended | Apple | Apple Intelligence features | Yes |

Log Extraction Commands

# Extract all AI bot hits from Apache/Nginx access logs
grep -iE "(GPTBot|ChatGPT-User|OAI-SearchBot|ClaudeBot|PerplexityBot|Bytespider|CCBot|Applebot-Extended)" access.log > ai_bots.log

# Count hits by bot
awk -F'"' '{print $6}' ai_bots.log | grep -oE "(GPTBot|ChatGPT-User|OAI-SearchBot|ClaudeBot|PerplexityBot|Bytespider|CCBot)" | sort | uniq -c | sort -rn

# Top pages crawled by AI bots
awk '{print $7}' ai_bots.log | sort | uniq -c | sort -rn | head -50

# Crawl frequency by day
awk '{print $4}' ai_bots.log | cut -d: -f1 | tr -d '[' | sort | uniq -c

# Response codes for AI bots (are they getting 200s or errors?)
awk '{print $9}' ai_bots.log | sort | uniq -c | sort -rn

Phase 2: Crawl Pattern Analysis

What to Look For

| Pattern | What It Means | Action | |---------|--------------|--------| | Bot fetches page frequently | Page is in retrieval index, content matters | Optimize this page first | | Bot fetches page once then stops | Page was evaluated and deprioritized | Improve content quality/freshness | | Bot never fetches a page | Page not discovered or blocked | Check internal linking, sitemap, robots.txt | | Bot gets 404/500 | Technical issue blocking retrieval | Fix immediately | | Bot fetches but doesn't cite | Content retrieved but not selected for answers | Improve structure, uniqueness, authority |

Crawl Budget Analysis

AI bots have crawl budgets like traditional bots. If your site is large:

QUESTIONS TO ANSWER:
1. What % of pages are being crawled by AI bots?
2. Are high-value pages being fetched?
3. Are AI bots wasting time on low-value pages (tag pages, pagination)?
4. What's the crawl frequency — daily? weekly? sporadic?
5. Do different AI bots prioritize different pages?

Comparative Bot Behavior

Map how each bot interacts with your site differently:

ANALYSIS TEMPLATE:

GPTBot:
  Pages fetched: ___
  Top pages: ___
  Crawl frequency: ___
  Response codes: ___

PerplexityBot:
  Pages fetched: ___
  Top pages: ___
  Crawl frequency: ___
  Response codes: ___

ClaudeBot:
  Pages fetched: ___
  Top pages: ___
  Crawl frequency: ___
  Response codes: ___

Phase 3: Understanding Retrieval Mechanics

Each AI product uses a different retrieval pipeline. Optimizing requires understanding the mechanics.

Perplexity: Embedding Similarity + Source Diversification

Perplexity uses high embedding similarity to match content to queries, then actively diversifies sources.

What this means for you:

• Semantic match matters more than keyword match
• Being the single best source isn't enough — Perplexity diversifies
• Your content needs to be retrievable AND complementary to other sources
• Structured, extractable content wins (tables, definitions, clear claims)

Google AI Overviews: Search Index + LLM Layer

AI Overviews sit on top of existing Google Search rankings. Your traditional SEO signals matter.

What this means for you:

• If you don't rank on page 1 for traditional search, you're unlikely to appear in AI Overviews
• The AI layer selects from already-ranked pages and synthesizes
• E-E-A-T signals are inherited from search ranking

Google AI Mode: Multi-Step Query Fan-Out

AI Mode decomposes complex questions into sub-queries, retrieves for each, then synthesizes.

What this means for you:

• Content that answers sub-questions gets included
• Comprehensive topical coverage across your site matters
• Internal linking between related topics helps AI Mode stitch answers together

Phase 4: LLM Vulnerability Awareness

Understanding known LLM processing weaknesses helps you position content for maximum retrieval.

4 Key LLM Vulnerabilities

| Vulnerability | Description | Optimization | |--------------|-------------|-------------| | Recency bias | LLMs weight recent information higher, even when older info is more accurate | Date your content clearly. Update regularly. Recent timestamps = retrieval advantage | | Lost-in-the-middle | LLMs process beginnings and endings of context better than middles | Place key claims