Google Search Console to Google Sheets, new queries
You find a “new” keyword opportunity… three weeks late. Not because you weren’t looking, but because Search Console hides the good stuff inside filters, date ranges, and a lot of clicking.
This Search Console Sheets setup hits SEO leads first, honestly. But marketing managers and small business owners feel it too when content planning turns into guesswork. The outcome is simple: new queries land in a spreadsheet, already sorted into “zero click” versus “has click,” so you can act faster.
Below you’ll see how the workflow works, what it outputs, and how to make it run weekly so you stop missing fresh SEO wins.
How This Automation Works
The full n8n workflow, from trigger to final output:
n8n Workflow Template: Google Search Console to Google Sheets, new queries
flowchart LR
subgraph sg0["Flow 1"]
direction LR
n0@{ icon: "mdi:cog", form: "rounded", label: "Manual Start", pos: "b", h: 48 }
n1@{ icon: "mdi:cog", form: "rounded", label: "Compare search analytics bet..", pos: "b", h: 48 }
n2@{ icon: "mdi:swap-horizontal", form: "rounded", label: "Filter (No Past Impressions)", pos: "b", h: 48 }
n3@{ icon: "mdi:swap-horizontal", form: "rounded", label: "Zero Click", pos: "b", h: 48 }
n4@{ icon: "mdi:swap-horizontal", form: "rounded", label: "Has Click", pos: "b", h: 48 }
n0 --> n1
n2 --> n3
n2 --> n4
n1 --> n2
end
%% Styling
classDef trigger fill:#e8f5e9,stroke:#388e3c,stroke-width:2px
classDef ai fill:#e3f2fd,stroke:#1976d2,stroke-width:2px
classDef aiModel fill:#e8eaf6,stroke:#3f51b5,stroke-width:2px
classDef decision fill:#fff8e1,stroke:#f9a825,stroke-width:2px
classDef database fill:#fce4ec,stroke:#c2185b,stroke-width:2px
classDef api fill:#fff3e0,stroke:#e65100,stroke-width:2px
classDef code fill:#f3e5f5,stroke:#7b1fa2,stroke-width:2px
classDef disabled stroke-dasharray: 5 5,opacity: 0.5
class n2,n3,n4 decision
The Problem: New Search Queries Get Missed
Google Search Console is great at telling you what already happened. It’s less great at surfacing what just changed. New queries appear quietly, mixed into thousands of rows, and if you don’t compare date ranges properly you will never notice them. Then you keep publishing based on old assumptions while a handful of “almost there” keywords sit with impressions but zero clicks. That’s the frustrating part: the opportunity is already in your data, but it doesn’t show up in your weekly routine.
The friction compounds. Here’s where it breaks down in real life:
- You end up doing the same date-range comparison every week, which can burn about an hour once you include exporting and cleanup.
- “Zero click” queries don’t get separated, so CTR fixes (titles, meta descriptions, on-page alignment) get pushed to “later.”
- Someone inevitably copies the wrong table, filters the wrong property, or forgets the country/device setting, and the report becomes unreliable.
- By the time the team sees the data, the moment to create supporting content or internal links has already cooled off.
The Solution: Track “New Queries” Weekly, Automatically
This n8n workflow pulls search analytics from Google Search Console, compares the last 7 days against a reference period, and isolates only queries that are truly new (they had no impressions before). Then it splits those new queries into two useful buckets: queries getting impressions but still no clicks (“Zero Click”), and queries that already have clicks (“Has Click”). Instead of staring at Search Console charts, you get two clean datasets you can paste into a report, send to a stakeholder, or append to a running Google Sheet for week-over-week tracking. It’s the same analysis you would do manually, just consistent every time.
The workflow starts with a manual run (so you can test it safely). It pulls the comparison data from Search Console, filters out anything that isn’t new, then routes what’s left into “no clicks yet” versus “clicks present” paths. From there, output can go straight to Google Sheets or Excel 365 if you want a shared report.
What You Get: Automation vs. Results
| What This Workflow Automates | Results You’ll Get |
|---|---|
|
|
Example: What This Looks Like
Say you manage one site and do a “new queries check” every Monday. Manually, it’s usually 20 minutes to set the right date ranges and filters, another 20 minutes to export and clean the rows, then 20 minutes to split “zero click” vs “has click” and share it. That’s about an hour weekly. With this workflow, you run it in under a minute, then spend maybe 10 minutes reviewing the two lists and turning them into actions. You get most of that hour back, every week.
What You’ll Need
- n8n instance (try n8n Cloud free)
- Self-hosting option if you prefer (Hostinger works well)
- Google Search Console with access to your property.
- Google Sheets to store and share weekly query lists.
- Google account connection (authorize inside n8n credentials).
Skill level: Beginner. You’ll connect Search Console, pick a property, and adjust one date comparison if needed.
Don’t want to set this up yourself? Talk to an automation expert (free 15-minute consultation).
How It Works
Manual run (or schedule it later). The workflow starts with a manual trigger so you can test on demand. Once you trust it, swapping to a weekly schedule is straightforward.
Search Console comparison pull. n8n queries Google Search Console and compares the last 7 days against a reference period you choose. This is the key move because it separates “new” from “already known.”
Keep only the truly new queries. A filter removes anything that had impressions in the past. What’s left is the list you actually care about: keywords Google is testing your pages for right now.
Split into action-ready buckets. One branch collects “Zero Click” queries (impressions but no clicks). The other collects “Has Click” queries, which are great candidates for supporting content and internal linking.
You can easily modify the date ranges to match your reporting cadence (weekly, biweekly, or monthly) based on your needs. See the full implementation guide below for customization options.
Step-by-Step Implementation Guide
Step 1: Configure the Manual Trigger
This workflow starts manually to let you run the Search Console comparison on demand.
- Add or confirm the Manual Execution Start node at the beginning of the canvas.
- Ensure Manual Execution Start is connected to Compare Search Insights as the first execution step.
Step 2: Connect Google Search Console
Fetch and compare query insights from Google Search Console.
- Select the Compare Search Insights node.
- Set Operation to
comparePageInsights. - Set Compare Mode to
custom. - Set Date Range Mode A to
last7d. - Set Date Range Mode B to
customwith Start Date B2024-08-01T00:00:00and End Date B2025-08-12T00:00:00. - Set Site URL Compare to
sc-domain:example.com. - Set Row Limit Compare to
10000. - Under Dimensions Compare, add
query. - Credential Required: Connect your Google Search Console credentials.
Step 3: Filter for New Queries
Identify queries with no prior impressions in the comparison period.
- Open Filter No Prior Impressions.
- Add a condition where Left Value is
{{ $json.impr_b }}, Operation isequals, and Right Value is0.
Step 4: Route Results by Clicks (Parallel)
Split new queries into two outcomes based on click performance.
- Confirm Filter No Prior Impressions outputs to both No Click Results and Click Present Results in parallel.
- In No Click Results, set a condition where Left Value is
{{ $json.clicks_a }}, Operation isequals, and Right Value is0. - In Click Present Results, set a condition where Left Value is
{{ $json.clicks_a }}, Operation isgt, and Right Value is0.
Step 5: Test & Activate Your Workflow
Validate that the comparison and filters produce the expected query groups.
- Click Execute Workflow to run from Manual Execution Start.
- Confirm Compare Search Insights returns query rows and that Filter No Prior Impressions passes only items with
{{ $json.impr_b }}equal to0. - Verify that results are split between No Click Results and Click Present Results based on
{{ $json.clicks_a }}. - When satisfied, toggle the workflow to Active for production use.
Common Gotchas
- Google Search Console credentials can expire or lack property permissions. If things break, check the n8n Credentials screen and confirm the account has access to that exact property.
- If you’re using Wait nodes or external rendering, processing times vary. Bump up the wait duration if downstream nodes fail on empty responses.
- Default prompts in AI nodes are generic. Add your brand voice early or you’ll be editing outputs forever.
Frequently Asked Questions
About 20 minutes if your Search Console access is already sorted.
No. You’ll connect your Google account and adjust a couple of settings inside the Search Console node.
Yes. n8n has a free self-hosted option and a free trial on n8n Cloud. Cloud plans start at $20/month for higher volume. Google Search Console and Google Sheets don’t add per-request fees for typical usage.
Two options: n8n Cloud (managed, easiest setup) or self-hosting on a VPS. For self-hosting, Hostinger VPS is affordable and handles n8n well. Self-hosting gives you unlimited executions but requires basic server management.
Yes, and it’s one of the most common tweaks. Update the date ranges inside the “Compare Search Insights” (Search Console compare) node so it compares “last 30 days” against your prior reference window. Many teams also add extra filters for CTR thresholds, country, or device so the Sheet only shows queries worth acting on. If you want delivery instead of a spreadsheet, swap the output for Slack or email once the two branches are created.
Usually it’s expired authorization or the connected Google account doesn’t have access to the property you selected. Reconnect the credential in n8n, then double-check property permissions inside Search Console. If you recently changed from a domain property to a URL-prefix property (or the other way around), update the selected property in the node because the old one can look “valid” but still fail.
A lot for normal SEO reporting. On n8n Cloud, it mainly depends on your execution limits; on self-hosted n8n there’s no platform cap, just what your server can comfortably run.
Sometimes, yes. The bigger issue is that “new queries” is a compare-and-filter problem, not a simple “send rows from A to B” problem, so you need a tool that handles branching cleanly. n8n is strong here because you can split into “Zero Click” and “Has Click” paths without paying extra for every little step, and you can self-host if you want predictable costs. Zapier or Make can be fine if you’re only exporting a single report on a simple schedule, but they get awkward once you start doing comparisons and multi-branch logic. If you want a second opinion, Talk to an automation expert and we’ll point you to the simplest setup for your situation.
Once this is running, new queries stop being a surprise and start being a weekly input to decisions. The workflow handles the repetitive part so you can spend your time on the fixes that actually move CTR and rankings.
Need Help Setting This Up?
Our automation experts can build and customize this workflow for your specific needs. Free 15-minute consultation—no commitment required.
