🔓 Unlock all 10,000+ workflows & prompts free Join Newsletter →
✅ Full access unlocked — explore all 10,000 AI workflow and prompt templates Browse Templates →
Home › n8n › Workflow
January 22, 2026

Google Sheets + Search Console: cannibalization alerts

Google Sheets + Search Console: cannibalization alerts - n8n workflow automation template
Lisa Granqvist Partner Workflow Automation Expert
Google Sheets + Search Console: cannibalization alerts - n8n workflow automation template
Get a free AI assessment → Get a free AI assessment → ⬇️ Use template

Your keyword tracking sheet says “all good.” Google Search Console says two (or five) different URLs are fighting for the same query. And you find out only after rankings wobble, traffic dips, or a client asks why the “main page” isn’t the one showing up.

SEO managers feel this first because they own performance. Agency owners and in-house marketers get dragged into it next, usually mid-sprint. This cannibalization alerts automation keeps the monitoring constant and the diagnosis consistent, without living in Search Console tabs.

This workflow watches your Google Sheet, pulls the last 30 days from Search Console for up to four sites, runs an AI risk assessment, then writes clean, client-ready notes back into the sheet. You’ll see how it works, what you need, and what results to expect.

How This Automation Works

The full n8n workflow, from trigger to final output:

n8n Workflow Template: Google Sheets + Search Console: cannibalization alerts

The Problem: Cannibalization Hides in Plain Sight

Keyword cannibalization is sneaky because it looks like “coverage.” You see a query driving impressions, but the clicks are scattered across multiple URLs. Rankings bounce, CTR drops, and nobody can confidently say which page should win. Then you do the manual loop: export Search Console, filter by query, group by page, compare positions, and write notes that explain it all in human language. That’s fine once. It’s brutal when you’re doing it weekly across several clients, with new keywords added all the time.

It adds up fast. Here’s where it usually breaks down.

  • You spend about 30 minutes per site just pulling and reshaping the same 30-day Search Console data.
  • Keywords get added to the tracking sheet, but nobody remembers to check if multiple URLs are now ranking for them.
  • When 3–5 pages compete, prioritization turns into opinion instead of a repeatable risk rule.
  • Client notes take longer than the analysis because you have to explain “why this is risky” every single time.

The Solution: AI-Powered Cannibalization Monitoring in Sheets

This n8n workflow turns your Google Sheet into a living cannibalization monitor. It starts by watching the sheet for keyword changes (every minute), then loads your target keywords and the client site URLs you care about. From there, it routes each client through its own Google Search Console API request and grabs a clean 30-day snapshot: queries, pages, positions, clicks, impressions, and CTR. The workflow groups the raw results by keyword, reconciles them against the keywords you’re tracking, and filters out anything that isn’t actually ranking. Finally, an AI agent reviews the “which pages rank for this query” pattern and assigns a risk level with plain-English reasoning and remediation suggestions, then writes everything back into the same spreadsheet.

The workflow begins in Google Sheets, so your team doesn’t need a new tool. Search Console data is fetched and normalized across up to four client sites, then AI summarizes the competitive overlap. The output lands back in Google Sheets, ready to sort, prioritize, and paste into a client update.

What You Get: Automation vs. Results

Example: What This Looks Like

Say you manage 4 client sites and track 50 keywords per site. Manually, pulling 30-day GSC data, grouping by keyword, and writing a short note often takes about 2 hours per site, so you lose most of a day. With this workflow, you add or edit keywords in the Google Sheet, wait a few minutes for the GSC pulls and AI analysis, and your sheet fills in with risk, reasoning, and next steps. You still review the recommendations, but the messy part is already done.

What You’ll Need

  • n8n instance (try n8n Cloud free)
  • Self-hosting option if you prefer (Hostinger works well)
  • Google Sheets to store tracked keywords and results.
  • Google Search Console for the query/page performance data.
  • OpenAI API key (get it from your OpenAI dashboard’s API keys page).

Skill level: Intermediate. You’ll connect Google credentials, add an API key, and match your sheet columns to the workflow fields.

Don’t want to set this up yourself? Talk to an automation expert (free 15-minute consultation).

How It Works

A keyword changes in Google Sheets. The workflow runs on a frequent Google Sheets trigger, so new keywords or edits automatically kick off an updated check.

Client sites get routed to the right data pull. It loads your client URLs, then uses simple “if this is client 1/2/3/4” routing so each property goes through the correct Search Console request.

Search Console data gets grouped into something you can act on. The HTTP requests fetch 30 days of metrics, then the workflow aggregates by keyword and reconciles those results against your tracked keyword list. Missing keywords can be flagged and skipped, which keeps the output clean.

AI assigns risk and writes the note. The AI agent reviews how many pages are competing and how strong each page is, then outputs structured fields like risk level, reasoning, observations, and remediation steps. Those fields are written back into your sheet as report-ready rows.

