Google Search Console Branded vs. Non-Branded Queries With Regex

Rakibul SumonRakibul Sumon
Published: Nov 18, 2026
Google Search Console Branded vs. Non-Branded Queries With Regex

TL;DR Summary

Copy a Search Console regex for branded queries, test common misspellings, and compare branded and non-branded clicks without misreading hidden queries.

I separate branded search when I want to know whether readers find a site by looking up a problem or by typing a name they already know. Brand demand can dominate clicks and hide how little search visibility the site has for its broader topics.

If Google's branded queries filter is available for your property, start there. Use a custom regex when you want an explicit definition you can inspect and reuse.

Build a pattern from actual brand variants

In Performance → Search results, add a Query → Custom (regex) filter. Choose the matching option. Here is the pattern I would start with for this site.

rakibul[ .-]*sumon|rakibul[ .-]+islam[ .-]+sumon

The first branch captures the compact spelling and versions separated by spaces, periods, or hyphens. The second handles the longer name. Search Console uses RE2. Default matching is partial and case-insensitive, so the first branch also matches within a domain query. Google's filtering instructions explain the matching rules.

  • Rakibul Sumon or rakibulsumon.com blog should match.
  • rakibul-islam-sumon seo should match.
  • rakibul is ambiguous and deserves its own review.
  • saas trial tracking should remain non-branded.

Read the matched rows, then run the same pattern with Doesn't match regex. Keep a note of the pattern and date. If you change the definition after finding a misspelling, you can distinguish a reporting change from a traffic change.

Growth mechanics, zero fluff.

Join SaaS founders and operators getting weekly notes and tear-downs on organic acquisition and churn reduction.

Decide how to handle a brand plus a task

“Rakibul Sumon GA4 tracking” contains both. I count it as branded to keep the weekly view interpretable. For a product campaign, a separate brand-plus-feature filter can answer a narrower question. Record explicit rules for domain spelling and product nicknames if they overlap with common words.

Leave room for hidden queries

Search Console's Queries table omits anonymized queries. Filtering by query also changes which data the chart can show. I label the comparison reported branded vs. reported non-branded and keep the unfiltered total separately. Subtracting branded impressions from the unfiltered total can accidentally classify hidden queries as non-branded.

After the split, pick a relevant non-branded query and inspect its landing page. My Search Console workflow for SaaS SEO explains where Performance and URL Inspection fit.

Rakibul Sumon

Written by · SaaS Growth Marketer

Rakibul Sumon

SaaS growth marketer who learns deeply, experiments openly, and shares results publicly. Focused on content-led SEO, brand positioning, and building growth systems that compound over time.

Learning In Public

SaaS growth insights,_

No hype, no recycled advice - just honest experiments, frameworks, and lessons from the trenches, delivered when there's something worth sharing.

No spam, ever. Unsubscribe anytime.