SEO & AEO Strategy

Workspace Context

Read bootstrap context before asking questions: strategy/brand.md for brand, audience, offer, channels, tools, constraints, and metrics; about/me.md for personal voice; content/ideas.md and content/calendar.md for content planning. Use legacy product-marketing context files only as fallback. Save generated drafts to content/<platform>/drafts/YYYY-MM-DD_short-topic-slug.md, and route durable learnings back to strategy/brand.md, about/me.md, or content/ideas.md.

Operating Contract

This skill is self-contained for its frontmatter scope: use its local instructions, references, scripts, and assets as the playbook; ask only for missing task-specific inputs; hand off to adjacent skills instead of expanding scope; and return an actionable artifact, decision, plan, draft, or diagnostic.

Traditional SEO gets pages ranked. AI search optimization (AEO/GEO) gets content cited. This skill covers both.

SEO  → Rank in traditional search results (blue links)
AEO  → Appear in featured snippets, AI Overviews, voice answers
GEO  → Get cited in generative AI responses (ChatGPT, Claude, Perplexity)

2025 reality: AI Overviews appear in ~47% of Google searches. 58% of queries end without a click. Optimize for citation, not just ranking.

---

Initial Assessment

Use the Workspace Context above first. Only ask for what is missing.

Before auditing, understand:

1. Site context — Type (SaaS, e-commerce, blog), primary SEO goal, priority keywords/topics
2. Current state — Known issues, organic traffic level, recent changes or migrations
3. AI visibility — Does the brand appear in AI-generated answers today? Checked ChatGPT, Perplexity, Google AI Overviews?
4. Scope — Full site vs. specific pages? Technical + on-page + AI, or one focus area?

---

Technical SEO

Crawlability

Indexation

• site:domain.com check vs. Search Console coverage report
• Verify no noindex on important pages
• Check canonical tags (self-referencing on unique pages, HTTP→HTTPS, www consistency)
• Identify redirect chains/loops, soft 404s, duplicate content

Core Web Vitals & Speed

Mobile & Security

• Responsive design (not separate m. site), viewport configured, adequate tap targets (48px min)
• HTTPS across entire site, valid SSL, no mixed content, HSTS header

URL Structure

• Lowercase, hyphen-separated, < 75 characters
• Include target keywords naturally, avoid unnecessary parameters

---

On-Page SEO

Title Tags

• 50–60 characters, primary keyword near beginning
• Unique per page, brand name at end (unless homepage)
• Compelling and click-worthy

Meta Descriptions

• 150–160 characters, include primary keyword
• Clear value proposition with call-to-action, unique per page

Heading Structure

• Single <h1> per page containing primary keyword
• Logical hierarchy (H1 → H2 → H3), no skipped levels
• Descriptive headings (not generic), include keywords naturally

Image SEO

• Descriptive filenames with keywords, alt text on all images
• Compressed, modern formats (WebP/AVIF), lazy load below-fold
• Responsive images with width/height attributes

Internal Linking

• Descriptive anchor text with keywords (not "click here")
• Important pages well-linked, no broken internal links
• Breadcrumb navigation for hierarchy

Content Quality (E-E-A-T)

---

AI Search Optimization (AEO/GEO)

How AI Search Platforms Select Sources

For detailed platform-specific ranking factors, see references/platform-ranking-factors.md and references/platform-algorithms.md.

The Three Pillars

1. Structure — Make content extractable

AI systems extract passages, not pages. Every key claim should work standalone.

• Lead every section with a direct answer (don't bury it)
• Keep key answer passages to 40–60 words (optimal for snippet extraction)
• Use H2/H3 headings that match how people phrase queries
• Tables beat prose for comparisons; numbered lists beat paragraphs for processes

Inverted pyramid pattern:

┌──────────────────────────────────┐
│  DIRECT ANSWER (1-2 sentences)   │ ← AI extracts this first
├──────────────────────────────────┤
│  KEY FACTS & CONTEXT             │ ← Supporting bullets/data
├──────────────────────────────────┤
│  DETAILED EXPLANATION            │ ← Background, examples
└──────────────────────────────────┘

2. Authority — Make content citable

The Princeton GEO research (KDD 2024) ranked 9 optimization methods:

Best combination: Fluency + Statistics = maximum boost. Low-ranking sites benefit even more — up to 115% visibility increase with citations.

For detailed GEO research, see references/geo-research.md.

3. Presence — Be where AI looks

AI systems cite where you appear, not just your site:

• Wikipedia mentions (7.8% of all ChatGPT citations)
• Reddit discussions, YouTube content, Quora answers
• Review sites (G2, Capterra, TrustRadius for B2B SaaS)
• Industry publications and guest posts

Semantic Triples (Key AEO Technique)

Compact, unambiguous facts AI can't misread. Pattern: [Subject] [specific verb] [concrete object].

✅ "HubSpot CRM syncs contact and company data."
✅ "Lead Scoring assigns priority based on engagement."
❌ "The system helps with various tasks."
❌ "It can do many things for users."

AI Crawler Configuration

Ensure robots.txt allows AI crawlers:

User-agent: GPTBot          # OpenAI
Allow: /
User-agent: ChatGPT-User    # ChatGPT browsing
Allow: /
User-agent: PerplexityBot   # Perplexity
Allow: /
User-agent: ClaudeBot        # Anthropic
Allow: /
User-agent: Google-Extended  # Gemini/AI Overviews
Allow: /

See references/ai-crawlers.md for full configuration.

---

Structured Data for Search & AI

Schema markup improves AI visibility by 30–40%. Priority types:

For full JSON-LD templates, see references/schema-templates.md and references/schema-for-ai.md.

Validate at Google Rich Results Test (https://search.google.com/test/rich-results) and Schema.org Validator (https://validator.schema.org/).

---

Content Types That Get Cited Most

Underperformers: Generic blog posts without structure, thin product pages, gated content, undated content, PDF-only content.

For content templates and patterns, see references/content-patterns.md and references/content-templates.md.

---

AEO Measurement

Track these four metrics monthly:

1. AI Visibility

Test priority queries across ChatGPT, Perplexity, Gemini, Google AI Overviews. Target: Appear in 60%+ of priority queries.

2. AI Share of Voice

Share of Voice = (Your mentions / Total brand mentions) × 100. Target: Match or exceed traditional search market share.

3. AI Citations

How often YOUR WEBSITE is the source. Target: Cited in 30%+ of relevant queries.

4. Referral Demand

Traffic originating in AI but arriving later (brand search after AI mention). Track via post-purchase survey: "How did you first hear about us?"

Monitoring Tools

Interpreting Results

---

Audit Checklists

Critical (Fix Immediately)

• HTTPS enabled, valid SSL
• robots.txt allows crawling (including AI bots)
• No noindex on important pages
• Title tags present, unique, with primary keyword
• Single <h1> per page
• AI crawlers not blocked in robots.txt

High Priority

• Meta descriptions present and compelling
• XML sitemap submitted to Search Console
• Canonical URLs set correctly
• Mobile-responsive, Core Web Vitals passing
• FAQPage schema on FAQ/support pages
• Article schema with author on blog/guide pages
• "Last updated" date visible on content

Medium Priority

• Internal linking strategy implemented
• Image alt text on all images
• Descriptive URLs with keywords
• Breadcrumb navigation + schema
• Author bios with credentials
• Statistics cited with sources
• Content answers queries in first paragraph

Ongoing

• Fix crawl errors in Search Console
• Update sitemap when content changes
• Refresh content quarterly (competitive topics)
• Monitor AI visibility monthly (manual or tools)
• Check for broken links
• Track AI share of voice vs. competitors

For complete SEO checklist, see references/seo-checklist.md.

---

Tools

See references/tools-and-apis.md for API reference.

Scripts available in scripts/: SEO audit, keyword research, SERP analysis, backlink analysis, competitor gap analysis, autocomplete ideas. See script files for usage.

---

References

• references/platform-ranking-factors.md — How each AI platform selects sources
• references/platform-algorithms.md — Detailed ranking factors per platform
• references/geo-research.md — Princeton GEO research (9 methods)
• references/content-patterns.md — AI-optimized content block templates
• references/content-templates.md — Page structure templates for AI
• references/schema-templates.md — JSON-LD schema templates
• references/schema-for-ai.md — Schema markup for AI visibility
• references/ai-crawlers.md — AI crawler robots.txt configuration
• references/seo-checklist.md — Complete SEO audit checklist
• references/aeo-geo-patterns.md — Content patterns for AI citation
• references/ai-writing-detection.md — AI writing patterns to avoid
• references/query-research.md — Query research methodology
• references/tools-and-apis.md — Tools and API reference
• references/google-docs-summary.md — Google documentation summary

Related Skills

• keyword-research-and-clustering — Keyword research, expansion, and topic clustering
• keyword-research-and-clustering — Keyword expansion and clustering before SEO page planning
• competitor-analysis — Comparison pages and competitor-backed search strategy
• content-strategy-and-planning — Turning SEO opportunities into an editorial roadmap
• content-strategy-and-planning — Planning what content to create
• data-and-funnel-analytics — Measuring SEO/AEO performance

---

Supporting file: examples/opc-skills-case-study.md

Case Study: OPC Skills Website SEO/GEO Optimization

Real-world example of applying SEO and GEO optimization to opc.dev.

---

Background

Website: opc.dev
Product: AI Agent Skills for Solopreneurs
Platforms: Claude Code, Cursor, Codex, Factory Droid, OpenCode
Date: January 2026

Initial Status

---

Problem Analysis

1. Keyword Conflict

The term "OPC" has different meanings in different markets:

Decision: Focus on long-tail keywords for English market:

• "AI agent skills for solopreneurs"
• "Claude Code skills"
• "indie hacker tools"

2. Missing Schema Markup

No structured data meant:

• No rich results in Google
• Poor AI visibility
• No FAQ display

3. No GEO Optimization

Content lacked:

• Statistics and data points
• Expert citations
• FAQ format
• Answer-first structure

---

Implementation

Phase 1: Meta Tags Optimization

Before:

<title>OPC Skills</title>
<meta name="description" content="Skills for one person companies">

After:

<title>OPC Skills - AI Agent Skills for Solopreneurs & Indie Hackers | Claude Code, Cursor, Codex</title>
<meta name="description" content="10+ AI agent skills for solopreneurs. Domain hunting, social media research, logo creation. Works with Claude Code, Cursor, Codex, Factory Droid. One-click install, 100% open source.">

Keywords targeted:

• solopreneur (high intent, low competition)
• indie hacker (community term)
• Claude Code skills (specific platform)
• AI agent skills (emerging category)

Phase 2: Schema Markup Implementation

Added comprehensive JSON-LD:

{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@type": "WebPage",
      "name": "OPC Skills - AI Agent Skills for Solopreneurs",
      "description": "10+ agent skills for Claude Code, Cursor, Codex...",
      "dateModified": "2026-01-20",
      "speakable": {
        "@type": "SpeakableSpecification",
        "cssSelector": ["h1", ".hero-description", ".faq-answer"]
      }
    },
    {
      "@type": "SoftwareApplication",
      "name": "OPC Skills",
      "applicationCategory": "DeveloperApplication",
      "operatingSystem": "Cross-platform",
      "offers": {
        "@type": "Offer",
        "price": "0",
        "priceCurrency": "USD"
      }
    },
    {
      "@type": "FAQPage",
      "mainEntity": [
        {
          "@type": "Question",
          "name": "What is OPC Skills?",
          "acceptedAnswer": {
            "@type": "Answer",
            "text": "OPC Skills is a collection of 10+ AI agent skills..."
          }
        }
        // 12 total FAQ items
      ]
    }
  ]
}

Phase 3: GEO Optimization (Princeton Methods)

Statistics Addition (+37%)

Before:

"Skills for one person companies"

After:

"10+ Skills | 5 Platforms | One-Click Install | 100% Open Source"

FAQ Section (+40% AI Visibility)

Added 12 FAQ questions targeting high-search queries:

1. What is OPC Skills?
2. What platforms does OPC Skills support?
3. How do I install OPC Skills?
4. Is OPC Skills free?
5. What skills are included in OPC Skills?
6. How does the domain-hunter skill work?
7. Can I use OPC Skills with Claude Code?
8. What is the twitter skill used for?
9. How do I create a logo with OPC Skills?
10. Is OPC Skills open source?
11. How do I contribute to OPC Skills?
12. What is a solopreneur?

Authoritative Tone (+25%)

Before:

"Some tools for solo workers"

After:

"AI Agent Skills for Solopreneurs - The definitive skill library for 
one-person companies. Trusted by indie hackers worldwide."

Citations (+40%)

Added references to:

• Anthropic (Claude Code official documentation)
• Industry statistics on solopreneur growth
• Sam Altman's "billion-dollar one-person company" prediction

Phase 4: AI Bot Configuration

Updated robots.txt considerations:

# Allow AI bots for GEO visibility
User-agent: GPTBot
Allow: /

User-agent: PerplexityBot
Allow: /

User-agent: ClaudeBot
Allow: /

Phase 5: Hero Section Rewrite

Before:

OPC Skills
Skills for OPCs

After:

AI Agent Skills for Solopreneurs

The skill library for one-person companies. 
Install once, use everywhere.

10+ Skills | 5 Platforms | One-Click Install | 100% Open Source

---

Results

Technical Improvements

SEO Improvements

GEO Improvements

Estimated total GEO visibility boost: 40-60%

---

Lessons Learned

1. Keyword Research is Critical

The "OPC" keyword conflict could have hurt visibility. Long-tail keywords solved this:

• "solopreneur tools" > "OPC tools"
• "Claude Code skills" > "AI skills"

2. FAQPage Schema is High-Impact

Adding 12 FAQ items with proper schema:

• Enables rich results
• Provides AI-extractable content
• Targets specific search queries

3. Statistics Make Content Quotable

"10+ Skills | 5 Platforms | One-Click Install | 100% Open Source"

These specific numbers are:

• Easy for AI to extract
• Memorable for users
• Differentiated from competitors

4. Answer-First Structure

Each FAQ answer starts with a direct answer:

• "OPC Skills is a collection of..." (not "Well, it depends...")
• This matches AI response patterns

---

Next Steps

Short-term (1 month)

• Submit sitemap to Google Search Console
• Submit to Bing Webmaster Tools
• Monitor indexing progress
• Track FAQ rich results

Medium-term (3 months)

• Monitor AI citation rate
• A/B test different FAQ questions
• Build backlinks from dev communities
• Create content for Reddit/HN

Long-term (6 months)

• Establish "OPC Skills = Solopreneur tools" brand
• Rank for "Claude Code skills" in AI search
• Get cited in AI responses about solopreneur tools

---

Replication Guide

To replicate this optimization for your own site:

1. Audit current state using seo-geo skill checklist
2. Research keywords - find long-tail opportunities
3. Write meta tags - include primary keyword in title/description
4. Add Schema markup - start with FAQPage and WebPage
5. Apply Princeton methods - statistics, citations, structure
6. Configure AI bot access - robots.txt
7. Validate schema - Google Rich Results Test
8. Submit to search engines - Search Console, Bing Webmaster
9. Monitor and iterate - track visibility, adjust content

---

Files Changed

---

Supporting file: references/aeo-geo-patterns.md

AEO and GEO Content Patterns

Reusable content block patterns optimized for answer engines and AI citation.

---

Answer Engine Optimization (AEO) Patterns

These patterns help content appear in featured snippets, AI Overviews, voice search results, and answer boxes.

Definition Block

Use for "What is [X]?" queries.

## What is [Term]?

