KCITService – AI Site Beacon
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
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