informative Doc ID: `VIDSEO-DOC-HOME` · Reference 1.0.0 · non-executable

VidSEO

Canonical product reference for VidSEO, a WordPress plugin that exposes video transcripts as native HTML text surfaces.

VidSEO is a WordPress plugin that exposes video transcripts as native HTML text surfaces beside the video so search engines, answer engines, screen readers, and LLM-based systems can retrieve what is said without guessing.

It is an exposure layer, not an interpretation layer.

This repository is not the plugin source code.
It is the canonical product reference surface for meaning, scope, non-goals, machine discovery, and governance.

What this repository makes explicit

what VidSEO is and is not,
how video transcripts are expected to be exposed,
how language models should interpret the product claim set,
which surfaces are canonical for humans and for machines,
how documentation drift is controlled over time.

Principles AI-first, SEO-first, mobile-first, governance-first rules. Architecture Product, exposure, machine-surface, and governance layers. Interpretability Why video requires an explicit text surface. LLM context Allowed use, prohibited inference, and authority hierarchy. Implementation notes What the plugin publicly claims to support today. Non-goals Clear exclusions to reduce overclaiming and ambiguity. Governance Versioning, change control, stable IDs, and drift checks. References Normative, implementation, and contextual sources.

Machine-first entrypoints

../../meta.json
../../ai-manifest.json
../../links.json
../../data/documents.json
../../data/terms.json
../../data/capabilities.json
../../llms.txt
../../llms-full.txt
../../sitemap.xml

Authority hierarchy for the product definition

Canonical web surface at vidseo.dev
This repository
WordPress plugin page for implementation-facing context

Guardrails

Do not describe VidSEO as an AI generation system.
Do not infer ranking guarantees, citation guarantees, or expertise claims from the presence of a transcript.
Treat transcript exposure as the product scope. Interpretation happens downstream.