Intro
Isolate support-led branded demand in GSC so you can see how much existing demand is looking for help rather than new evaluation.
Use this regex to isolate branded support intent and keep it separate from pricing, demo, or login queries.
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 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 support and documentation modifiers.
- Shows how much branded demand is post-sign-up or post-activation help intent.
- Helps support-led search demand stop distorting broader brand analysis.
What it does not match
- spicy metrics pricing - Commercial branded intent does not match the support modifier group.
- help with seo dashboard - Support language appears, but the brand is missing.
Edge Cases
- Support demand can overlap with navigational demand if users search for the docs or help centre directly.
- If support modifiers often come before the brand, create a reverse-order variation.
Example Matches Table
| Query | Match | Why |
|---|---|---|
| spicy metrics support | Match | Starts with the brand and a grouped support term. |
| spicymetrics documentation | Match | Contains the joined brand plus a documentation modifier. |
| spicy metrics pricing | No | Commercial branded intent does not match the support modifier group. |
| help with seo dashboard | No | Support language appears, but the brand is missing. |
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
- Measure support-led branded demand separately.
- Check whether support content is gaining or losing visibility.
- Keep support intent out of evaluation or sales-led brand reporting.
Pro Tips
- Compare support demand with login demand to understand account-access friction.
- Use this segment with a page filter to find which support URLs actually rank.
- If users search for setup, migration, or troubleshooting often, add those modifiers explicitly.
Variations
Add troubleshooting phrasing
Adds another help-focused modifier for more operational support demand.
Core support terms only
Useful when you want a tighter branded help segment.
Related Regex Recipes
Regex for Brand + Login Queries
Use this regex to isolate branded account-access intent and keep it separate from support or pricing demand.
Regex for Branded Intent Queries
Use this regex to isolate branded intent queries where the trailing modifier reveals what the user actually wants from the brand.
Regex for Navigational Queries
Use this regex to surface branded navigational demand in GSC when users are trying to reach the site, dashboard, or app directly.
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