[Term] is [concise 1-sentence definition]. [Expanded 1-2 sentence explanation with key characteristics]. [Brief context on why it matters or how it's used].

Example:

## What is Answer Engine Optimization?

Answer Engine Optimization (AEO) is the practice of structuring content so AI-powered systems can easily extract and present it as direct answers to user queries. Unlike traditional SEO that focuses on ranking in search results, AEO optimizes for featured snippets, AI Overviews, and voice assistant responses. This approach has become essential as over 60% of Google searches now end without a click.

Step-by-Step Block

Use for "How to [X]" queries. Optimal for list snippets.

## How to [Action/Goal]

[1-sentence overview of the process]

1. **[Step Name]**: [Clear action description in 1-2 sentences]
2. **[Step Name]**: [Clear action description in 1-2 sentences]
3. **[Step Name]**: [Clear action description in 1-2 sentences]
4. **[Step Name]**: [Clear action description in 1-2 sentences]
5. **[Step Name]**: [Clear action description in 1-2 sentences]

[Optional: Brief note on expected outcome or time estimate]

Example:

## How to Optimize Content for Featured Snippets

Earning featured snippets requires strategic formatting and direct answers to search queries.

1. **Identify snippet opportunities**: Use tools like Semrush or Ahrefs to find keywords where competitors have snippets you could capture.
2. **Match the snippet format**: Analyze whether the current snippet is a paragraph, list, or table, and format your content accordingly.
3. **Answer the question directly**: Provide a clear, concise answer (40-60 words for paragraph snippets) immediately after the question heading.
4. **Add supporting context**: Expand on your answer with examples, data, and expert insights in the following paragraphs.
5. **Use proper heading structure**: Place your target question as an H2 or H3, with the answer immediately following.

Most featured snippets appear within 2-4 weeks of publishing well-optimized content.

Comparison Table Block

Use for "[X] vs [Y]" queries. Optimal for table snippets.

## [Option A] vs [Option B]: [Brief Descriptor]

| Feature | [Option A] | [Option B] |
|---------|------------|------------|
| [Criteria 1] | [Value/Description] | [Value/Description] |
| [Criteria 2] | [Value/Description] | [Value/Description] |
| [Criteria 3] | [Value/Description] | [Value/Description] |
| [Criteria 4] | [Value/Description] | [Value/Description] |
| Best For | [Use case] | [Use case] |

**Bottom line**: [1-2 sentence recommendation based on different needs]

Pros and Cons Block

Use for evaluation queries: "Is [X] worth it?", "Should I [X]?"

## Advantages and Disadvantages of [Topic]

[1-sentence overview of the evaluation context]

### Pros

- **[Benefit category]**: [Specific explanation]
- **[Benefit category]**: [Specific explanation]
- **[Benefit category]**: [Specific explanation]

### Cons

- **[Drawback category]**: [Specific explanation]
- **[Drawback category]**: [Specific explanation]
- **[Drawback category]**: [Specific explanation]

**Verdict**: [1-2 sentence balanced conclusion with recommendation]

FAQ Block

Use for topic pages with multiple common questions. Essential for FAQ schema.

## Frequently Asked Questions

### [Question phrased exactly as users search]?

[Direct answer in first sentence]. [Supporting context in 2-3 additional sentences].

### [Question phrased exactly as users search]?

[Direct answer in first sentence]. [Supporting context in 2-3 additional sentences].

### [Question phrased exactly as users search]?

[Direct answer in first sentence]. [Supporting context in 2-3 additional sentences].

Tips for FAQ questions:

• Use natural question phrasing ("How do I..." not "How does one...")
• Include question words: what, how, why, when, where, who, which
• Match "People Also Ask" queries from search results
• Keep answers between 50-100 words

Listicle Block

Use for "Best [X]", "Top [X]", "[Number] ways to [X]" queries.

## [Number] Best [Items] for [Goal/Purpose]

[1-2 sentence intro establishing context and selection criteria]

### 1. [Item Name]

[Why it's included in 2-3 sentences with specific benefits]

### 2. [Item Name]

[Why it's included in 2-3 sentences with specific benefits]

### 3. [Item Name]

[Why it's included in 2-3 sentences with specific benefits]

---

Generative Engine Optimization (GEO) Patterns

These patterns optimize content for citation by AI assistants like ChatGPT, Claude, Perplexity, and Gemini.

Statistic Citation Block

Statistics increase AI citation rates by 15-30%. Always include sources.

[Claim statement]. According to [Source/Organization], [specific statistic with number and timeframe]. [Context for why this matters].

Example:

Mobile optimization is no longer optional for SEO success. According to Google's 2024 Core Web Vitals report, 70% of web traffic now comes from mobile devices, and pages failing mobile usability standards see 24% higher bounce rates. This makes mobile-first indexing a critical ranking factor.

Expert Quote Block

Named expert attribution adds credibility and increases citation likelihood.

"[Direct quote from expert]," says [Expert Name], [Title/Role] at [Organization]. [1 sentence of context or interpretation].

Example:

"The shift from keyword-driven search to intent-driven discovery represents the most significant change in SEO since mobile-first indexing," says Rand Fishkin, Co-founder of SparkToro. This perspective highlights why content strategies must evolve beyond traditional keyword optimization.

Authoritative Claim Block

Structure claims for easy AI extraction with clear attribution.

[Topic] [verb: is/has/requires/involves] [clear, specific claim]. [Source] [confirms/reports/found] that [supporting evidence]. This [explains/means/suggests] [implication or action].

Example:

E-E-A-T is the cornerstone of Google's content quality evaluation. Google's Search Quality Rater Guidelines confirm that trust is the most critical factor, stating that "untrustworthy pages have low E-E-A-T no matter how experienced, expert, or authoritative they may seem." This means content creators must prioritize transparency and accuracy above all other optimization tactics.

Self-Contained Answer Block

Create quotable, standalone statements that AI can extract directly.

**[Topic/Question]**: [Complete, self-contained answer that makes sense without additional context. Include specific details, numbers, or examples in 2-3 sentences.]

Example:

**Ideal blog post length for SEO**: The optimal length for SEO blog posts is 1,500-2,500 words for competitive topics. This range allows comprehensive topic coverage while maintaining reader engagement. HubSpot research shows long-form content earns 77% more backlinks than short articles, directly impacting search rankings.

Evidence Sandwich Block

Structure claims with evidence for maximum credibility.

[Opening claim statement].

Evidence supporting this includes:
- [Data point 1 with source]
- [Data point 2 with source]
- [Data point 3 with source]

[Concluding statement connecting evidence to actionable insight].

---

Domain-Specific GEO Tactics

Different content domains benefit from different authority signals.

Technology Content

• Emphasize technical precision and correct terminology
• Include version numbers and dates for software/tools
• Reference official documentation
• Add code examples where relevant

Health/Medical Content

• Cite peer-reviewed studies with publication details
• Include expert credentials (MD, RN, etc.)
• Note study limitations and context
• Add "last reviewed" dates

Financial Content

• Reference regulatory bodies (SEC, FTC, etc.)
• Include specific numbers with timeframes
• Note that information is educational, not advice
• Cite recognized financial institutions

Legal Content

• Cite specific laws, statutes, and regulations
• Reference jurisdiction clearly
• Include professional disclaimers
• Note when professional consultation is advised

Business/Marketing Content

• Include case studies with measurable results
• Reference industry research and reports
• Add percentage changes and timeframes
• Quote recognized thought leaders

---

Voice Search Optimization

Voice queries are conversational and question-based. Optimize for these patterns:

Question Formats for Voice

• "What is..."
• "How do I..."
• "Where can I find..."
• "Why does..."
• "When should I..."
• "Who is..."

Voice-Optimized Answer Structure

• Lead with direct answer (under 30 words ideal)
• Use natural, conversational language
• Avoid jargon unless targeting expert audience
• Include local context where relevant
• Structure for single spoken response

---

Supporting file: references/ai-crawlers.md

AI Crawlers & Bot Management Guide

Table of Contents

1. AI Crawler Overview (#ai-crawler-overview)
2. robots.txt Configuration (#robotstxt-configuration)
3. Crawler Characteristics (#crawler-characteristics)
4. Strategic Decisions (#strategic-decisions)
5. Implementation Guide (#implementation-guide)

---

AI Crawler Overview

Major AI Crawlers (2025)

Key Distinction: Search vs Training

SEARCH CRAWLERS (Allow for visibility):
├── Googlebot          → Traditional search
├── OAI-SearchBot      → ChatGPT Search results
├── ChatGPT-User       → User asks ChatGPT to read a page
├── PerplexityBot      → Perplexity answers
└── ClaudeBot          → Claude features

TRAINING CRAWLERS (Block if data protection matters):
├── GPTBot             → OpenAI model training
├── Google-Extended    → Gemini training
├── CCBot              → Common Crawl datasets
├── Bytespider         → ByteDance training
└── FacebookBot        → Meta AI training

---

robots.txt Configuration

Recommended Configuration (Balanced)

# ===========================================
# AI SEARCH CRAWLERS - ALLOW
# ===========================================

# OpenAI Search (ChatGPT Search feature)
User-agent: OAI-SearchBot
Allow: /

# ChatGPT when users ask it to read a page
User-agent: ChatGPT-User
Allow: /

# Perplexity AI search
User-agent: PerplexityBot
Allow: /

# Claude AI
User-agent: ClaudeBot
Allow: /

# ===========================================
# AI TRAINING CRAWLERS - BLOCK
# ===========================================

# OpenAI training (not search)
User-agent: GPTBot
Disallow: /

# Google Gemini training
User-agent: Google-Extended
Disallow: /

# Common Crawl
User-agent: CCBot
Disallow: /

# ByteDance
User-agent: Bytespider
Disallow: /

# Meta AI training
User-agent: FacebookBot
Disallow: /

# ===========================================
# TRADITIONAL SEARCH - ALLOW
# ===========================================

User-agent: Googlebot
Allow: /

User-agent: Bingbot
Allow: /

User-agent: *
Allow: /

Sitemap: https://example.com/sitemap.xml

Maximum Visibility Configuration

# Allow all AI crawlers for maximum reach
User-agent: *
Allow: /

Sitemap: https://example.com/sitemap.xml

Maximum Protection Configuration

# Block all AI crawlers except traditional search
User-agent: Googlebot
Allow: /

User-agent: Bingbot
Allow: /

User-agent: GPTBot
Disallow: /

User-agent: OAI-SearchBot
Disallow: /

User-agent: ChatGPT-User
Disallow: /

User-agent: Google-Extended
Disallow: /

User-agent: PerplexityBot
Disallow: /

User-agent: ClaudeBot
Disallow: /

User-agent: CCBot
Disallow: /

User-agent: *
Disallow: /

---

Crawler Characteristics

Crawl Behavior Comparison

What AI Crawlers Index

Typically Indexed:
├── Main body content
├── Headers (H1-H6)
├── Meta descriptions
├── Alt text
├── Structured data (JSON-LD)
├── Tables
└── Lists

Often Missed:
├── JavaScript-rendered content
├── Content behind tabs/accordions
├── Lazy-loaded images
├── PDF content
├── Video transcripts (unless in HTML)
└── Content in iframes

---

Strategic Decisions

Decision Matrix

Questions to Ask

1. Is being cited by AI chatbots valuable to you?

   • Yes → Allow search crawlers
   • No → Block all AI crawlers

2. Are you concerned about AI training on your content?

   • Yes → Block training crawlers (GPTBot, Google-Extended)
   • No → Allow all

3. Do users ask AI to read your pages?

   • Yes → Allow ChatGPT-User
   • No → Can block

4. Is your content time-sensitive or frequently updated?

   • Yes → Allow all search crawlers for freshness
   • No → Selective blocking okay

---

Implementation Guide

Step 1: Audit Current Configuration

# Check current robots.txt
curl -s https://yoursite.com/robots.txt

# Test specific bot access
curl -A "GPTBot" -I https://yoursite.com/
curl -A "OAI-SearchBot" -I https://yoursite.com/

Step 2: Monitor Crawler Activity

In server logs, look for:

User-Agent patterns:
- "GPTBot/1.0"
- "OAI-SearchBot"
- "ChatGPT-User"
- "PerplexityBot"
- "ClaudeBot"

Log analysis command:

grep -E "GPTBot|OAI-SearchBot|ChatGPT-User|PerplexityBot|ClaudeBot" access.log | \
  awk '{print $1, $7}' | sort | uniq -c | sort -rn

Step 3: Implement WAF Rules (if needed)

Cloudflare example:

# Block specific bots at WAF level
(cf.client.bot and http.user_agent contains "GPTBot")

Step 4: Verify Implementation

# Test that robots.txt is being served correctly
curl -s https://yoursite.com/robots.txt | grep -A2 "GPTBot"

# Verify bot can/cannot access
curl -A "GPTBot" -s -o /dev/null -w "%{http_code}" https://yoursite.com/

Step 5: Monitor Impact

Track these metrics after changes:

• AI referral traffic (from Perplexity, ChatGPT, etc.)
• Brand mentions in AI responses (manual testing)
• Overall organic traffic (ensure no negative impact)

---

Emerging Crawlers to Watch

Recommendation: Monitor industry news and update robots.txt quarterly.

---

Supporting file: references/ai-writing-detection.md

AI Writing Detection

Words, phrases, and punctuation patterns commonly associated with AI-generated text. Avoid these to ensure writing sounds natural and human.

Sources: Grammarly (2025), Microsoft 365 Life Hacks (2025), GPTHuman (2025), Walter Writes (2025), Textero (2025), Plagiarism Today (2025), Rolling Stone (2025), MDPI Blog (2025)

---

Em Dashes: The Primary AI Tell

The em dash (—) has become one of the most reliable markers of AI-generated content.

Em dashes are longer than hyphens (-) and are used for emphasis, interruptions, or parenthetical information. While they have legitimate uses in writing, AI models drastically overuse them.

Why Em Dashes Signal AI Writing

• AI models were trained on edited books, academic papers, and style guides where em dashes appear frequently
• AI uses em dashes as a shortcut for sentence variety instead of commas, colons, or parentheses
• Most human writers rarely use em dashes because they don't exist as a standard keyboard key
• The overuse is so consistent that it has become the unofficial signature of ChatGPT writing

What To Do Instead

Guidelines

• Use commas for most parenthetical information
• Use colons to introduce explanations or lists
• Use parentheses for supplementary information
• Reserve em dashes for rare, deliberate emphasis only
• If you find yourself using more than one em dash per page, revise

---

Overused Verbs

---

Overused Adjectives

---

Overused Transitions and Connectors

---

Phrases That Signal AI Writing

Opening Phrases to Avoid

• "In today's fast-paced world..."
• "In today's digital age..."
• "In an era of..."
• "In the ever-evolving landscape of..."
• "In the realm of..."
• "It's important to note that..."
• "Let's delve into..."
• "Imagine a world where..."

Transitional Phrases to Avoid

• "That being said..."
• "With that in mind..."
• "It's worth mentioning that..."
• "At its core..."
• "To put it simply..."
• "In essence..."
• "This begs the question..."

Concluding Phrases to Avoid

• "In conclusion..."
• "To sum up..."
• "By [doing X], you can [achieve Y]..."
• "In the final analysis..."
• "All things considered..."
• "At the end of the day..."

Structural Patterns to Avoid

• "Whether you're a [X], [Y], or [Z]..." (listing three examples after "whether")
• "It's not just [X], it's also [Y]..."
• "Think of [X] as [elaborate metaphor]..."
• Starting sentences with "By" followed by a gerund: "By understanding X, you can Y..."

---

Filler Words and Empty Intensifiers

These words often add nothing to meaning. Remove them or find specific alternatives:

• absolutely
• actually
• basically
• certainly
• clearly
• definitely
• essentially
• extremely
• fundamentally
• incredibly
• interestingly
• naturally
• obviously
• quite
• really
• significantly
• simply
• surely
• truly
• ultimately
• undoubtedly
• very

---

Academic-Specific AI Tells

---

How to Self-Check

1. Read your text aloud. If phrases sound unnatural in speech, revise them
2. Ask: "Would I say this in a conversation with a colleague?"
3. Check for repetitive sentence structures
4. Look for clusters of the words listed above
5. Ensure varied sentence lengths (not all similar length)
6. Verify each intensifier adds genuine meaning

---

Supporting file: references/backlink-strategies.md

Backlink Strategy Playbooks

Detailed execution guides for each backlink strategy.

---

Link Stealing Playbook

Tools Required

• Ahrefs (Site Explorer, Backlinks)
• Hunter.io (email finder)
• Email client or outreach tool

Step-by-Step Process

1. Identify Target Keyword

Search: "AI headshot generator"
Find: Top ranking competitor (e.g., Canva)
Note: Exact URL of their ranking page

2. Analyze in Ahrefs

Site Explorer → Enter competitor URL
→ Backlinks tab
→ Filter: Dofollow only
→ Sort by: Domain Rating (high to low)

3. Evaluate Opportunities For each linking site, check:

□ Is it a blog/content site? (not a directory)
□ Does the article discuss your topic?
□ Is there room to add/replace your link?
□ What's the site's DA? (aim for 30+)

4. Find Contact Info

Hunter.io → Enter article URL
→ Get author/editor email
→ Verify email if possible

5. Craft Outreach

Subject: Re: Your [Article Title] article

Hi [Name],

I came across your piece on [topic] - really thorough comparison.

I noticed you mentioned [Competitor]. We recently launched [Product]
which [specific advantage - e.g., "uses the new Flux model for
2x better quality at half the price"].

Would you be open to testing it? I can set up a free account.
If you think it's worth including, that would be great - but no
pressure either way.

Best,
[Name]

6. Follow-Up Schedule

• Day 0: Initial email
• Day 4: First follow-up (if no response)
• Day 10: Final follow-up
• Stop after 3 attempts

Expected Results

• Response rate: 5-15%
• Conversion rate: 2-5% of outreach
• High-quality links from relevant sites

---

Affiliate Program Playbook

Setup Phase

1. Choose Platform

• Rewardful (recommended): Clean URLs, Stripe integration
• Alternatives: FirstPromoter, PartnerStack
• Budget: ~$200-300/month

2. Set Commission Structure

Standard: 30% recurring
Competitive: 40% recurring
Aggressive: 50% first payment + 30% recurring

3. Create Affiliate Assets

• Product screenshots
• Comparison graphics
• Key selling points
• Promo codes for affiliates

Recruiting Affiliates

Method 1: Steal Competitor Affiliates

Ahrefs → Site Explorer → competitor.com
→ Backlinks
→ Search: "?via=" or "?ref=" or "/ref/"
→ These are affiliate links
→ Contact each affiliate site

Outreach Template:

Subject: Double your affiliate income?

Hi [Name],

I noticed you're promoting [Competitor] on your site.

We're [Product] - similar product but [key differentiator].
Our conversion rate is [X%] and we're offering 40% commission
(vs their [X%]).

Would you like to test us out? Happy to send free access.

[Name]

Method 2: Affiliate Directories

• Post on affiliate forums
• List on affiliate networks
• Reach out to affiliate bloggers in niche

Managing Quality

Disavow Spammy Links:

1. Google Search Console → Links
2. Identify low-quality affiliate links
3. Disavow Tool → Upload list
4. Google ignores those links

---

Domain Acquisition Playbook

Finding Targets

1. Identify Candidates

• Old tool sites in your niche
• Abandoned projects with good DA
• Sites mentioned in old articles

2. Evaluate in Ahrefs

Check:
- Domain Rating (DR > 30 ideal)
- Number of referring domains
- Backlink quality (high DA sites linking)
- Domain age
- Any spam penalties

Outreach Template

Subject: Interested in acquiring [domain]

Hi,

I'm the founder of [Your Company]. I noticed [Domain] and
really appreciate what you built.

Are you open to discussing a potential acquisition? We'd be
interested in taking over the project.

If you're not looking to sell right now, no worries - just
wanted to reach out.

Best,
[Name]

Negotiation Tips

• Start at 50% of asking price
• Use Ahrefs data to justify valuation
• Consider domain age heavily
• Check for any Google penalties first

Post-Acquisition

Option 1: Link then Redirect

1. Keep site running, add links to your main site
2. Wait 1-2 months for Google to crawl
3. Then 301 redirect entire domain

Option 2: Immediate Redirect

1. 301 redirect all pages to relevant pages on your site
2. Faster but may lose some link value

---

HARO Playbook

Setup

1. Sign up at helpareporter.com
2. Sign up at helpab2bwriter.com
3. Set email frequency: Daily (recommended)
4. Filter by relevant categories

Daily Process

Morning (15-30 min):

1. Review incoming queries
2. Identify 2-3 relevant opportunities
3. Draft responses

Response Structure

SUBJECT: Re: [Query Topic] - Expert Response

Hi [Reporter Name],

[1-2 sentence intro establishing credibility]

[Direct answer to their question - 100-200 words]

[Supporting example or data point]

[Optional: Offer for follow-up interview]

---
[Name]
[Title], [Company]
[Credentials: X followers, featured in Y, Z years experience]
[Link to profile/site]

Differentiation Tips

Stand Out from AI Spam:

• Include Loom video explanation
• Reference specific recent events
• Provide unique data/statistics
• Share personal anecdotes
• Respond within 2 hours of query

Outsourcing

1. Hire VA to monitor and draft responses
2. VA sends drafts for your review
3. You add personal authority/edits
4. You send final response
5. Cost: ~$500/month for 10-20 responses

---

Case Study Exchange Playbook

Finding Opportunities

Identify Tools You Use:

□ Analytics tools
□ Marketing tools
□ Development tools
□ Design tools
□ Productivity tools

Evaluate Each:

• Do they have a case studies page?
• How many case studies do they have?
• Are they actively collecting?

Priority Order:

1. Tools with <10 case studies (hungry for content)
2. Newer tools building credibility
3. Tools where you have impressive results

Outreach Template

Subject: Case study offer - [Your Company] + [Their Tool]

Hi [Team],

We've been using [Tool] for [duration] and wanted to share
our results:

- [Metric 1: e.g., "Increased conversions by 40%"]
- [Metric 2: e.g., "Saved 10 hours/week"]
- [Metric 3: e.g., "Grew from $5K to $50K MRR"]

Would you be interested in featuring our story? We're happy
to do an interview, provide screenshots, whatever helps.

We'd just ask for a backlink to [your site] in the case study.

Best,
[Name]
[Company]

After Agreement

Be responsive and provide:

• Detailed answers to questions
• Screenshots with permission
• Metrics and data
• Quotes and testimonials
• Logo for their page

---

Content Ring Playbook

Planning

Identify Tool Opportunities:

□ Related to your main product
□ Can be built quickly (1-2 weeks)
□ Has some SEO potential itself
□ Provides genuine user value

Example Ring for HeadshotPro:

Main: HeadshotPro.com (AI headshots)
├── ProfilePicture.ai (free profile pic generator)
├── LinkedInGenerator.com (LinkedIn profile helper)
├── BackgroundRemover.io (background removal tool)
└── PhotoEnhancer.app (image enhancement)

Implementation

Each Tool Should Have:

• Real utility (not just a link farm)
• Basic SEO optimization
• Footer link to main product
• Occasional in-content CTAs

Launch Process:

1. Build and launch tool
2. Basic SEO setup (title, meta, content)
3. Add links to main product
4. Submit to Product Hunt / directories
5. Let Google index naturally

Maintenance

• Keep tools functional
• Update occasionally for freshness
• Monitor for any issues
• Don't overdo it (3-5 tools max)

---

Outreach Email Templates

Cold Outreach - Feature Request

Subject: [Product] for your [content type]?

Hi [Name],

Love your content on [topic]. Your piece on [specific article]
was particularly helpful.

We built [Product] that [key benefit]. Thought it might be
interesting for your readers since [relevance].

Happy to set you up with free access if you'd like to check
it out. No pressure to write about it - just thought you
might find it useful.

Best,
[Name]

Follow-Up Template

Subject: Re: [Original subject]

Hi [Name],

Just floating this back up in case it got buried.

Quick reminder: [Product] - [one-line value prop].

If it's not a fit, no worries at all. Just let me know
either way?

Thanks,
[Name]

Broken Link Outreach

Subject: Broken link on your [page title]

Hi [Name],

I was reading your article on [topic] and noticed the link
to [broken resource] is no longer working.

I recently published [your content] that covers similar
ground. Might be a good replacement?

[URL]

Either way, wanted to give you a heads up on the broken link.

Best,
[Name]

Guest Post Pitch

Subject: Guest post idea: [Topic]

Hi [Name],

I've been following [Site] and really enjoy your content on [niche].

I'd love to contribute a guest post on [specific topic].
I'm thinking something like:

"[Proposed Title]"
- [Bullet 1]
- [Bullet 2]
- [Bullet 3]

I'm [brief credentials]. Here are a few examples of my writing:
- [Link 1]
- [Link 2]

Would this be a fit?

Best,
[Name]

---

Tracking Spreadsheet Template

Outreach Tracker

Backlink Tracker

Monthly Metrics

---

Supporting file: references/content-patterns.md

AEO and GEO Content Patterns

Reusable content block patterns optimized for answer engines and AI citation.

---

Contents

• Answer Engine Optimization (AEO) Patterns (Definition Block, Step-by-Step Block, Comparison Table Block, Pros and Cons Block, FAQ Block, Listicle Block)
• Generative Engine Optimization (GEO) Patterns (Statistic Citation Block, Expert Quote Block, Authoritative Claim Block, Self-Contained Answer Block, Evidence Sandwich Block)
• Domain-Specific GEO Tactics (Technology Content, Health/Medical Content, Financial Content, Legal Content, Business/Marketing Content)
• Voice Search Optimization (Question Formats for Voice, Voice-Optimized Answer Structure)

Answer Engine Optimization (AEO) Patterns

These patterns help content appear in featured snippets, AI Overviews, voice search results, and answer boxes.

Definition Block

Use for "What is [X]?" queries.

## What is [Term]?

[Term] is [concise 1-sentence definition]. [Expanded 1-2 sentence explanation with key characteristics]. [Brief context on why it matters or how it's used].

Example:

## What is Answer Engine Optimization?

Answer Engine Optimization (AEO) is the practice of structuring content so AI-powered systems can easily extract and present it as direct answers to user queries. Unlike traditional SEO that focuses on ranking in search results, AEO optimizes for featured snippets, AI Overviews, and voice assistant responses. This approach has become essential as over 60% of Google searches now end without a click.

Step-by-Step Block

Use for "How to [X]" queries. Optimal for list snippets.

## How to [Action/Goal]

[1-sentence overview of the process]

1. **[Step Name]**: [Clear action description in 1-2 sentences]
2. **[Step Name]**: [Clear action description in 1-2 sentences]
3. **[Step Name]**: [Clear action description in 1-2 sentences]
4. **[Step Name]**: [Clear action description in 1-2 sentences]
5. **[Step Name]**: [Clear action description in 1-2 sentences]

[Optional: Brief note on expected outcome or time estimate]

Example:

## How to Optimize Content for Featured Snippets

Earning featured snippets requires strategic formatting and direct answers to search queries.

1. **Identify snippet opportunities**: Use tools like Semrush or Ahrefs to find keywords where competitors have snippets you could capture.
2. **Match the snippet format**: Analyze whether the current snippet is a paragraph, list, or table, and format your content accordingly.
3. **Answer the question directly**: Provide a clear, concise answer (40-60 words for paragraph snippets) immediately after the question heading.
4. **Add supporting context**: Expand on your answer with examples, data, and expert insights in the following paragraphs.
5. **Use proper heading structure**: Place your target question as an H2 or H3, with the answer immediately following.

Most featured snippets appear within 2-4 weeks of publishing well-optimized content.

Comparison Table Block

Use for "[X] vs [Y]" queries. Optimal for table snippets.

## [Option A] vs [Option B]: [Brief Descriptor]

| Feature | [Option A] | [Option B] |
|---------|------------|------------|
| [Criteria 1] | [Value/Description] | [Value/Description] |
| [Criteria 2] | [Value/Description] | [Value/Description] |
| [Criteria 3] | [Value/Description] | [Value/Description] |
| [Criteria 4] | [Value/Description] | [Value/Description] |
| Best For | [Use case] | [Use case] |

**Bottom line**: [1-2 sentence recommendation based on different needs]

Pros and Cons Block

Use for evaluation queries: "Is [X] worth it?", "Should I [X]?"

## Advantages and Disadvantages of [Topic]

[1-sentence overview of the evaluation context]

### Pros

- **[Benefit category]**: [Specific explanation]
- **[Benefit category]**: [Specific explanation]
- **[Benefit category]**: [Specific explanation]

### Cons

- **[Drawback category]**: [Specific explanation]
- **[Drawback category]**: [Specific explanation]
- **[Drawback category]**: [Specific explanation]

**Verdict**: [1-2 sentence balanced conclusion with recommendation]

FAQ Block

Use for topic pages with multiple common questions. Essential for FAQ schema.

## Frequently Asked Questions

### [Question phrased exactly as users search]?

[Direct answer in first sentence]. [Supporting context in 2-3 additional sentences].

### [Question phrased exactly as users search]?

[Direct answer in first sentence]. [Supporting context in 2-3 additional sentences].

### [Question phrased exactly as users search]?

[Direct answer in first sentence]. [Supporting context in 2-3 additional sentences].

Tips for FAQ questions:

• Use natural question phrasing ("How do I..." not "How does one...")
• Include question words: what, how, why, when, where, who, which
• Match "People Also Ask" queries from search results
• Keep answers between 50-100 words

Listicle Block

Use for "Best [X]", "Top [X]", "[Number] ways to [X]" queries.

## [Number] Best [Items] for [Goal/Purpose]

[1-2 sentence intro establishing context and selection criteria]

### 1. [Item Name]

[Why it's included in 2-3 sentences with specific benefits]

### 2. [Item Name]

[Why it's included in 2-3 sentences with specific benefits]

### 3. [Item Name]

[Why it's included in 2-3 sentences with specific benefits]

---

Generative Engine Optimization (GEO) Patterns

These patterns optimize content for citation by AI assistants like ChatGPT, Claude, Perplexity, and Gemini.

Statistic Citation Block

Statistics increase AI citation rates by 15-30%. Always include sources.

[Claim statement]. According to [Source/Organization], [specific statistic with number and timeframe]. [Context for why this matters].

Example:

Mobile optimization is no longer optional for SEO success. According to Google's 2024 Core Web Vitals report, 70% of web traffic now comes from mobile devices, and pages failing mobile usability standards see 24% higher bounce rates. This makes mobile-first indexing a critical ranking factor.

Expert Quote Block

Named expert attribution adds credibility and increases citation likelihood.

"[Direct quote from expert]," says [Expert Name], [Title/Role] at [Organization]. [1 sentence of context or interpretation].

Example:

"The shift from keyword-driven search to intent-driven discovery represents the most significant change in SEO since mobile-first indexing," says Rand Fishkin, Co-founder of SparkToro. This perspective highlights why content strategies must evolve beyond traditional keyword optimization.

Authoritative Claim Block

Structure claims for easy AI extraction with clear attribution.

[Topic] [verb: is/has/requires/involves] [clear, specific claim]. [Source] [confirms/reports/found] that [supporting evidence]. This [explains/means/suggests] [implication or action].

Example:

E-E-A-T is the cornerstone of Google's content quality evaluation. Google's Search Quality Rater Guidelines confirm that trust is the most critical factor, stating that "untrustworthy pages have low E-E-A-T no matter how experienced, expert, or authoritative they may seem." This means content creators must prioritize transparency and accuracy above all other optimization tactics.

Self-Contained Answer Block

Create quotable, standalone statements that AI can extract directly.

**[Topic/Question]**: [Complete, self-contained answer that makes sense without additional context. Include specific details, numbers, or examples in 2-3 sentences.]

Example:

**Ideal blog post length for SEO**: The optimal length for SEO blog posts is 1,500-2,500 words for competitive topics. This range allows comprehensive topic coverage while maintaining reader engagement. HubSpot research shows long-form content earns 77% more backlinks than short articles, directly impacting search rankings.

Evidence Sandwich Block

Structure claims with evidence for maximum credibility.

[Opening claim statement].

Evidence supporting this includes:
- [Data point 1 with source]
- [Data point 2 with source]
- [Data point 3 with source]

[Concluding statement connecting evidence to actionable insight].

---

Domain-Specific GEO Tactics

Different content domains benefit from different authority signals.

Technology Content

• Emphasize technical precision and correct terminology
• Include version numbers and dates for software/tools
• Reference official documentation
• Add code examples where relevant

Health/Medical Content

• Cite peer-reviewed studies with publication details
• Include expert credentials (MD, RN, etc.)
• Note study limitations and context
• Add "last reviewed" dates

Financial Content

• Reference regulatory bodies (SEC, FTC, etc.)
• Include specific numbers with timeframes
• Note that information is educational, not advice
• Cite recognized financial institutions

Legal Content

• Cite specific laws, statutes, and regulations
• Reference jurisdiction clearly
• Include professional disclaimers
• Note when professional consultation is advised

Business/Marketing Content

• Include case studies with measurable results
• Reference industry research and reports
• Add percentage changes and timeframes
• Quote recognized thought leaders

---

Voice Search Optimization

Voice queries are conversational and question-based. Optimize for these patterns:

Question Formats for Voice

• "What is..."
• "How do I..."
• "Where can I find..."
• "Why does..."
• "When should I..."
• "Who is..."

Voice-Optimized Answer Structure

• Lead with direct answer (under 30 words ideal)
• Use natural, conversational language
• Avoid jargon unless targeting expert audience
• Include local context where relevant
• Structure for single spoken response

---

Supporting file: references/content-templates.md

GEO/AEO Content Templates

Table of Contents

1. Definitional Content Template (#definitional-content-template)
2. How-To Content Template (#how-to-content-template)
3. Comparison Content Template (#comparison-content-template)
4. FAQ-Optimized Template (#faq-optimized-template)
5. Product/Service Template (#productservice-template)
6. Writing Guidelines (#writing-guidelines)

---

Definitional Content Template

Best for: "What is X?" queries, concept explanations

# What is [Topic]? [Subtitle with Context]

**TL;DR:** [Topic] is [concise 1-sentence definition]. [1-2 sentences on why it matters or key application].

## Definition

[Topic] is [expanded definition in 2-3 sentences]. [Include key characteristics].

> **Quick Definition:** [15-word definition suitable for snippet extraction]

## How [Topic] Works

[Explanation paragraph - use simple, clear language]

### Key Components

| Component | Purpose | Example |
|-----------|---------|---------|
| [Item 1] | [What it does] | [Concrete example] |
| [Item 2] | [What it does] | [Concrete example] |
| [Item 3] | [What it does] | [Concrete example] |

## Benefits of [Topic]

1. **[Benefit 1]**: [Explanation in 1-2 sentences]
2. **[Benefit 2]**: [Explanation in 1-2 sentences]
3. **[Benefit 3]**: [Explanation in 1-2 sentences]

## Common Use Cases

- **[Use case 1]**: [Brief description]
- **[Use case 2]**: [Brief description]
- **[Use case 3]**: [Brief description]

## FAQ

### What is the difference between [Topic] and [Related Topic]?
[Clear answer in 2-3 sentences]

### Who should use [Topic]?
[Clear answer identifying target audience]

### How do I get started with [Topic]?
[Actionable first steps]

## Summary

[2-3 sentence recap of key points - this is another extraction opportunity]

---
*Last updated: [Date] | Author: [Name, Credentials]*
*Sources: [List key sources for credibility]*

---

How-To Content Template

Best for: Process queries, tutorials, step-by-step guides

# How to [Action]: [Subtitle with Benefit]

**TL;DR:** To [action], you need to [high-level steps in 1 sentence]. This process takes approximately [time estimate] and requires [key requirements].

## Quick Overview

| | |
|---|---|
| **Time Required** | [X minutes/hours] |
| **Difficulty** | [Beginner/Intermediate/Advanced] |
| **What You'll Need** | [Key requirements] |
| **Expected Result** | [What user will achieve] |

## Before You Start

### Prerequisites
- [Requirement 1]
- [Requirement 2]
- [Requirement 3]

### Tools/Materials Needed
- [Tool 1] - [why needed]
- [Tool 2] - [why needed]

## Step-by-Step Instructions

### Step 1: [Action Verb + What]

[1-2 sentences explaining this step]

**How to do it:**
1. [Sub-step a]
2. [Sub-step b]
3. [Sub-step c]

> **Pro Tip:** [Helpful insight for this step]

### Step 2: [Action Verb + What]

[1-2 sentences explaining this step]

**How to do it:**
1. [Sub-step a]
2. [Sub-step b]

⚠️ **Warning:** [Common mistake to avoid]

### Step 3: [Action Verb + What]

[Continue pattern...]

## Troubleshooting

### [Common Problem 1]
**Cause:** [Why this happens]
**Solution:** [How to fix]

### [Common Problem 2]
**Cause:** [Why this happens]
**Solution:** [How to fix]

## FAQ

### How long does it take to [action]?
[Direct answer with context]

### What if [common concern]?
[Reassuring answer with solution]

### Can I [related question]?
[Clear yes/no with explanation]

## Summary

You've learned how to [action]. The key steps are:
1. [Step 1 summary]
2. [Step 2 summary]
3. [Step 3 summary]

---
*Last updated: [Date] | Author: [Name, Credentials]*

---

Comparison Content Template

Best for: "X vs Y" queries, decision-making content

# [Option A] vs [Option B]: [What You Need to Know in 2025]

**TL;DR:** [Option A] is best for [use case], while [Option B] excels at [different use case]. Choose [A] if [criteria]; choose [B] if [other criteria].

## Quick Comparison

| Feature | [Option A] | [Option B] |
|---------|------------|------------|
| **Best For** | [Primary use case] | [Primary use case] |
| **Price** | [Range] | [Range] |
| **Ease of Use** | [Rating/description] | [Rating/description] |
| **Key Strength** | [Main advantage] | [Main advantage] |
| **Key Weakness** | [Main drawback] | [Main drawback] |

## [Option A] Overview

### What is [Option A]?
[2-3 sentence definition]

### Pros
- ✅ [Advantage 1]
- ✅ [Advantage 2]
- ✅ [Advantage 3]

### Cons
- ❌ [Disadvantage 1]
- ❌ [Disadvantage 2]

### Best For
[Option A] is ideal for [specific users/situations] because [reason].

## [Option B] Overview

### What is [Option B]?
[2-3 sentence definition]

### Pros
- ✅ [Advantage 1]
- ✅ [Advantage 2]
- ✅ [Advantage 3]

### Cons
- ❌ [Disadvantage 1]
- ❌ [Disadvantage 2]

### Best For
[Option B] is ideal for [specific users/situations] because [reason].

## Detailed Comparison

### [Criteria 1]: [Option A] vs [Option B]
[Detailed comparison - 2-3 paragraphs]

**Winner:** [Option X] - [1 sentence reason]

### [Criteria 2]: [Option A] vs [Option B]
[Detailed comparison - 2-3 paragraphs]

**Winner:** [Option X] - [1 sentence reason]

### [Criteria 3]: [Option A] vs [Option B]
[Detailed comparison - 2-3 paragraphs]

**Winner:** [Option X] - [1 sentence reason]

## Which Should You Choose?

### Choose [Option A] if:
- [Condition 1]
- [Condition 2]
- [Condition 3]

### Choose [Option B] if:
- [Condition 1]
- [Condition 2]
- [Condition 3]

## FAQ

### Is [Option A] better than [Option B]?
[Nuanced answer - "it depends on..."]

### Can I use both [Option A] and [Option B]?
[Clear answer]

### What's the main difference between [A] and [B]?
[1-2 sentence core difference]

## Conclusion

**Our Recommendation:** For [most common use case], we recommend [Option X] because [key reason]. However, if [alternative scenario], [Option Y] is the better choice.

---
*Last updated: [Date] | Author: [Name, Credentials]*
*Methodology: [How comparison was conducted]*

---

FAQ-Optimized Template

Best for: Question clusters, comprehensive topic coverage

# [Topic]: Frequently Asked Questions

**TL;DR:** This guide answers the most common questions about [topic], including [key question areas]. Last updated [Date].

## Quick Answers

| Question | Short Answer |
|----------|--------------|
| [Question 1]? | [10-word answer] |
| [Question 2]? | [10-word answer] |
| [Question 3]? | [10-word answer] |

## Detailed FAQ

### Basic Questions

#### What is [topic]?
[2-3 sentence complete answer that can stand alone]

#### Why is [topic] important?
[Complete answer with specific benefits/reasons]

#### Who needs [topic]?
[Clear description of target audience with examples]

### How-To Questions

#### How do I [common action]?
[Step-by-step answer, can be brief list]

#### How long does [process] take?
[Specific timeframe with context]

#### How much does [topic] cost?
[Price range with factors that affect cost]

### Comparison Questions

#### What's the difference between [X] and [Y]?
[Clear distinction in 2-3 sentences]

#### Is [topic] better than [alternative]?
[Balanced answer with "it depends" context]

### Troubleshooting Questions

#### What if [common problem]?
[Solution-focused answer]

#### Why isn't [expected outcome] happening?
[Diagnostic approach with solutions]

### Advanced Questions

#### Can I [advanced use case]?
[Yes/no with explanation and how-to if applicable]

#### What are the limitations of [topic]?
[Honest assessment of boundaries]

## Still Have Questions?

[Call to action - contact, comment, related resources]

---
*Last updated: [Date] | Expert: [Name, Credentials]*

---

Writing Guidelines

For AI Extraction Optimization

Lead with the Answer

❌ "In this article, we'll explore what SEO means..."
✅ "SEO (Search Engine Optimization) is the practice of improving website visibility in search results."

Use Complete Sentences

❌ "Benefits: faster, cheaper, better"
✅ "The main benefits include faster processing times, lower costs, and improved quality."

Be Specific with Numbers

❌ "This can significantly improve results"
✅ "This typically improves results by 25-40% within 3 months"

Attribute Claims

❌ "Studies show that..."
✅ "According to a 2024 HubSpot study of 5,000 websites..."

Format for Scanning

- Use bullet points for 3+ items
- Bold key terms on first use
- Keep paragraphs under 4 sentences
- Use tables for comparisons
- Include clear section headers

Word Count Guidelines

---

Supporting file: references/geo-research.md

GEO Research: Princeton Study & Optimization Methods

Paper Overview

Title: GEO: Generative Engine Optimization
Authors: Princeton University, IIT Delhi, Georgia Tech, Allen Institute for AI
Published: November 2023 (arXiv:2311.09735)
Accepted: KDD 2024 (30th ACM SIGKDD Conference)
Link: https://arxiv.org/abs/2311.09735

---

Key Findings

What is GEO?

Generative Engine Optimization (GEO) is a novel framework to help content creators improve their visibility in generative engine responses (AI search engines like ChatGPT, Perplexity, Google SGE).

Unlike traditional SEO (ranking in search results), GEO focuses on being cited by AI systems.

Core Results

Why GEO Matters

1. Traditional search engines are being replaced by generative engines
2. Content creators have little control over how their content appears in AI responses
3. GEO provides systematic methods to improve visibility
4. Different domains need different strategies - no one-size-fits-all

---

The 9 Optimization Methods

Method 1: Cite Sources (+40%)

What: Add authoritative citations and references to your content.

Why it works: AI systems prefer content that appears well-researched and credible. Citations signal authority.

How to apply:

# Before
"Studies show that AI improves productivity."

# After
"According to a 2024 Stanford University study, AI tools improve developer 
productivity by 55% on average (Chen et al., 2024)."

Best for: All content types, especially academic/professional topics.

---

Method 2: Statistics Addition (+37%)

What: Include specific numbers, data points, and quantitative information.

Why it works: AI systems prioritize factual, verifiable information. Numbers make content more quotable.

How to apply:

# Before
"Many companies use AI for customer service."

# After
"67% of Fortune 500 companies now use AI chatbots for customer service, 
handling an average of 85% of routine inquiries without human intervention."

Best for: Business, finance, technology, health content.

---

Method 3: Quotation Addition (+30%)

What: Add expert quotes with proper attribution.

Why it works: Quotes from recognized experts boost credibility and provide extractable content for AI.

How to apply:

# Before
"AI will transform the workforce."

# After
"'We're likely to see the first one-person billion-dollar company in the 
next few years,' predicts Sam Altman, CEO of OpenAI. 'AI will be the 
great equalizer for small businesses.'"

Best for: Law, academic, news, thought leadership content.

---

Method 4: Authoritative Tone (+25%)

What: Write with confidence and expertise.

Why it works: AI systems assess content quality partly through linguistic signals of authority.

How to apply:

# Before
"This might help with SEO, I think."

# After
"This strategy demonstrably improves SEO performance. Based on our 
analysis of 10,000 websites, implementing structured data increases 
organic traffic by an average of 30%."

Best for: Business, professional services, technical documentation.

---

Method 5: Easy-to-Understand (+20%)

What: Simplify complex concepts for broader accessibility.

Why it works: AI aims to provide helpful answers to users of all knowledge levels.

How to apply:

# Before
"The RAG architecture utilizes vector embeddings for semantic retrieval 
in conjunction with LLM-based generation."

# After
"RAG (Retrieval-Augmented Generation) works like a research assistant: 
it first searches for relevant information, then uses AI to write a 
coherent answer based on what it found."

Best for: Health, education, general consumer content.

---

Method 6: Technical Terms (+18%)

What: Include domain-specific terminology appropriately.

Why it works: Technical terms signal expertise and help AI match content to specialized queries.

How to apply:

# Before
"The website loads slowly."

# After
"The website suffers from poor Core Web Vitals: LCP (Largest Contentful 
Paint) exceeds 4 seconds, and CLS (Cumulative Layout Shift) scores 0.3, 
indicating significant layout instability."

Best for: Technology, science, medical, legal content.

---

Method 7: Unique Words (+15%)

What: Increase vocabulary diversity and use distinctive phrasing.

Why it works: Diverse vocabulary indicates depth of knowledge and makes content more distinguishable.

How to apply:

• Use synonyms and varied terminology
• Avoid repetitive phrasing
• Include industry-specific jargon where appropriate
• Add contextual variations

Best for: All content types.

---

Method 8: Fluency Optimization (+15-30%)

What: Improve readability, flow, and grammatical quality.

Why it works: Well-written content is easier for AI to parse and more likely to be selected as authoritative.

How to apply:

• Use clear sentence structure
• Maintain logical flow between paragraphs
• Eliminate redundancy
• Use transition words
• Keep paragraphs focused (2-3 sentences)

Best for: All content types.

---

Method 9: Keyword Stuffing (-10%) ⚠️

What: Overloading content with target keywords.

Why it HURTS: Unlike traditional SEO, keyword stuffing actively decreases AI visibility.

Avoid:

# BAD - Keyword stuffing
"SEO optimization for SEO is the best SEO strategy. Our SEO experts 
provide SEO services for all your SEO needs. SEO is important for SEO."

# GOOD - Natural writing
"Search engine optimization is essential for online visibility. Our 
experts help businesses improve their search rankings through strategic 
content development and technical improvements."

---

Best Combinations

The Princeton research found that combining methods yields better results:

---

Domain-Specific Recommendations

---

GEO Metrics

The paper introduces visibility metrics for evaluating GEO effectiveness:

Position-Adjusted Word Count

Measures how much of your content appears in AI responses, weighted by position (earlier = better).

Subjective Impression Score

Human evaluation of how prominently your content is featured in responses.

Word Count Share

Percentage of AI response that comes from your content vs. competitors.

---

Implementation Checklist

Content Optimization

• Add 2-3 authoritative citations per major section
• Include at least 5 relevant statistics with sources
• Add 1-2 expert quotes with attribution
• Use confident, authoritative language
• Ensure content is accessible to general audience
• Include appropriate technical terminology
• Vary vocabulary throughout
• Improve overall fluency and readability
• Remove any keyword stuffing

Structure Optimization

• Use "answer-first" format (direct answer at top)
• Clear H1 > H2 > H3 hierarchy
• Bullet points for lists
• Tables for comparisons
• Short paragraphs (2-3 sentences)
• Logical flow between sections

Schema Optimization

• Implement FAQPage schema (+40% AI visibility)
• Add Article schema with author info
• Include datePublished and dateModified
• Add SpeakableSpecification for voice search

---

Validation on Commercial Platforms

The researchers validated GEO methods on Perplexity.ai, a commercial generative engine:

These results confirm that GEO methods work on real-world AI search engines, not just research benchmarks.

---

Future of GEO

The paper concludes that GEO is essential for:

1. Content creators - Maintain visibility in AI-dominated search
2. Businesses - Ensure brand presence in AI responses
3. Publishers - Adapt to the citation economy
4. SEO professionals - Evolve practices for generative search

As AI search engines become more prevalent, GEO will become as important as traditional SEO.

---

Supporting file: references/google-docs-summary.md

Google Official SEO Documentation Summary

Quick reference from Google Search Central.

---

Search Three-Stage Process

---

Core Web Vitals

---

Structured Data Types

---

Spam Policies (Avoid)

• Keyword stuffing
• Hidden text/links
• Link schemes
• Auto-generated content
• Scraped content
• Cloaking

---

Official Tools

---

Reference

• https://developers.google.com/search
• https://developers.google.com/search/docs/fundamentals/seo-starter-guide

---

Supporting file: references/platform-algorithms.md

Platform Ranking Algorithms

Detailed ranking factors for AI search engines and traditional search engines (2025-2026).

---

1. ChatGPT Ranking Factors

Core Ranking System

ChatGPT uses a two-phase system:

1. Pre-training Knowledge - Built from diverse datasets (Wikipedia, books, web)
2. Real-time Retrieval - Web browsing for current information

Ranking Factor Weights

Key Findings (SE Ranking Study - 129K domains)

ChatGPT Top Citation Sources

Content-Answer Fit Analysis (400K pages study)

Optimization Checklist

• Build strong backlink profile (quality > quantity)
• Update content within 30 days
• Use clear H1/H2/H3 structure
• Include verifiable statistics with citations
• Write in ChatGPT's conversational style
• Ensure domain has high trust score

---

2. Perplexity AI Ranking Factors

Architecture

Perplexity uses Retrieval-Augmented Generation (RAG) with a 3-layer reranking system:

1. Layer 1 (L1): Basic relevance retrieval
2. Layer 2 (L2): Traditional ranking factors scoring
3. Layer 3 (L3): ML models for quality evaluation (can discard entire result sets)

Core Ranking Factors

Perplexity Sonar Model Insights

Technical Requirements

# robots.txt - Allow PerplexityBot
User-agent: PerplexityBot
Allow: /

# Provide clean sitemap
Sitemap: https://example.com/sitemap.xml

Optimization Checklist

• Allow PerplexityBot in robots.txt
• Implement FAQ Schema markup
• Create publicly accessible PDF resources
• Use Article schema with timestamps
• Focus on semantic relevance, not keywords
• Build topical authority in your niche

---

3. Google AI Overview (SGE) Ranking Factors

Architecture

Google AI Overviews use multiple AI models:

• PaLM2 - Language understanding
• MUM - Multimodal understanding
• Gemini - Advanced reasoning

5-Stage Source Prioritization Pipeline

1. Retrieval - Identify candidate sources
2. Semantic Ranking - Evaluate topical relevance
3. LLM Re-ranking - Assess contextual fit (using Gemini)
4. E-E-A-T Evaluation - Filter for expertise/authority/trust
5. Data Fusion - Synthesize from multiple sources with citations

Key Statistics

Ranking Factors

Content Requirements

Traditional SEO still matters:
- Quality backlinks
- Original, helpful content
- Fast page speed
- Mobile-friendly design
- Secure (HTTPS)

Optimization Checklist

• Implement comprehensive Schema markup
• Build topical authority with content clusters
• Include authoritative citations and references
• Use E-E-A-T signals (author bios, credentials)
• Optimize for Google Merchant Center (e-commerce)
• Target informational "how-to" queries

---

4. Microsoft Copilot / Bing AI Ranking Factors

Architecture

Copilot is integrated into:

• Microsoft Edge browser
• Windows 11
• Microsoft 365 apps
• Bing Search

Uses Bing Index as primary data source.

Ranking Factors

Technical Requirements

# robots.txt
User-agent: Bingbot
Allow: /

User-agent: msnbot
Allow: /

# Submit to Bing Webmaster Tools
# Use IndexNow for faster indexing

Optimization Checklist

• Submit site to Bing Webmaster Tools
• Ensure Bingbot can crawl all pages
• Use IndexNow for new content
• Optimize page speed (< 2 seconds)
• Clear entity definitions in content
• Build presence on LinkedIn, GitHub

---

5. Claude AI Ranking Factors

Architecture

Important: Claude uses Brave Search, NOT Google or Bing!

Claude decides when to search based on:

• Query freshness requirements
• Specificity of question
• User intent

Ranking Factors

Key Statistic

Crawl-to-Refer Ratio: 38,065:1

• Claude consumes massive amounts of content
• Very selective about what it cites
• Quality and relevance are critical

Technical Requirements

# robots.txt
User-agent: ClaudeBot
Allow: /

User-agent: anthropic-ai
Allow: /

Optimization Checklist

• Ensure Brave Search indexing
• Allow ClaudeBot in robots.txt
• Create high factual density content
• Use clear, extractable structure
• Include verifiable data points
• Cite authoritative sources

---

6. Traditional Google SEO Ranking Factors (2026)

Core Ranking Systems

Top 10 Ranking Factors

Core Web Vitals

E-E-A-T Guidelines

Optimization Checklist

• Build quality backlinks (guest posts, PR, original research)
• Create comprehensive, original content
• Optimize Core Web Vitals
• Ensure mobile-friendly design
• Use HTTPS
• Implement Schema markup
• Match content to search intent
• Update content regularly
• Add author bios with credentials
• Include E-E-A-T signals

---

Cross-Platform Optimization Summary

Universal Best Practices

1. Allow all major bots in robots.txt
2. Implement Schema markup (FAQPage, Article, Organization)
3. Build authoritative backlinks
4. Update content regularly (within 30 days)
5. Use clear structure (H1 > H2 > H3, lists, tables)
6. Include statistics and citations
7. Optimize page speed (< 2 seconds)
8. Ensure mobile-friendly design

---

Supporting file: references/platform-ranking-factors.md

How Each AI Platform Picks Sources

Each AI search platform has its own search index, ranking logic, and content preferences. This guide covers what matters for getting cited on each one.

Sources cited throughout: Princeton GEO study (KDD 2024), SE Ranking domain authority study, ZipTie content-answer fit analysis.

---

The Fundamentals

Every AI platform shares three baseline requirements:

1. Your content must be in their index — Each platform uses a different search backend (Google, Bing, Brave, or their own). If you're not indexed, you can't be cited.
2. Your content must be crawlable — AI bots need access via robots.txt. Block the bot, lose the citation.
3. Your content must be extractable — AI systems pull passages, not pages. Clear structure and self-contained paragraphs win.

Beyond these basics, each platform weights different signals. Here's what matters and where.

---

Google AI Overviews

Google AI Overviews pull from Google's own index and lean heavily on E-E-A-T signals (Experience, Expertise, Authoritativeness, Trustworthiness). They appear in roughly 45% of Google searches.

What makes Google AI Overviews different: They already have your traditional SEO signals — backlinks, page authority, topical relevance. The additional AI layer adds a preference for content with cited sources and structured data. Research shows that including authoritative citations in your content correlates with a 132% visibility boost, and writing with an authoritative (not salesy) tone adds another 89%.

Importantly, AI Overviews don't just recycle the traditional Top 10. Only about 15% of AI Overview sources overlap with conventional organic results. Pages that wouldn't crack page 1 in traditional search can still get cited if they have strong structured data and clear, extractable answers.

What to focus on:

• Schema markup is the single biggest lever — Article, FAQPage, HowTo, and Product schemas give AI Overviews structured context to work with (30-40% visibility boost)
• Build topical authority through content clusters with strong internal linking
• Include named, sourced citations in your content (not just claims)
• Author bios with real credentials matter — E-E-A-T is weighted heavily
• Get into Google's Knowledge Graph where possible (an accurate Wikipedia entry helps)
• Target "how to" and "what is" query patterns — these trigger AI Overviews most often

---

ChatGPT

ChatGPT's web search draws from a Bing-based index. It combines this with its training knowledge to generate answers, then cites the web sources it relied on.

What makes ChatGPT different: Domain authority matters more here than on other AI platforms. An SE Ranking analysis of 129,000 domains found that authority and credibility signals account for roughly 40% of what determines citation, with content quality at about 35% and platform trust at 25%. Sites with very high referring domain counts (350K+) average 8.4 citations per response, while sites with slightly lower trust scores (91-96 vs 97-100) drop from 8.4 to 6 citations.

Freshness is a major differentiator. Content updated within the last 30 days gets cited about 3.2x more often than older content. ChatGPT clearly favors recent information.

The most important signal is content-answer fit — a ZipTie analysis of 400,000 pages found that how well your content's style and structure matches ChatGPT's own response format accounts for about 55% of citation likelihood. This is far more important than domain authority (12%) or on-page structure (14%) alone. Write the way ChatGPT would answer the question, and you're more likely to be the source it cites.

Where ChatGPT looks beyond your site: Wikipedia accounts for 7.8% of all ChatGPT citations, Reddit for 1.8%, and Forbes for 1.1%. Brand official sites are cited frequently but third-party mentions carry significant weight.

What to focus on:

• Invest in backlinks and domain authority — it's the strongest baseline signal
• Update competitive content at least monthly
• Structure your content the way ChatGPT structures its answers (conversational, direct, well-organized)
• Include verifiable statistics with named sources
• Clean heading hierarchy (H1 > H2 > H3) with descriptive headings

---

Perplexity

Perplexity always cites its sources with clickable links, making it the most transparent AI search platform. It combines its own index with Google's and runs results through multiple reranking passes — initial relevance retrieval, then traditional ranking factor scoring, then ML-based quality evaluation that can discard entire result sets if they don't meet quality thresholds.

What makes Perplexity different: It's the most "research-oriented" AI search engine, and its citation behavior reflects that. Perplexity maintains curated lists of authoritative domains (Amazon, GitHub, major academic sites) that get inherent ranking boosts. It uses a time-decay algorithm that evaluates new content quickly, giving fresh publishers a real shot at citation.

Perplexity has unique content preferences:

• FAQ Schema (JSON-LD) — Pages with FAQ structured data get cited noticeably more often
• PDF documents — Publicly accessible PDFs (whitepapers, research reports) are prioritized. If you have authoritative PDF content gated behind a form, consider making a version public.
• Publishing velocity — How frequently you publish matters more than keyword targeting
• Self-contained paragraphs — Perplexity prefers atomic, semantically complete paragraphs it can extract cleanly

What to focus on:

• Allow PerplexityBot in robots.txt
• Implement FAQPage schema on any page with Q&A content
• Host PDF resources publicly (whitepapers, guides, reports)
• Add Article schema with publication and modification timestamps
• Write in clear, self-contained paragraphs that work as standalone answers
• Build deep topical authority in your specific niche

---

Microsoft Copilot

Copilot is embedded across Microsoft's ecosystem — Edge, Windows, Microsoft 365, and Bing Search. It relies entirely on Bing's index, so if Bing hasn't indexed your content, Copilot can't cite it.

What makes Copilot different: The Microsoft ecosystem connection creates unique optimization opportunities. Mentions and content on LinkedIn and GitHub provide ranking boosts that other platforms don't offer. Copilot also puts more weight on page speed — sub-2-second load times are a clear threshold.

What to focus on:

• Submit your site to Bing Webmaster Tools (many sites only submit to Google Search Console)
• Use IndexNow protocol for faster indexing of new and updated content
• Optimize page speed to under 2 seconds
• Write clear entity definitions — when your content defines a term or concept, make the definition explicit and extractable
• Build presence on LinkedIn (publish articles, maintain company page) and GitHub if relevant
• Ensure Bingbot has full crawl access

---

Claude

Claude uses Brave Search as its search backend when web search is enabled — not Google, not Bing. This is a completely different index, which means your Brave Search visibility directly determines whether Claude can find and cite you.

What makes Claude different: Claude is extremely selective about what it cites. While it processes enormous amounts of content, its citation rate is very low — it's looking for the most factually accurate, well-sourced content on a given topic. Data-rich content with specific numbers and clear attribution performs significantly better than general-purpose content.

What to focus on:

• Verify your content appears in Brave Search results (search for your brand and key terms at search.brave.com)
• Allow ClaudeBot and anthropic-ai user agents in robots.txt
• Maximize factual density — specific numbers, named sources, dated statistics
• Use clear, extractable structure with descriptive headings
• Cite authoritative sources within your content
• Aim to be the most factually accurate source on your topic — Claude rewards precision

---

Allowing AI Bots in robots.txt

If your robots.txt blocks an AI bot, that platform can't cite your content. Here are the user agents to allow:

User-agent: GPTBot           # OpenAI — powers ChatGPT search
User-agent: ChatGPT-User     # ChatGPT browsing mode
User-agent: PerplexityBot    # Perplexity AI search
User-agent: ClaudeBot        # Anthropic Claude
User-agent: anthropic-ai     # Anthropic Claude (alternate)
User-agent: Google-Extended   # Google Gemini and AI Overviews
User-agent: Bingbot          # Microsoft Copilot (via Bing)
Allow: /

Training vs. search: Some AI bots are used for both model training and search citation. If you want to be cited but don't want your content used for training, your options are limited — GPTBot handles both for OpenAI. However, you can safely block CCBot (Common Crawl) without affecting any AI search citations, since it's only used for training dataset collection.

---

Where to Start

If you're optimizing for AI search for the first time, focus your effort where your audience actually is:

Start with Google AI Overviews — They reach the most users (45%+ of Google searches) and you likely already have Google SEO foundations in place. Add schema markup, include cited sources in your content, and strengthen E-E-A-T signals.

Then address ChatGPT — It's the most-used standalone AI search tool for tech and business audiences. Focus on freshness (update content monthly), domain authority, and matching your content structure to how ChatGPT formats its responses.

Then expand to Perplexity — Especially valuable if your audience includes researchers, early adopters, or tech professionals. Add FAQ schema, publish PDF resources, and write in clear, self-contained paragraphs.

Copilot and Claude are lower priority unless your audience skews enterprise/Microsoft (Copilot) or developer/analyst (Claude). But the fundamentals — structured content, cited sources, schema markup — help across all platforms.

Actions that help everywhere:

1. Allow all AI bots in robots.txt
2. Implement schema markup (FAQPage, Article, Organization at minimum)
3. Include statistics with named sources in your content
4. Update content regularly — monthly for competitive topics
5. Use clear heading structure (H1 > H2 > H3)
6. Keep page load time under 2 seconds
7. Add author bios with credentials

---

Supporting file: references/programmatic-seo-playbooks.md

The 12 Programmatic SEO Playbooks

Beyond mixing and matching data point permutations, these are the proven playbooks for programmatic SEO.

1. Templates

Pattern: "[Type] template" or "free [type] template" Example searches: "resume template", "invoice template", "pitch deck template"

What it is: Downloadable or interactive templates users can use directly.

Why it works:

• High intent—people need it now
• Shareable/linkable assets
• Natural for product-led companies

Value requirements:

• Actually usable templates (not just previews)
• Multiple variations per type
• Quality comparable to paid options
• Easy download/use flow

URL structure: /templates/[type]/ or /templates/[category]/[type]/

---

2. Curation

Pattern: "best [category]" or "top [number] [things]" Example searches: "best website builders", "top 10 crm software", "best free design tools"

What it is: Curated lists ranking or recommending options in a category.

Why it works:

• Comparison shoppers searching for guidance
• High commercial intent
• Evergreen with updates

Value requirements:

• Genuine evaluation criteria
• Real testing or expertise
• Regular updates (date visible)
• Not just affiliate-driven rankings

URL structure: /best/[category]/ or /[category]/best/

---

3. Conversions

Pattern: "[X] to [Y]" or "[amount] [unit] in [unit]" Example searches: "$10 USD to GBP", "100 kg to lbs", "pdf to word"

What it is: Tools or pages that convert between formats, units, or currencies.

Why it works:

• Instant utility
• Extremely high search volume
• Repeat usage potential

Value requirements:

• Accurate, real-time data
• Fast, functional tool
• Related conversions suggested
• Mobile-friendly interface

URL structure: /convert/[from]-to-[to]/ or /[from]-to-[to]-converter/

---

4. Comparisons

Pattern: "[X] vs [Y]" or "[X] alternative" Example searches: "webflow vs wordpress", "notion vs coda", "figma alternatives"

What it is: Head-to-head comparisons between products, tools, or options.

Why it works:

• High purchase intent
• Clear search pattern
• Scales with number of competitors

Value requirements:

• Honest, balanced analysis
• Actual feature comparison data
• Clear recommendation by use case
• Updated when products change

URL structure: /compare/[x]-vs-[y]/ or /[x]-vs-[y]/

See also: competitor-analysis for detailed comparison-page frameworks.

---

5. Examples

Pattern: "[type] examples" or "[category] inspiration" Example searches: "saas landing page examples", "email subject line examples", "portfolio website examples"

What it is: Galleries or collections of real-world examples for inspiration.

Why it works:

• Research phase traffic
• Highly shareable
• Natural for design/creative tools

Value requirements:

• Real, high-quality examples
• Screenshots or embeds
• Categorization/filtering
• Analysis of why they work

URL structure: /examples/[type]/ or /[type]-examples/

---

6. Locations

Pattern: "[service/thing] in [location]" Example searches: "coworking spaces in san diego", "dentists in austin", "best restaurants in brooklyn"

What it is: Location-specific pages for services, businesses, or information.

Why it works:

• Local intent is massive
• Scales with geography
• Natural for marketplaces/directories

Value requirements:

• Actual local data (not just city name swapped)
• Local providers/options listed
• Location-specific insights (pricing, regulations)
• Map integration helpful

URL structure: /[service]/[city]/ or /locations/[city]/[service]/

---

7. Personas

Pattern: "[product] for [audience]" or "[solution] for [role/industry]" Example searches: "payroll software for agencies", "crm for real estate", "project management for freelancers"

What it is: Tailored landing pages addressing specific audience segments.

Why it works:

• Speaks directly to searcher's context
• Higher conversion than generic pages
• Scales with personas

Value requirements:

• Genuine persona-specific content
• Relevant features highlighted
• Testimonials from that segment
• Use cases specific to audience

URL structure: /for/[persona]/ or /solutions/[industry]/

---

8. Integrations

Pattern: "[your product] [other product] integration" or "[product] + [product]" Example searches: "slack asana integration", "zapier airtable", "hubspot salesforce sync"

What it is: Pages explaining how your product works with other tools.

Why it works:

• Captures users of other products
• High intent (they want the solution)
• Scales with integration ecosystem

Value requirements:

• Real integration details
• Setup instructions
• Use cases for the combination
• Working integration (not vaporware)

URL structure: /integrations/[product]/ or /connect/[product]/

---

9. Glossary

Pattern: "what is [term]" or "[term] definition" or "[term] meaning" Example searches: "what is pSEO", "api definition", "what does crm stand for"

What it is: Educational definitions of industry terms and concepts.

Why it works:

• Top-of-funnel awareness
• Establishes expertise
• Natural internal linking opportunities

Value requirements:

• Clear, accurate definitions
• Examples and context
• Related terms linked
• More depth than a dictionary

URL structure: /glossary/[term]/ or /learn/[term]/

---

10. Translations

Pattern: Same content in multiple languages Example searches: "qué es pSEO", "was ist SEO", "マーケティングとは"

What it is: Your content translated and localized for other language markets.

Why it works:

• Opens entirely new markets
• Lower competition in many languages
• Multiplies your content reach

Value requirements:

• Quality translation (not just Google Translate)
• Cultural localization
• hreflang tags properly implemented
• Native speaker review

URL structure: /[lang]/[page]/ or yoursite.com/es/, /de/, etc.

---

11. Directory

Pattern: "[category] tools" or "[type] software" or "[category] companies" Example searches: "ai copywriting tools", "email marketing software", "crm companies"

What it is: Comprehensive directories listing options in a category.

Why it works:

• Research phase capture
• Link building magnet
• Natural for aggregators/reviewers

Value requirements:

• Comprehensive coverage
• Useful filtering/sorting
• Details per listing (not just names)
• Regular updates

URL structure: /directory/[category]/ or /[category]-directory/

---

12. Profiles

Pattern: "[person/company name]" or "[entity] + [attribute]" Example searches: "stripe ceo", "airbnb founding story", "elon musk companies"

What it is: Profile pages about notable people, companies, or entities.

Why it works:

• Informational intent traffic
• Builds topical authority
• Natural for B2B, news, research

Value requirements:

• Accurate, sourced information
• Regularly updated
• Unique insights or aggregation
• Not just Wikipedia rehash

URL structure: /people/[name]/ or /companies/[name]/

---

Choosing Your Playbook

Match to Your Assets

Combine Playbooks

You can layer multiple playbooks:

• Locations + Personas: "Marketing agencies for startups in Austin"
• Curation + Locations: "Best coworking spaces in San Diego"
• Integrations + Personas: "Slack for sales teams"
• Glossary + Translations: Multi-language educational content

---

Supporting file: references/query-research.md

Query Research Methods for GEO/AEO

Table of Contents

1. Conversational Query Discovery (#conversational-query-discovery)
2. Question Clustering (#question-clustering)
3. Intent Classification (#intent-classification)
4. AI Platform Testing (#ai-platform-testing)
5. Competitive Intelligence (#competitive-intelligence)

---

Conversational Query Discovery

Tools & Methods

Process: Building Question Maps

1. Start with seed topic
   └── Example: "email marketing"

2. Generate question variations
   ├── What questions: "what is email marketing"
   ├── How questions: "how to do email marketing"
   ├── Why questions: "why email marketing works"
   ├── When questions: "when to send marketing emails"
   ├── Where questions: "where to learn email marketing"
   ├── Who questions: "who needs email marketing"
   └── Which questions: "which email marketing tool"

3. Expand with modifiers
   ├── For beginners
   ├── In 2025
   ├── vs [alternative]
   ├── examples
   ├── best practices
   └── mistakes to avoid

4. Mine "People Also Ask"
   └── Click through 3+ levels to discover chains

Conversational Query Patterns

AI chatbots receive queries like:

Traditional Search:
"best email marketing software"

Conversational Equivalent:
"What's the best email marketing software for a small 
e-commerce business with less than 10,000 subscribers 
that integrates with Shopify?"

Optimize for:

• Long-tail, specific queries
• Context-rich questions
• Multi-part queries
• Scenario-based questions

---

Question Clustering

Cluster Framework

Topic: [Main Topic]
│
├── Cluster 1: Definitions & Basics
│   ├── What is [topic]?
│   ├── What does [topic] mean?
│   ├── [Topic] definition
│   └── [Topic] explained simply
│
├── Cluster 2: How-To & Process
│   ├── How to [action] with [topic]
│   ├── How does [topic] work?
│   ├── Steps to [achieve outcome]
│   └── [Topic] tutorial
│
├── Cluster 3: Comparisons
│   ├── [Topic] vs [Alternative]
│   ├── Difference between [A] and [B]
│   ├── [Topic] alternatives
│   └── Best [topic] options
│
├── Cluster 4: Problems & Solutions
│   ├── [Topic] not working
│   ├── Common [topic] mistakes
│   ├── How to fix [problem]
│   └── [Topic] troubleshooting
│
├── Cluster 5: Cost & Value
│   ├── How much does [topic] cost?
│   ├── Is [topic] worth it?
│   ├── [Topic] pricing
│   └── Free vs paid [topic]
│
└── Cluster 6: Advanced & Specific
    ├── [Topic] for [specific audience]
    ├── Advanced [topic] techniques
    ├── [Topic] best practices
    └── [Topic] examples

Prioritization Matrix

---

Intent Classification

The 4 Intent Types

1. INFORMATIONAL (Know)
   Signal words: what, why, how, guide, tutorial, learn
   AI behavior: Synthesizes answers from multiple sources
   Optimization: Comprehensive, authoritative content

2. NAVIGATIONAL (Go)
   Signal words: [brand name], login, official, website
   AI behavior: Directs to specific destinations
   Optimization: Brand presence, clear site structure

3. COMMERCIAL (Compare)
   Signal words: best, top, vs, review, comparison
   AI behavior: Provides options with analysis
   Optimization: Comparison content, honest reviews

4. TRANSACTIONAL (Do)
   Signal words: buy, price, discount, download, sign up
   AI behavior: Often defers to websites
   Optimization: Clear CTAs, product pages

Intent-to-Content Mapping

---

AI Platform Testing

Manual Testing Protocol

For each target query, test across:
□ ChatGPT (free and Plus)
□ Perplexity
□ Google (AI Overview)
□ Claude
□ Bing Copilot
□ Google Gemini

Document:
1. Is your brand/site mentioned?
2. Is your content cited?
3. What sources are cited?
4. How is the answer structured?
5. What's missing from the answer?

Testing Queries Template

Base query: "[Your topic]"

Test variations:
1. "What is [topic]?"
2. "How do I [action related to topic]?"
3. "Best [topic] for [use case]"
4. "[Your brand] vs [competitor]"
5. "[Topic] in [current year]"
6. "Explain [topic] simply"
7. "[Topic] examples"
8. "Is [topic] worth it?"

Competitor Citation Analysis

# Pseudocode for tracking citations
queries = load_target_queries()
for query in queries:
    for platform in [ChatGPT, Perplexity, Google]:
        response = query_platform(platform, query)
        citations = extract_citations(response)
        
        record({
            'query': query,
            'platform': platform,
            'our_site_cited': our_domain in citations,
            'competitors_cited': [c for c in citations if c in competitor_domains],
            'citation_position': get_position(our_domain, citations)
        })

---

Competitive Intelligence

Citation Gap Analysis

Step 1: Identify who's being cited

Query your target topics across AI platforms
Record all cited domains
Tally citation frequency by domain

Step 2: Analyze cited content

For top-cited competitors:
├── Content structure (headers, formatting)
├── Content depth (word count, comprehensiveness)
├── Authority signals (author, sources, data)
├── Freshness (last updated date)
└── Technical factors (speed, schema, crawlability)

Step 3: Gap identification

Questions to answer:
├── What topics do they cover that we don't?
├── What formats are they using?
├── What unique data/research do they have?
├── How recent is their content?
└── What E-E-A-T signals are present?

Competitive Content Audit Template

Action Planning

Priority actions based on gaps:
1. QUICK WINS: Easy to implement, high impact
   - Add FAQ sections
   - Update publish dates
   - Add author bios
   
2. MEDIUM EFFORT: Moderate effort, solid impact
   - Expand thin content
   - Add original data/statistics
   - Implement schema markup
   
3. LONG-TERM: High effort, transformative impact
   - Original research
   - Thought leadership content
   - Building topical authority

---

Supporting file: references/schema-examples.md

Schema Markup Examples

Complete JSON-LD examples for common schema types.

Contents

• Organization
• WebSite (with SearchAction)
• Article / BlogPosting
• Product
• SoftwareApplication
• FAQPage
• HowTo
• BreadcrumbList
• LocalBusiness
• Event
• Multiple Schema Types
• Implementation Example (Next.js)

Organization

For company/brand homepage or about page.

{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Example Company",
  "url": "https://example.com",
  "logo": "https://example.com/logo.png",
  "sameAs": [
    "https://twitter.com/example",
    "https://linkedin.com/company/example",
    "https://facebook.com/example"
  ],
  "contactPoint": {
    "@type": "ContactPoint",
    "telephone": "+1-555-555-5555",
    "contactType": "customer service"
  }
}

---

WebSite (with SearchAction)

For homepage, enables sitelinks search box.

{
  "@context": "https://schema.org",
  "@type": "WebSite",
  "name": "Example",
  "url": "https://example.com",
  "potentialAction": {
    "@type": "SearchAction",
    "target": {
      "@type": "EntryPoint",
      "urlTemplate": "https://example.com/search?q={search_term_string}"
    },
    "query-input": "required name=search_term_string"
  }
}

---

Article / BlogPosting

For blog posts and news articles.

{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "How to Implement Schema Markup",
  "image": "https://example.com/image.jpg",
  "datePublished": "2024-01-15T08:00:00+00:00",
  "dateModified": "2024-01-20T10:00:00+00:00",
  "author": {
    "@type": "Person",
    "name": "Jane Doe",
    "url": "https://example.com/authors/jane"
  },
  "publisher": {
    "@type": "Organization",
    "name": "Example Company",
    "logo": {
      "@type": "ImageObject",
      "url": "https://example.com/logo.png"
    }
  },
  "description": "A complete guide to implementing schema markup...",
  "mainEntityOfPage": {
    "@type": "WebPage",
    "@id": "https://example.com/schema-guide"
  }
}

---

Product

For product pages (e-commerce or SaaS).

{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "Premium Widget",
  "image": "https://example.com/widget.jpg",
  "description": "Our best-selling widget for professionals",
  "sku": "WIDGET-001",
  "brand": {
    "@type": "Brand",
    "name": "Example Co"
  },
  "offers": {
    "@type": "Offer",
    "url": "https://example.com/products/widget",
    "priceCurrency": "USD",
    "price": "99.99",
    "availability": "https://schema.org/InStock",
    "priceValidUntil": "2024-12-31"
  },
  "aggregateRating": {
    "@type": "AggregateRating",
    "ratingValue": "4.8",
    "reviewCount": "127"
  }
}

---

SoftwareApplication

For SaaS product pages and app landing pages.

{
  "@context": "https://schema.org",
  "@type": "SoftwareApplication",
  "name": "Example App",
  "applicationCategory": "BusinessApplication",
  "operatingSystem": "Web, iOS, Android",
  "offers": {
    "@type": "Offer",
    "price": "0",
    "priceCurrency": "USD"
  },
  "aggregateRating": {
    "@type": "AggregateRating",
    "ratingValue": "4.6",
    "ratingCount": "1250"
  }
}

---

FAQPage

For pages with frequently asked questions.

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "What is schema markup?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Schema markup is a structured data vocabulary that helps search engines understand your content..."
      }
    },
    {
      "@type": "Question",
      "name": "How do I implement schema?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "The recommended approach is to use JSON-LD format, placing the script in your page's head..."
      }
    }
  ]
}

---

HowTo

For instructional content and tutorials.

{
  "@context": "https://schema.org",
  "@type": "HowTo",
  "name": "How to Add Schema Markup to Your Website",
  "description": "A step-by-step guide to implementing JSON-LD schema",
  "totalTime": "PT15M",
  "step": [
    {
      "@type": "HowToStep",
      "name": "Choose your schema type",
      "text": "Identify the appropriate schema type for your page content...",
      "url": "https://example.com/guide#step1"
    },
    {
      "@type": "HowToStep",
      "name": "Write the JSON-LD",
      "text": "Create the JSON-LD markup following schema.org specifications...",
      "url": "https://example.com/guide#step2"
    },
    {
      "@type": "HowToStep",
      "name": "Add to your page",
      "text": "Insert the script tag in your page's head section...",
      "url": "https://example.com/guide#step3"
    }
  ]
}

---

BreadcrumbList

For any page with breadcrumb navigation.

{
  "@context": "https://schema.org",
  "@type": "BreadcrumbList",
  "itemListElement": [
    {
      "@type": "ListItem",
      "position": 1,
      "name": "Home",
      "item": "https://example.com"
    },
    {
      "@type": "ListItem",
      "position": 2,
      "name": "Blog",
      "item": "https://example.com/blog"
    },
    {
      "@type": "ListItem",
      "position": 3,
      "name": "SEO Guide",
      "item": "https://example.com/blog/seo-guide"
    }
  ]
}

---

LocalBusiness

For local business location pages.

{
  "@context": "https://schema.org",
  "@type": "LocalBusiness",
  "name": "Example Coffee Shop",
  "image": "https://example.com/shop.jpg",
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "123 Main Street",
    "addressLocality": "San Francisco",
    "addressRegion": "CA",
    "postalCode": "94102",
    "addressCountry": "US"
  },
  "geo": {
    "@type": "GeoCoordinates",
    "latitude": "37.7749",
    "longitude": "-122.4194"
  },
  "telephone": "+1-555-555-5555",
  "openingHoursSpecification": [
    {
      "@type": "OpeningHoursSpecification",
      "dayOfWeek": ["Monday", "Tuesday", "Wednesday", "Thursday", "Friday"],
      "opens": "08:00",
      "closes": "18:00"
    }
  ],
  "priceRange": "$$"
}

---

Event

For event pages, webinars, conferences.

{
  "@context": "https://schema.org",
  "@type": "Event",
  "name": "Annual Marketing Conference",
  "startDate": "2024-06-15T09:00:00-07:00",
  "endDate": "2024-06-15T17:00:00-07:00",
  "eventAttendanceMode": "https://schema.org/OnlineEventAttendanceMode",
  "eventStatus": "https://schema.org/EventScheduled",
  "location": {
    "@type": "VirtualLocation",
    "url": "https://example.com/conference"
  },
  "image": "https://example.com/conference.jpg",
  "description": "Join us for our annual marketing conference...",
  "offers": {
    "@type": "Offer",
    "url": "https://example.com/conference/tickets",
    "price": "199",
    "priceCurrency": "USD",
    "availability": "https://schema.org/InStock",
    "validFrom": "2024-01-01"
  },
  "performer": {
    "@type": "Organization",
    "name": "Example Company"
  },
  "organizer": {
    "@type": "Organization",
    "name": "Example Company",
    "url": "https://example.com"
  }
}

---

Multiple Schema Types

Combine multiple schema types using @graph.

{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@type": "Organization",
      "@id": "https://example.com/#organization",
      "name": "Example Company",
      "url": "https://example.com"
    },
    {
      "@type": "WebSite",
      "@id": "https://example.com/#website",
      "url": "https://example.com",
      "name": "Example",
      "publisher": {
        "@id": "https://example.com/#organization"
      }
    },
    {
      "@type": "BreadcrumbList",
      "itemListElement": [...]
    }
  ]
}

---

Implementation Example (Next.js)

export default function ProductPage({ product }) {
  const schema = {
    "@context": "https://schema.org",
    "@type": "Product",
    name: product.name,
    // ... other properties
  };

  return (
    <>
      <Head>
        <script
          type="application/ld+json"
          dangerouslySetInnerHTML={{ __html: JSON.stringify(schema) }}
        />
      </Head>
      {/* Page content */}
    </>
  );
}

---

Supporting file: references/schema-for-ai.md

Schema Markup for AI Optimization

Table of Contents

1. Schema Priority for AI (#schema-priority-for-ai)
2. High-Impact Schema Types (#high-impact-schema-types)
3. Implementation Patterns (#implementation-patterns)
4. AI-Specific Considerations (#ai-specific-considerations)

---

Schema Priority for AI

Why Schema Matters for AI

AI systems use structured data to:

• Understand content type and context
• Extract specific facts and attributes
• Validate information accuracy
• Determine content authority

Priority Schema Types for GEO/AEO

---

High-Impact Schema Types

FAQPage (Highest AI Impact)

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "What is [topic]?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Complete answer that can stand alone. Include key facts, figures, and context. This entire text may be extracted by AI systems."
      }
    },
    {
      "@type": "Question",
      "name": "How does [topic] work?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Step-by-step or explanatory answer. Be comprehensive but concise."
      }
    }
  ]
}

Best practices for AI:

• Questions should match real user queries
• Answers must be complete and standalone
• Include specific facts, not just fluff
• Keep answers 50-300 words each

HowTo (High AI Impact)

{
  "@context": "https://schema.org",
  "@type": "HowTo",
  "name": "How to [Action]",
  "description": "Brief overview of what this guide teaches",
  "totalTime": "PT30M",
  "step": [
    {
      "@type": "HowToStep",
      "position": 1,
      "name": "Step name (action verb)",
      "text": "Detailed instructions for this step. Be specific and actionable.",
      "image": "https://example.com/step1.jpg"
    },
    {
      "@type": "HowToStep",
      "position": 2,
      "name": "Next step name",
      "text": "Detailed instructions for this step."
    }
  ]
}

Best practices for AI:

• Step names should be scannable actions
• Step text should be complete instructions
• Include time estimates when possible
• Each step should be independently understandable

Article + Author (Authority Signal)

{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "Article Title (max 110 chars)",
  "description": "Meta description - comprehensive summary",
  "image": "https://example.com/image.jpg",
  "datePublished": "2025-01-08T08:00:00Z",
  "dateModified": "2025-01-08T10:00:00Z",
  "author": {
    "@type": "Person",
    "name": "Author Name",
    "url": "https://example.com/author/name",
    "jobTitle": "Subject Matter Expert",
    "description": "Brief bio establishing expertise",
    "sameAs": [
      "https://linkedin.com/in/authorname",
      "https://twitter.com/authorname"
    ]
  },
  "publisher": {
    "@type": "Organization",
    "name": "Publisher Name",
    "logo": {
      "@type": "ImageObject",
      "url": "https://example.com/logo.png"
    }
  },
  "mainEntityOfPage": {
    "@type": "WebPage",
    "@id": "https://example.com/article-url"
  }
}

AI authority signals:

• Author with credentials and bio
• Publisher organization details
• dateModified shows freshness
• sameAs links validate identity

Speakable (Voice/AI Extraction)

{
  "@context": "https://schema.org",
  "@type": "WebPage",
  "name": "Page Title",
  "speakable": {
    "@type": "SpeakableSpecification",
    "cssSelector": [".tldr", ".key-takeaway", "#summary"]
  }
}

Marks content sections optimized for:

• Voice assistant reading
• AI summary extraction
• Audio content generation

---

Implementation Patterns

Combined Schema for Content Pages

{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@type": "Article",
      "@id": "https://example.com/page#article",
      "headline": "Complete Guide to [Topic]",
      "author": {"@id": "https://example.com/#author"},
      "publisher": {"@id": "https://example.com/#org"},
      "datePublished": "2025-01-08",
      "dateModified": "2025-01-08"
    },
    {
      "@type": "FAQPage",
      "@id": "https://example.com/page#faq",
      "mainEntity": [...]
    },
    {
      "@type": "BreadcrumbList",
      "@id": "https://example.com/page#breadcrumb",
      "itemListElement": [
        {"@type": "ListItem", "position": 1, "name": "Home", "item": "https://example.com/"},
        {"@type": "ListItem", "position": 2, "name": "Category", "item": "https://example.com/category/"},
        {"@type": "ListItem", "position": 3, "name": "Page Title"}
      ]
    },
    {
      "@type": "Organization",
      "@id": "https://example.com/#org",
      "name": "Company Name",
      "url": "https://example.com",
      "logo": "https://example.com/logo.png"
    },
    {
      "@type": "Person",
      "@id": "https://example.com/#author",
      "name": "Author Name",
      "jobTitle": "Expert Title"
    }
  ]
}

E-commerce Product Page

{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@type": "Product",
      "name": "Product Name",
      "description": "Detailed product description",
      "image": ["image1.jpg", "image2.jpg"],
      "brand": {"@type": "Brand", "name": "Brand"},
      "offers": {
        "@type": "Offer",
        "price": "99.99",
        "priceCurrency": "USD",
        "availability": "https://schema.org/InStock"
      },
      "aggregateRating": {
        "@type": "AggregateRating",
        "ratingValue": "4.5",
        "reviewCount": "127"
      }
    },
    {
      "@type": "FAQPage",
      "mainEntity": [
        {
          "@type": "Question",
          "name": "What is included with [Product]?",
          "acceptedAnswer": {
            "@type": "Answer",
            "text": "Complete list of what's included..."
          }
        }
      ]
    }
  ]
}

---

AI-Specific Considerations

Schema That AI Systems Prioritize

1. Factual extraction

   • FAQPage → Direct Q&A extraction
   • HowTo → Step extraction
   • Product → Spec extraction

2. Authority signals

   • Person (author) → Expertise validation
   • Organization → Publisher trust
   • sameAs → Identity verification

3. Content structure

   • Article → Content type identification
   • BreadcrumbList → Topic hierarchy
   • WebPage → Page purpose

Schema That Has Less AI Impact

• Event (unless for event queries)
• Recipe (unless for recipe queries)
• Video (unless for video queries)
• Music (domain-specific)

Validation for AI Optimization

Checklist before publishing:
□ Rich Results Test passes
□ Schema matches visible content exactly
□ No exaggerated claims
□ dateModified is accurate
□ Author has real credentials
□ FAQ questions match real search queries
□ All URLs are absolute and HTTPS
□ Images are accessible and properly sized

Common Mistakes to Avoid

---

Supporting file: references/schema-templates.md

JSON-LD Schema Templates

Ready-to-use JSON-LD structured data templates for SEO and GEO optimization.

---

1. FAQPage Schema (+40% AI Visibility)

Best for: FAQ sections, knowledge base pages, product pages with Q&A.

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "What is [Your Product/Service]?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "[Comprehensive answer with statistics. According to X, 85% of users report Y benefit.]"
      }
    },
    {
      "@type": "Question",
      "name": "How does [Product/Service] work?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "[Step-by-step explanation. First, you... Then... Finally...]"
      }
    },
    {
      "@type": "Question",
      "name": "What are the benefits of [Product/Service]?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "[List key benefits with data. Users save an average of X hours per week.]"
      }
    },
    {
      "@type": "Question",
      "name": "How much does [Product/Service] cost?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "[Pricing information. Plans start at $X/month with a free tier available.]"
      }
    },
    {
      "@type": "Question",
      "name": "How do I get started with [Product/Service]?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "[Installation/signup instructions. Visit example.com/docs/install or download the installer from example.com/download.]"
      }
    }
  ]
}

---

2. WebPage Schema

Best for: Standard content pages, landing pages.

{
  "@context": "https://schema.org",
  "@type": "WebPage",
  "name": "[Page Title]",
  "description": "[Page description, 150-160 characters]",
  "url": "https://example.com/page",
  "datePublished": "2024-01-15",
  "dateModified": "2024-12-20",
  "inLanguage": "en-US",
  "isPartOf": {
    "@type": "WebSite",
    "name": "[Site Name]",
    "url": "https://example.com"
  },
  "author": {
    "@type": "Person",
    "name": "[Author Name]",
    "url": "https://example.com/about"
  },
  "publisher": {
    "@type": "Organization",
    "name": "[Organization Name]",
    "logo": {
      "@type": "ImageObject",
      "url": "https://example.com/logo.png"
    }
  },
  "speakable": {
    "@type": "SpeakableSpecification",
    "cssSelector": ["h1", ".summary", ".key-points"]
  }
}

---

3. Article Schema

Best for: Blog posts, news articles, tutorials.

{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "[Article Title - Max 110 characters]",
  "description": "[Article summary]",
  "image": [
    "https://example.com/image-1x1.jpg",
    "https://example.com/image-4x3.jpg",
    "https://example.com/image-16x9.jpg"
  ],
  "datePublished": "2024-01-15T08:00:00+00:00",
  "dateModified": "2024-12-20T10:30:00+00:00",
  "author": {
    "@type": "Person",
    "name": "[Author Name]",
    "url": "https://example.com/author/name",
    "jobTitle": "[Job Title]",
    "worksFor": {
      "@type": "Organization",
      "name": "[Company]"
    }
  },
  "publisher": {
    "@type": "Organization",
    "name": "[Publisher Name]",
    "logo": {
      "@type": "ImageObject",
      "url": "https://example.com/logo.png",
      "width": 600,
      "height": 60
    }
  },
  "mainEntityOfPage": {
    "@type": "WebPage",
    "@id": "https://example.com/article-url"
  },
  "keywords": ["keyword1", "keyword2", "keyword3"],
  "articleSection": "[Category]",
  "wordCount": 2500
}

---

4. SoftwareApplication Schema

Best for: Tools, apps, software products.

{
  "@context": "https://schema.org",
  "@type": "SoftwareApplication",
  "name": "[App Name]",
  "description": "[App description]",
  "applicationCategory": "DeveloperApplication",
  "operatingSystem": "Cross-platform",
  "url": "https://example.com",
  "downloadUrl": "https://example.com/download",
  "softwareVersion": "1.0.0",
  "releaseNotes": "https://example.com/changelog",
  "screenshot": "https://example.com/screenshot.png",
  "featureList": [
    "Feature 1 description",
    "Feature 2 description",
    "Feature 3 description"
  ],
  "offers": {
    "@type": "Offer",
    "price": "0",
    "priceCurrency": "USD",
    "availability": "https://schema.org/InStock"
  },
  "aggregateRating": {
    "@type": "AggregateRating",
    "ratingValue": "4.8",
    "ratingCount": "150",
    "bestRating": "5",
    "worstRating": "1"
  },
  "author": {
    "@type": "Organization",
    "name": "[Company Name]",
    "url": "https://example.com"
  }
}

---

5. Organization Schema

Best for: About pages, company pages.

{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "[Organization Name]",
  "alternateName": "[Alternate Name]",
  "url": "https://example.com",
  "logo": "https://example.com/logo.png",
  "description": "[Organization description]",
  "foundingDate": "2024",
  "founders": [
    {
      "@type": "Person",
      "name": "[Founder Name]"
    }
  ],
  "address": {
    "@type": "PostalAddress",
    "addressLocality": "[City]",
    "addressRegion": "[State]",
    "addressCountry": "[Country]"
  },
  "contactPoint": {
    "@type": "ContactPoint",
    "contactType": "customer service",
    "email": "support@example.com"
  },
  "sameAs": [
    "https://twitter.com/example",
    "https://github.com/example",
    "https://linkedin.com/company/example"
  ]
}

---

6. Product Schema

Best for: E-commerce product pages.

{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "[Product Name]",
  "description": "[Product description]",
  "image": [
    "https://example.com/product-image-1.jpg",
    "https://example.com/product-image-2.jpg"
  ],
  "sku": "[SKU]",
  "brand": {
    "@type": "Brand",
    "name": "[Brand Name]"
  },
  "offers": {
    "@type": "Offer",
    "url": "https://example.com/product",
    "priceCurrency": "USD",
    "price": "99.99",
    "priceValidUntil": "2025-12-31",
    "availability": "https://schema.org/InStock",
    "seller": {
      "@type": "Organization",
      "name": "[Seller Name]"
    }
  },
  "aggregateRating": {
    "@type": "AggregateRating",
    "ratingValue": "4.5",
    "reviewCount": "89"
  },
  "review": [
    {
      "@type": "Review",
      "reviewRating": {
        "@type": "Rating",
        "ratingValue": "5",
        "bestRating": "5"
      },
      "author": {
        "@type": "Person",
        "name": "[Reviewer Name]"
      },
      "reviewBody": "[Review text]"
    }
  ]
}

---

7. HowTo Schema

Best for: Tutorials, guides, how-to articles.

{
  "@context": "https://schema.org",
  "@type": "HowTo",
  "name": "How to [Do Something]",
  "description": "[Brief description of what this guide covers]",
  "image": "https://example.com/how-to-image.jpg",
  "totalTime": "PT15M",
  "estimatedCost": {
    "@type": "MonetaryAmount",
    "currency": "USD",
    "value": "0"
  },
  "supply": [
    {
      "@type": "HowToSupply",
      "name": "[Required item 1]"
    }
  ],
  "tool": [
    {
      "@type": "HowToTool",
      "name": "[Required tool 1]"
    }
  ],
  "step": [
    {
      "@type": "HowToStep",
      "name": "Step 1: [Step Name]",
      "text": "[Detailed step instructions]",
      "image": "https://example.com/step-1.jpg",
      "url": "https://example.com/guide#step1"
    },
    {
      "@type": "HowToStep",
      "name": "Step 2: [Step Name]",
      "text": "[Detailed step instructions]",
      "image": "https://example.com/step-2.jpg",
      "url": "https://example.com/guide#step2"
    },
    {
      "@type": "HowToStep",
      "name": "Step 3: [Step Name]",
      "text": "[Detailed step instructions]",
      "image": "https://example.com/step-3.jpg",
      "url": "https://example.com/guide#step3"
    }
  ]
}

---

8. BreadcrumbList Schema

Best for: All pages with navigation hierarchy.

{
  "@context": "https://schema.org",
  "@type": "BreadcrumbList",
  "itemListElement": [
    {
      "@type": "ListItem",
      "position": 1,
      "name": "Home",
      "item": "https://example.com"
    },
    {
      "@type": "ListItem",
      "position": 2,
      "name": "[Category]",
      "item": "https://example.com/category"
    },
    {
      "@type": "ListItem",
      "position": 3,
      "name": "[Current Page]",
      "item": "https://example.com/category/page"
    }
  ]
}

---

9. LocalBusiness Schema

Best for: Local business pages.

{
  "@context": "https://schema.org",
  "@type": "LocalBusiness",
  "name": "[Business Name]",
  "description": "[Business description]",
  "image": "https://example.com/business-image.jpg",
  "url": "https://example.com",
  "telephone": "+1-555-555-5555",
  "email": "contact@example.com",
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "[Street Address]",
    "addressLocality": "[City]",
    "addressRegion": "[State]",
    "postalCode": "[ZIP]",
    "addressCountry": "US"
  },
  "geo": {
    "@type": "GeoCoordinates",
    "latitude": 37.7749,
    "longitude": -122.4194
  },
  "openingHoursSpecification": [
    {
      "@type": "OpeningHoursSpecification",
      "dayOfWeek": ["Monday", "Tuesday", "Wednesday", "Thursday", "Friday"],
      "opens": "09:00",
      "closes": "17:00"
    }
  ],
  "priceRange": "$$"
}

---

10. SpeakableSpecification (GEO Enhancement)

Best for: Voice search optimization, AI extraction.

{
  "@context": "https://schema.org",
  "@type": "WebPage",
  "name": "[Page Title]",
  "speakable": {
    "@type": "SpeakableSpecification",
    "cssSelector": [
      "h1",
      ".summary",
      ".key-takeaways",
      ".faq-answer"
    ]
  }
}

---

Combined Schema Example

For a software product page with FAQ:

{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@type": "WebPage",
      "name": "OPC Skills - AI Agent Skills for Solopreneurs",
      "description": "10+ agent skills for Claude Code, Cursor, Codex. Domain hunting, social media research, logo creation.",
      "url": "https://opc.dev",
      "dateModified": "2024-12-20",
      "speakable": {
        "@type": "SpeakableSpecification",
        "cssSelector": ["h1", ".hero-description", ".faq-answer"]
      }
    },
    {
      "@type": "SoftwareApplication",
      "name": "OPC Skills",
      "applicationCategory": "DeveloperApplication",
      "operatingSystem": "Cross-platform",
      "offers": {
        "@type": "Offer",
        "price": "0",
        "priceCurrency": "USD"
      }
    },
    {
      "@type": "FAQPage",
      "mainEntity": [
        {
          "@type": "Question",
          "name": "What is OPC Skills?",
          "acceptedAnswer": {
            "@type": "Answer",
            "text": "OPC Skills is a collection of 10+ AI agent skills for solopreneurs, supporting Claude Code, Cursor, and Codex."
          }
        }
      ]
    },
    {
      "@type": "Organization",
      "name": "OPC Skills",
      "url": "https://opc.dev",
      "sameAs": ["https://github.com/ReScienceLab/opc-skills"]
    }
  ]
}

