# How VidSEO makes video transcripts indexable on your site.

<p class="lead">VidSEO 2.0 publishes transcript text in the HTML of your own WordPress pages. These notes distinguish that text indexability from video structured data, video indexing and player behavior.</p>

## Indexable HTML on your own page

The reviewed transcript is part of the HTML produced by WordPress, rather than text that exists only within an external player. It belongs to your page’s URL and can be crawled and considered for indexing when the page is public, accessible and not excluded by indexing controls. Making text indexable does not guarantee that a search engine will index it.

This does not mean that search engines are unable to analyze video without a transcript. VidSEO adds an explicit text version on your own site. That text can also be read by visitors without JavaScript fetching it or the video being played.

Keep the transcript visible, faithful to the video and useful on the page. When it is included in structured data, it must correspond to the supported visible output.

## Saved document and published version

Imports and AI responses create private candidates. Adopting a candidate changes the working document. Saving, reviewing and publishing are separate actions.

The public output uses the published version, subject to current access and publication conditions. Later changes to the working draft do not silently replace that version. A source that becomes private or unavailable must not remain public solely because its ID was inserted somewhere else.

## Video metadata and key moments

Indexing a page’s text is distinct from indexing its video or showing a video result. VideoObject, Clip and the video sitemap describe or expose eligible media information. They complement the transcript HTML and do not replace it.

VidSEO resolves eligible metadata for diagnostics and public output from the same rules. The chosen thumbnail is fixed in the published version. Dates are normalized for structured output, including dates stored with milliseconds by the editor.

Required video details, publication state, permission checks and enabled settings determine whether a `VideoObject` is emitted. Valid chapter timing and the applicable options determine whether `Clip` is included. Turning off all key moments removes that structured chapter output while retaining eligible essential video data and visible chapters.

The video sitemap, public transcript endpoints, machine exports, public catalog and discovery references have their own activation and access rules. A complete metadata form is not evidence of indexing or of search-result eligibility outside the plugin's checks.

## Existing pages and integrations

Both editions can select an eligible existing main page. Pro can create a draft watch page. Creating or publishing one object does not implicitly publish another.

Use the block or shortcode in a supported page context. On archives and the posts homepage, output is restricted to the main post loop. Arbitrary sidebar, footer and mismatched custom-loop placement is not supported.

For developers, the `vidseo_public_video_v1` filter provides a supported integration point for the public video projection, including integration into an SEO plugin's graph. Validate an integration against the actual page and avoid duplicate, contradictory video entities.

## Player loading and external requests

Click loading delays the external player until the visitor's action. Integrated loading allows the player to load with the page, subject to consent configuration. Loading is separate from autoplay. The available consent paths include WordPress Consent API and site-managed consent.

A loaded external player connects the visitor's browser to its media provider. Normal network details, cookies and referrer information may be sent under that provider's policies. Self-hosted media and external media have different destinations; inspect the source you publish.

## Cache behavior

VidSEO 2.0 uses `DONOTCACHEPAGE` and private, no-store response directives for its public projections and detected video host pages. This supports its publication and withdrawal model and can reduce the benefits of full-page caching.

Check the actual behavior with your cache plugin and CDN. Purge adapters are best effort. Do not claim a performance score, universal cache compatibility or a ranking benefit from configuration alone.

## Optional acquisition and providers

Manual text and authorized UTF-8 TXT, SRT or VTT imports are available without an AI account.

Optional AI requests send the video URL, instructions, requested language, model and generation parameters through OpenRouter to Google AI Studio for the configured Gemini model. The connection uses your key, requires spending permission and returns a private candidate. VidSEO does not add an application-attribution header containing the site's URL. Provider availability, cost and factual quality depend on the provider and the request. Pro does not include provider credits.

YouTube captions API acquisition and authorization flows are disabled in 2.0 in both editions. Explicit disconnection of a previously stored connection can still contact Google's revocation endpoint. Known API-derived copies remain blocked by the relevant plugin output and publication paths, including after restoration. Independent manual transcripts are not classified as API copies merely because they mention a YouTube video.

## Service references

- YouTube: [terms](https://www.youtube.com/t/terms), [Google privacy](https://policies.google.com/privacy).
- Vimeo: [terms](https://vimeo.com/legal/terms), [privacy](https://vimeo.com/legal/privacy/policy).
- OpenRouter: [terms](https://openrouter.ai/terms), [privacy](https://openrouter.ai/privacy).
- Gemini API: [additional terms](https://ai.google.dev/gemini-api/terms), [Google privacy](https://policies.google.com/privacy).
- YouTube API: [developer policies](https://developers.google.com/youtube/terms/developer-policies), [API terms](https://developers.google.com/youtube/terms/api-services-terms-of-service).
- Freemius: [terms](https://freemius.com/terms/), [privacy](https://freemius.com/privacy/).

Freemius supports connection, licensing, purchases and applicable updates. Those workflows can send account, site, installation, environment and licence information to Freemius. Use the SDK's applicable choices and the provider's account workflow.

## Public documentation and machine files

The product pages describe what VidSEO does. Files such as `llms.txt`, `product.jsonld` and the published interpretation policies help describe that same product consistently. Their presence does not prove crawler obedience, correct model interpretation, indexing, citations or runtime enforcement.

[Source precedence](/source-precedence/) · [AI policy](/ai-policy/) · [References](/references/)
