Description
Bring the content of your videos into your site’s SEO.
VidSEO publishes a video’s transcription as visible text on your own WordPress site. The explanations and topics discussed in the video become part of the page’s HTML, where search engines can crawl the text and consider it for indexing.
Add a supported YouTube, Vimeo or HTML5 video, write or import its transcript, then review and publish it. WordPress renders that text on the server, without requiring playback or JavaScript. Visitors can also read the transcript and find a passage. Start free; no AI account is needed.
From video to published page in three steps
- Video: add the source, title, thumbnail and original upload date. The publication summary shows which metadata still needs attention.
- Text: write your transcript or import a UTF-8 TXT, SRT or VTT file. Review an imported candidate before using it, then edit the text and add chapters.
- Go live: save your draft, review the preview and publish its saved version. Insert it with the VidSEO block or the shortcode [vidseo id=”123″], using your video’s actual ID.
Saving a draft does not replace the published version. You can prepare corrections while visitors continue to read the version you previously published.
Included in VidSEO Free
- Video and placement: reusable YouTube, Vimeo and HTML5 video records, a WordPress block and a shortcode.
- Transcripts: manual writing and local TXT, SRT or VTT imports.
- Editing: headings, lists, emphasis, links, find and replace, and segment editing.
- Chapters: titles, start times, optional end times and ordering controls.
- Publication: drafts, explicit publication, review status, revision checks, recovery tools and selection of an existing main page.
- Video SEO: eligible VideoObject and Clip output, plus an optional video sitemap.
- Presentation and sharing: player-loading settings, an optional transcript-origin mention and controlled public exports.
- Optional AI: single-video requests with your own supported provider connection, explicit spending permission and usage information.
What VidSEO Pro adds
- Custom chapter identifiers and descriptions.
- Add caption files to supported HTML5 players and record speaker details.
- AI batch preparation and submission, with status tracking, pause, cancellation and selected retries.
- Creation of a new WordPress viewing-page draft for a video, ready for you to review and publish.
Existing content, permitted published output, withdrawal and recovery do not require a new paid operation. Creating or changing Pro-only features requires the applicable entitlement. AI provider usage is billed separately in both editions; Pro does not include AI credits.
Video SEO that follows the published content
Publishing a transcript makes the video’s spoken content available as text on the page that hosts it. That page must be accessible to search engines and permitted to be indexed. Search engines decide whether to index it and how to use its content.
Indexing the page’s text is distinct from indexing the video or displaying video rich results. VidSEO also supports eligible VideoObject structured data, Clip key moments and video sitemap entries. Those outputs describe the video and have their own requirements; a published transcript does not establish eligibility for video results.
Enable the outputs you need. Public transcript endpoints, machine-readable exports, the catalog and llms.txt references require their site settings and the video’s own permissions. The FAQ explains metadata requirements, key moments and custom SEO integrations.
VidSEO makes the topics in your video explicit in the page’s published text. It does not guarantee indexing, rich results, rankings, traffic, AI citations or accurate interpretation by an AI system.
Player loading and presentation
Choose a click-to-load external player or an embedded player, subject to your site’s consent configuration. Click-to-load keeps the external player unloaded until a visitor requests it. Embedded mode allows loading without a click when consent permits; iframe players use browser lazy loading. Loading a player and starting playback are different actions.
The transcript can be read independently of the external player. The public transcript-origin mention is hidden by default and can be enabled in settings. Use the VidSEO thumbnail selector to choose or upload an image through WordPress media, or provide a thumbnail URL. Entering a URL alone does not make the server download that image.
Empty drafts and storage
Resume a draft from the video library. An explicitly abandoned empty draft goes to the trash only if it has no saved work, source, acquisition, revision or placement. Older drafts are not swept by age or title.
VidSEO requires InnoDB for the relevant posts, postmeta and options tables, and a recognized MySQL or MariaDB identity. The local diagnostic checks storage and write capabilities. VidSEO refuses writes when transactional guarantees cannot be established and never converts tables automatically.
Page caches
VidSEO marks public projections and detected host pages private and no-store to support content withdrawal. Your cache plugin may exclude these pages from caching and related optimization. Check the effect with your theme, cache and CDN before adding VidSEO to a high-traffic page. Purges are best effort; a CDN that ignores response directives is not covered.
On archive pages and the posts homepage, supported placements render within the main post loop. Placements in sidebars, footers or secondary loops without the verified host do not render. A static homepage can host a video when the usual publication and access conditions are met.
External services and data
Video playback
When an external player loads, the visitor’s browser connects to the selected media host. That host receives the media address and normal network information, including the IP address, browser information and any applicable cookies or referrer. In click-to-load mode, VidSEO does not load the external player before the visitor’s request. In embedded mode, a permitted player can load without a click. Your site’s consent integration can withhold either mode.
- YouTube: https://www.youtube.com/ ; terms: https://www.youtube.com/t/terms ; privacy: https://policies.google.com/privacy .
- Vimeo: https://vimeo.com/ ; terms: https://vimeo.com/legal/terms ; privacy: https://vimeo.com/legal/privacy/policy .
- Other HTML5 media: the destination is determined by the media URL you enter. Review that host’s terms and privacy policy before using it.
Optional AI transcription
AI is disabled by default. After an authorized user confirms a request and spending permission, VidSEO sends the saved video URL, requested language, transcription instructions, model and generation parameters to OpenRouter using your API key. OpenRouter routes the request to Google AI Studio for the configured Gemini model. Providers receive the server’s network address. VidSEO does not add the site’s URL or a public application-attribution header.
The included adapter accepts supported YouTube URLs. Model availability and access to the source determine whether a request can be completed. A configured connection is not a guarantee that any particular video can be transcribed or that the result is accurate.
Responses become private candidates for review; they are not adopted or published automatically. Provider charges and data handling follow your own agreements. No transcript is automatically sent to support.
- OpenRouter: https://openrouter.ai/ ; terms: https://openrouter.ai/terms ; privacy: https://openrouter.ai/privacy .
- Google AI Studio: https://aistudio.google.com/ ; Gemini API terms: https://ai.google.dev/gemini-api/terms ; privacy: https://policies.google.com/privacy .
YouTube captions API
Caption retrieval through the YouTube API is disabled in both editions of VidSEO 2.0, including new connections, OAuth completion, renewal and track selection. Restored account records or server credentials do not enable it. Video playback and the separate AI connection are independent of this disabled connector.
Maintenance tools can still inventory existing API-derived copies, remove explicitly selected copies and disconnect an existing account. Disconnection can send its saved token to Google’s revocation endpoint. VidSEO distinguishes a confirmed revocation from an uncertain result that needs checking in the Google account.
- YouTube API service: https://developers.google.com/youtube/v3 ; policies: https://developers.google.com/youtube/terms/developer-policies ; terms: https://developers.google.com/youtube/terms/api-services-terms-of-service ; privacy: https://policies.google.com/privacy .
Freemius
The bundled Freemius SDK supports account connection, license activation, purchases and applicable update checks. When those workflows are used, it can send account and contact details, the site URL, plugin and environment versions, installation identifiers and license information to Freemius. The SDK presents the applicable connection choices. Payment and account management use Freemius’s workflow.
- Service: https://freemius.com/ ; terms: https://freemius.com/terms/ ; privacy: https://freemius.com/privacy/ .
Installation
New installation
- Install VidSEO from WordPress.org and activate it. For Pro, use the package and license provided through the official VidSEO purchase channel.
- Open VidSEO in the WordPress administration and follow the Start guide. Review the local diagnostic if a storage requirement needs attention.
- Add a video and its thumbnail, title and original upload date.
- Write a transcript or import an authorized TXT, SRT or VTT file. Review and save your text.
- Add the VidSEO block or the video’s shortcode to a page. Review your publication settings, publish the page and explicitly publish the saved video version.
- Visit the page while signed out. Check the transcript, player behavior and any enabled structured data. Provider connections are optional.
Upgrading from VidSEO 1.x
Back up the database, plugin files, settings and media BEFORE deactivating 1.x: its historical remove_settings option can erase settings during deactivation. Keep the original package and test the upgrade on a copy with your theme, cache and other plugins.
Existing 1.x transcripts remain stored and are not blocked solely because of their age or YouTube URL. Normal publication and access rules still apply. YouTube API caption retrieval is disabled in 2.0; copies identified as API-derived remain blocked. You can continue to use independent manual text, authorized local-file imports, video playback and the separate optional AI connection.
Follow the migration guidance and local diagnostic before migrating existing content. Restoring an older version requires the matching database and files from the same backup. Replacing the plugin files alone is not a complete rollback, and restoring a backup can discard newer edits.
FAQ
Do I need an API key or a paid subscription to get started?
No. VidSEO Free includes manual writing, local transcript imports, the editor, chapters and publication controls. An AI connection is optional and uses your own provider account. Pro is a separate edition for its additional features.
Which video sources and transcript files can I use?
VidSEO recognizes supported YouTube and Vimeo URLs and HTML5 media URLs. Import UTF-8 TXT, SRT or VTT files that you are authorized to use. A supported player URL does not mean VidSEO can retrieve that service’s captions.
Does VidSEO automatically transcribe any video?
No. You can supply the transcript yourself or import a local file. Optional AI requests use the included OpenRouter adapter for supported YouTube URLs and the configured Gemini model. Provider availability and source access vary. Review the result before adopting or publishing it. Direct YouTube API caption retrieval is disabled in 2.0.
Are AI costs included in Pro?
No. Your provider bills you directly in both editions. Each submission requires spending permission. Before enabling AI, choose a monthly attempt limit or explicitly choose no local limit. Attempts include errors and uncertain outcomes; this is not a monetary budget. An output-token limit is not a guaranteed total spending cap. Configure monetary controls with your provider.
Unknown costs and media durations are not shown as zero. When a provider outcome is uncertain, reconcile it before another attempt; VidSEO does not silently resubmit the paid request.
Will an import or a saved correction change my live transcript?
An import first creates a private candidate. Adopting it updates the working document. Saving and publishing are separate actions, so the live version remains the one you explicitly published until you publish another saved version. Publication and access controls can also withdraw output.
Why is my VideoObject or video sitemap entry missing?
Check the publication summary and the public page. VideoObject needs an eligible title, thumbnail and original upload date, enabled schema output and a permitted placement. A transcript is included in the structured data only when the corresponding text is shown in that placement. A video sitemap entry also needs the relevant settings, an eligible description and media URL, and an eligible public destination. A private or unavailable main page can prevent public output.
Use the thumbnail picker in VidSEO. A supported legacy featured image can be used as a fallback when preparing a new publication; the selected thumbnail is then fixed in that published version. An older publication is not silently rewritten by a later draft edit. Review and publish again when you intend to change its metadata.
Can I use VidSEO with another SEO plugin?
VidSEO offers independent output, integration-only mode and disabled output. A developer can use vidseo_public_video_v1 to connect the permitted video data to another plugin’s graph. Check the resulting page for duplicated or conflicting video markup. No named third-party SEO plugin integration is implied by this setting.
Will VidSEO improve my rankings or make AI assistants cite my site?
VidSEO publishes the words and topics from your videos as visible text on your site. Systems that retrieve the page can read that text, subject to the site’s access and indexing settings. Search engines and AI services decide whether and how to use it. Publishing a transcript does not guarantee indexing, rich results, rankings, traffic or citations.
What happens to timestamps, chapters and captions?
Unknown or invalid timing is not invented. Editing words can make an earlier alignment stale. Untimed text remains usable, while outputs that require valid timing are withheld. Free includes chapter titles and times; Pro adds custom identifiers and descriptions.
Pro caption-track settings are for supported HTML5 playback and require public track files hosted on your site’s hostname. They do not replace the caption controls provided inside YouTube or Vimeo players. Speaker profiles are editable metadata; they do not identify speakers automatically.
What if my main page becomes private or is deleted?
You can continue editing the video’s draft while an unchanged main-page selection is unavailable. The editor reports that condition and public output remains subject to the destination’s access rules. Choose another eligible page, or restore the intended page, before making that destination available again. An editorial save does not publish a draft or make a private page public.
Can I control public exports and key moments?
Yes. Public transcript endpoints, machine exports, the catalog, discovery references and sitemap entries require the relevant settings and video-level permission. Turning off an opt-in or withdrawing the source removes the corresponding plugin-controlled output. Personal recovery downloads are separate from public endpoints.
The key-moments creation default applies to new videos. The separate Suspend all key moments setting removes Clip output across the site, including integrations, while preserving visible chapters and essential VideoObject data. Clearing the suspension restores only otherwise authorized videos.
How are provider keys stored?
Use server configuration or authenticated encrypted database storage with a separate server master key. Saved keys are not returned to the browser, and there is no plaintext fallback. A PHP constant takes priority over the same environment variable. A server-managed VIDSEO_OPENROUTER_API_KEY takes priority over the encrypted database connection.
Keep VIDSEO_SECRET_KEY separately from database backups. If that master key is lost, configure a new one and reconnect. Editing a video alone does not grant permission to spend through the site’s provider connection.
What happens to old YouTube API copies and backups?
Known API-derived copies remain blocked in plugin-controlled public output, adoption, publication and recovery, including after restoring an older database. Editing an identified API copy does not remove its provenance. A YouTube URL by itself does not turn an independent manual transcript into an API copy.
This change does not automatically erase adopted documents, revisions, candidates or backups. Review mixed documents and host backups separately. Native WXR and XML-RPC exports omit transcript payloads and private metadata for documents containing API copies; independent manual documents remain exportable.
What happens when I deactivate, uninstall or change editions?
VidSEO 2.0 deactivation preserves content. Removing the last edition preserves transcripts and recovery records. The explicit cleanup preference removes settings and locally stored credentials; it does not erase transcripts or host backups. Old plaintext connection copies in the migration-settings backup are scrubbed.
Permanent content deletion has a separate review in VidSEO’s deletion and private-copies tools. The WordPress trash and a force deletion do not bypass that review. Review private copies before removing the last edition, because their cleanup needs the plugin code. Existing stored Pro information remains readable and recoverable when a new Pro operation is unavailable.
How do I preserve work before a rollback?
Keep a personal recovery export and the migration backup. Rollback preparation preserves current text for the older plugin only when it will not publish an unpublished draft implicitly. Version 1.x cannot represent all jobs, provenance or timing structures. Restore matching database and files when reverting the installation.
Where are the readable interface sources?
The package includes the common settings interface sources and locked build inputs in vue/. See vue/BUILD.md for reproduction. The block and transcript editor scripts are also provided as readable JavaScript. Premium creation modules are excluded from the Free edition.
Screenshots






