Intro
Track SaaS comparison searches in GSC so you can isolate evaluation demand around alternatives, versus queries, and side-by-side comparisons.
Use this regex to group the main SaaS evaluation modifiers that show up when buyers compare tools.
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.
?
The question mark usually makes the previous character or group optional. That is handy when a query modifier appears inconsistently.
\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 the main comparison and alternatives modifiers used in SaaS evaluation.
- Surfaces commercial research demand rather than direct purchase intent.
- Helps benchmark comparison-page visibility.
What it does not match
- ga4 dashboard reviews - Reviews only matches if you use the variation.
- ga4 dashboard pricing - Pricing is a separate late-stage modifier.
Edge Cases
- Reviews can attract a different SERP shape from versus queries, so keep them separate if you need tighter analysis.
- Alternatives often overlaps with competitor-intent recipes, so compare the outputs rather than assuming they are identical.
Example Matches Table
| Query | Match | Why |
|---|---|---|
| spicy metrics vs looker studio | Match | Vs is directly included. |
| ga4 dashboard alternatives | Match | Alternatives is part of the grouped comparison set. |
| ga4 dashboard reviews | No | Reviews only matches if you use the variation. |
| ga4 dashboard pricing | No | Pricing is a separate late-stage modifier. |
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 comparison demand for SaaS products.
- Audit whether comparison pages rank for evaluation terms.
- Compare comparison intent against pricing and purchase intent.
Pro Tips
- This recipe is reusable beyond SaaS, but it is particularly valuable where comparison content drives sign-ups.
- Use competitor page filters or branded terms to see which brands dominate the query family.
- Review page overlap because comparison queries often create cannibalisation between templates, blogs, and landing pages.
- Add reviews only if you want a broader evaluation segment.
Variations
Include review-led terms
Broadens the evaluation set with another common SaaS modifier.
Related Regex Recipes
Regex for Comparison Intent
Use this regex to focus on comparison intent in GSC when you want a tighter segment built around direct option-versus-option evaluation.
Regex for Competitor Comparisons (vs)
Use this regex to isolate explicit comparison searches in GSC when users are evaluating your brand against a named competitor.
CTA
Regex is powerful in GSC, but manual filtering still leaves you exporting, comparing, and rebuilding the same views. Spicy Metrics turns those segments into reporting your team can reuse.
Turn regex into repeatable reporting