Use when an org role acts as a GEO writer and must structure content to get cited by ChatGPT, Perplexity, Gemini and Google AI Overviews. Covers answer blocks, original data, E-E-A-T and FAQPage schema layered on SEO; for a full AI search audit use ai-seo.
Installs into .claude/skills of the current project.
Are you the author of Ai Citation?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/monoes-ai-citation)
---
name: ai-citation
description: "Use when an org role acts as a GEO writer and must structure content to get cited by ChatGPT, Perplexity, Gemini and Google AI Overviews. Covers answer blocks, original data, E-E-A-T and FAQPage schema layered on SEO; for a full AI search audit use ai-seo."
tags: ["writing","marketing","seo","content"]
tools: []
license: Apache-2.0
source: https://github.com/monoes/monomind
---
# AI Citation — Best Practices
## Focus
Structures content so it gets extracted and cited by generative AI answer engines (ChatGPT, Perplexity, Gemini, AI Overviews) — generative engine optimization (GEO), layered on top of a strong SEO foundation.
## Best practices
- Write clear, standalone factual statements — data points with sources, direct answers, expert definitions — over flowing narrative prose; AI systems extract discrete sentences, not paragraphs.
- Put a concise 40-60 word answer block near the top of each page that directly answers the page's core question.
- Publish original research, proprietary data, or first-hand findings — competitors can't duplicate it, and it disproportionately earns citations.
- Reinforce E-E-A-T signals (experience, expertise, authoritativeness, trustworthiness) — they influence AI citation the same way they influence classic rankings.
- Build strong technical/content SEO first (fast load times, clean URLs, organized headings) — GEO is additive, not a replacement.
- Use FAQPage and Article structured data (schema.org) to make answer boundaries and entities machine-legible.
- Build clear entity relationships (consistent naming, disambiguation) so AI systems can confidently attribute claims to your source.
## Common pitfalls
- Writing exclusively for keyword ranking and ignoring whether individual sentences are extractable as standalone answers.
- Assuming GEO is separate from SEO instead of layered on top of it — skipping the technical/content foundation undermines both.
- No structured data at all, leaving AI crawlers to guess at page structure and entity meaning.
- Chasing citation volume with generic content instead of differentiated original research or expert analysis.
## Tools & techniques
- Structured data validation (FAQPage, Article, Organization schema) before publish.
- Answer-block placement audit: is the direct answer visible without scrolling or extra context?
- Citation tracking across AI answer engines to see which pages/passages actually get surfaced and cited.
- E-E-A-T audit: author bylines, credentials, cited sources, and first-hand data visible on the page itself.