Managing 20+ client properties in Search Console without losing your mind

If you run search for other people, the hard part is not reading a chart. It is holding twenty or thirty properties in your head, knowing which three need attention this week, and avoiding the specific professional damage of a client noticing a drop before you did. Search Console is a superb tool for one site at a time. At twenty, its interface becomes the problem.

This is how the portfolio problem actually breaks down, and how QueryWatch is built around it.

Three ways a portfolio goes wrong

The picker. Search Console’s property switcher is a dropdown followed by a full page reload. A morning check across twenty client sites is twenty of those, on a phone, and after the sixth one you stop. Which means the properties at the bottom of the list get looked at monthly, if then.

The account mess. Agency properties are never all under one login. Some are yours, verified from your own account. Some were granted by the client, under their account, with a permission level they chose. Some live in a second Google account you made three years ago for a reason you no longer remember. Search Console shows you one account’s view at a time.

The silent property. The dormant client site, the one on a small retainer that nobody opens, drops thirty percent in March and nobody knows until the client’s quarterly review. There was no error, no manual action, nothing Google would email about. Just less traffic, unobserved.

A portfolio, not a picker

The fix for the first problem is a different shape of screen: one list, every property you have access to, with yesterday’s clicks and a sparkline on each row. You read the whole portfolio the way you read a stock list, and you only open a property when its row looks wrong.

In QueryWatch that list is the home screen, and the organisation on it is yours. Client tags group properties by who they belong to; each tag gets a colour, so a row is recognisable before you read it. Favourites pin the four sites you check daily to the top. Hidden properties take the dormant ones you inherited out of the list without removing your access. And the permission level is shown per property, owner or full or restricted, so you know before you promise a client something whether you can actually do it. Our demo dataset has a property tagged Brightloom in orange next to one you only have restricted access to, which is roughly what a real agency’s list looks like.

All of that is on the free tier. Every property, with real numbers on each, tagged and coloured however you like.

Multiple Google accounts

The second problem is a Pro feature, because it is an agency problem rather than an edge case. Multi-account switching lets you sign in with more than one Google account and see the properties from all of them in the same portfolio. The client-granted properties and your own sit in one list, tagged by client rather than by which login they happen to live under.

The silent property

The third problem is what the alerts are for, and it is the one that costs money. A push notification when any property’s clicks or impressions move outside their normal range, with the page that explains most of it attached, means the dormant site gets watched exactly as closely as the big one, without you doing anything. How to get notified when traffic drops covers the options, including the ones that are not us.

A weekly rhythm

What a portfolio on a phone looks like in practice, with Pro:

Monday morning, the digest lands: every property, the week against the previous one, which queries entered or left the top ten, which alerts fired, and the biggest mover across the portfolio. You know which two clients need a sentence in their update before you open a laptop.

Wednesday at 11:40, a push says one property’s clicks are down 34 percent and one page explains 56 percent of it. You open the change investigation on the walk back from lunch and see the page, its before and after, and the one URL that moved the other way. You email the client first.

Thursday, before the call, a branded PDF from the phone with their name, your logo and your colour. Reports a client can read goes into what should be in it.

Priced per person, not per property

Pro costs $4.99 a month or $14.99 a year and covers every property you have access to, three or thirty. This is the one thing we will not change. Every competing app we have looked at either paywalls the property count or hides most of the data until you pay, which makes the free tier useless for exactly the person this is built for. We charge for depth, history, alerts, exports, because depth is what costs us money to provide; the number of sites is never the thing you pay for. The comparison pages have each app’s pricing from its own listing.

What is not there yet

Being clear now is cheaper than disappointing you later. There are no read-only client logins; sharing a live dashboard with a client is on the roadmap, and today you send an export. There are no team seats; one person, one subscription, and three people at an agency are three subscriptions. There is no GA4 overlay, and no Bing Webmaster Tools yet, though Bing is next. And there is no rank tracking, which is a permanent non-goal rather than a gap: why QueryWatch is not a rank tracker explains.