You can easily modify the risk thresholds to match how aggressive your team wants to be (for example, treating “2 pages in the top 10” as Moderate instead of Low). See the full implementation guide below for customization options.

Step-by-Step Implementation Guide

Step 1: Configure the Google Sheets Trigger

Set up the workflow to watch for changes in your keyword tracking sheet.

  1. Add the Keyword Sheet Watcher node and set Poll Times to everyMinute.
  2. Set Document to https://docs.google.com/spreadsheets/d/[YOUR_ID]/edit and Sheet Name to Keywords.
  3. Credential Required: Connect your Google Sheets OAuth2 credentials.
  4. Confirm that Keyword Sheet Watcher outputs to both Retrieve Client URLs and Load Target Keywords in parallel.
Tip: Ensure the sheet has a Keywords tab and that the worksheet ID matches the cached sheet name to avoid trigger mismatches.

Step 2: Connect Google Sheets Data Sources

Load client URLs and target keywords from Google Sheets before routing and analysis.

  1. Configure Retrieve Client URLs with Document set to Client URLs and Sheet Name set to URL.
  2. Configure Load Target Keywords with Document set to Client URLs and Sheet Name set to Keywords.
  3. Credential Required: Connect your Google Sheets OAuth2 credentials to both Retrieve Client URLs and Load Target Keywords.
  4. Verify Retrieve Client URLs outputs to Client 1 Router, Client 2 Router, Client 3 Router, and Client 4 Router in parallel.
⚠️ Common Pitfall: The workflow expects a column named Client Website in the URL sheet. If it’s missing or differently named, the routers will never match.

Step 3: Set Up Client Routing and GSC Requests

Route each client to the correct Google Search Console request and pull query/page data.

  1. In Client 1 Router, set the condition Left Value to {{$json['Client Website'].trimStart().trimEnd()}} and Right Value to https://client-one.example/.
  2. In Client 2 Router, set the condition Right Value to client-two.example using {{$json['Client Website'].trimStart().trimEnd()}} as the left value.
  3. In Client 3 Router and Client 4 Router, set the Right Value to https://client-three.example/ and https://client-four.example/ respectively.
  4. For all four GSC Request Client 1–GSC Request Client 4 nodes, set Method to POST and JSON Body to { "startDate": "{{ $now.minus(30, 'days').format('yyyy-MM-dd') }}", "endDate": "{{ $now.format('yyyy-MM-dd') }}", "dimensions": ["query", "page"] }.
  5. Credential Required: Connect your Google OAuth2 API credentials to all four GSC request nodes.

Step 4: Aggregate and Reconcile Keyword Data

Combine GSC results with the target keyword list and remove missing entries.

  1. Keep the JavaScript logic intact in Aggregate Keywords C1, Aggregate Keywords C2, Aggregate Keywords C3, and Aggregate Keywords C4 to group keywords by URL with CTR, clicks, impressions, and position.
  2. Set Combine All GSC Inputs to Number Inputs 5 to merge all four client aggregates plus Load Target Keywords.
  3. Leave Reconcile Sheet Keywords code as-is to match sheet keywords against GSC data and flag missing keywords with not_found_in_gsc.
  4. In Exclude Missing Keywords, set the condition Left Value to {{$json.status}} and Right Value to not_found_in_gsc with the notEquals operator.
Tip: Because Keyword Sheet Watcher runs in parallel to Retrieve Client URLs and Load Target Keywords, ensure both sheets are in the same Google Drive account to avoid permission mismatches.

Step 5: Set Up AI Cannibalization Analysis

Analyze cannibalization risk using the AI agent with structured output.

  1. In Cannibalization Risk Analyst, keep the Text prompt with expressions {{$json.keyword}} and {{ JSON.stringify($json.urls) }}.
  2. Set OpenAI Chat Model to model gpt-4o and connect it as the language model for Cannibalization Risk Analyst.
  3. Keep the Structured Output Parser JSON schema as provided to enforce structured output.
  4. Credential Required: Connect your OpenAI API credentials to OpenAI Chat Model (not the parser).
⚠️ Common Pitfall: The Structured Output Parser is a sub-node; add credentials to OpenAI Chat Model, not the parser itself.

Step 6: Configure Output to Google Sheets

Write the analysis results back to your data sheet with append/update logic.

  1. In Write Analysis to Sheet, set Operation to appendOrUpdate and select the Sheet Name data.
  2. Map columns exactly as defined, including Data set to {{$json.output['URLs for Keyword'].map(i => `${i.url} | Position: ${i.position} | Clicks: ${i.clicks} | Impressions: ${i.impressions} | CTR: ${i.ctr}`).join('\n')}}.
  3. Set Date to {{$now.format('yyyy-MM-dd')}} and Status to {{$('Reconcile Sheet Keywords').item.json.status}}.
  4. Credential Required: Connect your Google Sheets OAuth2 credentials to Write Analysis to Sheet.

Step 7: Test and Activate Your Workflow

