Detect keyword cannibalization with GPT-4o and Google Search Console
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
What this workflow does
This AI workflow has 22 nodes and runs on Google Sheets events. Along the way it connects OpenAI Chat Model and Google Sheets.
How it runs
Trigger: On Google Sheets events.
- Fetch Client Website URLs (Google Sheets): uses Google Sheets
- Fetch Target Keywords from Sheet (Google Sheets): uses Google Sheets
- Route to Client (If): checks a condition and branches into true / false
- Route to Client (If): checks a condition and branches into true / false
- Route to Client (If): checks a condition and branches into true / false
- Route to Client (If): checks a condition and branches into true / false
- Merge: merges the data from its input branches
- Fetch GSC Data (Client 1) (HTTP Request): calls an HTTP API (POST)
- Fetch GSC Data (Client 2) (HTTP Request): calls an HTTP API (POST)
- Fetch GSC Data (Client 3) (HTTP Request): calls an HTTP API (POST)
…plus 9 more steps. See the full node list below.
Services it uses
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (9)
- Code
n8n-nodes-base.code - Merge
n8n-nodes-base.merge - AI Agent
@n8n/n8n-nodes-langchain.agent - OpenAI Chat Model
@n8n/n8n-nodes-langchain.lmChatOpenAi - Structured Output Parser
@n8n/n8n-nodes-langchain.outputParserStructured - Google Sheets Trigger
n8n-nodes-base.googleSheetsTrigger - Google Sheets
n8n-nodes-base.googleSheets - If
n8n-nodes-base.if - HTTP Request
n8n-nodes-base.httpRequest
From the author
AI-Powered Keyword Cannibalization Detection Workflow Overview This is an advanced n8n automation workflow designed to detect and analyze keyword cannibalization issues across multiple client websites using Google Search Console data and artificial…