CeeWP

CeeWP Robots.txt Manager is a lightweight and user-friendly plugin that allows you to easily manage your WordPress site’s virtual robots.txt file. Add custom rules without creating physical files, with full control over search engine access to your content.
Why Choose Robots.txt Manager?
<ul>
<li>No File Management: Works with WordPress’s built-in virtual robots.txt system</li>
<li>Two Operating Modes: Choose between appending to or replacing default rules</li>
<li>User-Friendly Interface: Clean admin panel with helpful examples</li>
<li>WordPress Standards: Follows all WordPress coding and security standards</li>
<li>Automatic Cleanup: Removes all data when uninstalled</li>
</ul>
Key Features:
<ul>
<li>Simple interface to add custom robots.txt rules</li>
<li>Replace Mode: Option to completely replace WordPress default robots.txt with custom rules</li>
<li>Append Mode: Add custom rules to existing WordPress robots.txt (default behavior)</li>
<li>Dynamic Textarea: Automatically adjusts height based on content</li>
<li>Live Preview: Direct link to view your robots.txt file</li>
<li>Smart Warnings: Alerts when search engines are discouraged</li>
<li>Privacy Respect: Honors WordPress privacy settings</li>
<li>Examples Included: Ready-to-use code snippets for common scenarios</li>
<li>Professional UI: Modern interface with WordPress dashicons</li>
</ul>
Perfect for:
<ul>
<li>SEO Professionals: Fine-tune search engine crawling behavior</li>
<li>Website Owners: Block access to private directories and files</li>
<li>Developers: Prevent indexing of development or staging content</li>
<li>E-commerce Sites: Control bot access to sensitive areas</li>
<li>Content Creators: Manage sitemap declarations and crawl rates</li>
</ul>
How It Works:
The plugin adds a new menu item under Settings > Robots.txt Manager where you can easily add your custom rules. Choose between two modes:
<ul>
<li>Append Mode (Default): Your custom rules are added to WordPress’s default robots.txt</li>
<li>Replace Mode: Your custom rules completely replace WordPress’s default robots.txt</li>
</ul>
The interface includes helpful examples, real-time textarea sizing, and a direct link to view your live robots.txt file.
<h3>Privacy</h3>
This plugin does not collect, store, or transmit any personal data. All settings are stored locally in your WordPress database and are only used to generate your robots.txt file.
<h3>Credits</h3>
Developed with ❤️ by CeeWP – https://ceewp.com/
Special thanks to the WordPress community for continuous inspiration and feedback.

CeeWP Robots.txt Manager

Easily manage your WordPress site's virtual robots.txt file with custom rules. No physical file needed!

Ayuda WordPress

Fernando Tellado

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:
<ul>
<li>robots.txt — Cloudflare Content Signals (search / ai-input / ai-train)</li>
<li>HTTP header — <code>X-Robots-Tag: noai, noimageai</code></li>
<li>HTML meta — robots <code>noai, noimageai</code></li>
<li>/.well-known/tdmrep.json — W3C Text and Data Mining Reservation Protocol</li>
<li>EU Directive 2019/790 rights reservation</li>
</ul>
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:
<ul>
<li>search — allow or deny search indexing and traditional search results (links and short snippets)</li>
<li>ai-input — allow or deny using your content for real-time AI answers (RAG, grounding, AI Overviews)</li>
<li>ai-train — allow or deny using your content to train or fine-tune AI models</li>
</ul>
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: <code>noai, noimageai</code> in an HTML meta tag and an <code>X-Robots-Tag</code> header, plus a <code>tdm-reservation</code> in your TDMRep manifest. Declaring the same preference in several places means a crawler that ignores one signal may still honor another.
Key Features
<ul>
<li>Easy-to-use settings page in WordPress admin</li>
<li>Set global defaults for all crawlers</li>
<li>Configure specific settings for individual AI bots (GPTBot, ClaudeBot, PerplexityBot, etc.)</li>
<li>Add custom bot User-Agents</li>
<li>Supports both physical and virtual robots.txt files</li>
<li>Option to create physical robots.txt with basic WordPress rules</li>
<li>Preview generated Content Signals before applying</li>
<li>Export and import settings as JSON for easy migration between sites</li>
<li>Optional legal text with EU Directive reference</li>
<li>Developer-friendly: filter hook to extend the predefined bots list</li>
<li>Works with existing robots.txt from SEO plugins</li>
<li>Automatic sitemap detection and inclusion</li>
<li>Optional extra output surfaces: HTML robots meta tag (noai, noimageai), X-Robots-Tag header, and a W3C TDMRep file at /.well-known/tdmrep.json</li>
</ul>
Supported Bots
The plugin includes predefined settings for 28 major AI crawlers:
<ul>
<li>OpenAI GPTBot, OAI-SearchBot, and ChatGPT-User</li>
<li>Anthropic ClaudeBot, Claude-Web, and anthropic-ai</li>
<li>Perplexity Bot and Perplexity-User</li>
<li>Google Extended (Gemini) and GoogleOther</li>
<li>Amazon Bot</li>
<li>Apple Extended</li>
<li>Meta/Facebook Bot and meta-externalagent</li>
<li>DuckDuckGo DuckAssistBot</li>
<li>Allen Institute AI2Bot</li>
<li>Mistral AI</li>
<li>ByteDance Bytespider</li>
<li>DeepSeek AI</li>
<li>xAI Grok</li>
<li>Huawei Pangu</li>
<li>Common Crawl, Cohere AI, Diffbot, You.com Bot, and more</li>
</ul>
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.
<h3>Support</h3>
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 <a href="mailto:ai-content-signals@ayudawp.com" rel="nofollow ugc">contact me</a> and tell me what you need.
Need help or have suggestions?
<ul>
<li><a href="https://servicios.ayudawp.com" rel="nofollow ugc">Official website</a></li>
<li><a href="https://wordpress.org/support/plugin/ai-content-signals/" rel="ugc">WordPress support forum</a></li>
<li><a href="https://www.youtube.com/AyudaWordPressES" rel="nofollow ugc">YouTube channel</a></li>
<li><a href="https://ayudawp.com" rel="nofollow ugc">Documentation and tutorials</a></li>
</ul>
Love the plugin? Please leave us a <a href="https://wordpress.org/support/plugin/ai-content-signals/reviews/#new-post" rel="ugc">5-star review</a> and help spread the word!
<h3>About AyudaWP.com</h3>
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.

AI Content Signals

Control how AI uses your content — search, AI answers or training — via robots.txt Content Signals, HTTP headers, meta tags and TDMRep.

CeeWP Robots.txt Manager vs AI Content Signals