Skip to main content

Weekly Google Search Console SEO pulse: Catch top movers across keyword segments

Workflow preview

Workflow preview
100%
Weekly Google Search Console SEO pulse: Catch top movers across keyword segments preview
Open on n8n.io

Important notice

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

1. Workflow Overview

This workflow tracks week over week changes in Google Search Console performance and highlights the top movers across keyword segments like brand, nonbrand, and content categories. Instead of provi...

Best for

  • Market Research automation workflows
  • advanced n8n builders looking for reusable templates

Tools used

n8n-nodes-base.scheduletrigger, n8n-nodes-base.if, n8n-nodes-base.httprequest, n8n-nodes-base.code, n8n-nodes-base.merge, n8n-nodes-base.slack, n8n-nodes-base.gmail, n8n-nodes-base.switch

Source and attribution

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

Original n8n.io source

1.1 Workflow description

Title
Weekly Google Search Console SEO pulse: Catch top movers across keyword segments
Workflow name
Weekly Google Search Console SEO pulse: Catch top movers across keyword segments

This workflow tracks week-over-week changes in Google Search Console performance and highlights the top movers across keyword segments like brand, nonbrand, and content categories.

Instead of providing a routine check, it focuses on significant movements by:

  • Sending a Slack alert only if a query crosses a defined movement threshold.
  • Emailing a structured report with the Top 25 increases and Top 25 decreases for clicks, including % changes and linked URLs

It’s designed to surface the most important shifts, helping SEO teams catch big wins, losses, or anomalies early.

How it works

  1. Runs weekly (e.g. every Monday) to compare last week’s GSC data to the week prior.
  2. Segments traffic based on query and page (e.g. brand terms, category page URLs, etc.).
  3. Calculates delta and % change for clicks, CTR, impressions, and position.
  4. Filters and flags top movers with large shifts (default: ±200 clicks and ±30%).
  5. Sends Slack alerts only if meaningful changes are detected.
  6. Emails a full HTML table report showing the Top 25 up/down queries per segment.

Setup steps

  • Requires a connected Google Search Console account.
  • Slack alert is included by default (can be replaced with email, webhook, or other tools).
  • Customize your brand terms and URL filters to match your segments (e.g. recipes, blog, category pages).
  • Typical setup time: 15–25 minutes depending on the number of segments and filters you want.

Note: “Recipes” is used in the example to show how to segment by content type. You can update this to reflect your own site’s structure.

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 - Schedule Trigger

Type / Role
n8n-nodes-base.scheduleTrigger - scheduleTrigger
Config choices
Version 1.2

Block 2 - If

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

Block 3 - priorWeek

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

Block 4 - lastWeek

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

Block 5 - label

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

Block 6 - label1

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

Block 7 - Flatten

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

Block 8 - Flatten1

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

Block 9 - Define Weeks

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

Block 10 - Merge

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

Block 11 - Merge Weeks

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

Block 12 - Tag Brand / Recipes / Nonbrand

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

Block 13 - Top Movers Filter

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

Block 14 - Top 25 Filter

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

Block 15 - Top WoW Movers Alert

Type / Role
n8n-nodes-base.slack - slack
Config choices
Version 2.3

Block 16 - Code

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

Block 17 - Top WoW Movers Email

Type / Role
n8n-nodes-base.gmail - gmail
Config choices
Version 2.1

Block 18 - Merge4

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

Block 19 - Top WoW Movers Alert1

Type / Role
n8n-nodes-base.slack - slack
Config choices
Version 2.3

Block 20 - Top 25 Filter1

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

Block 21 - Top Movers Filter1

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

Block 22 - Top WoW Movers Alert3

Type / Role
n8n-nodes-base.slack - slack
Config choices
Version 2.3

Block 23 - Top WoW Movers Alert2

Type / Role
n8n-nodes-base.slack - slack
Config choices
Version 2.3

Block 24 - Top 25 Filter3

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

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

3. Summary Table

Workflow Weekly Google Search Console SEO pulse: Catch top movers across keyword segments
Complexity advanced
Nodes 35
Categories Market Research
Author MattF
Published 14 Jul 2025

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/6006/6006.json as the source template for this automation.

  2. 2. Import the template into n8n

    Open n8n, import the downloaded JSON, and review each node before activating the workflow.

  3. 3. Configure credentials and variables

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

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

Frequently asked questions

What does Weekly Google Search Console SEO pulse: Catch top movers across keyword segments do?

This workflow tracks week over week changes in Google Search Console performance and highlights the top movers across keyword segments like brand, nonbrand, and content categories. Instead of provi...

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 use case.