---

Validation Tools

1. Google Rich Results Test

   https://search.google.com/test/rich-results?url={your-url}
   

2. Schema.org Validator

   https://validator.schema.org/?url={your-url}
   

3. Google Search Console

   • Check "Enhancements" for schema issues
   • Monitor rich result performance

---

Supporting file: references/seo-checklist.md

SEO/GEO Audit Checklist

Complete checklist for auditing and optimizing websites for both traditional SEO and GEO (AI search visibility).

Priority Levels

---

Technical SEO

P0 - Critical

• P0 robots.txt allows important pages
• P0 Site is accessible (no 5xx errors)
• P0 HTTPS enabled (valid SSL certificate)
• P0 Mobile-responsive design
• P0 No critical pages blocked by noindex
• P0 Site is indexed in Google (check: site:domain.com)

P1 - Important

• P1 robots.txt allows AI bots (GPTBot, PerplexityBot, ClaudeBot)
• P1 XML sitemap exists and is submitted
• P1 Site is indexed in Bing (for Copilot visibility)
• P1 Canonical tags properly implemented
• P1 No duplicate content issues
• P1 Page load time < 3 seconds
• P1 LCP (Largest Contentful Paint) < 2.5s

P2 - Recommended

• P2 FID (First Input Delay) < 100ms
• P2 CLS (Cumulative Layout Shift) < 0.1
• P2 Images optimized (WebP format, lazy loading)
• P2 CSS/JS minified
• P2 GZIP/Brotli compression enabled
• P2 CDN configured
• P2 Mobile-friendly test passed
• P2 No mixed content warnings
• P2 Secure headers configured

