KCITService – AI Site Beacon vs VidSEO – Video transcript embedding for WordPress & LLM

KCITService – AI Site Beacon generates the four standard AI-readable files (llms.txt, llms-full.txt, llms-index.json, llms-sitemap.xml) plus an optional /ai.txt for training permissions, and integrates with your /robots.txt. Where it differs from other plugins in this category: How this plugin is different Multilingual UI out of the box — 8 bundled language packs (English, Simplified Chinese, Traditional Chinese, Japanese, Korean, Spanish, French, German). No separate language pack downloads, no machine-translated strings — every UI label, button, help text, and FAQ entry was hand-translated. CJK-aware processing — the word counter and summary builder correctly handle Chinese, Japanese, and Korean characters. Most llms.txt generators undercount CJK content (counting an entire 1,000-character Chinese article as “1 word”) or produce mangled URL-encoded TOC anchors. We don’t. All three signal files in one plugin — llms.txt for content discovery, robots.txt integration for crawl signals, and ai.txt (Spawning.ai format) for training permissions. One admin area, consistent UX, single generation pipeline. Per-bot training controls — the ai.txt tab ships with a curated list of 13 known AI user-agents (OpenAI’s GPTBot/ChatGPT-User/OAI-SearchBot, Anthropic’s ClaudeBot, Google-Extended, Common Crawl’s CCBot, PerplexityBot, ByteDance’s Bytespider, Applebot-Extended, Amazonbot, Meta-ExternalAgent, cohere-ai) with default/allow/disallow radios for each. Settings version history with rollback — every settings change is snapshotted (last 20 versions kept), and one click rolls back to any prior state. The rollback itself is reversible. Privacy-first — the free version makes zero external API calls. Everything is processed locally inside WordPress. Customer/order/account data from WooCommerce is never read. Generated files /llms.txt — concise Markdown guide and index /llms-full.txt — fuller Markdown content package /llms-index.json — structured machine-readable index /llms-sitemap.xml — XML list of AI-readable resources /ai.txt — optional Spawning.ai-style training permissions file /robots.txt — integrated via WordPress’s robots_txt filter (does not write a physical file, plays well with SEO plugins) Standard features Clean Markdown conversion of your public WordPress content Two deployment modes: static files written to your site root, or virtual endpoints if root is not writable Per-post include / exclude control via a sidebar meta box Category, tag, and URL pattern exclusions Manual or scheduled regeneration via WP-Cron (daily, weekly, monthly) Live preview of the generated files before publishing What this plugin does NOT claim This plugin does not claim that ChatGPT, Claude, Gemini, Perplexity, or any specific AI system will automatically crawl, index, train on, or use the generated files. The llms.txt and ai.txt conventions are emerging standards and adoption by individual AI providers is voluntary. Treat this plugin as making your signals available, not as a guarantee of how any specific AI service will behave.

VidSEO is a WordPress plugin designed to solve a common and often overlooked problem: valuable information explained in videos is largely invisible to machines. Videos are excellent for human visitors, but search engines, screen readers, and modern answer engines still rely primarily on text to understand what a page contains. When important explanations live only in audio or video form, machines are forced to approximate or ignore that content. VidSEO addresses this limitation by exposing video transcripts as native HTML text directly embedded in the page, alongside the video itself. This allows machines to read what is said in the video without guessing. VidSEO does not generate content. VidSEO does not summarize or rewrite transcripts. VidSEO does not infer missing information. Its role is exposure, not interpretation. A precise, machine-first definition of VidSEO and its scope is available here: https://vidseo.dev Why transcripts still matter Despite major advances in search and AI systems, video content remains fundamentally opaque without an explicit text surface. Search engines may detect that a video exists, but they rely on surrounding text to understand its meaning. Language models face the same constraint: without readable text, they must infer what a video contains. By rendering transcripts as clean HTML, VidSEO ensures that: – the meaning expressed in the video is explicitly available, – long explanations delivered in video form are preserved as text, – machines do not need to extrapolate or hallucinate. Industry context This limitation is now widely acknowledged across the industry. In its January 2026 guide on AEO and GEO, Microsoft highlights the importance of exposing readable text surfaces alongside video content so answer engines and AI systems can reliably extract meaning. From Discovery to Influence: A Guide to AEO and GEO VidSEO provides a concrete WordPress implementation aligned with this principle. What VidSEO allows you to do With VidSEO, you can: Embed YouTube or Vimeo videos using a simple shortcode Retrieve existing YouTube subtitles automatically (when available) Associate each video with a full text transcript Display the transcript as clean HTML inside the page Structure transcripts with headings, paragraphs and links (PRO) Hide the transcript visually while keeping it readable in the source code Keep full editorial control over the transcript content Common situations where VidSEO is useful VidSEO is often used when: Important information is explained mainly in video form Videos contain long explanations, tutorials, interviews or talks You want search engines to understand what is said in your videos Accessibility requires a text alternative to audiovisual content You want to reuse existing video subtitles as readable page content Example A tutorial video explains a complex process in several minutes. With VidSEO, the full explanation becomes readable text on the same page. Search engines and answer engines can now understand what is explained, even if the visitor never plays the video. How it works VidSEO adds a dedicated content type to WordPress. For each video, you: – choose the video platform (YouTube or Vimeo), – paste the video URL, – retrieve existing YouTube subtitles automatically (when available) or add a transcript manually, – optionally format the transcript using standard HTML, – insert the generated shortcode anywhere on your site. The transcript is rendered as standard HTML directly in the page, without external files, iframes, or API dependencies. About the publisher VidSEO is developed by Pagup, a digital readability firm based in Quebec, Canada. Video content is increasingly consumed and summarized by AI systems. Without structured video metadata (VideoObject schema, proper titles, descriptions, and thumbnail references), your videos are invisible to the machine reading layer. VidSEO ensures that your video content is described in a structured format that search engines and AI systems can parse, index, and cite. Part of the Pagup ecosystem pagup.com — Digital readability firm. Diagnostic, semantic architecture, AI governance. gautierdorval.com — Doctrine, canonical definitions, interpretive governance research. interpretive-governance.org — Formal versioned standard for interpretive governance. vidseo.dev — Documentation and resources for VidSEO. Technical references VidSEO outputs transcripts as native HTML within the page DOM. No external files. No API dependencies. No inference layer. Canonical definition and scope: https://vidseo.dev Interpretability reference: https://github.com/GautierDorval/vidseo-video-llm-interpretability Who develops VidSEO? VidSEO is developed by Pagup, a digital readability firm based in Quebec, Canada. Pagup specializes in semantic architecture, interpretive SEO, and AI governance. Why does video structured data matter for AI systems? AI systems rely on structured data to understand what a video contains, who produced it, and how it relates to the page it appears on. Without VideoObject schema markup, your video is just an embedded iframe — the system cannot extract its title, description, duration, or thumbnail. This means your video content does not contribute to your site’s overall digital readability and cannot be cited in AI-generated answers. What is digital readability? Digital readability is the capacity of a website to be correctly understood by all four reading layers: humans, search engines, generative AI systems, and autonomous agents. Learn more at pagup.com.