Why 2026 is different

Two years ago, “AI content” meant pasting a ChatGPT dump into Gutenberg and hoping Google didn’t notice. In 2026 it does notice — the March 2026 helpful content update flattened thousands of AI-only sites — but publishers who treat LLMs as a pipeline stage instead of a replacement writer are shipping more, ranking better, and paying editors less per finished piece.

This post is a working reference to the six AI workflows I actually run for client WordPress sites right now.

1. Brief → outline (Claude, structured JSON)

Give Claude the target keyword, top 5 SERP URLs (fetched via the Anthropic web_fetch tool), and your site’s tone guide. Ask for outline JSON: H2s, H3s, entity coverage checklist, internal link candidates. Paste into the editor as a scaffold. Time per brief: ~90 seconds vs. 25 minutes manual.

2. First-draft with retrieval, not from thin air

Never let the model write from memory. Use MCP or a RAG layer to pull: your existing posts (for internal linking and voice consistency), the client’s product docs, and 2–3 authoritative external sources. Claude 4.7 with the retrieval context produces drafts that need light editing instead of full rewrites.

3. Editorial pass with a second model

Cross-check with a different provider. If Claude drafted, run the piece through GPT-5 with a prompt like “flag every unsupported claim, weak transition, and paragraph that reads like AI filler.” Two models catch what one misses. Costs cents per article.

4. E-E-A-T injection (human, non-negotiable)

Author quotes, screenshots from your actual dashboard, a case study number nobody else has. This is the only step Google’s helpful content system cannot reverse-engineer. If you skip it, you rank for a week and disappear.

5. On-page SEO via Rank Math API

Rank Math exposes a REST endpoint for meta title, description, focus keyword, and schema. Wire your workflow to POST these fields at publish time so the writer never touches the meta box. Cuts publishing time by ~4 minutes per post.

6. Post-publish QA loop

A weekly WP-Cron job pulls Search Console impressions for AI-assisted posts. Anything with impressions but no clicks after 21 days goes back into the queue for a title + intro rewrite. This is the single highest-ROI habit in the entire pipeline.

Stack I run in 2026

• Models: Claude 4.7 (drafting, retrieval), GPT-5 (editorial pass), Haiku 4.5 (bulk meta descriptions)
• Orchestration: n8n for scheduled jobs, custom MCP server for WordPress read/write
• Storage: Custom post type ai_brief with ACF fields for prompt, source URLs, model version
• Guardrails: No post publishes without a human “approved” flag in the ACF group

What to avoid

Bulk publishing 50 AI posts per day. Trusting a single-model draft. Skipping the human E-E-A-T layer. Using AI for YMYL topics without a licensed reviewer. Every one of these is a documented deindex trigger in 2026.

Next step

Pick one existing post that’s stuck on page 3. Run it through workflow 6 (rewrite title + intro, add one original data point). Measure impressions in Search Console after 14 days. That’s your baseline — every other workflow above scales from that single data point.