Intro
Segment recurring query patterns when reviewing period-over-period declines in GSC so trend analysis is faster and more structured.
Use this regex to review declining query groups in GSC after comparing date ranges and sorting for the biggest negative changes.
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.
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 one practical mix of branded, shortlist, informational, and commercial modifiers.
- Creates a reusable slice for comparing old and new query performance.
- Helps you spot whether one intent family is falling faster than others.
What it does not match
- search intent guide - Guide only matches in the broader variation.
- seo dashboard free - No grouped decline-review modifier appears.
Edge Cases
- Decline detection depends on date-range comparisons, not the regex itself.
- Use smaller subsegments if this broad comparison slice feels too mixed.
Example Matches Table
| Query | Match | Why |
|---|---|---|
| spicy metrics pricing | Match | Contains a real brand example and a commercial modifier from the grouped set. |
| what is search intent | Match | Contains what is, a common informational pattern to compare over time. |
| search intent guide | No | Guide only matches in the broader variation. |
| seo dashboard free | No | No grouped decline-review modifier appears. |
How to Use This in Google Search Console
- Open Performance and compare two date ranges.
- Review the Queries tab and sort by click or impression decline.
- Add a Query filter with Custom (regex).
- Paste the regex and click Apply.
When to Use This
- Compare which intent groups are losing traffic fastest.
- Spot whether declines are concentrated in branded examples, informational modifiers, or commercial demand.
- Build repeatable decline-review workflows across properties.
Pro Tips
- Regex does not detect decline itself, so always use date comparisons first.
- Review both clicks and impressions because different decline types imply different causes.
- Split the segment further if one modifier family dominates the decline.
- Use exports to compare the same regex group across multiple properties.
Variations
Include guide-led demand
Adds one more content-style modifier for broader decline reviews.
Related Regex Recipes
Regex for Underperforming Queries
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.
Regex for Emerging Trends
Use this regex to isolate trend-sensitive queries in GSC when you want a fast view of emerging demand patterns and freshness-led search behaviour.
CTA
Manual regex checks in GSC are useful, but they do not scale well across properties, date ranges, and recurring reporting. Spicy Metrics turns repeat regex workflows into faster monitoring and clearer action.
See how Spicy Metrics scales this