Google Search Console to Gmail, weekly SEO snapshot
You check Google Search Console, you export, you paste into a sheet, and you tell yourself you’ll “send the update later.” Later turns into never, or worse, a rushed note with missing context. This GSC email snapshot automation fixes that.
SEO consultants feel this when Monday reporting starts piling up. A marketing manager just wants a steady signal without logging into five tools. And if you own the site, frankly, you need a weekly “is this going up or down?” recap you can trust.
This workflow pulls the last 7 days of clicks, impressions, CTR, and average position, formats it into a clean summary, then emails it every Monday morning. You’ll see what it does, what you need, and how to tailor it.
How This Automation Works
The full n8n workflow, from trigger to final output:
n8n Workflow Template: Google Search Console to Gmail, weekly SEO snapshot
flowchart LR
subgraph sg0["Flow 1"]
direction LR
n0@{ icon: "mdi:cog", form: "rounded", label: "Weekly Trigger (Monday 7AM)", pos: "b", h: 48 }
n1["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/httprequest.dark.svg' width='40' height='40' /></div><br/>Get SEO Data from GSC"]
n2@{ icon: "mdi:code-braces", form: "rounded", label: "Generate SEO Report", pos: "b", h: 48 }
n3@{ icon: "mdi:message-outline", form: "rounded", label: "Send Weekly Report by Email", pos: "b", h: 48 }
n2 --> n3
n1 --> n2
n0 --> n1
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 n1 api
class n2 code
classDef customIcon fill:none,stroke:none
class n1 customIcon
The Problem: Weekly SEO reporting turns into busywork
Weekly SEO reporting sounds simple until you’re the person responsible for it. You open Search Console, set the date range, grab key metrics, and then try to explain what they mean in plain language. Next week you do it again, and the week after that. The time cost is annoying, but the bigger issue is consistency: different date ranges, different filters, and “quick checks” that turn into misleading updates. You end up reacting late because you never built a clean rhythm.
The friction compounds. Here’s where it usually breaks down.
- You lose about 30 minutes every Monday just pulling numbers and reformatting them for email.
- Small mistakes slip in, like comparing the wrong 7-day window or pasting CTR as a percentage in one report and a decimal in the next.
- Stakeholders stop trusting the updates because they feel different every week, even when performance is stable.
- When traffic dips, you notice late because checking “when you have time” is not a system.
The Solution: A Monday-morning Google Search Console snapshot email
This n8n workflow runs on a schedule and pulls your site’s last 7 days of performance metrics directly from the Google Search Console API. It takes the raw response (which is not email-friendly), cleans it up, and builds a readable weekly summary that you can skim in under a minute. Then it sends the finished snapshot to your inbox using Gmail, so you always have a timestamped “weekly check-in” without logging into Search Console at all. If you want it to be more opinionated, you can also layer in an AI-generated summary so the email highlights what changed and what might be worth checking.
The workflow starts every Monday morning via Cron. It fetches clicks, impressions, CTR, and average position for the previous 7 days, then formats the results in a Function step. Finally, Gmail delivers the report to the recipients you choose.
What You Get: Automation vs. Results
| What This Workflow Automates | Results You’ll Get |
|---|---|
|
|
Example: What This Looks Like
Say you manage 4 sites and you send a weekly update to each client or internal owner. Manually, it’s maybe 30 minutes per site to open Search Console, set “last 7 days,” capture clicks/impressions/CTR/position, and write a short email, so you’re at about 2 hours every Monday. With this workflow, setup takes around 10 minutes once, then the weekly “work” is basically zero because the email arrives automatically. You get those 2 hours back, and the numbers are consistent every time.
What You’ll Need
- n8n instance (try n8n Cloud free)
- Self-hosting option if you prefer (Hostinger works well)
- Google Search Console to access your verified site metrics.
- Gmail to send the weekly email snapshot.
- Google OAuth2 credentials (create in Google Cloud Console).
Skill level: Beginner. You’ll paste your site URL, connect Google, and adjust an email recipient.
Don’t want to set this up yourself? Talk to an automation expert (free 15-minute consultation).
How It Works
A Monday schedule triggers the run. The Cron node fires at the start of the week, so the snapshot shows up reliably without someone remembering to “go run the report.”
Search Console data gets pulled automatically. An HTTP Request connects to the Google Search Console API using your Google OAuth2 credentials and requests clicks, impressions, CTR, and average position for the last 7 days for your domain.
The report is cleaned up for humans. A Function step takes the raw API response and formats it into a readable weekly summary, which is the difference between “data” and something you can send to a client or team lead.
Gmail delivers the snapshot. The final node sends the formatted summary to your chosen recipients with a subject line you can standardize (helpful when you want to search your inbox later).
You can easily modify the email format to include extra metrics or a short commentary based on your needs. See the full implementation guide below for customization options.
Step-by-Step Implementation Guide
Step 1: Configure the Cron Trigger
Set the workflow to run at the start of each week using the schedule trigger.
- Add the Scheduled Week Start Trigger node as the workflow trigger.
- Configure your desired weekly schedule in the node’s trigger settings (for example, every Monday morning).
- Connect Scheduled Week Start Trigger to Fetch GSC Metrics.
Step 2: Connect Google Search Console Metrics
Pull search analytics data from Google Search Console for your site.
- Open Fetch GSC Metrics and set URL to
https://searchconsole.googleapis.com/webmasters/v3/sites/YOUR_SITE_URL/searchAnalytics/query. - Set Authentication to
genericCredentialTypeand Generic Auth Type tohttpBasicAuth. - Credential Required: Connect your httpBasicAuth credentials.
- Connect Fetch GSC Metrics to Build SEO Summary.
YOUR_SITE_URL with your verified Search Console site URL, otherwise the API will return an error.Step 3: Set Up the Processing Node
Transform the raw metrics into a formatted weekly report.
- Open Build SEO Summary and paste the provided Function Code exactly as shown in the workflow to format the report output.
- Ensure the function outputs a report field for the email body.
- Connect Build SEO Summary to Dispatch Weekly Email.
Step 4: Configure the Email Output
Send the weekly SEO report via Gmail.
- Open Dispatch Weekly Email and set Send To to
[YOUR_EMAIL]. - Set Subject to
Send Weekly Report by Email. - Credential Required: Connect your gmailOAuth2 credentials.
Step 5: Test and Activate Your Workflow
Validate the workflow end-to-end before turning it on.
- Click Execute Workflow to run a manual test from Scheduled Week Start Trigger.
- Confirm Fetch GSC Metrics returns rows and Build SEO Summary produces a formatted report output.
- Verify the email from Dispatch Weekly Email arrives with the expected subject and report content.
- Switch the workflow Active toggle on to run automatically each week.
Common Gotchas
- Google Search Console credentials can expire or need specific permissions. If things break, check the Google OAuth consent screen and token status in your n8n credential settings first.
- 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 10 minutes if your Google account is ready.
No. You’ll connect Google credentials and adjust a couple of fields like your site URL and email recipient.
Yes. n8n has a free self-hosted option and a free trial on n8n Cloud. Cloud plans start at $20/month for higher volume. You’ll also need to factor in Google API usage, which is typically minimal for weekly pulls.
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, but you’ll want one run per property. The simplest approach is duplicating the “Fetch GSC Metrics” HTTP Request and “Dispatch Weekly Email” Gmail node for each site, then updating the site URL and recipient list. Common customizations include adding a second email for your client, changing the subject line to include the domain, and tweaking the Function step to show week-over-week deltas.
Usually it’s an OAuth issue: the wrong Google account is connected, the consent screen wasn’t configured properly, or the token expired. Reconnect the Google OAuth2 credential in n8n and confirm the account has access to the verified property in Search Console. Also check that you replaced YOUR_SITE_URL with the exact property URL format you verified (domain vs. URL-prefix can trip people up). If it still fails, look at the HTTP Request node’s error message and confirm the Search Console API is enabled in Google Cloud.
A lot. On n8n Cloud Starter you’re mainly limited by monthly executions, so think in terms of “one weekly run per site” and you’ll usually have plenty of room; higher plans handle more volume. If you self-host, there’s no execution limit (it mostly depends on your server). Practically, many teams start with 5–20 sites and scale from there.
Often, yes. Search Console reporting tends to need light data shaping, and n8n’s Function step makes that straightforward without paying for multi-step zaps every week. It also gives you the option to self-host, which keeps recurring automation costs predictable when you add more sites. Zapier or Make can still be fine if you want a very simple “pull data, send email” with minimal formatting. If you’re unsure, Talk to an automation expert and you’ll get a quick recommendation based on your setup.
A weekly SEO snapshot that arrives on time is surprisingly powerful. Set it up once, and let the workflow handle the routine reporting while you focus on the decisions.
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.
