Tomjesch

Tomjesch AI Blog Writer adds an “Add with AI” button to selected post types in the WordPress admin list screens. From there, you can describe the post you want, and the plugin will call your configured AI provider to generate a draft (title + HTML content) and open it directly in the editor for review.
The plugin is provider-agnostic and currently supports:
<ul>
<li>OpenAI Chat Completions API (GPT-4.x, GPT-4o, GPT-5 families, etc.)</li>
<li>Anthropic Claude Messages API (Claude 4.x Sonnet and Haiku variants)</li>
</ul>
All AI calls are made directly from your WordPress site to the provider’s HTTPS API using your own API key. No data is sent to any server operated by the plugin author.
<h3>Key features</h3>
<ul>
<li>“Add with AI” action on supported post types in the admin list table</li>
<li>Provider-specific model selection for OpenAI and Anthropic</li>
<li>Base (master) prompt for tone, structure, SEO and style</li>
<li>Connection test from the settings page, including basic token limit hints</li>
<li>Robust response normalization (handles JSON, embedded JSON, labeled text, HTML, and plain text)</li>
<li>Optional debug view showing the most recent generations (prompts + token usage)</li>
</ul>
<h3>SaaS and external services</h3>
This plugin is an interface to third-party AI services. To function, it requires you to configure an API key for at least one provider:
<ul>
<li>OpenAI – <code>https://platform.openai.com/</code></li>
<li>Anthropic Claude – <code>https://console.anthropic.com/</code></li>
</ul>
These services may be paid and are governed by their own terms of use and privacy policies. This plugin does not alter or override those terms; it simply sends your prompts and instructions to the provider you choose and displays the generated content.
<h3>Privacy</h3>
This plugin:
<ul>
<li>Sends the base prompt and the per-request user prompt to your configured AI provider over HTTPS when you test the connection or generate a post.</li>
<li>Does not send any data to servers controlled by the plugin author.</li>
<li>Stores recent prompts and token usage locally in your WordPress database for debugging purposes only.</li>
</ul>
<h3>Debug log</h3>
When you generate a post, the following data is stored in a small rotating debug log:
<ul>
<li>Timestamp</li>
<li>Post type</li>
<li>Provider and model name</li>
<li>User prompt (truncated to 4,000 characters)</li>
<li>Base prompt (truncated to 4,000 characters)</li>
<li>Token usage information where the provider reports it</li>
<li>A small excerpt of the raw provider response</li>
<li>A normalized title excerpt and normalization metadata (detected format + any repairs applied)</li>
</ul>
Only the 20 most recent entries are kept. You can review them on the “AI Blog Writer Debug” page under Settings, and you can clear the entire history with the “Clear debug history” button on that page.
If you consider prompts or base prompts to contain personal data, you should clear the debug history regularly and avoid including personal data in prompts.
<h3>API keys</h3>
API keys can be stored in one of two ways:
<ul>
<li>In the plugin settings (stored in the WordPress options table).</li>
<li>In <code>wp-config.php</code> using the constant <code>TOMJESCH_AI_BLOG_WRITER_API_KEY</code>, which is recommended for extra security.</li>
</ul>
When the plugin is uninstalled from the Plugins screen, it automatically deletes its options, including any API key stored in the database and all debug entries.
If you choose to define an API key in <code>wp-config.php</code>, that key is stored in code, not in the database. When you stop using the plugin or rotate keys, you should also remove or update the <code>TOMJESCH_AI_BLOG_WRITER_API_KEY</code> constant in <code>wp-config.php</code>.

Tomjesch | AI Blog Writer

Generate AI-powered draft posts from the WordPress admin using OpenAI or Anthropic, with an "Add with AI" button and local debug view.

Tyler Martin

