Skip to main content

Automated SEO performance collection from Google Search Console to NocoDB

Workflow preview

Workflow preview
100%
Automated SEO performance collection from Google Search Console to NocoDB preview
Open on n8n.io

Important notice

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

1. Workflow Overview

Problem Monitoring SEO performance from Google Search Console (GSC) manually is repetitive and prone to human error. For marketers or analysts managing multiple domains, checking reports manually a...

Best for

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

Tools used

n8n-nodes-base.nocodb, n8n-nodes-base.stickynote, n8n-nodes-base.scheduletrigger, n8n-nodes-base.httprequest, n8n-nodes-base.code

Source and attribution

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

Original n8n.io source

1.1 Workflow description

Title
Automated SEO performance collection from Google Search Console to NocoDB
Workflow name
Automated SEO performance collection from Google Search Console to NocoDB

Problem

Monitoring SEO performance from Google Search Console (GSC) manually is repetitive and prone to human error. For marketers or analysts managing multiple domains, checking reports manually and copying data into spreadsheets or databases is time-consuming. There is a strong need for an automated solution that collects, stores, and updates SEO metrics regularly for easier analysis and dashboarding.

Solution

This workflow automatically pulls performance metrics from Google Search Console — including queries, pages, CTR, impressions, positions, and devices — and stores them in a structured format inside a NocoDB table. It’s ideal for SEO specialists, marketing teams, or data analysts who need to automate SEO reporting and centralize data for analytics or dashboards (like Superset or Metabase).

Setup Instructions

  1. Authorize your Google Search Console account
    Connect via OAuth2 (requires GSC API access).

  2. Create a NocoDB table
    Define fields to match GSC response:

    • query (text)
    • page (URL)
    • device (text)
    • clicks (number)
    • impressions (number)
    • ctr (percentage)
    • position (number)
  3. Add credentials in n8n
    Use credential nodes for both:

    • Google OAuth2
    • NocoDB API Token
  4. Customize schedule trigger
    Set the frequency (e.g., weekly) and adjust the domain/date range as needed.

  5. Generalize domains
    Replace specific domains like martechmafia.net with your-domain.com before submission.

NocoDB Table Structure

The NocoDB table must match the fields coming from GSC's Search Analytics API. Here's a sample schema:

{
  "query": "string",
  "page": "string",
  "device": "string",
  "clicks": "number",
  "impressions": "number",
  "ctr": "number",
  "position": "number"
}

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

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

Block 2 - Sticky Note

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

Block 3 - Sticky Note3

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

Block 4 - Sticky Note4

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

Block 5 - Sticky Note5

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

Block 6 - Schedule Trigger1

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

Block 7 - HTTP Request1

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

Block 8 - Code1

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

3. Summary Table

Workflow Automated SEO performance collection from Google Search Console to NocoDB
Complexity intermediate
Nodes 8
Categories Market Research
Author Martech Mafia
Published 26 Apr 2025

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/3721/3721.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 Automated SEO performance collection from Google Search Console to NocoDB do?

Problem Monitoring SEO performance from Google Search Console (GSC) manually is repetitive and prone to human error. For marketers or analysts managing multiple domains, checking reports manually 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.