# SEO Strategy Deck — B2B Observability Platform for ML/LLM Applications

**Prepared:** April 14, 2026
**Business type:** SaaS (B2B)
**Stage:** Pre-launch (no live site)
**Competitors:** LangSmith (LangChain), Arize AI, WhyLabs

---

## Table of Contents

1. [Market & Competitive Landscape](#1-market--competitive-landscape)
2. [Target Keyword Clusters](#2-target-keyword-clusters)
3. [Site Architecture & Pillar Pages](#3-site-architecture--pillar-pages)
4. [Programmatic SEO Opportunities](#4-programmatic-seo-opportunities)
5. [Schema & Structured Data Strategy](#5-schema--structured-data-strategy)
6. [AI Search & GEO Readiness](#6-ai-search--geo-readiness)
7. [Technical SEO Foundation](#7-technical-seo-foundation)
8. [E-E-A-T & Content Quality Plan](#8-e-e-a-t--content-quality-plan)
9. [90-Day Action Plan](#9-90-day-action-plan)
10. [KPIs & Measurement](#10-kpis--measurement)

---

## 1. Market & Competitive Landscape

### Competitor SEO Positioning

| Competitor | Domain Authority Signal | Content Moat | Primary SEO Play |
|-----------|------------------------|-------------|-----------------|
| **LangSmith** (LangChain) | Very high — rides LangChain's massive open-source community + docs domain | Owns "LangChain" brand keyword cluster (~100K+ monthly searches) | Documentation-led SEO; integrations pages; open-source community content |
| **Arize AI** | High — strong blog, glossary, ML observability pillar content | "ML observability" glossary + educational content | Glossary/educational programmatic SEO; "ML monitoring" keyword cluster |
| **WhyLabs** | Medium-high — strong in data/ML monitoring keywords | Open-source whylogs community content | Open-source-led content; "data monitoring" + "AI observability" keywords |

### Competitive Gaps (Our Opportunity)

1. **LLM-specific observability** — Competitors still frame content around general ML; the "LLM observability" and "LLM monitoring" keyword space is undercontested
2. **Prompt engineering + evaluation** — Massive search volume growth, weak coverage from observability tools
3. **Comparison & alternative pages** — "[Competitor] alternatives" queries have no authoritative first-party source
4. **Integration-specific content** — Model-specific and framework-specific pages (OpenAI, Anthropic, Mistral, LlamaIndex, CrewAI, etc.)
5. **Compliance/governance for AI** — Emerging keyword cluster with almost no observability-tool content ranking

---

## 2. Target Keyword Clusters

### Cluster 1: Core Product Keywords (High Intent — Bottom of Funnel)

| Keyword | Est. Monthly Volume | Difficulty | Priority |
|---------|-------------------|-----------|----------|
| llm observability | 1,200–2,400 | Medium | **Critical** |
| llm monitoring tool | 800–1,600 | Medium | **Critical** |
| llm observability platform | 400–800 | Low-Med | **Critical** |
| ai observability | 1,000–2,000 | Medium | **Critical** |
| llm tracing | 600–1,200 | Low | **High** |
| llm evaluation platform | 500–1,000 | Low-Med | **High** |
| llm analytics | 400–800 | Low | **High** |
| ai application monitoring | 800–1,600 | Medium | **High** |
| genai observability | 200–500 | Low | **High** |
| llm ops platform | 300–600 | Low | **High** |

**Strategy:** These map directly to the homepage, product pages, and feature pages. Own every variation with dedicated landing pages.

### Cluster 2: Competitor & Comparison Keywords (High Intent — Decision Stage)

| Keyword | Est. Monthly Volume | Difficulty | Priority |
|---------|-------------------|-----------|----------|
| langsmith alternatives | 1,500–3,000 | Low-Med | **Critical** |
| arize ai alternatives | 500–1,000 | Low | **Critical** |
| whylabs alternatives | 300–600 | Low | **Critical** |
| langsmith vs arize | 400–800 | Low | **High** |
| llm observability tools comparison | 300–600 | Low | **High** |
| langsmith pricing | 2,000–4,000 | Low | **High** |
| arize ai pricing | 500–1,000 | Low | **High** |
| best llm monitoring tools 2026 | 400–800 | Medium | **High** |

**Strategy:** Build a `/compare/` section with programmatic competitor pages (see Section 4). These queries signal purchase-ready buyers.

### Cluster 3: Use-Case & Problem-Aware Keywords (Mid-Funnel)

| Keyword | Est. Monthly Volume | Difficulty | Priority |
|---------|-------------------|-----------|----------|
| llm hallucination detection | 1,500–3,000 | Medium | **Critical** |
| how to monitor llm in production | 800–1,600 | Low-Med | **High** |
| llm cost tracking | 600–1,200 | Low | **High** |
| prompt regression testing | 300–600 | Low | **High** |
| llm latency optimization | 500–1,000 | Low-Med | **High** |
| ai agent debugging | 400–800 | Low | **High** |
| rag evaluation metrics | 1,000–2,000 | Medium | **High** |
| llm token cost optimization | 400–800 | Low | **Medium** |
| detect prompt injection attacks | 800–1,600 | Medium | **Medium** |
| llm output quality scoring | 300–600 | Low | **Medium** |
| trace langchain requests | 500–1,000 | Low | **Medium** |
| monitor openai api usage | 1,000–2,000 | Medium | **Medium** |

**Strategy:** Map each to a dedicated solution page or in-depth blog post within pillar clusters.

### Cluster 4: Educational / Top-of-Funnel Keywords

| Keyword | Est. Monthly Volume | Difficulty | Priority |
|---------|-------------------|-----------|----------|
| what is llm observability | 1,500–3,000 | Medium | **Critical** |
| llmops | 3,000–6,000 | High | **High** |
| llm evaluation metrics | 2,000–4,000 | Medium-High | **High** |
| ml observability | 2,500–5,000 | High | **High** |
| prompt engineering best practices | 5,000–10,000 | High | **Medium** |
| rag architecture patterns | 2,000–4,000 | Medium | **Medium** |
| ai agent architecture | 1,500–3,000 | Medium | **Medium** |
| llm guardrails | 1,000–2,000 | Medium | **Medium** |
| ai governance framework | 1,500–3,000 | High | **Medium** |
| responsible ai monitoring | 800–1,600 | Medium | **Medium** |

**Strategy:** Build pillar content hubs (glossary + guides) to capture top-of-funnel traffic and establish topical authority.

### Cluster 5: Integration & Ecosystem Keywords (Mid-to-Bottom Funnel)

| Keyword | Est. Monthly Volume | Difficulty | Priority |
|---------|-------------------|-----------|----------|
| openai api monitoring | 1,000–2,000 | Low-Med | **High** |
| anthropic api observability | 200–500 | Low | **High** |
| langchain observability | 800–1,600 | Med (LangSmith competes) | **High** |
| llamaindex tracing | 300–600 | Low | **High** |
| crewai monitoring | 200–500 | Low | **High** |
| autogen observability | 200–400 | Low | **Medium** |
| aws bedrock monitoring | 500–1,000 | Low-Med | **Medium** |
| azure openai monitoring | 400–800 | Low-Med | **Medium** |
| vertex ai observability | 300–600 | Low | **Medium** |
| hugging face model monitoring | 400–800 | Low | **Medium** |

**Strategy:** Build `/integrations/[name]` programmatic pages (see Section 4). Each becomes a landing page for that ecosystem's users.

### Cluster 6: Compliance & Enterprise Keywords (Expansion — High ACV)

| Keyword | Est. Monthly Volume | Difficulty | Priority |
|---------|-------------------|-----------|----------|
| ai compliance monitoring | 800–1,600 | Medium | **Medium** |
| eu ai act compliance tools | 500–1,000 | Low-Med | **Medium** |
| llm audit trail | 300–600 | Low | **Medium** |
| ai model governance | 400–800 | Medium | **Medium** |
| soc 2 ai monitoring | 200–400 | Low | **Low** |
| hipaa compliant llm monitoring | 200–400 | Low | **Low** |

**Strategy:** Build long-form "Compliance Hub" pillar page. Enterprise buyers search these terms; high-value low-competition.

---

## 3. Site Architecture & Pillar Pages

### Recommended URL Structure

```
/                                   ← Homepage (core value prop)
├── /product/                       ← Product overview
│   ├── /product/tracing/           ← LLM trace explorer
│   ├── /product/evaluation/        ← Eval & testing
│   ├── /product/monitoring/        ← Production monitoring
│   ├── /product/analytics/         ← Cost & usage analytics
│   ├── /product/guardrails/        ← Safety & guardrails
│   └── /product/playground/        ← Prompt playground
├── /solutions/                     ← Use-case landing pages
│   ├── /solutions/hallucination-detection/
│   ├── /solutions/rag-evaluation/
│   ├── /solutions/agent-debugging/
│   ├── /solutions/cost-optimization/
│   ├── /solutions/prompt-regression-testing/
│   └── /solutions/compliance/
├── /integrations/                  ← Programmatic (Section 4)
│   ├── /integrations/openai/
│   ├── /integrations/anthropic/
│   ├── /integrations/langchain/
│   └── ... (30+ pages)
├── /compare/                       ← Programmatic (Section 4)
│   ├── /compare/langsmith/
│   ├── /compare/arize/
│   └── ... (10+ pages)
├── /customers/                     ← Case studies (post-launch)
│   └── /customers/[company-slug]/
├── /docs/                          ← Technical documentation
│   ├── /docs/getting-started/
│   ├── /docs/sdk/python/
│   ├── /docs/sdk/typescript/
│   ├── /docs/api-reference/
│   └── /docs/guides/
├── /blog/                          ← Content hub
│   └── /blog/[slug]/
├── /glossary/                      ← Programmatic (Section 4)
│   └── /glossary/[term]/
├── /pricing/                       ← Pricing page
├── /about/                         ← About + team
├── /changelog/                     ← Product updates
└── /llms.txt                       ← AI crawler manifest
```

### Pillar Page Strategy (5 Pillars)

Each pillar page is a comprehensive, 3,000–5,000 word hub that links to 10–25 cluster pages. Cluster pages link back to the pillar and to each other.

---

#### Pillar 1: "The Complete Guide to LLM Observability" 🎯 TOP PRIORITY

**URL:** `/blog/llm-observability-guide/`
**Target keyword:** `what is llm observability`, `llm observability`
**Word count:** 4,000–5,000 words
**Content outline:**

1. What is LLM Observability? (Definition, why it differs from traditional APM)
2. The Three Pillars: Traces, Metrics, Evaluations
3. Key Metrics to Track (latency, token usage, cost, quality scores)
4. Observability for Different LLM Architectures (single-call, RAG, agents, chains)
5. Setting Up Observability: Instrumentation Approaches
6. Evaluating LLM Outputs at Scale
7. Production Monitoring vs. Development Debugging
8. Open-Source vs. Commercial Tools (landscape overview)
9. Building an Observability Stack: What to Look For
10. Implementation Checklist

**Cluster pages (link targets):**
- `/glossary/llm-observability/`
- `/glossary/llm-tracing/`
- `/blog/llm-observability-vs-traditional-apm/`
- `/blog/rag-observability-guide/`
- `/blog/ai-agent-observability/`
- `/solutions/hallucination-detection/`
- `/solutions/cost-optimization/`
- `/compare/langsmith/`
- `/integrations/openai/`
- `/integrations/langchain/`

---

#### Pillar 2: "LLM Evaluation: Metrics, Methods & Best Practices"

**URL:** `/blog/llm-evaluation-guide/`
**Target keyword:** `llm evaluation metrics`, `llm evaluation`
**Word count:** 3,500–4,500 words
**Content outline:**

1. Why Evaluation is the Hardest Problem in LLM Apps
2. Taxonomy of Evaluation Methods (reference-based, reference-free, human, LLM-as-judge)
3. Core Metrics: Faithfulness, Relevance, Coherence, Toxicity, Groundedness
4. RAG-Specific Evaluation (context relevance, answer faithfulness)
5. Evaluating AI Agents (task completion, tool use correctness)
6. Automated vs. Human Evaluation Tradeoffs
7. Building an Evaluation Pipeline
8. Regression Testing for Prompts
9. Statistical Significance in LLM Evals
10. Tools & Frameworks Comparison

**Cluster pages:** 12–15 glossary entries, 3 solution pages, 5+ blog posts

---

#### Pillar 3: "LLMOps: The Definitive Guide to Operating LLMs in Production"

**URL:** `/blog/llmops-guide/`
**Target keyword:** `llmops`, `llm ops`
**Word count:** 4,000–5,000 words
**Content outline:**

1. What is LLMOps? (Definition + relationship to MLOps)
2. The LLMOps Lifecycle: Build → Evaluate → Deploy → Monitor → Iterate
3. Prompt Management & Version Control
4. Model Gateway Patterns
5. Cost Management & Token Optimization
6. Latency Optimization Techniques
7. Safety & Guardrails in Production
8. CI/CD for LLM Applications
9. Team Workflows & Collaboration
10. The LLMOps Tool Stack

**Cluster pages:** 15–20 linked pages across blog, glossary, and solutions

---

#### Pillar 4: "AI Compliance & Governance for LLM Applications"

**URL:** `/blog/ai-compliance-governance-guide/`
**Target keyword:** `ai compliance monitoring`, `ai governance framework`
**Word count:** 3,000–4,000 words
**Content outline:**

1. The Regulatory Landscape (EU AI Act, NIST AI RMF, state-level laws)
2. Audit Trails for LLM Applications
3. Data Privacy in LLM Pipelines
4. Bias Detection & Fairness Monitoring
5. Content Safety & Output Filtering
6. SOC 2 / HIPAA Considerations for AI-Powered Products
7. Building a Governance Framework
8. Role of Observability in Compliance
9. Enterprise Requirements Checklist

**Cluster pages:** 8–12 compliance-focused blog + glossary pages

---

#### Pillar 5: "RAG Architecture: Design Patterns, Evaluation & Optimization"

**URL:** `/blog/rag-architecture-guide/`
**Target keyword:** `rag architecture patterns`, `rag evaluation`
**Word count:** 3,500–4,500 words
**Content outline:**

1. RAG Architecture Fundamentals
2. Retrieval Strategies (dense, sparse, hybrid, reranking)
3. Chunking Strategies & Their Impact
4. RAG Evaluation: Context Relevance, Faithfulness, Answer Correctness
5. Debugging RAG Failures with Observability
6. Advanced Patterns (multi-hop, agentic RAG, CRAG)
7. Production RAG: Caching, Fallbacks, Monitoring
8. Cost-Performance Tradeoffs
9. Common Failure Modes & How to Detect Them

**Cluster pages:** 10–15 linked pages

---

## 4. Programmatic SEO Opportunities

### Opportunity 1: Integration Pages — `/integrations/[name]/`

**Estimated pages:** 30–50
**Template:** Each page follows the same structure, populated with integration-specific data.

**Template structure:**

```
H1: [Product Name] + [Integration Name] Integration
Hero: One-line value prop + "Get Started Free" CTA

Section 1: Overview (200+ words, unique per integration)
  - What is [Integration]?
  - Why monitor [Integration] with [Product]?
  - Key use cases for this integration

Section 2: Key Features (bullet list)
  - Automatic [framework/model]-specific tracing
  - [Feature specific to this integration]
  - Cost & latency dashboards for [Integration]
  - Custom eval metrics for [Integration] outputs

Section 3: How It Works (3 steps with code snippet)
  - Install SDK
  - Add [integration-specific] wrapper/decorator
  - View traces in dashboard

Section 4: Metrics You Can Track (data table)
  - [Integration-specific metrics list]

Section 5: Related Integrations (internal links)

Section 6: CTA (Free trial / docs link)
```

**Target integrations (initial 30):**

| Category | Integrations |
|----------|-------------|
| **LLM Providers** | OpenAI, Anthropic, Google Gemini, Mistral, Cohere, Meta Llama, AWS Bedrock, Azure OpenAI, Google Vertex AI, Groq, Together AI, Fireworks AI, Perplexity API |
| **Frameworks** | LangChain, LlamaIndex, CrewAI, AutoGen, Haystack, Semantic Kernel, Vercel AI SDK, Spring AI |
| **Vector DBs** | Pinecone, Weaviate, Chroma, Qdrant, Milvus, pgvector |
| **Infra** | Kubernetes, Docker, Terraform |

**Quality gates (per quality-gates.md):**
- ✅ 100% template variable coverage — no empty fields
- ✅ Unique intro paragraph per page (200+ words)
- ✅ 3–8 internal links per 1,000 words
- ✅ Canonical tags matching served URLs
- ✅ <5% thin page ratio

---

### Opportunity 2: Competitor Comparison Pages — `/compare/[competitor]/`

**Estimated pages:** 8–12
**Template:**

```
H1: [Product Name] vs. [Competitor]: [Year] Comparison
Meta title: [Product] vs [Competitor] — Honest Comparison ([Year])

Section 1: TL;DR Comparison Table
  Feature | [Product] | [Competitor]
  Traces  | ✅         | ✅
  Evals   | ✅         | ⚠️ Limited
  ...

Section 2: Overview of Both Tools (200+ words each, balanced and fair)

Section 3: Feature-by-Feature Deep Dive (800+ words)
  - Tracing & Debugging
  - Evaluation & Testing
  - Production Monitoring
  - Pricing & Scalability
  - Integrations
  - Self-Hosting / Data Residency

Section 4: Where [Competitor] Wins (builds credibility — critical for E-E-A-T)

Section 5: Where [Product] Wins

Section 6: Who Should Choose What (decision framework)

Section 7: Migration Guide (if switching from competitor)

Section 8: FAQ (3-5 questions, targeting People Also Ask)
```

**Target competitors:**
LangSmith, Arize AI, WhyLabs, Helicone, Braintrust, Weights & Biases (Weave), Datadog LLM Monitoring, New Relic AI Monitoring, Dynatrace, Honeycomb

**Quality gates:**
- ✅ Min 600 words per comparison page
- ✅ 60%+ unique content per page (not just swapping competitor name)
- ✅ "Where [Competitor] Wins" section required (E-E-A-T trust signal)
- ✅ Updated quarterly with freshness date visible

---

### Opportunity 3: Glossary / Learning Hub — `/glossary/[term]/`

**Estimated pages:** 60–100
**Template:**

```
H1: What is [Term]? — Definition & Guide
Meta: "[Term] explained: definition, how it works, and why it matters for LLM applications."

Section 1: Definition (50–100 words, concise — optimized for AI Overview extraction)

Section 2: How It Works (300+ words with diagram/visual placeholder)

Section 3: Why It Matters for LLM Apps (200+ words — ties back to our product domain)

Section 4: Example (code snippet or scenario)

Section 5: Related Concepts (internal links to other glossary pages)

Section 6: Learn More (links to pillar pages, blog posts, docs)
```

**Seed terms (organized by category):**

| Category | Terms |
|----------|-------|
| **Core Concepts** | LLM Observability, LLM Tracing, LLM Monitoring, LLM Evaluation, LLMOps, AI Observability, GenAI Observability |
| **Metrics** | Token Usage, LLM Latency, Time to First Token, Tokens per Second, LLM Cost per Query, Perplexity Score |
| **Evaluation** | Faithfulness, Groundedness, Context Relevance, Answer Relevance, LLM-as-a-Judge, BLEU Score, ROUGE Score, BERTScore, G-Eval, Ragas |
| **Architecture** | RAG (Retrieval-Augmented Generation), AI Agent, Chain of Thought, Function Calling, Tool Use, Prompt Chaining, Embedding, Vector Search, Reranking |
| **Safety** | Hallucination, Prompt Injection, Jailbreak, Guardrails, Content Filtering, Toxicity Detection, PII Detection |
| **Ops** | Prompt Versioning, A/B Testing for Prompts, Canary Deployment (LLMs), Model Gateway, Semantic Caching, Fallback Routing |
| **Compliance** | AI Audit Trail, Model Card, EU AI Act, NIST AI RMF, Algorithmic Impact Assessment |

**Quality gates:**
- ✅ Unique intro definition per term (no boilerplate swaps)
- ✅ Min 500 words per glossary entry (per quality-gates.md FAQ threshold)
- ✅ Internal linking cluster (each page links to 3–8 related terms)
- ✅ Breadcrumb trail: Home > Glossary > [Term]

---

### Opportunity 4: "Best [Tool Type] for [Use Case]" Listicle Pages

**Estimated pages:** 8–12
**URL:** `/blog/best-[category]-tools/`

| Page | Target Keyword |
|------|---------------|
| Best LLM Observability Tools (2026) | best llm observability tools |
| Best LLM Evaluation Frameworks | best llm evaluation frameworks |
| Best AI Agent Monitoring Tools | best ai agent monitoring tools |
| Best RAG Evaluation Tools | best rag evaluation tools |
| Best LLMOps Platforms | best llmops platforms |
| Best AI Monitoring Tools for Production | best ai monitoring tools production |
| Best Open Source LLM Tracing Tools | open source llm tracing |
| Best Prompt Management Tools | best prompt management tools |

**Quality gates:** Min 800 words, 85% unique, own product listed but not always #1 (E-E-A-T credibility).

---

## 5. Schema & Structured Data Strategy

### Site-Wide Schema (Every Page)

```jsonld
{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@type": "Organization",
      "@id": "https://[domain]/#organization",
      "name": "[Product Name]",
      "url": "https://[domain]",
      "logo": {
        "@type": "ImageObject",
        "url": "https://[domain]/logo.png"
      },
      "sameAs": [
        "https://twitter.com/[handle]",
        "https://github.com/[org]",
        "https://linkedin.com/company/[name]"
      ],
      "contactPoint": {
        "@type": "ContactPoint",
        "contactType": "sales",
        "email": "sales@[domain]"
      }
    },
    {
      "@type": "WebSite",
      "@id": "https://[domain]/#website",
      "name": "[Product Name]",
      "url": "https://[domain]",
      "publisher": { "@id": "https://[domain]/#organization" },
      "potentialAction": {
        "@type": "SearchAction",
        "target": "https://[domain]/search?q={search_term_string}",
        "query-input": "required name=search_term_string"
      }
    },
    {
      "@type": "WebPage",
      "@id": "https://[domain]/[current-page]/#webpage",
      "url": "https://[domain]/[current-page]/",
      "name": "[Page Title]",
      "isPartOf": { "@id": "https://[domain]/#website" },
      "breadcrumb": { "@id": "https://[domain]/[current-page]/#breadcrumb" }
    },
    {
      "@type": "BreadcrumbList",
      "@id": "https://[domain]/[current-page]/#breadcrumb",
      "itemListElement": [
        { "@type": "ListItem", "position": 1, "name": "Home", "item": "https://[domain]/" },
        { "@type": "ListItem", "position": 2, "name": "[Section]", "item": "https://[domain]/[section]/" },
        { "@type": "ListItem", "position": 3, "name": "[Page Title]" }
      ]
    }
  ]
}
```

### Page-Type Specific Schema

| Page Type | Schema Type(s) | Rich Result Target |
|-----------|---------------|-------------------|
| **Homepage** | `Organization`, `WebSite`, `WebPage` | Knowledge Panel, Sitelinks Search Box |
| **Blog posts** | `BlogPosting` + `Person` (author) | Article rich result |
| **Glossary pages** | `Article` (type: `TechArticle`) + `BreadcrumbList` | Article rich result, breadcrumbs |
| **Comparison pages** | `WebPage` + `BreadcrumbList` + `Table` (for comparison data) | Breadcrumbs |
| **Integration pages** | `SoftwareApplication` + `WebPage` + `BreadcrumbList` | Software rich result, breadcrumbs |
| **Pricing page** | `WebPage` + `Product` + `Offer` (for each tier) | Product/pricing snippet |
| **Documentation** | `TechArticle` + `BreadcrumbList` + `SiteNavigationElement` | Breadcrumbs |
| **Case studies** | `Article` + `Organization` (customer) | Article rich result |
| **Changelog** | `Article` (per entry) + `ItemList` | — |
| **Author pages** | `ProfilePage` + `Person` with `sameAs` links | Profile badge in SERP |

### Schema Rules (per schema-types.md)

- ✅ JSON-LD format only (no Microdata or RDFa)
- ✅ Use `@graph` pattern when multiple entities on one page
- ✅ `WebPage.url` must match canonical URL
- ✅ All `BlogPosting` and `Article` must include `image` property
- ✅ All blog posts must include `Person` schema with `sameAs` links to author profiles
- ⛔ Do NOT use `HowTo` schema (deprecated September 2023)
- ⚠️ Do NOT add `FAQPage` schema for Google rich results (restricted to .gov / healthcare since August 2023)
- ℹ️ FAQ content is still fine on-page — it helps AI search citation even without schema benefit

### Pricing Page Schema (Detailed)

```jsonld
{
  "@type": "Product",
  "name": "[Product Name] — [Tier Name]",
  "description": "[Tier description]",
  "brand": { "@id": "https://[domain]/#organization" },
  "offers": {
    "@type": "Offer",
    "price": "99",
    "priceCurrency": "USD",
    "priceSpecification": {
      "@type": "UnitPriceSpecification",
      "price": "99",
      "priceCurrency": "USD",
      "billingDuration": "P1M"
    },
    "availability": "https://schema.org/InStock",
    "url": "https://[domain]/pricing/"
  }
}
```

---

## 6. AI Search & GEO Readiness

Modern SEO must optimize for AI search engines (ChatGPT, Perplexity, Gemini, Claude) alongside Google. This is especially critical for B2B SaaS where developers and engineers are primary buyers.

### 6.1 `llms.txt` Manifest

Create `/llms.txt` at site root — provides AI crawlers with a structured overview of your site.

```
# [Product Name]

## About
[Product Name] is a B2B observability platform for LLM and AI applications. 
We provide tracing, evaluation, monitoring, and analytics for teams building 
with large language models.

## Documentation
- [Getting Started](https://[domain]/docs/getting-started/)
- [Python SDK](https://[domain]/docs/sdk/python/)
- [TypeScript SDK](https://[domain]/docs/sdk/typescript/)
- [API Reference](https://[domain]/docs/api-reference/)

## Key Pages
- [Product Overview](https://[domain]/product/)
- [Integrations](https://[domain]/integrations/)
- [Pricing](https://[domain]/pricing/)
- [Blog](https://[domain]/blog/)
- [Glossary](https://[domain]/glossary/)
```

### 6.2 Citability Optimization

For every key page, ensure the first 2–3 sentences are **self-contained, citable statements** that AI systems can extract:

> ❌ "In this article, we'll explore what LLM observability means."
> ✅ "LLM observability is the practice of collecting, analyzing, and visualizing traces, metrics, and evaluations from large language model applications in production to understand behavior, debug issues, and optimize performance."

**Rules:**
- Lead with a clear definition or factual claim
- Include the target keyword in the first sentence
- Keep the opening paragraph under 60 words for extraction
- Structure content with descriptive H2/H3 headers (AI systems use headers for comprehension)
- Use tables and bullet lists for structured data (high citability)

### 6.3 Brand Mention Strategy

AI systems learn brand associations from co-occurrence in content. Ensure the product name appears in contexts like:

- "Tools like LangSmith, Arize, **[Product Name]**, and WhyLabs provide LLM observability..."
- External content (guest posts, open-source READMEs, community forums) that naturally mentions the product alongside competitors
- Comparison pages that clearly position the product in the competitive landscape

### 6.4 `robots.txt` for AI Crawlers

```
User-agent: *
Allow: /

# Explicitly allow AI crawlers
User-agent: GPTBot
Allow: /

User-agent: ChatGPT-User
Allow: /

User-agent: Claude-Web
Allow: /

User-agent: PerplexityBot
Allow: /

User-agent: Google-Extended
Allow: /

Sitemap: https://[domain]/sitemap.xml
```

---

## 7. Technical SEO Foundation

Since we're building from scratch, we can get the technical foundation right from day one.

### 7.1 Core Technical Requirements

| Requirement | Spec | Priority |
|------------|------|----------|
| **HTTPS** | TLS 1.3, HSTS enabled, all resources over HTTPS | Critical |
| **Canonical tags** | Self-referencing canonical on every page | Critical |
| **XML Sitemap** | Auto-generated, submitted to GSC, <50K URLs per file | Critical |
| **Robots.txt** | Allow all public content, block /app/ dashboard, allow AI bots | Critical |
| **Mobile responsive** | Mobile-first design, viewport meta tag | Critical |
| **Core Web Vitals** | LCP < 2.5s, INP < 200ms, CLS < 0.1 | Critical |
| **Page speed** | Target < 1.5s LCP on 4G connection | High |
| **Heading hierarchy** | Single H1 per page, logical H2→H3→H4 nesting | High |
| **Image optimization** | WebP/AVIF, lazy loading, descriptive alt text, responsive srcset | High |
| **Internal linking** | 3–8 links per 1,000 words, contextual anchors | High |
| **URL structure** | Lowercase, hyphens, no trailing params, max 3 levels deep | High |
| **Security headers** | CSP, HSTS, X-Content-Type-Options, X-Frame-Options | Medium |
| **404 handling** | Custom 404 page with search + popular links | Medium |
| **Redirect strategy** | 301 only, no chains > 2 hops | Medium |

### 7.2 Sitemap Strategy

```
/sitemap.xml                    ← Index sitemap
  ├── /sitemap-pages.xml        ← Core pages (product, solutions, pricing, about)
  ├── /sitemap-blog.xml         ← Blog posts
  ├── /sitemap-docs.xml         ← Documentation
  ├── /sitemap-glossary.xml     ← Glossary entries
  ├── /sitemap-integrations.xml ← Integration pages
  ├── /sitemap-compare.xml      ← Comparison pages
  └── /sitemap-changelog.xml    ← Changelog entries
```

### 7.3 Rendering & JavaScript

- **Recommendation:** Use Next.js (App Router) or Astro with SSG/ISR for marketing pages
- Static generation for blog, glossary, integrations, comparisons
- SSR only where personalization is needed
- Ensure all critical content is in the initial HTML (not client-rendered behind JS)
- Pre-render all programmatic pages at build time

---

## 8. E-E-A-T & Content Quality Plan

### Building E-E-A-T from Zero (Pre-Launch)

Since this is a new domain with no authority, E-E-A-T must be deliberately constructed.

#### Experience Signals
- **Founding team content**: Blog posts from founders/engineers describing building the product, technical challenges, design decisions
- **Dogfooding**: "How we use [Product] to monitor our own LLM features" (publish post-launch)
- **Original research**: Run benchmarks, publish original data (e.g., "We analyzed 1M LLM API calls — here's what we found about latency distributions")

#### Expertise Signals
- **Author pages** for every content creator: `/blog/authors/[name]/`
  - Include bio, credentials, LinkedIn, GitHub, Twitter links
  - `Person` schema with `sameAs` links
- **Technical depth**: Every blog post should demonstrate genuine expertise (not surface-level AI-generated content)
- **Code examples**: Real, runnable code in blog posts and docs

#### Authoritativeness Signals (Build Over 90 Days)
- **Open-source project**: Publish SDK / instrumentation library on GitHub (generates backlinks + trust)
- **Conference talks**: Submit to AI/ML conferences (PyCon, MLOps World, AI Engineer Summit)
- **Guest posts**: Write for established ML/AI publications (Towards Data Science, The New Stack, dev.to)
- **Community presence**: Active in LLM-related Discord servers, Reddit (r/MachineLearning, r/LangChain), Hacker News

#### Trustworthiness Signals (Day One)
- ✅ HTTPS enforced site-wide
- ✅ Clear company information on `/about/`
- ✅ Privacy policy and terms of service
- ✅ Transparent pricing (no "contact us for pricing" on lower tiers)
- ✅ Security page with SOC 2 status, data handling practices
- ✅ Real team photos (not stock)

### Content Quality Gates (per quality-gates.md)

| Content Type | Minimum Words | Unique Content |
|-------------|--------------|----------------|
| Blog posts | 800 (target 1,500–3,000) | 85%+ unique |
| Glossary entries | 500+ | Unique intro per term |
| Integration pages | 500+ (200+ unique intro) | 60%+ unique |
| Comparison pages | 600+ | 60%+ unique |
| Solution pages | 500+ | 70%+ unique |
| Case studies | 700+ | 85%+ unique |
| Documentation | 600+ | N/A (technical accuracy > uniqueness) |

---

## 9. 90-Day Action Plan

### Phase 1: Foundation (Days 1–30) — 🔴 CRITICAL

**Goal:** Launch site with technical SEO best practices, core pages live, first pillar content published.

#### Week 1–2: Technical Setup
| Task | Owner | Priority |
|------|-------|----------|
| Register domain, set up hosting (Vercel / Cloudflare) | Engineering | Critical |
| Implement Next.js / Astro with SSG for marketing pages | Engineering | Critical |
| Set up HTTPS, security headers, HSTS | Engineering | Critical |
| Configure robots.txt (allow AI bots, block /app/) | Engineering | Critical |
| Create XML sitemap generation (auto from routes) | Engineering | Critical |
| Set up Google Search Console + Bing Webmaster Tools | SEO Lead | Critical |
| Set up Google Analytics 4 + server-side tracking | SEO Lead | Critical |
| Implement site-wide schema (Organization, WebSite, BreadcrumbList) | Engineering | Critical |
| Create llms.txt manifest | SEO Lead | High |

#### Week 2–3: Core Pages
| Task | Owner | Priority |
|------|-------|----------|
| Homepage (300+ words, clear value prop, product schema) | Marketing + SEO | Critical |
| Product overview page + 4–6 feature sub-pages | Marketing + SEO | Critical |
| Pricing page (with Product + Offer schema) | Marketing | Critical |
| About page (team bios, company story, photos) | Marketing | High |
| Create author page template with Person schema | Engineering + SEO | High |
| Privacy policy, terms of service, security page | Legal + Marketing | High |
| Set up blog infrastructure (BlogPosting schema, author attribution) | Engineering | High |

#### Week 3–4: First Content
| Task | Owner | Priority |
|------|-------|----------|
| **Publish Pillar 1**: "Complete Guide to LLM Observability" (4,000+ words) | Content Lead | Critical |
| Publish 3 supporting blog posts for Pillar 1 cluster | Content Lead | High |
| Launch first 5 glossary pages (LLM Observability, LLM Tracing, LLM Monitoring, LLM Evaluation, LLMOps) | Content Lead | High |
| Launch first 3 integration pages (OpenAI, Anthropic, LangChain) | Content + Engineering | High |
| Launch first 2 comparison pages (vs LangSmith, vs Arize) | Content Lead | High |
| Submit sitemap to Google Search Console | SEO Lead | High |

**Phase 1 Deliverables:**
- ✅ Site live with technical SEO foundation
- ✅ 15–20 indexable pages
- ✅ 1 pillar page published
- ✅ Schema implemented on all page types
- ✅ GSC + GA4 tracking live

---

### Phase 2: Scale Content & Programmatic SEO (Days 31–60) — 🟡 HIGH

**Goal:** Launch programmatic page templates, publish second pillar, build backlink pipeline.

#### Week 5–6: Programmatic Page Buildout
| Task | Owner | Priority |
|------|-------|----------|
| Build integration page template + launch 15 more integrations (total: 18) | Engineering + Content | High |
| Build comparison page template + launch 5 more comparisons (total: 7) | Content Lead | High |
| Build glossary page template + launch 20 more terms (total: 25) | Content Lead | High |
| Ensure all programmatic pages pass quality gates (unique intros, no empty variables) | SEO Lead (QA) | High |
| Implement internal linking audit — verify 3–8 links per 1K words across all pages | SEO Lead | High |

#### Week 6–7: Second Pillar & Blog Cadence
| Task | Owner | Priority |
|------|-------|----------|
| **Publish Pillar 2**: "LLM Evaluation: Metrics, Methods & Best Practices" | Content Lead | High |
| Publish 4 supporting blog posts for Pillar 2 cluster | Content Lead | High |
| Begin 2x/week blog publishing cadence | Content Lead | High |
| Launch 3 solution pages (Hallucination Detection, RAG Evaluation, Cost Optimization) | Content + Marketing | High |

#### Week 7–8: Authority Building
| Task | Owner | Priority |
|------|-------|----------|
| Publish open-source SDK/library on GitHub (with README backlinks) | Engineering | High |
| Submit 2–3 guest post pitches to AI/ML publications | Content Lead | Medium |
| Launch product on Product Hunt / Hacker News | Marketing | Medium |
| Begin community engagement (Reddit, Discord, Twitter/X) | DevRel | Medium |
| Submit talks to 2 upcoming ML/AI conferences | DevRel | Medium |

**Phase 2 Deliverables:**
- ✅ 60–80 indexable pages
- ✅ 2 pillar pages published
- ✅ Programmatic templates live and passing quality gates
- ✅ Open-source project published
- ✅ First backlinks acquired

---

### Phase 3: Optimize & Expand (Days 61–90) — 🟢 MEDIUM

**Goal:** Publish remaining pillars, reach 100+ pages, start measuring organic traffic, optimize based on GSC data.

#### Week 9–10: Content Expansion
| Task | Owner | Priority |
|------|-------|----------|
| **Publish Pillar 3**: "LLMOps Definitive Guide" | Content Lead | High |
| **Publish Pillar 4**: "AI Compliance & Governance Guide" | Content Lead | Medium |
| Launch 15 more glossary pages (total: 40) | Content Lead | High |
| Launch 10 more integration pages (total: 28) | Content + Engineering | Medium |
| Launch 3 more comparison pages (total: 10) | Content Lead | Medium |
| Publish 4 "Best [X] Tools" listicle posts | Content Lead | Medium |

#### Week 10–11: Optimization Cycle
| Task | Owner | Priority |
|------|-------|----------|
| Review GSC data: identify impressions without clicks → optimize titles/metas | SEO Lead | High |
| Review GSC data: identify queries ranking 5–20 → create/improve content | SEO Lead | High |
| Run Core Web Vitals audit → fix any regressions | Engineering | High |
| Update internal linking across all new content | SEO Lead | Medium |
| A/B test meta titles on top 10 landing pages | SEO Lead | Medium |

#### Week 11–12: Case Studies & Expansion
| Task | Owner | Priority |
|------|-------|----------|
| **Publish Pillar 5**: "RAG Architecture Guide" | Content Lead | Medium |
| Publish first 2 customer case studies (if available) | Marketing | Medium |
| Launch changelog page with regular updates | Engineering + Marketing | Medium |
| Publish original research piece (benchmark data, survey, analysis) | Content Lead | Medium |
| Plan Phase 4: international/hreflang strategy, video SEO, advanced link building | SEO Lead | Low |

**Phase 3 Deliverables:**
- ✅ 100–130 indexable pages
- ✅ 5 pillar pages published
- ✅ First organic traffic data analyzed and acted on
- ✅ CWV passing on all templates
- ✅ Content cadence established at 2x/week blog + regular programmatic page additions

---

## 10. KPIs & Measurement

### Primary Metrics (Track Monthly)

| KPI | Day 30 Target | Day 60 Target | Day 90 Target |
|-----|--------------|--------------|--------------|
| Indexed pages | 15–20 | 60–80 | 100–130 |
| Organic impressions (GSC) | Baseline | 5,000–15,000/mo | 20,000–50,000/mo |
| Organic clicks | Baseline | 200–800/mo | 1,000–3,000/mo |
| Avg. position (target keywords) | Baseline | Top 30 for 10+ keywords | Top 20 for 20+ keywords |
| Referring domains | 0 | 10–20 | 30–50 |
| Core Web Vitals pass rate | 100% | 100% | 100% |
| Blog posts published | 4 | 15 | 30 |
| Programmatic pages live | 10 | 50 | 80 |

### Secondary Metrics

| KPI | Measurement |
|-----|-------------|
| CTR from SERP | GSC (target >3% avg) |
| Bounce rate on blog | GA4 (target <65%) |
| Time on page (blog) | GA4 (target >2 min) |
| Scroll depth (pillar pages) | GA4 (target >60% reach midpoint) |
| Schema validation errors | GSC Enhancement reports (target: 0 errors) |
| AI search citations | Manual tracking — weekly searches on Perplexity/ChatGPT for target queries |
| Brand search volume | GSC — track "[Product Name]" query growth |

### Reporting Cadence

| Report | Frequency | Audience |
|--------|-----------|----------|
| Keyword rankings tracker | Weekly | SEO Lead |
| Content pipeline status | Weekly | Content Lead + Marketing |
| GSC performance summary | Bi-weekly | Marketing + Leadership |
| Full SEO health report | Monthly | Leadership |
| Competitive SERP analysis | Monthly | SEO Lead + Marketing |
| AI search citation audit | Monthly | SEO Lead |

---

## Appendix A: Content Calendar Template (Weeks 1–12)

| Week | Pillar Content | Blog Posts | Programmatic Pages | Backlink Actions |
|------|---------------|------------|-------------------|-----------------|
| 1–2 | — | — | — | Set up profiles (GitHub, social, directories) |
| 3 | Pillar 1: LLM Observability Guide | 1 supporting post | 5 glossary + 3 integrations + 2 comparisons | — |
| 4 | — | 2 supporting posts | — | Submit to product directories |
| 5 | — | 2 posts (Pillar 2 cluster) | 10 glossary + 8 integrations + 2 comparisons | — |
| 6 | Pillar 2: LLM Evaluation Guide | 2 supporting posts | 5 glossary + 4 integrations + 3 comparisons | Open-source SDK launch |
| 7 | — | 2 posts | 3 solution pages | Guest post #1 pitch |
| 8 | — | 2 posts | — | Product Hunt / HN launch |
| 9 | Pillar 3: LLMOps Guide | 2 supporting posts | 8 glossary + 5 integrations | Guest post #1 published |
| 10 | Pillar 4: AI Compliance Guide | 2 posts (listicles) | 7 glossary + 5 integrations + 3 comparisons | Conference talk submit |
| 11 | — | 2 posts (optimization from GSC data) | 2 case studies | Guest post #2 pitch |
| 12 | Pillar 5: RAG Architecture Guide | 2 posts + 1 original research | Remaining integrations | Community engagement ramp |

---

## Appendix B: Quick Wins Checklist (First 48 Hours After Site Launch)

- [ ] Submit domain to Google Search Console and verify ownership
- [ ] Submit XML sitemap via GSC
- [ ] Submit to Bing Webmaster Tools
- [ ] Request indexing for homepage + top 5 pages via GSC URL Inspection
- [ ] Set up Google Analytics 4 with enhanced measurement
- [ ] Verify robots.txt is accessible and correct
- [ ] Verify all schema validates in Google Rich Results Test
- [ ] Verify Core Web Vitals pass on all page templates
- [ ] Submit to AI search indexes: Perplexity, Bing (powers Copilot/ChatGPT)
- [ ] Ensure llms.txt is accessible
- [ ] Create and submit to relevant SaaS directories (G2, Product Hunt, AlternativeTo, etc.)
- [ ] Set up rank tracking for top 30 target keywords

---

*Generated via `/seo plan saas` — B2B LLM Observability Platform*
*Framework version: SEO Skill v2026.04*