Intro

Track branded pricing intent in GSC so you can analyse lower-funnel brand demand separately from general brand awareness.

Use this regex to isolate branded pricing demand in GSC when users already know the brand and want commercial information.

The Regex

^(spicy metrics|spicymetrics|spicemetrics)\s+(pricing|price|cost|plans?)\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 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 commercial modifiers such as pricing, price, cost, and plans.
  • Separates lower-funnel branded demand from generic brand and support demand.
  • Helps SEO teams benchmark how visible pricing-led demand really is.

What it does not match

  • spicy metrics login - This is account-access intent, not pricing intent.
  • seo dashboard pricing - Commercial demand is present, but the brand is missing.

Edge Cases

  • Pricing intent can overlap with support queries if users search for billing or plan changes. Add those terms only if you want them.
  • If your audience uses quote or demo instead of pricing, keep those in a separate branded intent segment.

Example Matches Table

Query Match Why
spicy metrics pricing Match Starts with the brand and a grouped pricing modifier.
spicymetrics cost Match Uses the joined brand plus a commercial cost modifier.
spicy metrics login No This is account-access intent, not pricing intent.
seo dashboard pricing No Commercial demand is present, but the brand is missing.

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 lower-funnel branded demand cleanly.
  • Track whether pricing pages or pricing modules gain visibility over time.
  • Compare branded pricing demand against generic commercial demand.

Pro Tips

  • Use this segment alongside demo and trial modifiers to see how branded evaluation demand splits out.
  • Pair the query regex with a page filter to find which URLs rank for pricing-led branded searches.
  • If your pricing language includes plans, seats, or subscription, add them to the grouped modifiers.

Variations

Add subscription phrasing

^(spicy metrics|spicymetrics|spicemetrics)\s+(pricing|price|cost|plans?|subscription)\b.*

Adds another common commercial modifier for SaaS-style pricing searches.

Strict commercial terms only

^(spicy metrics|spicymetrics|spicemetrics)\s+(pricing|price|cost)\b.*

Use this when you want the tightest pricing segment possible.

Related Regex Recipes

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