A client in Pune runs a financial advisory blog — 8–10 posts per month, targeting specific questions their consultation clients ask most. Before I set up their content pipeline, their process was: think of topic, write it manually, spend an hour on SEO, find an image, publish. Each post took 5–7 hours of someone's time. They were publishing twice a month at most.
I set up their automation pipeline over about two weeks. Now they publish 8 posts per month. The total human time per post: about 40 minutes of review, editing, and light rewriting. The rest is automated. Here's exactly how.
Step 1 — The content pipeline starts with topic research, not writing
The mistake most people make with content automation is jumping straight to "AI writes the blog post." The output is generic, thin, and sounds like every other blog post on the topic. It might get published but it won't rank.
The right starting point is research automation. What questions are people actually asking? What's ranking for those terms right now, and what are those posts missing? What's the specific angle that will be better than the top 3 results?
The automated research layer I use: Google Search Console data (via the API, pulled into a Google Sheet on a weekly schedule) shows what queries the site is already getting impressions for but not converting. Ahrefs or Semrush keyword export (even the free tiers) gives volume and competition data. These two sources go into a Claude prompt: "I have a financial advisory blog targeting Indian professionals. Here are the top 20 low-competition queries from our Search Console data and keyword research [paste data]. Identify the 5 highest-priority topics for new posts — ones where our existing content has no direct competitor and where the search intent is clearly informational and high-value. For each topic, suggest the specific angle that would be most useful and differentiated."
The output is a prioritised content brief, not a written post. This is what gets reviewed and approved. The writing comes after.
Step 2 — First-draft automation with Claude via the API
Once a brief is approved (which takes 10 minutes of a human reading the AI-produced brief and making edits), n8n sends it to the Claude API with a custom system prompt that contains the brand voice guidelines, the blog's target audience, and examples of the best-performing posts. The prompt includes: the topic, the specific angle, the target keyword, the word count, and any specific claims or data points to include.
Claude returns a structured HTML first draft: heading structure with H2s and H3s already written, body paragraphs with reasonable specificity, a meta description, and a suggested title. This draft goes to the human editor via a Slack notification with a direct link to review it in a Google Doc (n8n creates the Google Doc automatically via the Google Docs API).
The editor spends 20–30 minutes: rewriting the opening hook to sound like them specifically, adding any personal client examples, fixing any factual claims that need verification, adjusting the tone where the draft is too generic. Then they approve it with a click in Slack.
Step 3 — Automated SEO processing via Rank Math
Rank Math Pro has an AI integration that, on post creation via the REST API, can run its SEO analysis and populate certain fields. But I don't rely on it for everything — I pre-populate the key SEO fields in the n8n workflow before publishing:
- Focus keyword: extracted from the brief
- Meta title: generated by Claude in the draft with a character-count constraint prompt
- Meta description: generated by Claude, under 160 characters, specific to the post angle
- Schema type: set per post category (Article for blog posts, FAQPage for FAQ sections)
- Internal links: n8n queries the WordPress REST API for existing posts in the same category and produces a list of internal linking candidates, which the editor can choose from during review
This means when the post goes live, Rank Math shows a green score from day one — not because we gamed it, but because the SEO fundamentals were handled in the workflow before publishing.
Step 4 — Image handling and featured image automation
I use Unsplash's API (free) or a curated folder of licensed images in Google Drive. n8n searches for images based on the post topic, downloads the selected image, uploads it to the WordPress media library via the REST API, and sets it as the featured image. The alt text is auto-generated from the post title and focus keyword.
For clients who want custom imagery, I have them use Midjourney or Ideogram to generate post-specific images — but this step requires human judgment, so it's outside the automated flow. A half-decent stock image that loads fast beats a pretty custom image that adds workflow delays.
Step 5 — Cross-posting and distribution automation
Once the post is live, n8n triggers the distribution workflow: LinkedIn post draft (Claude-generated summary with a link), Twitter/X thread draft (Claude-generated 3–4 tweet thread), email newsletter draft via Mailchimp API (for the client's subscriber list), and a WhatsApp message to the client confirming the post is live with the URL. These drafts go back to the human for review and scheduling — not auto-published, because social media tone needs more human judgment than blog content.
The total infrastructure cost for this whole pipeline: Rank Math Pro (₹3,500/year), n8n cloud (₹1,400/month — or self-hosted on a ₹1,000/month VPS for more control), Claude API usage (typically ₹300–900/month for 8–10 posts). Call it ₹3,500–4,000/month for the full setup. For a business that was spending 7 hours per post at any professional rate, this pays for itself on the first post of the month.
What breaks and how to handle it
No automation runs without failure. Here are the actual failure points I've hit across multiple client automations and how I've addressed each:
Claude API timeout on long drafts: for posts above 2,000 words, the API response occasionally times out or returns an incomplete output. Fix: split the draft into sections — introduction + body + FAQ as separate API calls — then merge in n8n. The final assembled draft is often better structured than a single-call output anyway.
WordPress REST API authentication failures: if the WordPress admin password gets reset, the application password used in the n8n WordPress node becomes invalid. Workflows fail silently and drafts stop publishing. Fix: use a dedicated API service account in WordPress — separate from the main admin — specifically for automation. When the service account credentials need updating, it's an isolated change that doesn't break anything else.
The biggest failure mode: the automation produces content and no one reviews it. I've seen this with clients who set up the pipeline excitedly, were impressed for two weeks, then gradually stopped reviewing drafts. AI content without review drifts — Claude's output is good but it will occasionally produce something factually off or tonally wrong. The review step must be a mandatory gate, not optional. Nothing publishes without human approval. That's the rule that keeps the quality high while the volume stays automated.
My honest take: the automation is not for businesses that find content creation hard because they don't know what to say. It's for businesses that know exactly what they want to say but don't have the time to produce it at the frequency that SEO requires. If the problem is "what do we write," the automation doesn't solve that. The brief quality going in determines the output quality coming out.
I built this specific pipeline for three client businesses — a financial advisory in Delhi, a manufacturing company in Hyderabad, and an e-commerce brand in Pune. The common thread: all three had founders who were genuinely knowledgeable about their industry but hadn't published a blog post in six months because "we don't have time." The automation didn't replace their voice — it gave their knowledge somewhere to go on a consistent schedule.
Handing over the automation to clients — what that looks like
Once an automation pipeline is running well, some clients want full ownership; others want me to maintain it. How I handle both:
For clients taking ownership: I document the n8n workflow with inline notes on every node, write a 1-page SOP covering what to do when something fails (restart position, how to check Claude API key validity, the WordPress application password reset process), and do a 90-minute hand-over call where they run through the workflow themselves while I watch. This creates real ownership rather than dependency. Clients who've had proper hand-overs maintain their automations. Those who got "the keys and a wave" mostly come back to me in 3 months having broken something.
For clients keeping me on maintenance: a monthly retainer of ₹7,000–12,000 covers checking the pipeline weekly, fixing failures, updating prompts as Claude releases shift output quality, and adding the occasional workflow improvement. Automation maintenance is one of the better recurring revenue sources for a solo technical freelancer — the work is low-stress once it's running and the value to the client is obvious.
Also see: How to automate your SEO and lead generation from WordPress and Why AI subscriptions are your highest-ROI business expense.