Validate the workflow end-to-end before enabling it for continuous monitoring.

  1. Use Execute Workflow to run a manual test with a sample row in the Keywords sheet.
  2. Confirm that Keyword Sheet Watcher triggers and that Retrieve Client URLs and Load Target Keywords both execute in parallel.
  3. Verify that Write Analysis to Sheet writes structured results, including Risk Level, Summary, and Target page.
  4. Turn the workflow Active to start continuous monitoring.
🔒

Unlock Full Step-by-Step Guide

Get the complete implementation guide + downloadable template

Common Gotchas

  • Google Search Console credentials can expire or lack access to a specific property. If things break, check the Google connection in n8n and confirm the account has access to each site in Search Console.
  • If you’re using Wait nodes or you’re hitting the Search Console API during busy periods, processing times vary. Bump up the wait duration if downstream nodes fail on empty responses.
  • Default prompts in AI nodes are generic. Add your brand voice and preferred recommendation format early or you’ll be editing outputs forever.

Related Workflows

If you like this approach but want a simpler “sheet-first” version for one property, Google Search Console to Google Sheets, spot cannibalization is a solid companion for quick audits or lightweight accounts.

For teams that need visibility without opening a spreadsheet, Search Console to Slack, daily SEO mover alerts is great when you want daily “what changed” pings alongside your cannibalization tracking.

When you’re expanding content and you want new opportunities to feed into the same planning sheet, Google Search Console to Google Sheets, new queries pairs nicely, because it surfaces fresh queries before they become messy overlaps.

Need alerts with a bit more structure (and a shared channel for the team)? Google Search Console + Slack: SEO movers alerts helps you catch ranking swings while this workflow explains the “why” behind cannibalization risk.

Finally, if your process ends with a brief or a content task, Slack to Google Sheets, SEO briefs done right helps you turn the AI notes into tracked deliverables without copying and pasting between tools.


Quick reference:

Frequently Asked Questions

How long does it take to set up this cannibalization alerts automation?

About an hour if your Google accounts are ready.

Do I need coding skills to automate cannibalization alerts?

No. You’ll mainly connect accounts and map your Google Sheet columns. The workflow’s logic is already built; you’re configuring it for your clients.

Is n8n free to use for this cannibalization alerts workflow?

Yes. n8n has a free self-hosted option and a free trial on n8n Cloud. Cloud plans start at $20/month for higher volume. You’ll also need to factor in OpenAI API costs, which are usually a few cents per run depending on how many keywords you analyze.

Where can I host n8n to run this cannibalization alerts automation?

Two options: n8n Cloud (managed, easiest setup) or self-hosting on a VPS. For self-hosting, Hostinger VPS is affordable and handles n8n well. Self-hosting gives you unlimited executions but requires basic server management.

Can I customize this cannibalization alerts workflow for more than 4 clients?

Yes, but you’ll duplicate the client routing and Search Console request path. In practice, you add another “client router” branch, another HTTP request for that property, and another aggregation path before everything merges. Many teams also customize the AI output to match their ticket template, like “recommended canonical URL,” “pages to merge,” and “internal links to update.”

Why is my Google Search Console connection failing in this cannibalization alerts workflow?

Usually it’s expired Google credentials or the connected account doesn’t have access to one of the properties. Reconnect Google in n8n and double-check the exact Search Console property URL matches what the workflow is requesting. Rate limiting can also show up if you’re pulling a lot of queries across several sites at once, so spacing runs out a bit helps.

How many keywords can this cannibalization alerts automation handle?

On n8n Cloud Starter, you’re limited by monthly executions, not keywords, so the practical cap depends on how often your sheet changes. If you self-host, there’s no execution limit; it mostly comes down to your server and the Search Console API responding quickly. For many small teams, a few hundred keywords across a handful of sites is comfortable. If you’re tracking thousands, you’ll want to reduce how often it runs and batch keywords more carefully.

Is this cannibalization alerts automation better than using Zapier or Make?

Often, yes. This workflow uses branching per client, merging streams, and structured AI output, which tends to get awkward or expensive in Zapier-style “one path” automations. n8n also gives you the self-hosting option, which is a big deal if you run checks frequently. If you only need a basic “send me a message when rankings change” flow, Zapier or Make can be faster to set up. If you’re unsure, Talk to an automation expert and describe your reporting cadence and keyword volume.

Once this is running, cannibalization stops being a surprise and becomes a sortable list. The workflow handles the repetitive checking. You make the calls that actually move rankings.

Need Help Setting This Up?

Our automation experts can build and customize this workflow for your specific needs. Free 15-minute consultation—no commitment required.

Talk to Automation Expert →

Lisa Granqvist

Workflow Automation Expert

Expert in workflow automation and no-code tools.

×

Use template

Get instant access to this n8n workflow Json file

Copy and import json workflow into your n8n workflow

💬
Get a free quote today!
Get a free quote today!

Tell us what you need and we'll get back to you within one working day.

Get a free quote today!
Get a free quote today!

Tell us what you need and we'll get back to you within one working day.