| 开发者 | wasimuc |
|---|---|
| 更新时间 | 2026年7月30日 14:12 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
/llms.txt, following the llms.txt convention. AI assistants can use it to understand your site structure and cite your best content. Choose which content types to include, how many items, whether to append descriptions, and which posts to exclude. Multilingual sites are fully supported: with WPML or Polylang active, every language gets its own sections. Cached and regenerated when content changes.
2. AI crawler control
Decide, bot by bot, which AI crawlers may access your site, with a plain-language explanation of what each block actually costs you. The plugin distinguishes:
ai_referral event with an ai_source parameter into your existing GA4 (gtag) or Google Tag Manager (dataLayer) setup, once per session.
Register ai_source as a GA4 custom dimension and you can segment any report by AI platform, build AI-traffic audiences, and see whether AI-referred visitors convert differently.
4. AI crawler activity log
See which AI crawlers actually visit your site: a 30-day count of real GPTBot, ClaudeBot, PerplexityBot (and more) visits, shown on your dashboard and settings screen. Identification is by user agent, so treat numbers as directional.
Plays well with your stack
The plugin detects your environment and tells you the truth about it instead of showing settings that silently do nothing:
wp avt status, wp avt regenerate), and a REST endpoint (/wp-json/sanivt/v1/sources) for headless front ends.ai_source.No. GPTBot collects training data. ChatGPT search visibility is governed by OAI-SearchBot, listed separately. The settings screen explains the trade-off for every bot.
If a physical robots.txt file exists in your site root, WordPress (and this plugin) cannot modify it. The settings screen warns you when this is the case. Remove the file or add the rules to it manually.
No. llms.txt output is cached, robots.txt rules are a tiny filter, and the attribution script is a small deferred file with no dependencies.
Only into your own GA4 property or GTM dataLayer. The plugin makes no external requests and sends nothing to us.
Yes, any languages. With WPML or Polylang active, the plugin loops every active language and lists each language's content under its own headings, e.g. "Posts (English)" and "Posts (العربية)". qTranslate language markers are resolved automatically. TranslatePress and Weglot translate at render time, so those sites list default-language content (a notice explains this). Very large multilingual sites are protected by a size cap (filterable via sanivt_llms_txt_max_bytes) so the file stays useful to AI assistants.
They coexist. The plugin respects noindex flags from Yoast, Rank Math and SEOPress (noindexed posts never appear in llms.txt), reuses their meta descriptions for entries, and appends robots.txt rules late enough that SEO plugins which rebuild robots.txt output don't discard them. If Yoast's own llms.txt feature is enabled, a warning tells you to keep exactly one generator active.
Yes. Adapters are tried in order: gtag, MonsterInsights, GTM dataLayer, Matomo, Plausible, Fathom, with a 10-second retry window for analytics that load late. You can also use our "AI Traffic Source" GTM community template for a pure-GTM setup.
Use the "Write rules to robots.txt file" button on the settings screen. Your rules are written as a clearly-marked block, kept in sync automatically on every settings save, and removed cleanly when you uninstall the plugin.