AI visibility for InfluxDB documentation — parent tracker

## Goal

Improve how InfluxDB is discovered, cited, and recommended in LLM-mediated surfaces — base-model chats, RAG-augmented assistants, and agent/code harnesses.

**Baseline** (980 LLM observations, 2026-04): Provider variance is large (xAI Grok, Anthropic Claude ~33%; OpenAI GPT-5 family <10%). Strong recommendation share in IIoT/BESS verticals; weak in generic monitoring.

This epic tracks the **docs-v2** workstreams. Measurement tooling lives in `influxdata/docs-tooling`. MCP server work lives in the MCP server and `influxdb_pro` repos.

## Phases

### Phase 0 — bug fixes and quick wins

- #7219 — "Which InfluxDB 3 should I use?" decision page
- #7240 — robots.txt AI-bot allow blocks
- #7241 — stop serving /__tests__/shortcodes/ paths in production
- #7242 — TechArticle + SoftwareApplication JSON-LD
- #7243 — Organization JSON-LD with sameAs links
- #7244 — ref-card shortcode
- #7245 — canonical audit of Core engine-concept pages
- #7246 — visual-agent compatibility verification

### Phase 1 — foundations

- #7202 — `/platform/faq.md` FAQ + FAQPage JSON-LD
- #7232 — job-led IA migration kickoff

### Phase 2 — sharing mechanism for IA

- #7233 — design review (decide route before implementation)
- #7297 — inverted-transclusion mechanism spike (IA content sharing)
- #7298 — pilot content-sharing conversion (IA migration de-risk)

### Phase 3 — ongoing editorial discipline

- #7234 — quarterly audits, anchor-deep linking, freshness reviews

## Out of scope for this epic

- Measurement tooling (`influxdata/docs-tooling` repo)
- MCP server improvements (MCP server and `influxdb_pro` repos)
- Marketing-led comparison content and brand-entity work
- The competitive positioning workstream

Start by reviewing the Phase 0–3 child issues listed in this parent tracker, then follow the relevant workstream issue rather than changing this epic directly. Done means the listed documentation workstreams are completed while the measurement tooling, MCP server, marketing content, and competitive positioning remain out of scope.

Written by the indexing model from the issue text.