AI Content Signals vs AIPCF – AI Provider for Cloudflare

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? Official website WordPress support forum YouTube channel Documentation and tutorials 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.

This plugin connects WordPress to Cloudflare Workers AI, making its hosted large language models available to any WordPress feature or plugin that uses the WordPress AI Client (introduced in WordPress 7.0). Supported models The plugin fetches the full list of available text generation models directly from your Cloudflare account and shows them in the settings dropdown, so you always see what is actually available to you. The list is cached for 12 hours and refreshed whenever you save your credentials. A built-in fallback list is used when your credentials are not yet configured or the API is unreachable. See Cloudflare’s model catalogue for the current full list. Why Cloudflare Workers AI? Unlike hosted AI services that charge per seat or per API call at a premium rate, Cloudflare Workers AI runs inference at the edge on a usage-based model. The free tier covers 10,000 neurons per day (Cloudflare’s billing unit — roughly 200–500 average generation requests) — enough for a content-heavy site to generate post summaries, meta descriptions, and moderation checks without any cost. Paid usage is billed per neuron, making it significantly cheaper at scale compared to per-token pricing from closed providers. Your prompts and completions also never leave Cloudflare’s network to reach a third-party AI company’s servers, which matters for sites with privacy or data-residency requirements. What you need A Cloudflare account with Workers AI enabled. Your Account ID — visible on the Workers AI dashboard sidebar. A Cloudflare API token with the “Workers AI – Edit” permission. Usage Once the plugin is configured, any WordPress AI Client-compatible feature or plugin will automatically use Cloudflare Workers AI as its provider. Developers can also call it directly: use WordPress\AiClient\AiClient; $result = AiClient::prompt( 'Summarise this post in two sentences.' ) ->usingProvider( 'cloudflare-workers-ai' ) ->usingModel( '@cf/meta/llama-4-scout-17b-16e-instruct' ) ->generateTextResult(); echo $result->toText(); Switch models without changing any other code — swap llama-4-scout-17b-16e-instruct for qwen2.5-coder-32b-instruct and you are running a coding assistant instead. This plugin does not add a chatbot or front-end widget by itself. It registers the provider so that other AI Client-powered features, plugins, and themes can use it. External Services This plugin connects to the Cloudflare Workers AI REST API to run AI inference. The service is used to: Run text generation requests against the model you select. Verify your Account ID and API token when you click “Test connection”. What data is sent and when When you click “Test connection” in the plugin settings, your Account ID and API token are sent to https://api.cloudflare.com/client/v4/accounts/{account_id}/ai/models/search to verify the credentials. No prompt data is sent during this check. When a compatible AI Client feature generates text, the plugin sends your API token, the selected model ID, and the prompt messages to https://api.cloudflare.com/client/v4/accounts/{account_id}/ai/run/{model_id}. Requests are only made when AI generation is explicitly triggered — nothing is sent automatically in the background. Service provider Cloudflare Workers AI is provided by Cloudflare, Inc. Cloudflare Workers AI documentation: https://developers.cloudflare.com/workers-ai/ Cloudflare Terms of Service: https://www.cloudflare.com/terms/ Cloudflare Privacy Policy: https://www.cloudflare.com/privacypolicy/ Roadmap Current version supports Workers AI edge inference. AI Gateway support for caching, rate-limiting, and analytics coming soon.