How I Manage Google Search Console for Multiple Sites
I run 8 sites and spent 3 hours a week switching GSC accounts. Here's the exact setup I use now — with data, tradeoffs, and what I wish I'd known.
TL;DR
- GSC has no native cross-domain aggregate view — by design
- Switching between 8 accounts manually cost me ~45 minutes every weekday
- I tried three approaches: Google Sheets + Data Studio, a custom Python script, and a unified dashboard
- The unified dashboard won, but only once I had enough sites to justify the setup time
The 30-Second Headache Checker
Picture this: it's 8 a.m. Monday. You open your browser, log into GSC account one, check the Performance tab, screenshot the clicks column, log out. Log into account two. Repeat. By account five your coffee is cold.
If you're running more than three sites and you still manage google search console multiple sites by logging in and out manually, that's the problem I had for about 14 months before I fixed it.
Why I Started Tracking Eight Sites in One Place
I'm Jim Liu — independent developer based in Sydney. Over the past two years I've built and grown eight small web properties: a finance tool, a couple of Roblox game guides, a SaaS site, and a few content plays in adjacent niches. None of them is a full-time business. All of them need regular SEO attention.
The moment I crossed site number four, something broke in my workflow. I was spending roughly three hours per week just switching accounts, noting down numbers in a spreadsheet, and trying to compare trends across properties. That's not analysis time. That's data-collection time — and it's almost entirely wasted.
What GSC's Native Interface Won't Let You Do
This is the part that took me embarrassingly long to fully accept.
Google Search Console is built per property. There is no "all sites" tab. No aggregate impression graph. No cross-domain click comparison. This is not an oversight — Google has never shipped this feature because GSC is a webmaster verification tool first, not an analytics aggregator.
Each account switch averages about 2.3 seconds of load time in my testing. Across 8 sites, with 3-4 tab checks per site, that's nearly 75 context switches per session. Add the cognitive cost of reloading your mental model for a different domain's query mix, and the real number lands somewhere around 45 minutes of lost productive time per day.
The GSC API exists and is fully public. But consuming it directly means OAuth for each property, rate-limit handling, and writing the aggregation layer yourself. I know because I built one.
My Setup: Three Options I Actually Tried
Option 1: Google Sheets + Looker Studio
I started here because it seemed "free." I set up a Looker Studio report pulling from the GSC connector, one data source per site, and tried to blend them on a single canvas.
It broke within three weeks. The data freshness lags differently per source. The blended tables lose context — you can't easily drill from aggregate clicks down to specific queries per property without rebuilding the whole view. I also burned about six hours setting it up. Not free.
Option 2: GSC API + Python script
I spent a weekend on this. The Google Python client handles OAuth tokens and the searchanalytics.query endpoint works reliably. I wrote a loop that pulls the top 50 queries per site, writes them to a local SQLite database, and renders a terminal summary.
This actually worked for about four months. The problem: it only runs when I remember to run it. There's no alerting. There's no diff between this week and last week. And adding a new site means editing the script, re-authenticating, and updating the SQLite schema. I am not proud of the last two migrations.
Option 3: Multi-site SEO dashboard
I switched to a unified dashboard roughly two months ago — specifically the one I'm running at Multi-Site SEO Management. The shift was not dramatic on day one. It becomes obvious over three weeks when you realize you haven't opened individual GSC accounts at all.
The value isn't the data. The data is the same. The value is the interface sitting between raw GSC numbers and the decision "which site needs attention this week."
The Numbers After 60 Days
I tracked my own time. These are real numbers, not guesses.
| Method | Weekly setup time | Weekly check time | Latency to catch a traffic drop |
|---|---|---|---|
| Manual GSC switching | 0 | ~3 hours | 2–5 days (I'd miss it) |
| Google Sheets + Looker | ~6 hours (one-time) | ~1.5 hours | 1 day (if I remembered to open it) |
| Custom Python script | ~8 hours (one-time) | ~25 minutes | Same day (if I ran it) |
| Unified dashboard | ~1 hour (one-time) | ~20 minutes | Same day (automated) |
The 20-minute weekly check is real. Most of that is me reading, not clicking around. If I want to dig into a specific site's ROI trajectory, I use the SEO ROI Tracker to cross-reference GSC performance data with what I know about conversion rates. That connection — ranking data to revenue signal — is what the manual workflow completely missed.
Who This Actually Helps (and Who It Doesn't)
If you run one site, stop reading. GSC's native interface is fine. It is genuinely good for a single property.
If you run two or three sites, you're in the grey zone. The friction is real but probably not worth a workflow overhaul yet. Start with a basic Looker Studio setup.
Once you hit four or more sites — especially if the sites are in different niches with different query patterns — the context-switching cost compounds fast. That's when a unified view pays back its setup time within the first month.
The compare page for SEO reporting tools for agencies has a more structured breakdown of the tool options if you want to evaluate the category more broadly.
FAQ
Can I use the GSC API for free?
Yes. The Google Search Console API is free to use with a standard Google Cloud project. You're limited to 1,200 queries per minute per project, which is more than enough for 8–10 sites on a daily polling schedule. The cost is OAuth setup time per property, not money.
How often does GSC data refresh?
GSC data typically lags 1–2 days. The API returns the same data as the web interface — no faster access, no additional freshness. If you need same-day organic traffic data, GSC is not the source; you want your analytics platform (GA4, Plausible, etc.).
What's the minimum number of sites where this setup makes sense?
In my experience: four. Below that, the Looker Studio connector approach (free, slower to set up, but good enough) is probably a better fit. Above four, the cognitive overhead of per-site logins starts eating into the time you'd spend on actual optimization work.
Do I need a developer to set this up?
For the Python API route, yes — or at least a few hours of comfortable scripting time. For a unified dashboard product, no. The Multi-Site SEO Management hub page has the non-code setup path if you want to skip the script-building weekend I spent.
About Jim Liu
I'm a Sydney-based independent developer who builds and grows small web properties. I write about the operational side of running multiple sites — the parts that don't show up in keyword research guides. If you're managing more than three sites with spreadsheets, I've probably already made the mistake you're about to make.
Next Step
If you're ready to stop switching between GSC accounts and start seeing all your sites in one view, the practical starting point is the Multi-Site SEO Management page. It covers the full setup path from Google OAuth through to a working dashboard — without the trial-and-error I went through.