workflows.fit
Back to n8n workflows
n8n templateFreeBy scrapeless official

Automated SEO content engine with Claude AI, Scrapeless, and competitor analysis

This workflow contains community nodes that are only compatible with the self-hosted version of n8n. How it works This n8n workflow helps you build a fully automated SEO content engine using [Scrapeless](https://www.s...

Data & StorageProductivityDevelopmentCore NodesAILangchainManual TriggerN8n-nodes-scrapeless.scrapeless
Loading interactive preview...

Template notes

This workflow contains community nodes that are only compatible with the self-hosted version of n8n.

How it works

This n8n workflow helps you build a fully automated SEO content engine using [Scrapeless](https://www.scrapeless.com/?utmsource=n8n&utmcampaign=seo-engine) and AI. It’s designed for teams running international websites—such as SaaS products, e-commerce platforms, or content-driven businesses—who want to grow targeted search traffic through high-conversion content, without relying on manual research or hit-or-miss topics.

The flow runs in three key phases:

🔍 Phase 1: Topic Discovery Automatically find high-potential long-tail keywords based on a seed keyword using Google Trends via Scrapeless. Each keyword is analyzed for trend strength and categorized by priority (P0–P3) with the help of an AI agent.

🧠 Phase 2: Competitor Research For each P0–P2 keyword, the flow performs a Google Search (via [Deep SerpAPI](https://www.scrapeless.com/en/product/deep-serp-api?utmsource=n8n&utmcampaign=seo-engine)) and extracts the top 3 organic results. Scrapeless then crawls each result to extract full article content in clean Markdown. This gives you a structured, comparable view of how competitors are writing about each topic.

✍️ Phase 3: AI Article Generation Using AI (OpenAI or other LLM), the workflow generates a complete SEO article draft, including: - SEO title - Slug - Meta description - Trend-based strategy summary - Structured JSON-based article body with H2/H3 blocks

Finally, the article is stored in Supabase (or any other supported DB), making it ready for review, API-based publishing, or further automation.