AI SEO
Make the company, product, category, use cases, and proof easy for AI answer engines to understand and cite.
Audit The Entity
Inspect what the web can verify:
- Official site pages that explain the product and category.
- Founder, team, or company pages.
- Docs, pricing, comparisons, case studies, changelog, integrations.
- Third-party mentions, directories, reviews, podcasts, GitHub, app stores, communities.
- Structured data and clean metadata.
If live research is needed, use current sources and prefer primary pages.
Diagnose Answerability
Ask:
- Can an AI system identify what this is in one sentence?
- Is the category explicit?
- Are use cases and target customers named?
- Are claims supported by public proof?
- Are comparisons stated cleanly without legal or factual overreach?
- Are there third-party corroboration points?
- Can important pages be crawled without app login or script-only rendering?
Improve The Evidence
Inventory public evidence by claim:
- Claim the company wants answer engines to repeat.
- Official source that supports it.
- Third-party corroboration.
- Query or buying question it helps answer.
- Evidence strength.
- Missing proof or crawl problem.
Then recommend assets that make weak claims easier to verify: canonical explainer, use case page, public example, customer story, fair comparison, documentation, review surface, or reputable third-party mention.
Guardrails
- Do not recommend fake reviews, synthetic citations, or spam directories.
- Do not overstate unsupported claims.
- Treat answer engines as retrieval and synthesis systems, not magic keyword boxes.
- Prefer durable public evidence over prompt-hack phrasing.
Output
AI answer presence read:
[one paragraph]
Entity clarity:
- Category:
- Audience:
- Use cases:
- Proof:
- Third-party corroboration:
Gaps:
1. [gap] -> [why it matters]
Evidence table:
| Claim | Official source | Third-party source | Query supported | Strength | Gap |
Assets to create:
| Asset | Query/job it supports | Proof required | Priority |
Schema and crawl fixes:
- [fix]
30-day presence plan:
1. [action]
2. [action]
3. [action]
1---2name: ai-seo3description: Use when optimizing a site or brand to show up in AI answers, LLM citations, AI search, product recommendations, and category answers.4---56# AI SEO78Make the company, product, category, use cases, and proof easy for AI answer engines to understand and cite.910## Audit The Entity1112Inspect what the web can verify:1314- Official site pages that explain the product and category.15- Founder, team, or company pages.16- Docs, pricing, comparisons, case studies, changelog, integrations.17- Third-party mentions, directories, reviews, podcasts, GitHub, app stores, communities.18- Structured data and clean metadata.1920If live research is needed, use current sources and prefer primary pages.2122## Diagnose Answerability2324Ask:2526- Can an AI system identify what this is in one sentence?27- Is the category explicit?28- Are use cases and target customers named?29- Are claims supported by public proof?30- Are comparisons stated cleanly without legal or factual overreach?31- Are there third-party corroboration points?32- Can important pages be crawled without app login or script-only rendering?3334## Improve The Evidence3536Inventory public evidence by claim:3738- Claim the company wants answer engines to repeat.39- Official source that supports it.40- Third-party corroboration.41- Query or buying question it helps answer.42- Evidence strength.43- Missing proof or crawl problem.4445Then recommend assets that make weak claims easier to verify: canonical explainer, use case page, public example, customer story, fair comparison, documentation, review surface, or reputable third-party mention.4647## Guardrails4849- Do not recommend fake reviews, synthetic citations, or spam directories.50- Do not overstate unsupported claims.51- Treat answer engines as retrieval and synthesis systems, not magic keyword boxes.52- Prefer durable public evidence over prompt-hack phrasing.5354## Output5556```text57AI answer presence read:58[one paragraph]5960Entity clarity:61- Category:62- Audience:63- Use cases:64- Proof:65- Third-party corroboration:6667Gaps:681. [gap] -> [why it matters]6970Evidence table:71| Claim | Official source | Third-party source | Query supported | Strength | Gap |7273Assets to create:74| Asset | Query/job it supports | Proof required | Priority |7576Schema and crawl fixes:77- [fix]787930-day presence plan:801. [action]812. [action]823. [action]83```