Split your queries
Search Console → Performance → Export → Download CSV, then use Queries.csv. The file is read in your browser and never uploaded.
A query is branded when it contains your company or product name, including spellings without spaces or with typos. Split them, then judge SEO by non-branded clicks and non-branded CTR. In Search Console itself, use a Query filter with "Custom (regex)": Matches regex for branded, Doesn't match regex for non-branded.
Why the blended numbers mislead
Branded and non-branded results behave so differently that an average of the two describes neither. A branded query usually puts you at position 1 with a very high CTR, because the searcher wanted you. A non-branded query is a contest with other sites.
| Example month | Clicks | Impressions | CTR |
|---|---|---|---|
| Branded | 2,400 | 4,000 | 60.0% |
| Non-branded | 1,100 | 90,000 | 1.2% |
| Blended | 3,500 | 94,000 | 3.7% |
The figures are an example. Notice what happens if next month a newsletter mention doubles branded clicks and non-branded clicks fall by a fifth: total clicks still rise, and the report looks like an SEO win.
Building a good brand list
- Company and product names, including old names after a rebrand.
- Joined and split spellings ("acmeanalytics", "acme analytics"). The tool already ignores spaces and hyphens, so one of the two is enough here; in Search Console the generated regex allows an optional space or hyphen.
- Common misspellings you can see in your own query list. Search the export for the first three letters of your name.
- Navigational product terms such as "acme login" or "acme pricing". They contain the name, so they match automatically.
- Not generic words that happen to be in your name. A company called "Bright" should not count every query with "bright" in it as branded; use "bright crm" instead.
Reading the trend month to month
| Branded clicks | Non-branded clicks | Likely story |
|---|---|---|
| Flat | Rising | Pages are winning new searches: the result SEO work should produce |
| Rising | Flat or falling | Awareness grew (ads, press, launches) while organic reach stalled |
| Falling | Falling | Check the site first: indexing, a migration, a penalty, or seasonality |
The same split inside Search Console
Search Console's Performance report accepts RE2 regular expressions in Query filters. Google's help page says they match partially by default and ignore case unless you begin with (?-i), so a short pattern is enough:
(acme|acme[ -]?analytics|akme)
# Branded: Query → Custom (regex) → Matches regex
# Non-branded: Query → Custom (regex) → Doesn't match regex
Save the comparison as a habit: every monthly report shows non-branded clicks and non-branded CTR on their own line. To see which non-branded results deserve a better title first, run the same export through the low-CTR finder.
For agencies, this is the line clients most often misread. A client running a big campaign will see total clicks jump; the non-branded line shows what your SEO work did. See how SiteTiller reports per client.
Questions people ask
Why separate branded and non-branded queries?
Branded searches mostly reflect awareness from ads, word of mouth and press. Non-branded searches show whether your pages win new people. Mixing them hides both: a TV mention can lift total clicks while non-branded traffic falls.
Is the Search Console regex case-sensitive?
No. Google's help page says custom regex filters in the Performance report use RE2 syntax, match partially by default and are not case-sensitive unless you start the pattern with (?-i).
Why don't the totals match Search Console's chart?
The export lists the queries Google shows in the table. Very rare queries are left out of the table for privacy, so a query-level split never adds up to the site total.
What about misspellings of my brand?
The tool ignores spaces, hyphens, dots and apostrophes, so "acme analytics", "acme-analytics" and "acmeanalytics" all match. Add common misspellings as extra terms separated by commas.
Related
Sources
- Search Console Help: Performance report, advanced filtering and comparison (regex), accessed 2026-11-12.
- Search Console Help: Performance report (Search results), accessed 2026-11-12.
- RE2 syntax reference, accessed 2026-11-12.