Block AI crawlers from scraping your site, or license your content and get paid. Your site, your choice.
AI companies are crawling your WordPress site right now. ChatGPT, Claude, Gemini, Grok – they’re all here, training on your content without asking. This plugin gives you two options: either block them with robots.txt, or add machine-readable licensing terms so compliant AI companies can pay you.
Here’s what makes this different: we do BOTH blocking AND licensing. Most services only do one or the other. We built the infrastructure to do both properly.
<h4>The Reality of AI Crawler Blocking</h4>
robots.txt is a voluntary standard – While OpenAI and Anthropic claim to respect robots.txt, the reality is more complex. Recent investigations by TollBit and Cloudflare found evidence of major AI companies bypassing blocks, and Perplexity was caught using undisclosed IPs to scrape sites that blocked their official crawler. Industry data shows 12.9% of bots now ignore robots.txt (up from 3.3%), with 26 million bypasses in March 2025 alone.
Why blocking still matters: Even as a voluntary measure, robots.txt raises the legal and technical barrier. It establishes clear notice of your access terms, strengthening your legal position if you need to enforce your rights. Most legitimate AI companies do respect it – but you need backup enforcement.
<h4>Coming Soon: HTTP 402 “Payment Required” Protocol</h4>
We’re implementing the HTTP 402 “Payment Required” status code protocol. When an AI bot hits your site without a valid license, we’ll serve a 402 response with your licensing terms in machine-readable format.
Transparency: This is also a voluntary protocol. Cloudflare launched their “Pay Per Crawl” implementation on July 1, 2025, and now serves over 1 billion 402 responses daily – but it’s currently in private beta limited to select major publications. Like robots.txt, HTTP 402 requires AI companies to cooperate. The difference is it’s newer, more standardized, and creates clearer legal standing for enforcement.
<h4>The Stick AND The Carrot</h4>
This plugin already blocks AI crawlers via robots.txt (the stick). Soon we’ll add x402 protocol enforcement (bigger stick). But you can also license your content and earn money from AI companies that want to do the right thing (the carrot).
Most creators don’t realize: News Corp got $250M+ from OpenAI. Reddit got $60M/year. The EU AI Act now requires licensed training data. The licensing market exists – it’s just been locked to big publishers. Until now.
<h4>Why WordPress Creators Need This Now</h4>
The traffic apocalypse is real. In 2025, 60% of Google searches end without any click to external sites – up from 44.2% just a year ago. When users do click, only 360 clicks per 1,000 searches go to the open web (374 in EU). The rest? 14.3% go to Google-owned properties like YouTube and Maps. For the first time in a decade, Google now keeps 90% of its ad revenue internally, with only 10% going to network publishers.
This isn’t theoretical – it’s happening right now. ChatGPT and Gemini answer questions using your content, but users never visit your site. Your ad revenue collapses. Your subscription model breaks when AI gives your insights away for free.
AI content licensing is the survival strategy. The big publishers already figured this out. News Corp got over $250M from OpenAI (5-year deal). Reddit: $60M/year. Nine major publishers have signed deals including Financial Times, Associated Press, Le Monde, and Axel Springer. Meanwhile, individual WordPress site owners – the backbone of the open web – get nothing while AI companies scrape freely.
WordPress is where we make our stand. Dave Winer, who invented blogging 30 years ago and co-created RSS, is now championing WordPress as the foundation for the independent web’s renaissance. In his 2025 writings and WordCamp Canada keynote, he argues that WordPress represents the “read/write web” Tim Berners-Lee originally envisioned – where creators own their content and control their distribution. While social media captured one generation of creativity and tech giants bought up the rest, WordPress remains the last great bastion of independent publishing. It’s where 43% of the web lives. It’s where creators still own their content.
That changes today.
<h4>EU AI Act Compliance</h4>
The EU AI Act now mandates that AI companies must respect opt-out mechanisms and maintain licensing documentation for training data. This plugin provides:
<ul>
<li>Enforceable crawl terms via robots.txt and upcoming x402 protocol</li>
<li>Opt-in training licenses with clear pricing and attribution</li>
<li>Compliant usage tracking that meets EU reporting requirements</li>
<li>Monetization infrastructure so you get paid, not just compliance paperwork</li>
</ul>
For WordPress sites serving EU audiences, this isn’t just about money – it’s about legal compliance for the AI companies that want to use your content.
<h4>The Technology Behind It</h4>
We’ve built the first true content licensing infrastructure for AI:
License Grammar v1.5 – The emerging standard for machine-readable licensing. Our meta tag format works with ChatGPT, Claude, Gemini, Grok, and 100+ AI systems. It’s being adopted as the industry standard because it’s simple, parseable, and extensible.
Dual-axis licensing – Control both the AI use case (training vs inference) and distribution level (private vs public). You can allow free private research while charging for commercial usage. Or block training entirely while allowing inference. Your content, your rules.
Immutable ledger – When AI companies use your content, it’s logged with cryptographic verification. This creates legal standing if you need to enforce your terms. It’s not just “hoping they comply” – it’s building an audit trail.
Layered protection – robots.txt provides the first barrier (voluntary but creates legal notice). Machine-readable licenses give compliant AI companies clear terms. The upcoming HTTP 402 protocol adds standardized payment signaling. Each layer strengthens your legal position.
<h4>How It Actually Works</h4>
1. Install the plugin (literally 1 minute) 
Search “Copyright.sh AI License” in your WordPress plugins, install, activate. Done.
2. Pick your approach 
– Want to block all AI crawlers? Set policy to “Deny” and enable the robots.txt blocker. 
– Want to get paid? Set “Allow”, pick a price (we suggest $0.10 per 1K tokens), and connect your account. 
– Want both? You can block most crawlers and whitelist specific ones you want to license to.
3. It runs automatically 
The plugin adds machine-readable license declarations to every page: 
– HTML meta tags that AI systems check before crawling 
– /ai-license.txt file at your domain root 
– robots.txt entries that block non-compliant crawlers (optional) 
– Coming soon: x402 HTTP responses that enforce payment requirements
4. Track what’s happening (if you’re licensing) 
Dashboard at dashboard.copyright.sh shows which AI companies are using your content and what you’ve earned. Set up PayPal, Venmo, or Stripe for payouts.
<h4>What You Get</h4>
Blocking capabilities: 
– robots.txt generator that blocks 100+ known AI crawlers (voluntary standard, but creates legal notice) 
– Preserves Google, Bing, and other search engines (won’t hurt your search rankings) 
– Optional – you can block all AI or just the ones that don’t pay 
– Coming soon: HTTP 402 protocol support for standardized payment signaling
Licensing capabilities: 
– Set prices per 1,000 tokens (industry standard pricing) 
– Different rates for private vs public usage 
– Per-post pricing overrides for premium content 
– Support for different AI use cases (training, inference, embedding, fine-tuning) 
– Works with OpenAI, Anthropic, Google, xAI, Meta, Perplexity, and 100+ other AI systems
Technical stuff: 
– Uses License Grammar v1.5 specification (the standard AI companies are adopting) 
– Magic link authentication – no passwords, no API keys to copy-paste 
– Clean code, minimal performance impact 
– Compatible with all major caching and SEO plugins
Works seamlessly with: 
– WP Rocket, W3 Total Cache, WP Super Cache, LiteSpeed Cache 
– Yoast SEO, Rank Math, All in One SEO 
– Elementor, Divi, Beaver Builder 
– WooCommerce, Easy Digital Downloads 
– Multisite installations
<h4>Who Should Use This</h4>
Honestly? Anyone with a WordPress site that AI companies might be scraping.
<ul>
<li>Bloggers: Your old posts are training ChatGPT right now. Either block that or get paid for it.</li>
<li>News sites: The big publishers are all licensing. You should too.</li>
<li>Niche experts: Got specialized knowledge? That’s worth more to AI companies.</li>
<li>Anyone who wants to block AI: You don’t have to license. You can just block all AI crawlers completely.</li>
</ul>
<h4>Why This Matters</h4>
The AI training data market is real. News Corp got $250M+. Reddit got $60M/year. The EU AI Act now mandates licensed training data. This isn’t hypothetical – it’s happening.
The difference is that until now, only massive publishers could negotiate these deals. This plugin gives individual site owners the same tools.
But here’s the thing: you don’t have to license your content. If you just want to block AI companies from using your stuff, this plugin does that too. It’s your site, your content, your choice.
<h4>What Makes This Different: Competitor Comparison</h4>
Cloudflare Pay Per Crawl: Launched July 2025, enables website owners to charge AI crawlers per request. While technically sound, it’s limited to Cloudflare’s network infrastructure and uses a flat-rate pricing model that doesn’t account for content value variations. Major limitation: Only works if you’re already on Cloudflare’s platform and restricted to high value customers.
TollBit: AI content licensing platform that requires heavy configuration and subdomain setup (tollbit.example.com) and routes AI traffic through their infrastructure. Good for enterprise publishers but creates technical overhead and dependency on their network for content delivery.
Perplexity Comet Plus: The $5/month subscription service that validates the whole business model of content licensing. Perplexity shares 80% of the revenue they charge Comet Plus customers with publishers based on human visits and AI interactions. Revenue-sharing model is innovative, but success depends entirely on user subscription adoption and limited to Perplexity’s ecosystem.
RSL Protocol (Really Simple Licensing): Open standard for publishers to set explicit licenses and fees for AI content use. Supported by Reddit, Yahoo, and other major platforms. Technically solid but again requires learning a custom XML schema and lacks customizability on a per page basis. RSL is still in early adoption phase (i.e. not available) and requires AI companies to implement the protocol.
What we do differently: We provide both content protection (robots.txt blocking) and monetization (licensing with payment) in a single WordPress plugin. No subdomain required, no network dependency, no platform lock-in. Works with any hosting provider you run WordPress from. Install, configure (or don’t), done.
If/when RSL Protocol becomes widely adopted, we’ll support it too. Until then, we give you the most accessible and comprehensive AI content licensing solution available today.
<h4>AI Systems That Work With This</h4>
The plugin uses the Copyrightish AI-License Grammar v1.5, which is becoming the standard format for AI licensing:
Served via MCP plugin, compatible with OpenAI (ChatGPT, GPT models), Anthropic (Claude), Google (Gemini), xAI (Grok), Meta (Llama), Perplexity, Microsoft (Copilot), DeepSeek, Alibaba (Qwen), and 100+ other AI systems.
As new AI companies launch, they’re adopting the same standard. Your protection scales automatically.

Copyright AI Content Licensing – Block AI Crawlers + Get Paid

AI content licensing for WordPress. Block AI crawlers or license your content and get paid. Works with ChatGPT, Claude, Gemini, and more.

Tomjesch | AI Blog Writer vs Copyright AI Content Licensing – Block AI Crawlers + Get Paid