Intro

Strip branded demand out of GSC so you can analyse generic search visibility without brand noise.

Use this regex with the Doesn't match regex query filter in GSC to exclude brand terms and leave non-brand demand behind.

The Regex

(spicy metrics|spicymetrics|spicemetrics)

How This Regex Works (Explained Simply)

()

Parentheses group terms together so GSC treats them as one unit. That is what lets one regex cover several query variants in a single filter.

|

The pipe means OR. GSC will match any term on either side of the pipe, which is useful for variants, modifiers, or alternative phrases.

GSC regex is case-insensitive by default, so capital letters do not need separate variants. GSC also uses partial matching by default, so the regex can match part of a longer query unless you anchor it with ^ or $.

What This Regex Does

  • Matches branded queries that should be excluded from a non-brand view.
  • Lets you reuse one brand filter instead of rebuilding a manual exclusion every time.
  • Supports cleaner non-brand trend analysis, landing-page audits, and opportunity reporting.

What it does not match

  • seo dashboard for agencies - No brand term matches, so the query stays in your non-brand view.
  • how to segment search console data - This is generic informational demand and will remain after the exclusion.

Edge Cases

  • The regex itself still matches branded terms. The non-brand workflow depends on using the negative regex filter in GSC.
  • If your brand overlaps with generic words, anchor the pattern or refine variants before excluding it.

Example Matches Table

Query Match Why
spicy metrics Match The regex matches it, so GSC excludes it when you use Doesn't match regex.
spicymetrics login Match Still matched as branded demand, so it is removed from the non-brand set.
seo dashboard for agencies No No brand term matches, so the query stays in your non-brand view.
how to segment search console data No This is generic informational demand and will remain after the exclusion.

How to Use This in Google Search Console

  1. Open Performance and go to Search results.
  2. Click Add filter and choose Query.
  3. Select Doesn't match regex.
  4. Paste the regex and click Apply.

When to Use This

  • Report non-brand growth without branded demand inflating the story.
  • Benchmark generic CTR and ranking movement more honestly.
  • Find non-brand landing pages that are driving discovery demand.

Pro Tips

  • This is a negative-filter workflow, so use Doesn't match regex rather than Matches regex.
  • Keep the same brand pattern in one shared document so teams exclude demand consistently.
  • Compare branded and non-brand clicks side by side over the same date range before drawing conclusions.
  • Add common misspellings to the pattern if brand leakage still appears in the non-brand set.

Variations

Broaden the exclusion

(spicy metrics|spicymetrics|spicemetrics|spicy metric)

Adds one more typo so fewer branded queries leak into the non-brand view.

Exclude exact brand only

^(spicy metrics|spicymetrics|spicemetrics)$

Use this when you want to keep branded modifier queries visible for a separate workflow.

Related Regex Recipes

CTA

Regex is only the first step. The real bottleneck is turning manual filters into a repeatable workflow your team actually uses. Spicy Metrics helps you move from ad hoc filtering to operational SEO workflows.

Move beyond manual regex work