Changelog
2.0.0
- Start with a guided video, text and publication workflow; keep imports and AI proposals separate from publication.
- Use the same admissible metadata in diagnostics, previews and public outputs; freeze the chosen thumbnail on publication.
- Select an existing main page in Free; generating a new watch page remains a Premium operation.
- Choose click or initial player loading with explicit consent integration; configure the public transcript-origin mention.
- Existing VidSEO 1.x transcripts remain stored and are not blocked solely because of their age or YouTube URL. Normal publication and access rules still apply. YouTube API caption retrieval is disabled in both editions; identified API copies remain blocked, including after restoration. Manual text, authorized local-file imports, video players and the separate AI connection remain available.
- Separate acquisition, adoption, review and publication.
- Preserve literal text, editorial HTML, unknown timing and immutable published projections.
- Keep literal video titles as text when creating native watch pages; refuse unsafe retained page titles without overwriting page edits.
- Translate provider, schema, export-policy and language option labels in the bundled French interfaces while preserving stored values.
- Enforce object/context permissions across native REST, block preview and public outputs.
- Add durable private jobs/candidates, revision conflicts and safe recovery.
- Prepare legacy migration and rollback with explicit limitations.
- Replace uncontrolled external-player loading with explicit player and consent settings; remove unsupported ranking promises.
- Preserve caption tracks when an external HTML5 player is loaded, and render approved chapter descriptions.
- Bound placement indexing and library reads; group public cache invalidations after successful writes.
- Protect native exports containing YouTube API copies and keep independent manual documents exportable.
- Use one VidSEO thumbnail selector, keep public provenance hidden unless enabled, and allow the start notice to be dismissed.
- Make the click-to-load thumbnail part of the player button and use lazy loading for embedded iframe players.
- Accept the fractional-second dates produced by the editor and existing saved publications while retaining date validation.
-
Allow draft corrections when an unchanged main-page selection becomes unavailable; preserve publication and access checks.
-
Keep chapter timestamps on one line on small screens.
