Expose video transcripts as native HTML for WordPress.

Product page Version v2.5.0 Updated 2026-03-15

References

Reference surface

Use this page when you need the primary product references, the main technical standards around crawlable text surfaces, and the public control files that narrow how VidSEO may be described.

Primary product references

  • Public site: https://vidseo.dev/
  • WordPress plugin page: https://wordpress.org/plugins/vidseo/
  • Pro checkout: https://checkout.freemius.com/plugin/4577/plan/7373/
  • Repository: https://github.com/GautierDorval/vidseo-video-llm-interpretability
  • Public Vimeo demo: https://vimeo.com/365180429

Public governance references

  • https://vidseo.dev/ai-governance.json
  • https://vidseo.dev/.well-known/ai-governance.json
  • https://vidseo.dev/.well-known/interpretation-policy.json
  • https://vidseo.dev/.well-known/response-legitimacy.json
  • https://vidseo.dev/.well-known/anti-plausibility.json
  • https://vidseo.dev/.well-known/output-constraints.json
  • https://vidseo.dev/.well-known/qlayer.json
  • llms.txt and llms-full.txt as shorter machine reading guides

Search and structured-data references

  • Google Search Central, structured data introduction
  • Google Search Central, breadcrumb structured data
  • Google Search Central, article structured data
  • Google Search Central, product structured data
  • Google Search Central, video structured data
  • Schema.org SoftwareApplication
  • Schema.org VideoObject
  • Sitemap protocol at sitemaps.org

Accessibility and standards references

  • WCAG success criterion 1.2.1 for audio-only and video-only alternatives
  • RFC 9309 for robots.txt
  • RFC 9116 for security.txt

Reading rule

Use visible product pages as the primary source. Use machine-readable files as a narrowing layer, not as a license to infer more than the product pages claim.

Reading order

  1. Start with the product pages.
  2. Move to the workflow, comparison, and FAQ pages.
  3. Use the blog for transcript-first publication models.
  4. Open machine-readable files only when you need precise ambiguity reduction, stop-rules, or response authorization.

Governance references

  • /source-precedence/
  • /response-legitimacy/
  • /anti-plausibility/
  • /output-constraints/
  • /.well-known/ai-governance.json
  • /doctrine-index.json
  • /governance-fingerprint.json
  • /entity-graph.jsonld
  • /datasets.jsonld