n8n Daily Google Search Console SEO Pulse: Catch Top Movers Across Keyword Segments

This n8n workflow is designed to proactively monitor Google Search Console data for significant changes in keyword performance across different segments. It acts as an "SEO pulse" by regularly fetching data, identifying top movers (keywords with substantial ranking or impression changes), and alerting relevant stakeholders via Slack.

What it does

This workflow automates the following steps:

1. Scheduled Trigger: Initiates the workflow on a predefined schedule (e.g., daily).
2. HTTP Request (Google Search Console API): Makes an API call to Google Search Console to fetch performance data for a specified property and date range.
3. Code (Data Processing): Processes the raw Google Search Console data. This likely involves:
   • Extracting key metrics (e.g., clicks, impressions, CTR, position).
   • Calculating daily changes for these metrics.
   • Segmenting keywords or queries based on predefined criteria (though the JSON doesn't explicitly show segmentation logic, the workflow name suggests it).
   • Identifying "top movers" – keywords with significant positive or negative shifts in performance.
4. If (Conditional Logic): Checks if any top movers were identified by the Code node.
5. Switch (Conditional Routing): (This node is present but not connected in the provided JSON. In a complete workflow, it would likely route messages based on the type or severity of the detected changes, e.g., different Slack channels for positive vs. negative movers, or different alert levels.)
6. Merge (Data Consolidation): (This node is present but not connected in the provided JSON. In a complete workflow, it might be used to combine data streams before a final action, for example, merging different types of alerts into a single message.)
7. Slack (Notification): Sends a notification to a designated Slack channel, detailing the identified top movers and their performance changes.
8. Sticky Note: Provides a textual description or context within the workflow for documentation purposes.

Prerequisites/Requirements

To use this workflow, you will need:

• Google Search Console API Access: Configured access to the Google Search Console API for the properties you wish to monitor. This typically involves setting up a Google Cloud Project and enabling the Search Console API.
• n8n Google Search Console Credentials: An n8n credential configured for Google Search Console (likely a Google OAuth2 credential).
• Slack Account: A Slack workspace and a channel where you want to receive notifications.
• n8n Slack Credentials: An n8n credential configured for Slack (e.g., a Slack OAuth2 or Webhook credential).

Setup/Usage

1. Import the Workflow: Import the provided JSON into your n8n instance.
2. Configure Credentials:
   • Set up your Google Search Console credentials in n8n.
   • Set up your Slack credentials in n8n.
3. Configure HTTP Request Node (ID: 19):
   • Update the URL and any necessary headers/parameters to correctly call the Google Search Console API for your desired property and date range.
   • Ensure the correct Google Search Console credential is selected.
4. Configure Code Node (ID: 834):
   • Review and modify the JavaScript code to define your specific logic for:
     • Parsing the Google Search Console API response.
     • Calculating performance changes (e.g., daily, weekly).
     • Defining what constitutes a "top mover" (e.g., a certain percentage change in position or impressions).
     • (Potentially) Implementing keyword segmentation logic.
5. Configure If Node (ID: 20):
   • Set the condition to check if the Code node output contains any identified top movers (e.g., {{ $json.length > 0 }}).
6. Configure Slack Node (ID: 40):
   • Select your Slack credential.
   • Specify the Slack channel where alerts should be posted.
   • Customize the message content to include relevant details from the Code node's output (e.g., keyword, old position, new position, change, impressions).
7. Configure Schedule Trigger (ID: 839):
   • Set your desired schedule for the workflow to run (e.g., daily at a specific time).
8. Activate the Workflow: Once configured, activate the workflow to start monitoring your Google Search Console data.