Detect Keyword Cannibalization with Google Search Console Data - n8n Workflow

SEO Specialists and Analysts seeking to identify and resolve internal ranking competition.
Content Managers needing data-driven insights into content performance.
Digital Marketing Agencies managing multiple client sites.
Anyone interested in leveraging the Google Search Console n8n node for advanced data processing.

Managing large content portfolios requires vigilance against keyword cannibalization—where multiple pages target the same terms, diluting authority and performance. This powerful n8n workflow provides a structured solution. It automatically pulls extensive search analytics data from Google Search Console (GSC) using the dedicated n8n node.

Unlike simple manual checks, this n8n workflow performs sophisticated grouping and filtering. It identifies queries that are served by more than one URL and confirms that the competing pages are actually receiving measurable clicks. By implementing this specific n8n template, you gain a clear, prioritized list of true cannibalization issues, enabling faster and more effective SEO optimization efforts. This core logic flow control ensures only actionable data points are surfaced.

This automation begins with the Manual Start n8n trigger, although it is easily adaptable to a time-based n8n trigger for scheduled runs.

1. Data Fetch: The process starts by connecting to Google Search Console via the Query Search Analytics n8n node. It retrieves 12 months of search analytics data, segmented by both query and page.


2. Grouping: The core of the logic resides in the Summarize by Query n8n node. This node groups all results by the search query, aggregating the associated ranking pages and their corresponding clicks into separate arrays for each unique query. It also counts how many distinct pages serve that query.


3. Filtering for Cannibalization: The subsequent Filter Cannibal Queries n8n node applies two crucial conditions to isolate genuine issues. It keeps only those items where:

1. Final Output: The resulting output delivers a clean list of cannibalized queries, complete with the competing URLs and the clicks they received, ready for remediation.

To set up this essential n8n workflow, follow these steps:

1. Import: Copy the provided n8n workflow JSON and paste it into your n8n instance via the 'New' menu and 'Import from JSON'.


2. Credential Setup: You must configure credentials for the Query Search Analytics n8n node. This requires a Google Search Console OAuth2 credential.


3. Configuration: Click on the Query Search Analytics n8n node.

1. Testing: Execute the n8n workflow using the Manual Start n8n trigger to verify the connection and data output. This n8n template is now ready to run.

Manual Start (n8n trigger): Initiates the execution of the n8n workflow. Configured for manual runs but can be easily swapped for an interval n8n trigger (e.g., weekly schedule).
Query Search Analytics (Google Search Console n8n node): Connects to GSC. Retrieves page insights, utilizing the query and page dimensions over the last 12 months. This n8n node is critical for extracting the necessary raw SEO data.
Summarize by Query (Summarize n8n node): A powerful data transformation n8n node. It groups input items by the query field, then uses the append aggregation to collect all associated page and clicks values into array fields for subsequent analysis.
Filter Cannibal Queries (Filter n8n node): Executes the flow control logic. It checks if the count of pages per query is greater than one AND if the second page in the result list has a click count greater than zero. This ensures the n8n workflow only surfaces actively cannibalized keywords.