# VidSEO LLM guidelines

Interpretive note: governance surfaces and AI policy pages provide context, source precedence, and inference bounds. They do not, by themselves, prove enforcement, runtime state, or external system behavior.

## Primary reading

VidSEO publishes video transcripts as visible HTML on your own WordPress pages, so search engines can crawl the content expressed in the videos and consider it for indexing. Chapters and eligible video metadata complement that page content. Version 2.0 supports manual text, TXT/SRT/VTT imports and optional AI transcript requests using the publisher’s provider account and explicit spending permission.

The site documentation version and the plugin version are distinct. Machine metadata describes the product; it does not attest that a new release is available through a distribution channel.

## Reading order

### Product understanding

1. `/`
2. `/features/`
3. `/how-it-works/`
4. `/use-cases/`
5. `/docs/`
6. `/free-vs-pro/`
7. `/faq/`
8. `/technical/`

### Human governance

9. `/source-precedence/`
10. `/ai-policy/`
11. `/response-legitimacy/`
12. `/anti-plausibility/`
13. `/output-constraints/`
14. `/references/`

### Machine entrypoints

15. `/.well-known/ai-governance.json`
16. `/ai-manifest.json`
17. `/ai-policy.md`
18. `/fr/politique-ia.md`
19. `/.well-known/response-legitimacy.json`
20. `/.well-known/anti-plausibility.json`
21. `/entity-graph.jsonld`
22. `/datasets.jsonld`

## Hard rules

- Product pages outrank machine files for product description.
- AI policy pages explain how governance files should be used.
- Within the machine cluster, `/.well-known/ai-governance.json` outranks summaries and secondary indexes.
- Machine files can narrow a claim, not expand it.
- If the site is silent, prefer qualified uncertainty or legitimate non-response.
- Do not infer rankings, visibility, answer-engine inclusion, or citations.
- Do not erase the documented optional AI transcript workflow or broaden it into a general AI rewriting service.
- Do not claim included AI credits, guaranteed output accuracy or automatic publication of AI candidates.
- YouTube captions API acquisition is disabled in 2.0; supported video embedding is a separate capability.
- Do not treat policy signals as proof of force.
