Every site's Search Console. One table.
Google Search Console shows one property at a time. If you run ten or fifty sites, that is ten or fifty tabs, exports and spreadsheets. Multisite Agent connects once to the Google account that owns your properties and lists every site side by side, with a 28-day trend and alerts that name the site that moved.
Read-only Google scope · One site free · Connect in two minutes
You didn't sign up to be a reporting department.
Building a site takes an afternoon now. Watching twenty of them takes the week, and most of it is clicking between properties that look exactly alike.
One property at a time
Search Console has no portfolio view. Comparing ten sites means opening ten properties, setting the same date range ten times, exporting ten CSVs and pasting them into a sheet nobody updates after the first month.
The drop you hear about from the client
A site loses its verification, a redirect goes wrong, index coverage slides. Nobody was looking at that property this week, so the first signal is an email asking why the phone stopped ringing.
Properties spread across Google accounts
Some sites were verified with the client's account, some with yours, some with an old agency login. Every check starts with the question of which account to switch to.
Monthly reports built by hand
Screenshots, pasted numbers, a sentence per site. It takes a morning per client and is already out of date when it is sent.
Every property in one sortable table, refreshed daily.
Connect once, map each property to a site, and read one overview instead of twenty dashboards. Sort by what moved and open only the sites that need you.
All sites side by side
Clicks, impressions, CTR, average position and indexed pages for every property, same metrics, same date range, sortable by any column.
A 28-day trend per site
Each row compares the last 28 days with the previous period, so the sites that grew or dropped sort to the top without a spreadsheet.
Alerts that name the site
Clicks down week over week, index coverage slipping, verification lost. The alert says which site, which metric and how much, before a client notices.
robots.txt watched on every site
Checked every 24 hours: valid format, no important crawler blocked by accident, and a diff when the file changes.
A workspace per client
Group sites by client, invite teammates, and give a client a read-only view of their own sites, in their language.
Exports and API
CSV and JSON per site or per workspace, and a REST API for the rows you see in the table, for the pipeline you already have.
The weekly check drops from a morning to twenty minutes.
The work doesn't disappear. The clicking does. One overview, sorted by change, tells you where to look first.
Before: Monday morning, twenty tabs
- Open each Search Console property and set the same date range.
- Export a CSV per site, paste into a spreadsheet, fix the columns.
- Scan the numbers for anything that looks off; miss the site you didn't open.
- Take screenshots for each client and write the report by hand.
- Find out about the real problem when the client writes.
After: one table, sorted by change
- Open the overview. Sites with the largest change sort to the top.
- Open the two or three that moved and read their top pages and queries.
- Check the alerts: each one names the site and the metric.
- Share a read-only view with the client instead of a report.
- Spend the rest of the morning on the sites, not on the reporting.
You hear first, not the client
Alerts arrive when a site drops, so the message to the client is "we saw it and fixed it", not an explanation after the fact.
Clients read their own table
A client sees their sites in their workspace, read-only, in their language. The monthly report becomes a link they can open any day.
One number, no argument
Everyone looks at the same metrics for the same date range from the same source, so the conversation is about what to do, not whose figure is right.
Set up once. Then it runs.
Add your sites
Name them and point them at their domains. Import a list if you have one.
Connect Google once
Sign in with the account that owns your properties. Every property is found and matched to a site by hostname.
Read one table
History imports, then the data syncs daily. Sort by the column that matters this week.
Share a view
Invite teammates, or give a client a read-only workspace with their own sites.
Questions about Multi Search Console.
Is this a replacement for Google Search Console?
No. It is a layer on top of it. Multisite Agent reads your data through Google's read-only API and shows all your properties in one table. Search Console stays the source and keeps every tool you use today.
Which properties are supported?
Domain properties and URL-prefix properties, with owner, full or restricted permission. Restricted properties import performance data but not URL inspection.
Can I see data for properties owned by different Google accounts?
Each workspace connects one Google account. The simplest setup is to add the connecting account as a user on every property, which takes a minute per property and needs no owner rights.
How far back does the data go?
Google keeps about 16 months of performance data. The first import pulls what is available; from then on Multisite Agent stores new data every day, so on the Enterprise plan your history grows beyond Google's limit from the day you connect.
Does it write anything to my properties?
No. The Google scope is read-only. Tokens are encrypted at rest and can be revoked from the integrations page at any time.
Stop opening twenty tabs.
Connect Search Console and see every site in one table before lunch. One site is free.