Intro
Isolate comparison-led searches in GSC so you can report on one of the clearest evaluation signals separately from broader research demand.
Use this regex to focus on comparison intent in GSC when you want a tighter segment built around direct option-versus-option evaluation.
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.
\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 common comparison markers such as vs and compare.
- Creates a narrower evaluation segment than the broader research intent view.
- Works well for competitor and alternatives reporting.
What it does not match
- best seo dashboard - Commercial evaluation is present, but this is not an explicit comparison query.
- how to build an seo dashboard - Instructional intent is present, not comparison intent.
Edge Cases
- Vs is concise and useful, but it can still be noisy if your dataset contains abbreviations or shorthand.
- Alternative phrasing broadens the segment beyond strict comparisons, so keep it as a variation if you need tighter reporting.
Example Matches Table
| Query | Match | Why |
|---|---|---|
| spicy metrics vs looker studio | Match | Contains vs, which directly signals comparison intent. |
| seo dashboard comparison | Match | Contains comparison as a standalone term. |
| best seo dashboard | No | Commercial evaluation is present, but this is not an explicit comparison query. |
| how to build an seo dashboard | No | Instructional intent is present, not comparison intent. |
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
- Track visibility for head-to-head evaluation queries.
- Measure how comparison pages perform against alternatives content.
- Find topics where direct competitor pages may be needed.
Pro Tips
- Because vs is short, keep the word boundary so you do not match stray strings.
- Cross-reference this segment with Cluster 1 competitor recipes for brand-aware comparisons.
- Use date comparisons after publishing alternatives pages to measure uptake.
- Comparison CTR often varies by SERP layout, so review snippets and titles alongside rankings.
Variations
Include alternative phrasing
Broadens the segment to include another common direct-evaluation modifier.
Related Regex Recipes
Regex for Research Intent
Use this regex to isolate research intent in GSC when searchers are gathering options and weighing routes before they move closer to conversion.
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
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