Skip to main content

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

Workflow preview

Workflow preview
100%
Daily 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 helps SEO teams catch top movers in Google Search Console by comparing daily performance across keyword segments like brand, nonbrand, and content categories. Instead of serving as a ...

Best for

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

Tools used

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

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
Daily Google Search Console SEO pulse: Catch top movers across keyword segments
Workflow name
Daily Google Search Console SEO pulse: Catch top movers across keyword segments

This workflow helps SEO teams catch top movers in Google Search Console by comparing daily performance across keyword segments like brand, nonbrand, and content categories.

Instead of serving as a routine check, it highlights the queries and pages with the biggest jumps or drops, making it ideal for spotting wins, losses, or unexpected shifts early.

How It Works

  1. Runs daily on a scheduled trigger (e.g. every morning).
  2. Pulls GSC data for the prior two days (e.g. yesterday vs. day before).
  3. Segments traffic by keyword type or URL pattern (e.g. brand, nonbrand, recipes, blogs, etc.).
  4. Calculates changes in clicks, impressions, CTR, and average position.
  5. Flags top movers with the biggest positive or negative deltas.
  6. Sends structured reports via Slack or email, grouped by segment and sorted by impact.

Setup Steps

  • Connect your Google Search Console account and optionally Gmail or Slack.
  • Swap in your own domain(s) and customize segmentation logic (e.g. brand terms, path filters).
  • By default, the workflow includes Slack alerts, but these can be easily switched to or combined with email, webhook, or other channels.
  • Full setup takes around 15–20 minutes with working GSC credentials.

Note: The “recipes” segment is included as an example of how to segment content. This can be changed to match blog, FAQ, product pages, or any other category.

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 - If

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

Block 2 - label

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

Block 3 - label1

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

Block 4 - Flatten

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

Block 5 - Flatten1

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

Block 6 - Merge

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

Block 7 - Top Movers Filter

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

Block 8 - Top Movers Filter1

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

Block 9 - Top Movers Filter2

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

Block 10 - Top Movers Filter3

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

Block 11 - Schedule Trigger1

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

Block 12 - priorDay

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

Block 13 - lastDay

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

Block 14 - Top DoD Movers Alert

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

Block 15 - Top DoD Movers Alert1

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

Block 16 - Top DoD Movers Alert2

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

Block 17 - Top DoD Movers Alert3

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

Block 18 - Tag KWs by Category

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

Block 19 - Define Days

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

Block 20 - Merge Days

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

Block 21 - Segment Switch

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

Block 22 - Sticky Note

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

Block 23 - Sticky Note1

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 25 workflow blocks. Download the JSON for the full node graph.

3. Summary Table

Workflow Daily Google Search Console SEO pulse: Catch top movers across keyword segments
Complexity advanced
Nodes 25
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/6004/6004.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 Daily Google Search Console SEO pulse: Catch top movers across keyword segments do?

This workflow helps SEO teams catch top movers in Google Search Console by comparing daily performance across keyword segments like brand, nonbrand, and content categories. Instead of serving as a ...

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.