Detect keyword cannibalization with GPT-4o and Google Search Console

Open on n8n.io

$20/month : Unlimited workflows

2500 executions/month

Try free

THE #1 IN WEB SCRAPING

Scrape any website without limits

Try free

HOSTINGER

Early Deal
DISCOUNT 20%

Self-hosted n8n

Unlimited workflows - from $4.99/mo

Try free

#1 hub for scraping, AI & automation

6000+ actors - $5 credits/mo

Try free

Important notice

This workflow is provided as-is. Please review and test before using in production.

1. Workflow Overview

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 websi...

Best for

Market Research automation workflows
AI Summarization automation workflows
advanced n8n builders looking for reusable templates

Tools used

n8n-nodes-base.code, n8n-nodes-base.merge, @n8n/n8n-nodes-langchain.agent, @n8n/n8n-nodes-langchain.lmchatopenai, @n8n/n8n-nodes-langchain.outputparserstructured, n8n-nodes-base.googlesheetstrigger, n8n-nodes-base.googlesheets, n8n-nodes-base.if

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Incrementors.

Original n8n.io source

1.1 Workflow description

Title: Detect keyword cannibalization with GPT-4o and Google Search Console
Workflow name: Detect keyword cannibalization with GPT-4o and Google Search Console

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 intelligence. The system provides real-time monitoring and comprehensive reporting to help SEO professionals identify and resolve internal competition between pages ranking for the same keywords.

Core Components

1. Automated Monitoring System

Real-time trigger: Monitors Google Sheets for keyword changes every minute
Multi-client support: Handles up to 4 different client websites simultaneously
Intelligent routing: Automatically directs each client's data through dedicated processing paths

2. Data Collection & Processing

GSC Integration: Fetches 30 days of search performance data from Google Search Console API
Comprehensive metrics: Collects keyword rankings, page URLs, positions, clicks, impressions, and CTR
Data transformation: Groups raw API responses by keywords for structured analysis
Cross-referencing: Matches target keywords from Google Sheets with actual GSC performance data

3. AI Analysis Engine

GPT-4o powered: Uses advanced AI to analyze keyword competition patterns
Risk categorization: Automatically classifies cannibalization risk as:
- High Risk: 5+ pages competing for the same keyword
- Moderate Risk: 3+ pages ranking in top 10 positions
- Low Risk: 2 pages with one clearly dominating
- No Risk: Single page ranking for the keyword
Intelligent reasoning: Provides detailed explanations for each risk assessment

4. Comprehensive Reporting

Automated output: Saves analysis results back to Google Sheets
Detailed insights: Includes risk levels, reasoning, observations, and actionable remediation steps
Performance tracking: Complete keyword performance metrics for client reporting
Status tracking: Identifies which keywords are ranking vs. missing from search results

1.2 Logical Blocks

This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.

2. Block-by-Block Analysis

Block 1 - Group GSC Data by Keyword (Client 2)

Type / Role: n8n-nodes-base.code - code
Config choices: Version 2

Block 2 - Group GSC Data by Keyword (Client 3)

Type / Role: n8n-nodes-base.code - code
Config choices: Version 2

Block 3 - Group GSC Data by Keyword (Client 4)

Type / Role: n8n-nodes-base.code - code
Config choices: Version 2

Block 4 - Group GSC Data by Keyword (Client 1)

Type / Role: n8n-nodes-base.code - code
Config choices: Version 2

Block 5 - Merge All Client GSC Data

Type / Role: n8n-nodes-base.merge - merge
Config choices: Version 3.2

Block 6 - Match Keywords from Sheet with GSC Data

Type / Role: n8n-nodes-base.code - code
Config choices: Version 2

Block 7 - Analyze Keyword Cannibalization Risk

Type / Role: @n8n/n8n-nodes-langchain.agent - agent
Config choices: Version 2.2

Block 8 - OpenAI GPT-4o Model

Type / Role: @n8n/n8n-nodes-langchain.lmChatOpenAi - lmChatOpenAi
Config choices: Version 1.2

Block 9 - Parse AI Analysis to Structured JSON

Type / Role: @n8n/n8n-nodes-langchain.outputParserStructured - outputParserStructured
Config choices: Version 1.3

Block 10 - Monitor Keywords Sheet for Changes

Type / Role: n8n-nodes-base.googleSheetsTrigger - googleSheetsTrigger
Config choices: Version 1

Block 11 - Save Cannibalization Analysis Results

Type / Role: n8n-nodes-base.googleSheets - googleSheets
Config choices: Version 4.7

Block 12 - Route to Client 1

Type / Role: n8n-nodes-base.if - if
Config choices: Version 2.2

Block 13 - Route to Client 2

Type / Role: n8n-nodes-base.if - if
Config choices: Version 2.2

Block 14 - Route to Client 3

