Intro
Create a broad review segment for queries that underperform against expectations so you can triage weak patterns more systematically in GSC.
Use this regex as a broad underperformance triage segment when you need to review weak query groups by intent instead of one query at a time.
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 intent modifiers that are useful for general underperformance reviews.
- Creates a practical catch-all segment for triage workflows.
- Helps you decide which modifier families need deeper analysis.
What it does not match
- office chair guide - Guide only matches in the broader variation.
- office chair dimensions - No grouped modifier from the base segment appears.
Edge Cases
- Underperformance is contextual, so the regex only helps organise the review.
- Use narrower recipes after the first pass if the query set is too broad.
Example Matches Table
| Query | Match | Why |
|---|---|---|
| review of seo dashboard | Match | Contains review, which is useful for underperformance triage. |
| buy office chair online | Match | Contains buy, a high-intent modifier worth separate review. |
| office chair guide | No | Guide only matches in the broader variation. |
| office chair dimensions | No | No grouped modifier from the base segment appears. |
How to Use This in Google Search Console
- Open Performance and identify queries with weak CTR, clicks, or position for their context.
- Add a Query filter with Custom (regex).
- Paste the regex and click Apply.
- Sort the filtered set by the metric you want to triage first.
When to Use This
- Create one broad review segment before splitting into narrower workflows.
- Spot recurring weak-performing modifier families quickly.
- Support triage across CTR, position, and click-performance reviews.
Pro Tips
- This is intentionally broad, so use it as a first-pass triage layer rather than a final diagnosis.
- Pair it with page filters and date comparisons for more reliable conclusions.
- Once you find the weak family, switch to a tighter recipe such as pricing or review intent.
- Keep expectations realistic because underperformance always depends on context.
Variations
Include guide modifiers
Adds another common intent family for broader underperformance reviews.
Related Regex Recipes
Regex for Low CTR Queries
Use this regex as a practical low-CTR triage segment in GSC after sorting by CTR and filtering for weak-performing query groups.
Regex for Declining Queries
Use this regex to review declining query groups in GSC after comparing date ranges and sorting for the biggest negative changes.
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