WordPress + Claude AI automation: 2026 practical guide

WordPress still powers 43% of the internet. The most valuable use case for LLMs like Claude is right here — sites that need continuous content generation.

In this guide, I'm sharing the essence of our 4 live production systems.

0. Infrastructure: Direct Claude API vs OpenRouter?

If you want to use Claude API directly, you can get it from console.anthropic.com. We prefer OpenRouter because:

• Switch between Claude + GPT-4 + Gemini with a single API key
• Easy rate limit management
• Cleaner cost dashboard
• Fallback routing (switch to another model on API error)

Setup: Shared API key in /root/.config/doktorbul/api.php. Access via include from all sites.

1. Use case: Recipe generation engine (italyanmutfagi)

Cron runs every night at 03:00:

1. SELECT a category that hasn't been generated yet 2. Select 2-3 random Turkish cuisine key ingredients 3. Prompt chain: - Prompt A: "Suggest a Turkish cuisine dish with these ingredients" → title - Prompt B: "List the ingredients for this dish (in grams)" → ingredient list - Prompt C: "Step-by-step preparation" → steps - Prompt D: "SEO title + meta for this recipe" → meta 4. Direct INSERT into WordPress DB wp_posts + wp_postmeta 5. Schema.org Recipe JSON-LD saved to _recipe_schema meta key

Result: 2-3 recipes every night, zero manual intervention.

2. Use case: FAQ harvester (memuratamalari)

Capture visitor questions in real-time:

1. Query Google Suggest API for kwd + ' ' autocomplete 2. `kwd + ne