Type / Role: n8n-nodes-base.if - if
Config choices: Version 2.2

Block 15 - Route to Client 4

Type / Role: n8n-nodes-base.if - if
Config choices: Version 2.2

Block 16 - Fetch Client Website URLs

Type / Role: n8n-nodes-base.googleSheets - googleSheets
Config choices: Version 4.7

Block 17 - Fetch Target Keywords from Sheet

Type / Role: n8n-nodes-base.googleSheets - googleSheets
Config choices: Version 4.7

Block 18 - Fetch GSC Data (Client 1)

Type / Role: n8n-nodes-base.httpRequest - httpRequest
Config choices: Version 4.2

Block 19 - Filter Keywords Found in GSC

Type / Role: n8n-nodes-base.if - if
Config choices: Version 2.2

Block 20 - Fetch GSC Data (Client 2)

Type / Role: n8n-nodes-base.httpRequest - httpRequest
Config choices: Version 4.2

Block 21 - Fetch GSC Data (Client 3)

Type / Role: n8n-nodes-base.httpRequest - httpRequest
Config choices: Version 4.2

Block 22 - Fetch GSC Data (Client 4)

Type / Role: n8n-nodes-base.httpRequest - httpRequest
Config choices: Version 4.2

Block 23 - Sticky Note

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 24 - Sticky Note2

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Showing the first 24 of 27 workflow blocks. Download the JSON for the full node graph.

3. Summary Table

Workflow	Detect keyword cannibalization with GPT-4o and Google Search Console
Complexity	advanced
Nodes	27
Categories	Market Research, AI Summarization
Author	Incrementors
Published	24 Sept 2025

4. Reproducing the Workflow from Scratch

1. Download the workflow JSON

Use the JSON export at /data/workflows/8897/8897.json as the source template for this automation.
2. Import the template into n8n

Open n8n, import the downloaded JSON, and review each node before activating the workflow.
3. Configure credentials and variables

Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
4. Test with sample data

Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
5. Activate and monitor

Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.

5. General Notes & Resources

Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.

Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.

Download workflow JSON Original n8n.io source Market Research workflows AI Summarization workflows

Frequently asked questions

What does Detect keyword cannibalization with GPT-4o and Google Search Console do?

What do I need before importing this workflow?

Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.

Can I customize this workflow?

Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your Market Research, AI Summarization use case.

Incrementors

63 workflows

Nodes

n8n-nodes-base.code n8n-nodes-base.merge @n8n/n8n-nodes-langchain.agent @n8n/n8n-nodes-langchain.lmchatopenai @n8n/n8n-nodes-langchain.outputparserstructured n8n-nodes-base.googlesheetstrigger n8n-nodes-base.googlesheets n8n-nodes-base.if

Complexity

advanced

Published 24 Sept 2025

Likes 0

View on n8n.io Download Workflow

Install path: /data/workflows/8897/8897.json

Share Your Workflow

Have a useful automation to share? Publish it and help the community.

Submit Your Template How to Submit

Related Workflows

Answer BigQuery questions in Microsoft Teams with Claude 3.5 dual agents

## Quick overview Turn Microsoft Teams into a natural language BI tool. This dual-agent Claude workflow intelligently classifies user questions, generates safe BigQuery SQL, executes the query, and returns a plain-English summary alongside a data preview directly to your Teams channel. ## How it works 1. The workflow listens for new messages in a designated Microsoft Teams channel or chat. 2. It checks a 24-hour static data cache for your BigQuery schema. If the cache is missing or expired, it automatically fetches the latest INFORMATION_SCHEMA metadata. 3. A main Claude 3.5 Sonnet agent classifies the user's intent (analytical, conversational, or unsafe) and identifies the relevant database tables. 4. If the intent is analytical, a specialized Claude SQL sub-agent generates a read-only SELECT query tailored exactly to your schema. 5. The workflow executes the query against BigQuery (safely constrained to a maximum of 100 rows). 6. A final Claude agent translates the raw query results into a concise, plain-English summary. 7. The answer is posted back to Teams as an Adaptive Card, complete with a formatted data preview and the generated SQL code. 8. Non-analytical questions or pipeline errors are intelligently routed to receive standard conversational replies in Teams. ## Setup 1. CRITICAL SECURITY: Restrict your Google Cloud Service Account IAM roles to BigQuery Data Viewer and BigQuery Job User ONLY. Do not use a highly privileged account. 2. Configure your Microsoft Teams trigger and posting credentials, specifying the target team and channel for the bot to operate in. 3. Configure your Google BigQuery credentials to allow reading metadata and executing queries. 4. Configure your Anthropic credentials for the three Claude LangChain nodes. 5. Update the "Configure Variables" node with your specific GCP Project ID and BigQuery Dataset ID. ## Requirements - A Google Cloud project with BigQuery enabled and existing structured datasets. - An Anthropic API key with access to the Claude 3.5 Sonnet model. - Microsoft Teams administrator access to authorize the n8n integration. ## Customization - Distributed Environments: If you are running n8n with multiple worker nodes (Queue Mode), you must swap the $getWorkflowStaticData() schema cache logic to read/write from a dedicated Key-Value store (like Redis or Supabase) to ensure state synchronization. - UI Layout: Modify the Create Teams Adaptive Card node to add corporate branding, custom colors, or alter the FactSet data preview structure. ## Additional info This architecture features built-in pipeline protections, including strict 40,000-character payload limits to prevent LLM context window blowouts, and fallback handling for "zero-row" query results to ensure users are never left without a response.