---

On-Page SEO

P0 - Critical

• P0 Unique <title> tag exists (50-60 characters)
• P0 Title contains primary keyword
• P0 Unique <meta description> exists (150-160 characters)
• P0 Single H1 tag per page
• P0 H1 contains primary keyword

P1 - Important

• P1 Description is compelling and includes keyword
• P1 <meta name="robots"> correctly set
• P1 Logical heading hierarchy (H1 > H2 > H3)
• P1 All images have alt attributes
• P1 Internal links to related content
• P1 No broken links (404s)
• P1 Anchor text is descriptive

P2 - Recommended

• P2 og:title set
• P2 og:description set
• P2 og:image set (1200x630px recommended)
• P2 og:url set (canonical URL)
• P2 og:type set (website/article)
• P2 twitter:card set (summary_large_image)
• P2 twitter:title set
• P2 twitter:description set
• P2 twitter:image set
• P2 Paragraphs are short (2-3 sentences)
• P2 Bullet points used for lists
• P2 Tables used for comparisons
• P2 Alt text includes keywords where natural
• P2 Image file names are descriptive
• P2 External links have rel="noopener noreferrer"

---

Schema Markup (Structured Data)

P1 - Important

• P1 Organization schema on homepage
• P1 WebPage schema on all pages
• P1 Article schema on blog posts
• P1 Schema passes Google Rich Results Test
• P1 No errors in Search Console "Enhancements"

