Title: AI Content Signals Author: Fernando Tellado Published: 2025年11月17日 Last modified: 2026年8月28日 --- プラグインを検索 ![](https://ps.w.org/ai-content-signals/assets/banner-772x250.jpg?rev=3397627) ![](https://ps.w.org/ai-content-signals/assets/icon-256x256.gif?rev=3397536) # AI Content Signals 作者: [Fernando Tellado](https://profiles.wordpress.org/fernandot/) [ダウンロード](https://downloads.wordpress.org/plugin/ai-content-signals.1.3.3.zip) [ライブプレビュー](https://ja.wordpress.org/plugins/ai-content-signals/?preview=1) * [詳細](https://ja.wordpress.org/plugins/ai-content-signals/#description) * [レビュー](https://ja.wordpress.org/plugins/ai-content-signals/#reviews) * [インストール](https://ja.wordpress.org/plugins/ai-content-signals/#installation) * [開発](https://ja.wordpress.org/plugins/ai-content-signals/#developers) [サポート](https://wordpress.org/support/plugin/ai-content-signals/) ## 説明 AI Content Signals lets you declare, in a machine-readable way, how AI systems may use your content: for search indexing, real-time AI answers (RAG), or model training. It started with Cloudflare’s Content Signals in robots.txt and now expresses the same preferences across several surfaces, so more crawlers and tools can read them: * **robots.txt** — Cloudflare Content Signals (search / ai-input / ai-train) * **HTTP header** — `X-Robots-Tag: noai, noimageai` * **HTML meta** — robots `noai, noimageai` * **/.well-known/tdmrep.json** — W3C Text and Data Mining Reservation Protocol * **EU Directive 2019/790** rights reservation Everything is opt-in and does not change your robots.txt output unless you enable it. **The signals you control** You set three preferences, and AI Content Signals expresses each one in the right format on every surface you enable: * **search** — allow or deny search indexing and traditional search results (links and short snippets) * **ai-input** — allow or deny using your content for real-time AI answers (RAG, grounding, AI Overviews) * **ai-train** — allow or deny using your content to train or fine-tune AI models These three come from Cloudflare’s Content Signals vocabulary, written to your robots. txt. When you deny AI training, the same opt-out is also emitted on any other surface you enable: `noai, noimageai` in an HTML meta tag and an `X-Robots-Tag` header, plus a `tdm-reservation` in your TDMRep manifest. Declaring the same preference in several places means a crawler that ignores one signal may still honor another. **Key Features** * Easy-to-use settings page in WordPress admin * Set global defaults for all crawlers * Configure specific settings for individual AI bots (GPTBot, ClaudeBot, PerplexityBot, etc.) * Add custom bot User-Agents * Supports both physical and virtual robots.txt files * Option to create physical robots.txt with basic WordPress rules * Preview generated Content Signals before applying * Export and import settings as JSON for easy migration between sites * Optional legal text with EU Directive reference * Developer-friendly: filter hook to extend the predefined bots list * Works with existing robots.txt from SEO plugins * Automatic sitemap detection and inclusion * Optional extra output surfaces: HTML robots meta tag (noai, noimageai), X-Robots- Tag header, and a W3C TDMRep file at /.well-known/tdmrep.json **Supported Bots** The plugin includes predefined settings for 28 major AI crawlers: * OpenAI GPTBot, OAI-SearchBot, and ChatGPT-User * Anthropic ClaudeBot, Claude-Web, and anthropic-ai * Perplexity Bot and Perplexity-User * Google Extended (Gemini) and GoogleOther * Amazon Bot * Apple Extended * Meta/Facebook Bot and meta-externalagent * DuckDuckGo DuckAssistBot * Allen Institute AI2Bot * Mistral AI * ByteDance Bytespider * DeepSeek AI * xAI Grok * Huawei Pangu * Common Crawl, Cohere AI, Diffbot, You.com Bot, and more **Important Notice** Content Signals is a declarative standard – it expresses your preferences but does not technically enforce them. AI companies are not legally required to respect these signals, though the plugin includes legal text referencing EU copyright directives. The IETF AI Preferences (AIPREF) Working Group is currently developing a formal standard based on similar concepts. This plugin implements the current Cloudflare Content Signals specification and will be updated as standards evolve. This plugin works best when combined with other protection measures like traditional robots.txt rules and server-level bot management. ### Support Need private support or custom development? Do you need one-on-one help, priority troubleshooting, or a custom feature, integration, or tweak built specifically for your site? I offer private support and custom development. Just [contact me](https://ja.wordpress.org/plugins/ai-content-signals/ai-content-signals@ayudawp.com?output_format=md) and tell me what you need. Need help or have suggestions? * [Official website](https://servicios.ayudawp.com) * [WordPress support forum](https://wordpress.org/support/plugin/ai-content-signals/) * [YouTube channel](https://www.youtube.com/AyudaWordPressES) * [Documentation and tutorials](https://ayudawp.com) Love the plugin? Please leave us a [5-star review](https://wordpress.org/support/plugin/ai-content-signals/reviews/#new-post) and help spread the word! ### About AyudaWP.com We are specialists in WordPress security, SEO, and performance optimization plugins. We create tools that solve real problems for WordPress site owners while maintaining the highest coding standards and accessibility requirements. ## スクリーンショット [⌊Main settings page with global Content Signals configuration⌉⌊Main settings page with global Content Signals configuration⌉[ Main settings page with global Content Signals configuration [⌊Bot-specific settings for granular control⌉⌊Bot-specific settings for granular control⌉[ Bot-specific settings for granular control [⌊Custom bots section for adding new AI crawlers⌉⌊Custom bots section for adding new AI crawlers⌉[ Custom bots section for adding new AI crawlers [⌊Live preview of generated robots.txt content⌉⌊Live preview of generated robots. txt content⌉[ Live preview of generated robots.txt content [⌊Export, import, and restore default settings⌉⌊Export, import, and restore default settings⌉[ Export, import, and restore default settings ## インストール 1. Upload the plugin files to `/wp-content/plugins/ai-content-signals/`, or install through the WordPress plugins screen 2. Activate the plugin through the ‘Plugins’ screen in WordPress 3. Go to Settings > AI Content Signals to configure your preferences 4. Save settings to apply Content Signals to your robots.txt ## FAQ ### What happens if I have a physical robots.txt file? The plugin will detect your physical robots.txt file and append Content Signals to the end of it. Make sure the file is writable (permissions 644 recommended). ### Can the plugin create a robots.txt file if I don’t have one? Yes! You can enable the option “Create physical robots.txt file if it doesn’t exist” in the settings. This will create a basic robots.txt with standard WordPress rules plus your Content Signals. ### What rules are included in the automatically created robots.txt? The plugin creates a basic robots.txt with these rules: * Disallow /wp-admin/ ( except admin-ajax.php) * Disallow /wp-includes/ * Disallow /wp-content/plugins/ * Disallow /wp-content/themes/ * Disallow /wp-content/cache/ * Disallow readme.html and license.txt * Automatically includes your WordPress sitemap if available ### What if I use an SEO plugin that manages robots.txt? No problem! The plugin uses WordPress’s robots_txt filter, so it will add Content Signals to the virtual robots.txt generated by your SEO plugin without conflicts. ### Will AI crawlers actually respect these signals? Content Signals is a proposed standard and not all AI companies have committed to respecting it. It’s a way to express your preferences, but not a guarantee of enforcement. However, major AI companies like OpenAI, Anthropic, and Google have shown interest in respecting such signals. ### Can I use this with Cloudflare? Yes! If you use Cloudflare’s managed robots.txt, you can still use this plugin. The settings will apply to your WordPress-generated robots.txt. ### What are the default settings? By default, all signals are set to “yes” (allowed) for all user-agents. The option to create a physical robots.txt is disabled by default. You can change any of these settings in the settings page. ### How do I remove Content Signals completely? Simply uninstall the plugin. The uninstall process will remove all settings and clean up your physical robots.txt if applicable. ### Can I transfer settings between sites? Yes! Use the Export button on the settings page to download a JSON file with your full configuration, then use Import on another site to restore it. This includes global settings, individual bot overrides, and custom bots. ### Is Content Signals an official web standard? Not yet. Cloudflare published the Content Signals Policy in September 2025 and released it under CC0. The IETF has since created the AI Preferences (AIPREF) Working Group to develop a formal standard based on similar concepts. The plugin implements the current Cloudflare specification and will be updated as standards evolve. ### Can developers extend the bot list programmatically? Yes. Use the `ayudawp_acs_predefined_bots` filter to add or remove bots without modifying the plugin. Add this to your theme’s `functions.php` or a custom plugin: ``` add_filter( 'ayudawp_acs_predefined_bots', function( $bots ) { // Add a new bot. $bots['MyCustomBot'] = 'My Custom AI Bot'; // Remove an existing bot. unset( $bots['Omgilibot'] ); return $bots; } ); ``` The array key is the User-Agent string used in robots.txt and the value is the label displayed in the settings page. ### Do I need to manually edit my robots.txt file? No! The plugin handles everything automatically. Just configure your preferences in the settings page and save. ## 評価 ![](https://secure.gravatar.com/avatar/8439c0b8e69dba402a16468e80e8f09ee3113b50c71fecbe41426ef070b3d1cd? s=60&d=retro&r=g) ### 󠀁[Amazing plugin](https://wordpress.org/support/topic/amazing-plugin-2840/)󠁿 [Alvaro Torres](https://profiles.wordpress.org/algato333/) 2026年1月16日 1 reply So useful ![](https://secure.gravatar.com/avatar/5b0a1b43796cabd58557441ad319e078e81a1cf7020562e73b1c377da0d5bd37? s=60&d=retro&r=g) ### 󠀁[Good](https://wordpress.org/support/topic/good-9074/)󠁿 [Héctor Tellado](https://profiles.wordpress.org/hectortellado/) 2026年1月12日 For what I've been needing it works ![](https://secure.gravatar.com/avatar/a299cf0eda34ddb3cfee009b60dcecf4dcdfe1662bdc29c08c27bc2c51343bfe? s=60&d=retro&r=g) ### 󠀁[Interesting](https://wordpress.org/support/topic/interesting-58/)󠁿 [freelancesgroup](https://profiles.wordpress.org/freelancesgroup/) 2025年11月26 日 1 reply I think it's a good idea and it can help us define how we want AI to use the content of our web pages. [ 3件のレビューをすべて表示 ](https://wordpress.org/support/plugin/ai-content-signals/reviews/) ## 貢献者と開発者 AI Content Signals はオープンソースソフトウェアです。以下の人々がこのプラグインに 貢献しています。 貢献者 * [ Fernando Tellado ](https://profiles.wordpress.org/fernandot/) * [ Ayuda WordPress ](https://profiles.wordpress.org/ayudawp/) “AI Content Signals” は2ロケールに翻訳されています。 [翻訳者](https://translate.wordpress.org/projects/wp-plugins/ai-content-signals/contributors) のみなさん、翻訳へのご協力ありがとうございます。 [“AI Content Signals” をあなたの言語に翻訳しましょう。](https://translate.wordpress.org/projects/wp-plugins/ai-content-signals) ### 開発に興味がありますか ? [コードを閲覧](https://plugins.trac.wordpress.org/browser/ai-content-signals/)する か、[SVN リポジトリ](https://plugins.svn.wordpress.org/ai-content-signals/)をチェック するか、[開発ログ](https://plugins.trac.wordpress.org/log/ai-content-signals/)を [RSS](https://plugins.trac.wordpress.org/log/ai-content-signals/?limit=100&mode=stop_on_copy&format=rss) で購読してみてください。 ## 変更履歴 #### 1.3.3 * Improved: The admin JavaScript that builds a custom bot row now escapes every value it writes into the markup, with a dedicated helper for each context: escAttr() for attributes, which encodes quotes, and escHtml() for text. The values come from the plugin own translatable strings, so nothing was exploitable, but a translation containing a double quote would have broken out of the placeholder attribute. * Fix: On a multisite network, the administrator of any subsite could create or rewrite the physical robots.txt at the root of the install, the single file every site on the network is served from, just by saving the plugin settings. The plugin settings are stored per site, but the file is shared, so a subsite could set the AI policy and the Sitemap line for the whole network, including sites where the plugin was not even active. Writing that file now requires network administrator rights, and the settings page says so instead of failing silently. Each subsite keeps full control of its own virtual robots.txt, and single sites behave exactly as before. * Fix: Notices raised on the settings page are now displayed. Import and restore errors were registered but never printed, so an invalid import file failed with nothing on screen. #### 1.3.2 * Improved: Compatible with WordPress 7.1. * Improved: Signal values are now validated against the Content Signals vocabulary( yes, no, or not specified) both when settings are saved and when they are written out, so only valid values can reach robots.txt, the HTTP header, the meta tag or the TDMRep manifest. #### 1.3.1 * Fix: Removing or regenerating the Content Signals block no longer joins the line before the block with the line after it. When the block sat between blocks written by other plugins, that join could turn a neighbouring comment into part of a directive, so a stray “Disallow: /” ended up applying to the whole site. * Fix: robots.txt is now always left with a single newline at the end, so the next plugin that appends to it starts on its own line. * Fix: Uninstalling the plugin no longer leaves an empty robots.txt behind when the file held nothing but the Content Signals block. A web server serves a physical robots.txt even when it is empty, which shadowed the virtual one WordPress generates, so the site quietly lost its core directives and its Sitemap line. The file is now deleted instead. #### 1.3.0 * New: Output surfaces beyond robots.txt. Optionally emit a robots meta tag with noai, noimageai in the page head when AI training is blocked. * New: Optionally send an X-Robots-Tag: noai, noimageai HTTP response header on the front-end. * New: Optionally serve a W3C TDMRep manifest at /.well-known/tdmrep.json to reserve text and data mining rights. * Improved: Added a settings-page notice explaining how AI Content Signals and VigIA complement each other. * Improved: Refreshed the recommended plugins shown in the promotional banner. For older changelog entries, please check the [changelog.txt](https://plugins.svn.wordpress.org/ai-content-signals/trunk/changelog.txt) file ## メタ * バージョン **1.3.3** * 最終更新日 **1か月前** * 有効インストール数 **800+** * WordPress バージョン ** 5.6またはそれ以降 ** * 検証済み最新バージョン: **7.1.3** * PHP バージョン ** 7.4またはそれ以降 ** * 言語 * [English (US)](https://wordpress.org/plugins/ai-content-signals/)、[Spanish (Chile)](https://cl.wordpress.org/plugins/ai-content-signals/)、 [Spanish (Spain)](https://es.wordpress.org/plugins/ai-content-signals/). * [プラグインを翻訳](https://translate.wordpress.org/projects/wp-plugins/ai-content-signals) * タグ * [AI](https://ja.wordpress.org/plugins/tags/ai/)[cloudflare](https://ja.wordpress.org/plugins/tags/cloudflare/) [crawlers](https://ja.wordpress.org/plugins/tags/crawlers/)[robots.txt](https://ja.wordpress.org/plugins/tags/robots-txt/) [seo](https://ja.wordpress.org/plugins/tags/seo/) * [詳細を表示](https://ja.wordpress.org/plugins/ai-content-signals/advanced/) ## 評価 5つ星中5つ星 * [ 3 5-星レビュー ](https://wordpress.org/support/plugin/ai-content-signals/reviews/?filter=5) * [ 0 4-星レビュー ](https://wordpress.org/support/plugin/ai-content-signals/reviews/?filter=4) * [ 0 3-星レビュー ](https://wordpress.org/support/plugin/ai-content-signals/reviews/?filter=3) * [ 0 2-星レビュー ](https://wordpress.org/support/plugin/ai-content-signals/reviews/?filter=2) * [ 0 1-星レビュー ](https://wordpress.org/support/plugin/ai-content-signals/reviews/?filter=1) [Your review](https://wordpress.org/support/plugin/ai-content-signals/reviews/#new-post) [すべてのレビューを見る](https://wordpress.org/support/plugin/ai-content-signals/reviews/) ## 貢献者 * [ Fernando Tellado ](https://profiles.wordpress.org/fernandot/) * [ Ayuda WordPress ](https://profiles.wordpress.org/ayudawp/) ## サポート 意見や質問がありますか ? [サポートフォーラムを表示](https://wordpress.org/support/plugin/ai-content-signals/)