Intro

Track abbreviated branded demand when users shorten the brand in GSC queries.

Use this regex to isolate abbreviated brand mentions that still signal brand familiarity but would be missed by a full-name brand filter.

The Regex

^(sm|smetrics)\s+(dashboard|seo|pricing|login|support)\b.*

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 short brand abbreviations when they appear before a branded modifier.
  • Keeps the segment tighter than a loose SM regex, which would be too broad on its own.
  • Helps you see whether experienced users search in shorthand.

What it does not match

  • social media pricing - SM can be ambiguous, but the rest of the phrase does not match the approved abbreviation pattern.
  • spicy metrics pricing - This is a full brand query, not an abbreviation query.

Edge Cases

  • Abbreviations are inherently ambiguous, so keep at least one trailing brand-like modifier in the pattern.
  • If your audience never uses shorthand, this segment may stay small even when brand demand is healthy.

Example Matches Table

Query Match Why
sm pricing Match Starts with the short abbreviation and then a tracked modifier.
smetrics login Match Starts with the longer shorthand included in the group.
social media pricing No SM can be ambiguous, but the rest of the phrase does not match the approved abbreviation pattern.
spicy metrics pricing No This is a full brand query, not an abbreviation query.

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 Custom (regex).
  4. Paste the regex and click Apply.

When to Use This

  • Measure shorthand branded demand from existing users.
  • Keep abbreviated searches out of your non-brand reporting.
  • Check whether support and login demand appears more often in shorthand.

Pro Tips

  • Do not use a loose SM regex on its own. It is too broad for most datasets.
  • Pair abbreviation tracking with support and login modifiers to keep the pattern precise.
  • Review matched queries manually at first to make sure the abbreviation is not colliding with another meaning.

Variations

Add a looser shorthand

^(sm|smetrics|spicy m)\s+(dashboard|seo|pricing|login|support)\b.*

Adds one more shorthand phrase while still requiring a clear branded modifier.

Broader abbreviation scan

^(sm|smetrics)\b.*

Useful for discovery work, but broad enough that you should validate the export manually.

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