P2 - Recommended - GEO Enhanced

• P2 FAQPage schema on FAQ sections (+40% AI visibility)
• P2 BreadcrumbList schema for navigation
• P2 SpeakableSpecification for voice search
• P2 datePublished and dateModified included
• P2 Author information with credentials
• P2 Publisher information with logo
• P2 Schema passes Schema.org Validator

---

GEO Optimization (AI Search)

P1 - Important - Princeton GEO Methods

• P1 Content includes authoritative citations (+40%)
• P1 Statistics and data points included (+37%)
• P1 Expert quotes with attribution (+30%)
• P1 NO keyword stuffing (causes -10%)

P2 - Recommended - GEO Enhancement

• P2 Authoritative, confident tone (+25%)
• P2 Content is accessible/easy to understand (+20%)
• P2 Appropriate technical terminology (+18%)
• P2 Diverse vocabulary throughout (+15%)
• P2 High fluency and readability (+15-30%)

Content Structure for AI

• "Answer-first" format (direct answer at top)
• Clear, extractable paragraphs
• FAQ format for common questions
• Tables for comparison data
• Lists for step-by-step processes

AI Bot Access

• GPTBot allowed in robots.txt
• PerplexityBot allowed in robots.txt
• ClaudeBot allowed in robots.txt
• Anthropic-ai allowed in robots.txt
• Bingbot allowed in robots.txt

