Intro
Group branded searches that reveal what users want from the brand once they already know it.
Use this regex to isolate branded intent queries where the trailing modifier reveals what the user actually wants from the brand.
The Regex
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.
.*
Dot-star means any characters can appear here. In GSC it is commonly used when you want to allow extra words before or after a core phrase.
^
The caret anchors the regex to the start of the query. Use it when you want to match terms only if they appear first in GSC.
?
The question mark usually makes the previous character or group optional. That is handy when a query modifier appears inconsistently.
+
The plus sign means one or more of the previous token. It helps when a term can repeat but still needs to be present at least once.
\s
Backslash-s matches a whitespace character. It is useful when spacing can vary between query formats.
\b
Backslash-b marks a word boundary. It helps stop short terms from matching inside longer words in GSC queries.
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 searches with high-signal modifiers.
- Turns a messy branded bucket into intent-led reporting.
- Helps teams see whether brand demand skews toward product evaluation, account access, or support.
What it does not match
- spicy metrics - Pure branded demand without an intent modifier does not match.
- best seo dashboard - The modifier suggests commercial intent, but the brand is not present.
Edge Cases
- This segment is deliberately broad. Use the child recipes when you want one modifier theme only.
- If your branded modifiers often appear before the brand, add a second branch to capture that order.
Example Matches Table
| Query | Match | Why |
|---|---|---|
| spicy metrics demo | Match | Starts with the brand and a grouped intent modifier. |
| spicymetrics pricing | Match | Contains the joined brand plus a grouped pricing modifier. |
| spicemetrics support | Match | Contains the typo variant and a grouped support modifier. |
| spicy metrics | No | Pure branded demand without an intent modifier does not match. |
| best seo dashboard | No | The modifier suggests commercial intent, but the brand is not present. |
How to Use This in Google Search Console
- Open Performance and go to Search results.
- Click Add filter and choose Query.
- Select Custom (regex).
- Paste the regex and click Apply.
When to Use This
- Break branded demand into practical intent buckets.
- Spot which branded modifiers need stronger landing pages.
- Compare branded evaluation, support, and access demand over time.
Pro Tips
- This is a useful umbrella segment, but keep pricing, login, and support in their own child segments when you need detail.
- Expand the modifier group carefully so the segment stays purposeful.
- Review landing pages for each modifier cluster to check whether intent alignment is clear.
Variations
Add comparison as a brand intent
Useful when comparison-style branded demand belongs in the same intent bucket.
Evaluation modifiers only
Tightens the segment around evaluation rather than account access or support.
Related Regex Recipes
Regex for Brand + Modifier Queries
Use this regex to isolate branded queries with clear modifiers so you can understand what existing brand demand is actually trying to do.
Regex for Brand + Pricing Queries
Use this regex to isolate branded pricing demand in GSC when users already know the brand and want commercial information.
Regex for Brand + Login Queries
Use this regex to isolate branded account-access intent and keep it separate from support or pricing demand.
CTA
Building query segments manually in GSC works for one-off checks, but it breaks down across multiple sites and stakeholders. Spicy Metrics keeps those segments organised and easy to monitor.
Scale segmentation in Spicy Metrics