View

Evaluate LinkedIn profiles with Apify and Groq Llama chat model

## Quick overview This workflow collects a LinkedIn profile URL via an n8n form, scrapes the public profile data using the Apify LinkedIn Profile Scraper actor, analyzes the results with a Groq-hosted Llama model, and displays an HTML-formatted evaluation back to the user. ## How it works 1. Receives a LinkedIn Profile URL when a user submits the n8n form. 2. Prepares the LinkedIn URL along with the Apify API token and Groq API key used for downstream requests. 3. Sends the profile URL to the Apify `harvestapi/linkedin-profile-scraper` actor and retrieves the scraped dataset items. 4. Passes the scraped profile JSON to a Groq chat model via an LLM chain to generate an HTML evaluation with a score and recommendations. 5. Displays the generated HTML evaluation to the user as the form completion message. ## Setup 1. Add a valid Apify API token and ensure the Apify actor endpoint (`harvestapi/linkedin-profile-scraper`) is accessible for your account. 2. Add Groq API credentials in n8n and confirm the selected model (meta-llama/llama-4-scout-17b-16e-instruct) is available to your Groq account. 3. Replace the placeholder API key values in the workflow (or move them to n8n credentials/environment variables) and verify the form field label matches `LinkedIn Profile URL`.

View

Validate startup ideas with Google Gemini, Groq, and Gmail

## Quick overview This workflow collects a startup idea via an n8n form, uses Google Gemini to generate a SWOT-style analysis, assigns a viability score, uses Groq to turn the results into a structured validation report, and emails the final report through Gmail. ## How it works 1. Receives a startup idea, industry, and target audience from an n8n Form trigger. 2. Sends the submission to Google Gemini to generate a professional analysis covering the problem, business model, and SWOT factors. 3. Generates a startup viability score (currently a random value from 80–100) and packages it with the Gemini analysis. 4. Sends the score and analysis to Groq (Llama 3.3 70B) to compile a full validation report with an executive summary, market potential, recommendations, and final verdict. 5. Emails the generated validation report to the configured recipient using Gmail. ## Setup 1. Add credentials for Google Gemini (PaLM) API, Groq API, and a Gmail OAuth2 connection. 2. Replace the placeholder recipient address in the Gmail step ("[email protected]") with your target email address before activating the workflow. 3. Publish the n8n form, then share the form URL with the users who should submit their startup ideas for validation.

View

Need Custom Automation?

Get help designing a custom n8n workflow that connects your stack and fits your process.

Detect keyword cannibalization with GPT-4o and Google Search Console

Workflow preview

Important notice

1. Workflow Overview

Best for

Tools used

Source and attribution

1.1 Workflow description

1.2 Logical Blocks

2. Block-by-Block Analysis

Block 1 - Group GSC Data by Keyword (Client 2)

Block 2 - Group GSC Data by Keyword (Client 3)

Block 3 - Group GSC Data by Keyword (Client 4)

Block 4 - Group GSC Data by Keyword (Client 1)

Block 5 - Merge All Client GSC Data

Block 6 - Match Keywords from Sheet with GSC Data

Block 7 - Analyze Keyword Cannibalization Risk

Block 8 - OpenAI GPT-4o Model

Block 9 - Parse AI Analysis to Structured JSON

Block 10 - Monitor Keywords Sheet for Changes

Block 11 - Save Cannibalization Analysis Results

Block 12 - Route to Client 1

Block 13 - Route to Client 2

Block 14 - Route to Client 3

Block 15 - Route to Client 4

Block 16 - Fetch Client Website URLs

Block 17 - Fetch Target Keywords from Sheet

Block 18 - Fetch GSC Data (Client 1)

Block 19 - Filter Keywords Found in GSC

Block 20 - Fetch GSC Data (Client 2)

Block 21 - Fetch GSC Data (Client 3)

Block 22 - Fetch GSC Data (Client 4)

Block 23 - Sticky Note

Block 24 - Sticky Note2

3. Summary Table

4. Reproducing the Workflow from Scratch

1. Download the workflow JSON

2. Import the template into n8n

3. Configure credentials and variables

4. Test with sample data

5. Activate and monitor

5. General Notes & Resources

Frequently asked questions