---

Off-Page SEO

Backlinks

• Quality backlinks from relevant sites
• Diverse referring domains
• No toxic/spammy backlinks
• Brand mentions (even without links)

E-E-A-T Signals

• Author bios with credentials
• About page with company info
• Contact information visible
• Privacy policy and terms
• Trust badges/certifications if applicable
• Customer reviews/testimonials

Social Presence

• Active social media profiles
• Links to social profiles on website
• Social sharing buttons on content
• Consistent branding across platforms

---

Content Strategy

Content Audit

• All pages have unique, valuable content
• No thin content (< 300 words for main pages)
• Content matches search intent
• Content is up-to-date (within 30 days for news/tech)
• Content provides unique value vs competitors

Keyword Strategy

• Primary keyword identified for each page
• Secondary keywords mapped
• Long-tail keywords targeted
• No keyword cannibalization
• Keywords match user intent

---

Monitoring & Analytics

Setup

• Google Analytics installed
• Google Search Console connected
• Bing Webmaster Tools connected
• Sitemap submitted to both

Regular Checks

• Weekly: Check Search Console for errors
• Weekly: Review Core Web Vitals
• Monthly: Analyze organic traffic trends
• Monthly: Review top performing pages
• Quarterly: Full SEO audit

---

Quick Audit Commands

