{"slug": "how-i-built-a-programmatic-seo-pipeline-with-n8n-claude-api-and-deployed-200-in", "title": "How I Built a Programmatic SEO Pipeline with n8n + Claude API (and deployed 200+ pages in 3 days)", "summary": "A developer built a programmatic SEO pipeline using n8n, Claude API, and WordPress REST API, deploying over 200 geo-targeted pages in three days. The pipeline reads input from Google Sheets, generates content via Claude, publishes to WordPress, and revalidates Next.js ISR cache. First rankings appeared within three weeks on low-competition queries.", "body_md": "A few months ago, a client asked me to rank on 150+ local search queries across 5 cities — with a budget that wouldn't cover a single traditional agency retainer.\n\nInstead of writing 150 articles manually, I built a pipeline. Here's exactly how it works.\n\nThe problem with traditional SEO at scale\n\nCreating geo-targeted content manually is slow, expensive, and inconsistent. You need a writer who understands SEO structure, knows the local context, and can maintain quality across hundreds of pages.\n\nI replaced that process with a system: n8n + Claude API + WordPress REST API.\n\nThe architecture\n\nGoogle Sheets (input)\n\n→ n8n workflow\n\n→ Claude API (content generation)\n\n→ WordPress REST API (publish)\n\n→ Next.js revalidation (ISR)\n\nThree tools. One trigger. Zero manual publishing.\n\nStep 1 — The input sheet\n\nEach row in Google Sheets defines one page:\n\ncity service target_keyword population competitors\n\nCotonou n8n automation consultant n8n cotonou 800000 ...\n\nAbidjan automatisation automatisation processus abidjan 4M ...\n\nn8n reads this sheet on a schedule (or on-demand via webhook).\n\nStep 2 — The n8n workflow\n\nThe core workflow has 6 nodes:\n\nGoogle Sheets trigger — reads unprocessed rows (status = \"pending\")\n\nHTTP Request — calls Claude API with a structured prompt\n\nJSON parser — extracts title, slug, content, excerpt, tags\n\nWordPress REST API — creates the post as draft\n\nGoogle Sheets update — marks row as \"published\" with the post URL\n\nNext.js revalidation — calls /api/revalidate to clear ISR cache\n\nThe Claude prompt is the critical piece. Here's a simplified version:\n\nYou are an SEO content expert. Write a complete article for:\n\nRequired structure:\n\nReturn valid JSON: { title, slug, excerpt, content, tags[], read_time }\n\nStep 3 — The WordPress REST API call\n\n// n8n HTTP Request node\n\nPOST [https://your-site.com/wp-json/wp/v2/posts](https://your-site.com/wp-json/wp/v2/posts)\n\nAuthorization: Bearer {{wp_token}}\n\n{\n\n\"title\": \"{{title}}\",\n\n\"slug\": \"{{slug}}\",\n\n\"content\": \"{{content}}\",\n\n\"status\": \"publish\",\n\n\"categories\": [{{category_id}}],\n\n\"meta\": {\n\n\"excerpt\": \"{{excerpt}}\"\n\n}\n\n}\n\nStep 4 — Next.js ISR revalidation\n\nIf you're running Next.js in front of WordPress (or a custom backend), you need to bust the cache after publishing:\n\n// app/api/revalidate/route.ts\n\nimport { revalidatePath } from 'next/cache';\n\nimport { NextRequest, NextResponse } from 'next/server';\n\nexport async function POST(req: NextRequest) {\n\nconst { slug } = await req.json();\n\nconst secret = req.headers.get('x-revalidate-secret');\n\nif (secret !== process.env.REVALIDATE_SECRET) {\n\nreturn NextResponse.json({ error: 'Unauthorized' }, { status: 401 });\n\n}\n\nrevalidatePath(`/blog/${slug}`\n\n);\n\nreturn NextResponse.json({ revalidated: true });\n\n}\n\nn8n calls this endpoint after each publish. The page is live and indexed within minutes.\n\nResults\n\n200+ geo-targeted pages deployed in 3 days\n\nAverage 2,100 words per page, consistent structure\n\nZero duplicate content issues (city + service combinations are unique)\n\nFirst rankings appearing within 3 weeks on low-competition queries\n\nThe pipeline runs unattended. I trigger it manually for client reviews, but it could run fully automated on a cron.\n\nWhat I learned\n\nPrompt engineering is the bottleneck. Getting Claude to output valid JSON with correct HTML structure every single time took more iteration than the n8n workflow itself. Add a validation node that checks the JSON before publishing — don't skip this.\n\nWordPress REST API rate limits exist. If you're deploying 200 pages in one run, add a Wait node between requests (2-3 seconds). Otherwise you'll hit 429s.\n\nISR cache busting matters. Without it, your newly published pages serve stale \"404 not found\" content for hours. Always wire the revalidation call into the workflow.\n\nThe bigger picture\n\nI build these kinds of systems for clients — SEO pipelines, automation workflows, AI integrations. If you're a dev who's curious about the business side of this, or an entrepreneur who wants to understand what's possible: this is what modern digital agencies actually do when they stop charging by the hour for manual work.\n\nI document more of this on my site: [paulmaximedossou.com](https://www.paulmaximedossou.com/)\n\nAudits are free. DMs are open.\n\nPaul Maxime Dossou — Founder of EkoMedia. I build automation systems, SEO pipelines, and AI integrations for businesses in France and West Africa.", "url": "https://wpnews.pro/news/how-i-built-a-programmatic-seo-pipeline-with-n8n-claude-api-and-deployed-200-in", "canonical_source": "https://dev.to/maxience/how-i-built-a-programmatic-seo-pipeline-with-n8n-claude-api-and-deployed-200-pages-in-3-days-2868", "published_at": "2026-06-21 06:20:55+00:00", "updated_at": "2026-06-21 06:36:50.489013+00:00", "lang": "en", "topics": ["artificial-intelligence", "large-language-models", "developer-tools", "ai-tools"], "entities": ["n8n", "Claude API", "WordPress", "Next.js", "Google Sheets"], "alternates": {"html": "https://wpnews.pro/news/how-i-built-a-programmatic-seo-pipeline-with-n8n-claude-api-and-deployed-200-in", "markdown": "https://wpnews.pro/news/how-i-built-a-programmatic-seo-pipeline-with-n8n-claude-api-and-deployed-200-in.md", "text": "https://wpnews.pro/news/how-i-built-a-programmatic-seo-pipeline-with-n8n-claude-api-and-deployed-200-in.txt", "jsonld": "https://wpnews.pro/news/how-i-built-a-programmatic-seo-pipeline-with-n8n-claude-api-and-deployed-200-in.jsonld"}}