# Sources and technical references

<p class="lead">Use the original product channels, technical standards and provider policies to check a specific question. These references support the documentation; they do not expand VidSEO's capabilities.</p>

## Product and support

- [VidSEO on WordPress.org](https://wordpress.org/plugins/vidseo/): the Free distribution page and public version history.
- [WordPress.org support forum](https://wordpress.org/support/plugin/vidseo/): public support.
- [Official Pro checkout](https://checkout.freemius.com/plugin/4577/plan/7373/): current commercial offer.
- [Documentation](/docs/) and [Free vs Pro](/free-vs-pro/): workflow and edition boundaries.
- <a href="/implementation-notes.md" target="_self">Implementation notes</a>: site implementation context.

## Video search and structured data

- [Google Search Central: video best practices](https://developers.google.com/search/docs/appearance/video).
- [Google Search Central: VideoObject and Clip](https://developers.google.com/search/docs/appearance/structured-data/video).
- [Schema.org: VideoObject](https://schema.org/VideoObject).
- [Schema.org: SoftwareApplication](https://schema.org/SoftwareApplication).
- [Sitemap protocol](https://www.sitemaps.org/protocol.html).

Video visibility depends on the page, the media, access conditions and search-engine decisions. Publishing schema is not a promise of indexing or rich results.

## Accessibility

- [W3C WAI: transcripts](https://www.w3.org/WAI/media/av/transcripts/).
- [W3C WAI: audio and video media](https://www.w3.org/WAI/media/av/).

A readable transcript is one part of making media useful and accessible. It does not alone establish full accessibility compliance.

## External services

See [Technical notes](/technical/#service-references) for the media, AI and licensing services used by the plugin, including their terms and privacy information. The applicable service depends on the connection or player you choose.

## Interpretation and machine files

- [Source precedence](/source-precedence/).
- [AI policy](/ai-policy/).
- [Response legitimacy](/response-legitimacy/).
- [Anti-plausibility](/anti-plausibility/).
- [Output constraints](/output-constraints/).
- [Canonical machine policy](/.well-known/ai-governance.json).
- [Short reading guide](/llms.txt) and [full reading guide](/llms-full.txt).
- [Document registry](/data/documents.json) and [capability registry](/data/capabilities.json).

Use the visible product documentation for product claims. The machine files describe the same scope and do not prove crawler obedience, runtime enforcement or AI citations.

## Other site standards

- [RFC 9309: robots.txt](https://www.rfc-editor.org/rfc/rfc9309).
- [RFC 9116: security.txt](https://www.rfc-editor.org/rfc/rfc9116).