# Check meta tags
curl -sL "https://example.com" | grep -E "<title>|<meta"

# Check robots.txt
curl -s "https://example.com/robots.txt"

# Check sitemap
curl -s "https://example.com/sitemap.xml" | head -30

# Check page speed (using PageSpeed Insights API)
# Requires API key
curl "https://www.googleapis.com/pagespeedonline/v5/runPagespeed?url=https://example.com&strategy=mobile"

# Check if indexed in Google
# Manual check: https://www.google.com/search?q=site:example.com

# Validate schema
# Open: https://search.google.com/test/rich-results?url=https://example.com

---

Priority Matrix

---

Supporting file: references/site-architecture-mermaid-templates.md

Mermaid Diagram Templates

Copy-paste-ready Mermaid diagrams for visual sitemaps. Customize node labels and connections for your site.

---

Basic Hierarchy

Simple top-down page hierarchy.

graph TD
    HOME["Homepage<br/>/"] --> FEAT["Features<br/>/features"]
    HOME --> PRICE["Pricing<br/>/pricing"]
    HOME --> BLOG["Blog<br/>/blog"]
    HOME --> ABOUT["About<br/>/about"]

    FEAT --> F1["Analytics<br/>/features/analytics"]
    FEAT --> F2["Automation<br/>/features/automation"]
    FEAT --> F3["Integrations<br/>/features/integrations"]

    BLOG --> B1["Post: SEO Guide<br/>/blog/seo-guide"]
    BLOG --> B2["Post: CRO Tips<br/>/blog/cro-tips"]

