AI Content Signals
Active Installs
500+
Last Updated
June 16, 2026
First Released
November 17, 2025
Download History (Last one month)
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 and tell me what you need.
Need help or have suggestions?
Love the plugin? Please leave us a 5-star review 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.
- Upload the plugin files to
/wp-content/plugins/ai-content-signals/, or install through the WordPress plugins screen - Activate the plugin through the ‘Plugins’ screen in WordPress
- Go to Settings > AI Content Signals to configure your preferences
- Save settings to apply Content Signals to your robots.txt
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).
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.
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
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.
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.
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.
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.
Simply uninstall the plugin. The uninstall process will remove all settings and clean up your physical robots.txt if applicable.
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.
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.
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.
No! The plugin handles everything automatically. Just configure your preferences in the settings page and save.
Changelog
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 file
" width="120" height="120">
