# Publish your video content as indexable HTML.

<p class="lead">Make what your videos say available for crawling and indexing on your own WordPress pages. Publish a reviewed transcript as visible HTML, then configure the separate video SEO outputs and the reading experience.</p>

## Understand the SEO result

VidSEO puts the transcript into your page’s HTML, on your own site. A public, accessible page that permits indexing gives search engines text they can consider alongside the rest of your content. A player embed alone does not add that transcript text to the page.

This is text indexability. Google’s video indexing and video results have separate requirements; schema and a video sitemap support that separate layer. VidSEO does not guarantee indexing, rankings, traffic or AI citations.

## Start here

- [Publish your first video](/how-it-works/): the Video, Text and Go live workflow.
- [Explore the features](/features/): what the plugin does on the page.
- [Compare Free and Pro](/free-vs-pro/): the exact edition boundaries.
- [Find a quick answer](/faq/): imports, AI, publication, caching and upgrades.

## Install the right edition

Get Free from [WordPress.org](https://wordpress.org/plugins/vidseo/). Get Pro through the official [Freemius purchase and account workflow](https://checkout.freemius.com/plugin/4577/plan/7373/). Install one edition at a time, then activate it and open VidSEO.

The 2.0 product requires WordPress 5.6.2 or later and PHP 7.4 or later. Its write workflow also needs the relevant WordPress posts, postmeta and options tables to use InnoDB, with a recognized MySQL or MariaDB identity. Use the local diagnostic to check an unfamiliar environment; the plugin does not convert your tables automatically.

## Understand the four content states

| State | What it means |
|---|---|
| Candidate | Imported or requested text that remains private until you adopt it. |
| Working document | Your saved editorial version, with revision checks. |
| Reviewed content | Content you have checked; review does not itself publish it. |
| Published version | The saved version deliberately made available through eligible public placements. |

An import, an AI result or a saved edit does not silently replace the published transcript. Publishing a video does not publish its host page.

## Prepare metadata and chapters

Use an accurate title, description, thumbnail and original publication date. Check the publication summary for missing information. The chosen thumbnail is part of the published version; publish again when an intended metadata change should become public.

Add chapter titles and valid times. Plain text is valid editorial content even when timing is unknown. Do not invent times or a publication date to satisfy a field.

`VideoObject`, key moments and the video sitemap are available in both editions under their relevant settings and eligibility rules. Public endpoints, exports and catalog entries also require their applicable permissions and opt-ins.

## Enable and check the video sitemap {#video-sitemap}

The sitemap helps search engines discover your videos and their host pages. It is available in **Free and Pro 2.0.0**, without an AI key. Enabling it does not publish a video or establish that Google has indexed it.

1. Using an administrator account allowed to manage settings, open **VidSEO → Start and settings** in WordPress, then **Settings**.
2. Open **Publication and SEO → Public outputs**, enable **Video sitemap**, then select **Save settings**.
3. In the video editor, open **3. Go live → Main page and visibility → Machine visibility** and check **Video sitemap opt-in**. Save the draft, refresh the saved preview and publish that version when the change should become public. The global switch alone does not add existing videos. A video needs an eligible public main page containing its block or shortcode, a title, description, thumbnail and usable media or player address.
4. Open **VidSEO → Help**, find **Public discovery routes**, and copy the address of the **`/vidseo-video-sitemap.xml`** link. This uses the actual WordPress site address, including any site subdirectory. The link is also shown while disabled, so check that it says **Enabled globally**.
5. Open that address in a private browser window, signed out of WordPress. The XML index should load successfully. Follow a child sitemap address supplied in its `loc` element; the first child uses `?page=1`.
6. Find a known published video. The outer `loc` should identify its main page, `video:thumbnail_loc` its thumbnail, and `video:content_loc` the media file or `video:player_loc` the embeddable player. Open those resources and compare them with the video actually presented on the page.

**If the output is unavailable:** save the global setting again and check the link copied from Help. A disabled output returns HTTP 404. If an enabled output remains inaccessible, examine site redirects, access rules and caching.

**If a video is missing:** check its individual permission, publication, main page, thumbnail and metadata. An accessible index can reference an empty child sitemap. A draft, private or password-protected page, removed placement or withdrawn permission is not an eligible public entry.

This is a separate output from the native WordPress sitemap or another SEO plugin's sitemap. Once these checks pass, use the real public address for any authorized Search Console submission. The [video sitemap guide](/guides/video-sitemap-wordpress/) explains the elements and how to interpret observations.

## Place your video

Use the VidSEO block or the shortcode shown in the editor. Both editions can select an eligible existing main page. Pro can create a draft watch page for further review.

On archives and the posts homepage, supported output belongs to the main post loop. Arbitrary sidebar, footer or mismatched custom-loop placements are not supported. A static singular homepage can be an eligible host, but check its layout and loading behavior first.

## Player loading, consent and cache

Choose click loading or an integrated player. Integrated loading can contact the external media provider when the page loads, subject to consent configuration. It is separate from autoplay. Configure the site-managed or WordPress Consent API path to match your existing consent setup.

VidSEO 2.0 marks detected video host pages and its public projections as private and no-store. That can affect page caching and optimization, including WP Rocket behavior. Measure the actual page with the site's cache enabled. A third-party CDN may need its own configuration; do not assume every cache obeys the same rules.

[See the cache and performance guide](/guides/video-player-cache-performance/#diagnose-caching-by-reading-responses) for response-header checks and the limits of page caching.

The transcript-origin mention is optional and hidden by default.

## Optional AI and provider charges

Manual editing and TXT, SRT or VTT imports work without a provider connection. Optional AI uses your OpenRouter account and a configured Gemini model for supported YouTube URLs. Enable it deliberately, authorize spending and review the source, model and settings before submitting.

Provider availability and transcription quality have not been established for every model or video. Results stay private until reviewed and adopted. Pro adds batch operations, not credits. Provider charges remain separate in both editions. A local attempt limit is not a guaranteed spending cap, and errors or uncertain outcomes can count as attempts.

YouTube captions API retrieval is disabled in both editions of 2.0. Its status is independent of the video player and the OpenRouter connection. Import an authorized transcript file instead.

## Upgrading {#upgrading}

Back up the database, files, settings and media **before deactivating 1.x**. Its historical cleanup option can remove settings during deactivation. Preserve the old package and test the update on a copy of your site.

Existing 1.x text is kept and is not blocked solely because of age or a YouTube video URL. Normal publication and access rules still apply. Copies identified as originating from the disabled YouTube captions API remain restricted, including after restoration.

Review one representative video, its published page, its metadata and its cache behavior. Restore matching database and file backups if a complete rollback is needed; replacing plugin files alone is not a full rollback. Preserve newer editorial work before restoring an older database.

## Recovery and removal

Use the available personal recovery exports for editorial content. Deactivation preserves content. Removing the last edition does not automatically erase transcripts or recovery records. Settings and locally stored credentials follow the explicit cleanup preference.

Review private copies and retained content through VidSEO's deletion tools before removing the last edition. Host backups are separate from the plugin's storage and require their own handling.

## Support and technical references

Use the [WordPress.org support forum](https://wordpress.org/support/plugin/vidseo/) for public support. For purchases and account matters, use the help supplied with your Freemius order or account.

[Technical notes](/technical/) explain output conditions, integrations and external services. [References](/references/) link to the original standards and provider information.

## Learn the method behind the settings

Use the [resource centre](/resources/) for editorial decisions and diagnosis. Start with [TXT, SRT and VTT](/guides/txt-srt-vtt-html-transcripts/), check [VideoObject](/guides/videoobject-wordpress/) and the [video sitemap](/guides/video-sitemap-wordpress/), then follow the [Search Console procedure](/guides/video-search-console/) to interpret search observations.