---

Hierarchy with Navigation Zones

Uses subgraphs to show which pages appear in which navigation area.

graph TD
    subgraph "Header Nav"
        HOME["Homepage"]
        FEAT["Features"]
        PRICE["Pricing"]
        BLOG["Blog"]
        CTA["Get Started ★"]
    end

    subgraph "Feature Pages"
        F1["Analytics"]
        F2["Automation"]
        F3["Integrations"]
    end

    subgraph "Footer Nav"
        ABOUT["About"]
        CAREERS["Careers"]
        CONTACT["Contact"]
        PRIVACY["Privacy"]
        TERMS["Terms"]
    end

    HOME --> FEAT
    HOME --> PRICE
    HOME --> BLOG
    FEAT --> F1
    FEAT --> F2
    FEAT --> F3
    HOME --> ABOUT
    ABOUT --> CAREERS
    HOME --> CONTACT

---

Hierarchy with URL Labels

Each node shows the page name and URL path.

graph TD
    HOME["Homepage<br/><small>/</small>"] --> PROD["Product<br/><small>/product</small>"]
    HOME --> PRICE["Pricing<br/><small>/pricing</small>"]
    HOME --> BLOG["Blog<br/><small>/blog</small>"]
    HOME --> DOCS["Docs<br/><small>/docs</small>"]
    HOME --> ABOUT["About<br/><small>/about</small>"]

    PROD --> P1["Analytics<br/><small>/product/analytics</small>"]
    PROD --> P2["Reports<br/><small>/product/reports</small>"]

    DOCS --> D1["Getting Started<br/><small>/docs/getting-started</small>"]
    DOCS --> D2["API Reference<br/><small>/docs/api</small>"]

---

Hub-and-Spoke Content Model

Shows a hub page connected to spoke articles, with spokes linking to each other.

graph TD
    HUB["SEO Guide<br/>(Hub Page)"]

    HUB --> S1["Keyword Research"]
    HUB --> S2["On-Page SEO"]
    HUB --> S3["Technical SEO"]
    HUB --> S4["Link Building"]

    S1 -.-> S2
    S2 -.-> S3
    S3 -.-> S4

    style HUB fill:#f9f,stroke:#333,stroke-width:2px

Legend:

• Solid lines = primary hub-spoke links
• Dashed lines = cross-links between spokes

---

Internal Linking Flow

Shows how different site sections link to each other.

graph LR
    subgraph "Marketing"
        HOME["Homepage"]
        FEAT["Features"]
        PRICE["Pricing"]
    end

    subgraph "Content"
        BLOG["Blog"]
        GUIDE["Guides"]
        CASE["Case Studies"]
    end

    subgraph "Product"
        DOCS["Docs"]
        API["API Ref"]
        CHANGE["Changelog"]
    end

    BLOG --> FEAT
    BLOG --> CASE
    CASE --> FEAT
    CASE --> PRICE
    FEAT --> DOCS
    GUIDE --> BLOG
    GUIDE --> DOCS
    HOME --> FEAT
    HOME --> BLOG
    HOME --> CASE

---

Before/After Restructuring

Compare current and proposed site structures side by side.

graph TD
    subgraph "Before"
        B_HOME["Homepage"] --> B_P1["Page 1"]
        B_HOME --> B_P2["Page 2"]
        B_HOME --> B_P3["Page 3"]
        B_HOME --> B_P4["Page 4"]
        B_HOME --> B_P5["Page 5"]
        B_HOME --> B_P6["Page 6"]
        B_HOME --> B_P7["Page 7"]
        B_HOME --> B_P8["Page 8"]
    end

    subgraph "After"
        A_HOME["Homepage"] --> A_S1["Features"]
        A_HOME --> A_S2["Resources"]
        A_HOME --> A_S3["Company"]
        A_S1 --> A_P1["Feature A"]
        A_S1 --> A_P2["Feature B"]
        A_S2 --> A_P3["Blog"]
        A_S2 --> A_P4["Guides"]
        A_S3 --> A_P5["About"]
        A_S3 --> A_P6["Contact"]
    end

---

Color-Coding Conventions

Use styles to highlight page status, priority, or type.

graph TD
    HOME["Homepage"] --> FEAT["Features"]
    HOME --> PRICE["Pricing"]
    HOME --> BLOG["Blog"]
    HOME --> NEW["New Section"]
    HOME --> REMOVE["Deprecated Page"]

    FEAT --> F1["Existing Feature"]
    FEAT --> F2["New Feature"]

    style HOME fill:#4CAF50,color:#fff
    style PRICE fill:#4CAF50,color:#fff
    style FEAT fill:#4CAF50,color:#fff
    style BLOG fill:#4CAF50,color:#fff
    style F1 fill:#4CAF50,color:#fff
    style NEW fill:#2196F3,color:#fff
    style F2 fill:#2196F3,color:#fff
    style REMOVE fill:#f44336,color:#fff

Color key:

• Green (#4CAF50): Existing pages (no changes)
• Blue (#2196F3): New pages to create
• Red (#f44336): Pages to remove or redirect
• Yellow (#FFC107): Pages to restructure or move
• Purple (#9C27B0): High-priority / CTA pages