Skip to main content

Weekly Google Search Console SEO pulse: Organic & brand vs non-brand performance

Workflow preview

Workflow preview
100%
Weekly Google Search Console SEO pulse: Organic & brand vs non-brand performance 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 generates a weekly performance summary from Google Search Console, focused on brand level SEO metrics and week over week trends. It provides a structured view of how each brand segmen...

Best for

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

Tools used

n8n-nodes-base.scheduletrigger, n8n-nodes-base.code, n8n-nodes-base.if, n8n-nodes-base.merge, n8n-nodes-base.httprequest, n8n-nodes-base.gmail, 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
Weekly Google Search Console SEO pulse: Organic & brand vs non-brand performance
Workflow name
Weekly Google Search Console SEO pulse: Organic & brand vs non-brand performance

This workflow generates a weekly performance summary from Google Search Console, focused on brand-level SEO metrics and week-over-week trends.

It provides a structured view of how each brand segment is performing, with clean formatting for quick insights.

Key Features

  • Sends a weekly email with a table showing clicks, impressions, CTR, and position — along with % change vs. the previous week.
  • Highlights both brand and non-brand clicks separately.
  • Color-coded % changes make it easy to spot wins (green) and losses (red) at a glance.

It’s designed to give SEO teams a consistent overview of performance by brand, helping to track directional shifts and support deeper analysis when needed.

How it works

  1. Runs weekly (e.g. every Monday) to compare “Last Week” vs. “2 Weeks Ago” from GSC data.
  2. Includes both brand + non-brand click breakdown.
  3. Calculates raw values and week-over-week % change for clicks, impressions, CTR, and position.
  4. Outputs a clean, formatted table with labeled rows and color-coded changes.
  5. Sends the table as part of a scheduled email (can also be adapted for Slack or other channels).

Setup steps

  • Requires connected Google Search Console data (per brand segment).
  • Email delivery is included by default (customizable to other platforms).
  • Update brand segmentation logic to match your tracking needs (e.g. domain, label, or custom filters).
  • Typical setup time: ~5-10 minutes with structured input data.

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 - Define Weeks

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

Block 3 - Brand Filter

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

Block 4 - Brand Filter1

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

Block 5 - Flatten8

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

Block 6 - Flatten9

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

Block 7 - If4

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

Block 8 - Merge 2 Weeks Ago

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

Block 9 - Merge Last Week

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

Block 10 - Brand/NB Pull1

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

Block 11 - Brand/NB Pull

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

Block 12 - Total Metrics Pull1

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

Block 13 - Total Metrics Pull

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

Block 14 - Add Brand Name

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

Block 15 - Merge Time Periods

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

Block 16 - Generate Brand Performance Table

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

Block 17 - Weekly GSC Metric Email

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

Block 18 - Sticky Note

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

Block 19 - Sticky Note1

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

Block 20 - Sticky Note2

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

Block 21 - Sticky Note3

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

3. Summary Table

Workflow Weekly Google Search Console SEO pulse: Organic & brand vs non-brand performance
Complexity advanced
Nodes 21
Categories Market Research, Multimodal AI
Author MattF
Published 09 Aug 2025

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/7203/7203.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: Organic & brand vs non-brand performance do?

This workflow generates a weekly performance summary from Google Search Console, focused on brand level SEO metrics and week over week trends. It provides a structured view of how each brand segmen...

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, Multimodal AI use case.