Intro

Catch messy branded demand where users misspell or compress the brand name in Search Console queries.

Use this regex to isolate misspelt branded demand so it does not disappear inside broader branded reporting.

The Regex

(spicemetrics|spice metrics|spicymetric|spicimetrix)

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 common misspelt versions of the brand.
  • Helps quantify how much branded demand arrives with inconsistent spelling.
  • Supports cleaner non-brand filters because you can exclude typo variants too.

What it does not match

  • spicy metrics pricing - This is the correct brand spelling, not a typo variant.
  • seo metrics dashboard - It overlaps semantically with metrics language but does not contain the brand typo variants.

Edge Cases

  • Typo patterns can overlap with unrelated words if you make them too short. Keep variants specific.
  • A typo-only segment should complement, not replace, your core branded segment.

Example Matches Table

Query Match Why
spicemetrics pricing Match Contains a common joined-word typo for the brand.
spice metrics login Match Contains the spaced typo variant included in the grouped options.
spicymetric reviews Match Contains the singular typo included in the group.
spicy metrics pricing No This is the correct brand spelling, not a typo variant.
seo metrics dashboard No It overlaps semantically with metrics language but does not contain the brand typo variants.

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 typo-driven brand demand separately.
  • Improve non-brand exclusion by covering misspelt brand terms.
  • Decide whether typo variants need defensive paid or organic treatment.

Pro Tips

  • Review Search Console exports regularly because misspellings often change over time.
  • Use this regex in a negative query filter when you want a cleaner non-brand segment.
  • Keep typo variants separate from core brand terms if you want to report on brand hygiene.

Variations

Add one more typo

(spicemetrics|spice metrics|spicymetric|spicimetrix|spicemetric)

Broadens the typo group so you catch another singular variant.

Exact typo matches only

^(spicemetrics|spice metrics|spicymetric|spicimetrix)$

Use this when you only want the typo terms themselves, not typo terms with trailing modifiers.

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