GEO Optimizer

What is GEO?

1. They fetch raw HTML - Many don't render JavaScript
2. They have size limits - Crawlers abandon pages >1MB HTML
3. They evaluate confidence - Hedged language ("maybe", "possibly") ranks 3x lower than confident assertions
4. They need machine-readable metadata - AgentFacts/NANDA protocol for AI agent discovery

Quick Audit Workflow

1. Technical Visibility Check

# Run full GEO audit
python3 ${CLAUDE_SKILL_DIR}/scripts/audit-geo.py https://example.com

# Check HTML size and JS dependency
curl -sI https://example.com | grep -i content-length

2. Content Authority Analysis

# Check hedge density of your content
python3 ${CLAUDE_SKILL_DIR}/scripts/check-hedge-density.py --url https://example.com/blog/post

# Or analyze text directly
python3 ${CLAUDE_SKILL_DIR}/scripts/check-hedge-density.py --text "Your content here"

3. Agent Infrastructure Setup

# Generate AgentFacts schema for your domain
python3 ${CLAUDE_SKILL_DIR}/scripts/generate-agentfacts.py \
  --domain example.com \
  --agent-name "Example Service" \
  --capabilities text,image \
  --output /.well-known/agent-facts

Core Metrics

Hedge Density Score

• maybe, possibly, perhaps, might, could be
• however, although, it seems, arguably
• some believe, it appears, potentially

references/hedge-density.md

HTML Size Budget

• 18% of pages abandoned by crawlers
• Content truncation risks
• Slower indexing

curl -sI URL | grep content-length

references/technical-visibility.md

JS Dependency Risk

• Rendering crawlers: GPTBot, PerplexityBot (sometimes)
• Non-rendering: ClaudeBot, many others

Discovery Gap

references/discovery-strategies.md

AgentFacts Setup

/.well-known/agent-facts

{
  "@context": "https://nanda.dev/ns/agent-facts/v1",
  "id": "nanda:example.com",
  "agent_name": "urn:agent:example:com",
  "endpoints": {
    "static": ["https://api.example.com/v1/agent"]
  },
  "capabilities": {
    "modalities": ["text"],
    "authentication": {
      "methods": ["oauth2", "jwt"]
    }
  },
  "trust": {
    "certification": "self-attested",
    "human_oversight": "true"
  }
}

references/agentfacts-schema.md

Audit Report Sections

1. Technical Visibility
   • HTML payload size (target: <1MB)
   • JS dependency assessment
   • Crawler accessibility
2. Content Authority
   • Hedge density score (target: <0.2%)
   • Confidence assessment
   • Entity density
3. Discovery Strategy
   • Site age analysis
   • Recency wall detection
   • Recommended approach
4. Agent Infrastructure
   • AgentFacts presence
   • Schema validation
   • NANDA compliance

Scripts

audit-geo.py

check-hedge-density.py

generate-agentfacts.py

Reference Documentation

hedge-density.md

agentfacts-schema.md

technical-visibility.md

discovery-strategies.md

Example Commands

# Full audit with report
python3 ${CLAUDE_SKILL_DIR}/scripts/audit-geo.py https://mysite.com --output report.md

# Quick hedge check
python3 ${CLAUDE_SKILL_DIR}/scripts/check-hedge-density.py --url https://mysite.com/about

# Generate AgentFacts for SaaS
python3 ${CLAUDE_SKILL_DIR}/scripts/generate-agentfacts.py \
  --domain myapp.com \
  --agent-name "MyApp AI" \
  --capabilities text \
  --auth oauth2,apikey

Key Takeaways

1. GEO != SEO - Different crawlers, different rules
2. Confidence wins - Hedge density <0.2% is the target
3. Size matters - Stay under 1MB HTML
4. JS is risky - Content must work without rendering
5. Age affects strategy - Startups need web-augmented signals
6. AgentFacts is future-proofing - Implement NANDA now