SKILL.md · 24000
ve-data-sharing) in June 2026 — a markdown spec for representing site content as a directory of cross-linked files with YAML frontmatter, agent-readable without scraping. Built primarily for data-team catalog metadata; the site-readable-by-agents repurposing was popularized by Suganthan Mohanadasan. No confirmed AI-search ranking signal today — treat it as protocol-layer registration like early schema.org. For the full breakdown, implementation paths (free generator, WordPress plugin, by-hand), hosting guidance, and when to skip, see references/okf.md.
Schema Markup for AI
Structured data helps AI systems understand your content. Key schemas:
| Content Type | Schema | Why It Helps |
|-------------|--------|-------------|
| Articles/Blog posts | Article, BlogPosting | Author, date, topic identification |
| How-to content | HowTo | Step extraction for process queries |
| FAQs | FAQPage | Direct Q&A extraction |
| Products | Product | Pricing, features, reviews |
| Comparisons | ItemList | Structured comparison data |
| Reviews | Review, AggregateRating | Trust signals |
| Organization | Organization | Entity recognition |
No well-documented study isolates a schema lift on AI citations, so treat schema as context that helps engines parse your pages and expect no fixed lift from it. Google's note: structured data is "not required for generative AI search" but is recommended for overall SEO strategy. For implementation, use the schema skill.
Agentic Experiences
Beyond AI search engines summarizing content, autonomous agents are starting to access sites directly — clicking, reading, comparing, even buying on behalf of users. Google's guide flags this as an emerging category to plan for.
How agents access your site:
- Visual rendering — they screenshot/read the page like a user would
- DOM inspection — they parse the page's HTML structure
- Accessibility tree — they rely on the same semantic information assistive tech uses (labels, roles, landmarks, headings)
What to do:
- Render meaningful content without heavy JS gymnastics — if the page is blank until 4 frameworks finish loading, agents see blank
- Semantic HTML — use
<main>,<nav>,<article>,<button>, proper heading hierarchy,alttext on images - Clean accessibility tree — every interactive element labelled; ARIA used correctly (or not at all when native HTML suffices)
- Stable selectors / predictable layouts — agents struggle with sites that re-render every interaction
- Visible pricing, specs, contact info — anything an agent would need to make a buying recommendation should be on a public, indexable page (this is where
/pricing.mdand similar files help). Date the facts that change ("4.7 on G2 as of October 2026") so an agent can judge freshness - Proof as text — testimonials, ratings, and named customer logos in the HTML as text, not baked into images or injected by a widget script. If you can't select it with the mouse, an agent may not read it
Emerging — Universal Commerce Protocol (UCP): Google references UCP as a forthcoming protocol that will give agents standardized hooks for commerce interactions (catalog discovery, pricing, checkout). Watch for adoption; for now, the structural recommendations above are the precursor.
For ecom and local business specifically, Google highlights:
- Merchant Center feeds + Google Business Profile for product/service visibility in AI Search
- Business Agent for conversational customer engagement (where applicable)
Content Types That Get Cited Most
Not all content is equally citable — and the format mix is volatile. The long-standing baseline had comparison articles (~33%) and listicles (~10%) among the top citation earners, but ChatGPT 5.6 (Aug 2026) demoted the exploited formats: listicle citations fell −50.5% and comparison-page citations −32.1%, while site: and "official" retrieval surged — a shift toward primary sources and owned pages. Format strategy is now per-platform (comparisons still work on Google AIO/Gemini/Perplexity). See references/format-volatility.md for the shift data, the per-platform format table, LinkedIn's citation numbers, and the ChatGPT fan-out extraction diagnostic.
Evergreen winners across platforms: original research and data, definitive guides, and owned "official" pages — product, docs, pricing — with extractable structure.
Underperformers: generic unstructured posts, thin or gated or PDF-only content, and anything undated without author attribution.
Citation ≠ recommendation. Getting cited means your content was useful to consult; getting recommended — onto the buyer's actual shortlist — is governed by web-wide consensus (reviews, forums, analysts, press) and is largely independent of your own content. Self-promotional "best [category]" listicles can even backfire for emerging brands: in one 100-query B2B study, 69% of the AI Overview citations that self-promotional listicles earned came in answers that recommended competitors instead of the publishing brand. See references/citations-vs-recommendations.md for the visibility ladder (retrieved → cited → mentioned → recommended), stage-dependent buyer's-guide strategy, what earns recommendations, and the attribution blind spot.
Monitoring AI Visibility
What to Track
| Metric | What It Measures | How to Check | |--------|-----------------|-------------| | AI Overview presence | Do AI Overviews appear for your queries? | Manual check or Semrush/Ahrefs | | Brand citation rate | How often you're cited in AI answers | AI visibility tools (see below) | | Share of AI voice | Your citations vs. competitors | Peec AI, Otterly, ZipTie, Omnia | | Citation sentiment | How AI describes your brand | Manual review + monitoring tools | | Recommendation rate | Whether you're on the shortlist, not just cited (see citations-vs-recommendations.md) | Prompt tracking + mention framing | | Source attribution | Which pages get cited, and what AI exposure does downstream | AI referrals plus delayed branded and direct visits (ai-attribution.md) |
AI Visibility Monitoring Tools
| Tool | Coverage | Best For | |------|----------|----------| | Otterly AI | ChatGPT, Perplexity, Google AI Overviews | Share of AI voice tracking | | Peec AI | ChatGPT, Gemini, Perplexity, Claude, Copilot+ | Multi-platform monitoring at scale | | ZipTie | Google AI Overviews, ChatGPT, Perplexity | Brand mention + sentiment tracking | | LLMrefs | ChatGPT, Perplexity, AI Overviews, Gemini | SEO keyword → AI visibility mapping | | Profound, Ahrefs Brand Radar, Semrush | Major assistants and Google AI surfaces | Larger programs: cited sources, answer text, prompt demand (Profound's studies are cited in the references as vendor research) | | Omnia | Google AI Mode, Google AI Overviews, ChatGPT, Perplexity, Gemini, Claude, Copilot | AI visibility monitoring |
DIY Monitoring (No Tools)
Monthly manual check:
- Pick your top 20 queries
- Run each through ChatGPT, Perplexity, and Google
- Record: Are you cited? Who is? What page? Log it in a spreadsheet and track month-over-month
AI answers are non-deterministic — one run is an anecdote, not a measurement. Run each query 3–5 times per platform and track the mention rate with its sample size ("cited 3/5, n=5"), comparing rates over time rather than single runs. Full rigor checklist in references/format-volatility.md.
Search Console expectations
Google's guide is explicit: there is no AI-specific Search Console reporting. AI Overviews and AI Mode use core Search ranking, so the standard Search Console reports (Performance, Coverage, Core Web Vitals) are still what you measure with for Google. The third-party tools above are the only way to see cross-platform AI citation behavior.
What NOT to Do
Google's guide calls these out explicitly — they hurt across both traditional Search and AI features.
- Write separate content "for AI". Same content should serve people and AI. Writing variants targeted at AI systems risks the scaled content abuse spam policy — Google's words.
- Chunk pages into AI-bait fragments. Google's guide is direct: "Don't break your content into tiny pieces for AI to better understand it." Use normal paragraph + heading structure.
- Generate at scale for ranking manipulation. AI-generated content is fine if it meets Search Essentials and spam policies. Mass-producing thin variations does not.
- Pursue inauthentic mentions. Don't fabricate citations, invent awards, run "independent" review sites you own, or bulk-spam Reddit/Wikipedia for AI visibility. Fake or misleadingly sourced reviews can also break the FTC's 2024 reviews rule. Real participation only.
- Treat every AI user agent as the same control.
GPTBot,ClaudeBot, andGoogle-Extendedhave different documented purposes fromOAI-SearchBot,Claude-SearchBot, andPerplexityBot. Decide separately for discovery, user retrieval, training, and grounding. - Hide your main content behind JS that doesn't render. Both core Search and AI agents need to see your content; JS-only rendering loses both audiences.
- Skip E-E-A-T fundamentals. Author identity, first-hand experience, expertise signals, transparent sourcing — Google's guide leans heavily on these for AI features.
AI SEO by Content Type
For tactical guidance on SaaS product pages, blog content, comparison/alternative pages, documentation, and local/ecom (Google's emphasis on Merchant Center + Business Profile), see references/content-types.md.
Common Mistakes
- Ignoring AI search entirely — AI Overviews appear on roughly half of tracked queries in many industries (BrightEdge, Feb 2026), and assistant usage keeps growing
- Treating AI SEO as separate from SEO — Good traditional SEO is the foundation; AI SEO adds structure and authority on top
- Writing for AI, not humans — If content reads like it was written to game an algorithm, it won't get cited or convert
- No freshness signals — Undated content loses to dated content because AI systems weight recency heavily. Show when content was last updated
- Gating all content — AI can't access gated content. Keep your most authoritative content open
- Ignoring third-party presence — Shortlist recommendations lean on what reviews, forums, and press say about you, even where your own site earns most citations
- No structured data — Schema markup gives AI systems structured context about your content
- Keyword stuffing — Unlike traditional SEO where it's just ineffective, keyword stuffing actively reduces AI visibility by 10% (Princeton GEO study)
- Hiding pricing behind "contact sales" or JS-rendered pages — AI agents evaluating your product on behalf of buyers can't parse what they can't read. Add a
/pricing.mdfile - Blocking discovery crawlers without checking their purpose — Restricting
OAI-SearchBot,PerplexityBot, orClaude-SearchBotmay reduce search visibility; training controls are separate - Generic content without data — "We're the best" won't get cited. "Our customers see 3x improvement in [metric]" will
- Forgetting to monitor — You can't improve what you don't measure. Check AI visibility monthly at minimum
Tool Integrations
For implementation, see the tools registry.
| Tool | Use For |
|------|---------|
| semrush | AI Overview tracking, keyword research, content gap analysis |
| ahrefs | Backlink analysis, content explorer, AI Overview data |
| gsc | Search Console performance data, query tracking |
| ga4 | Referral traffic from AI sources |
Related Skills
- seo-audit: For traditional technical and on-page SEO audits; link-building for earning links and mentions on the third-party pages AI engines cite
- schema: For implementing structured data that helps AI understand your content
- content-strategy: For planning what content to create
- competitors: For building comparison pages that get cited
- programmatic-seo: For building SEO pages at scale
- copywriting: For writing content that's both human-readable and AI-extractable
- lead-magnets: For packaging an owned course or content library as an installable agent skill (different from public-site AI visibility)