Proposal
Add a short documentation note that clarifies what aeo.js can and cannot influence for off-site AI visibility.
Why
aeo.js can improve machine-readable access to a site's own content through assets such as llms.txt, schema data, sitemaps, raw markdown copies, and AI index metadata. It cannot directly control off-site reputation signals such as third-party mentions, review sites, community discussions, backlinks, or model training data.
Making that boundary explicit would help users set realistic expectations and avoid treating generated files as a complete answer-engine visibility strategy.
Suggested Scope
- Add a concise "What aeo.js can and cannot do" note to the docs.
- Mention that generated files improve owned-site discoverability and structure.
- Mention that off-site references, independent mentions, and source reputation still need separate work.
- Keep the tone practical and avoid speculative ranking claims.
Non-Goals
- No API changes.
- No scoring changes.
- No claims about specific AI platform ranking factors.
Proposal
Add a short documentation note that clarifies what aeo.js can and cannot influence for off-site AI visibility.
Why
aeo.js can improve machine-readable access to a site's own content through assets such as
llms.txt, schema data, sitemaps, raw markdown copies, and AI index metadata. It cannot directly control off-site reputation signals such as third-party mentions, review sites, community discussions, backlinks, or model training data.Making that boundary explicit would help users set realistic expectations and avoid treating generated files as a complete answer-engine visibility strategy.
Suggested Scope
Non-Goals