Intro
Build a repeatable low-CTR opportunity workflow in GSC so you can isolate commercial and shortlist queries, then sort by impressions and CTR to find pages that should earn more clicks.
Use this regex as the first filter in a low-CTR workflow: pull a commercially important query set, then review high-impression rows with weak click-through rate.
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 shortlist and commercial modifiers where CTR often matters most.
- Creates a useful candidate set for low-CTR analysis.
- Helps you focus optimisation work on queries with clear commercial value.
What it does not match
- how to use search console regex - This is informational rather than commercial.
- seo reporting template free - No grouped shortlist or commercial modifier appears.
Edge Cases
- This regex only narrows the query family; CTR diagnosis still requires metric review inside GSC.
- If the set becomes too broad, split it by modifier family and compare the CTR patterns separately.
Example Matches Table
| Query | Match | Why |
|---|---|---|
| best seo dashboards | Match | Best is one of the grouped shortlist modifiers. |
| ga4 reporting tool pricing | Match | Pricing is included in the low-CTR candidate set. |
| how to use search console regex | No | This is informational rather than commercial. |
| seo reporting template free | No | No grouped shortlist or commercial modifier appears. |
How to Use This in Google Search Console
- Open Performance and go to Search results.
- Add a Query filter with Custom (regex) and paste the regex.
- Set a meaningful date range and compare against the previous period if needed.
- Sort the filtered queries by impressions, then review rows with weak CTR.
- Export the data and prioritise pages that have strong impressions but underperforming click-through rate.
When to Use This
- Pull a high-value query set before reviewing CTR.
- Focus optimisation on commercially meaningful impressions.
- Create a repeatable workflow for title-tag and snippet improvement.
Pro Tips
- Regex does not identify low CTR on its own; it narrows the candidate set before you sort and analyse the metrics.
- Use date comparisons so you can spot improving versus persistently weak CTR patterns.
- Review average position before acting, because very low CTR at poor rankings can be a ranking problem rather than a snippet problem.
- Export the filtered set and annotate likely causes such as poor titles, wrong page type, or SERP feature pressure.
Variations
Include alternatives demand
Adds another valuable commercial modifier to the CTR-review workflow.
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 High Impressions, Low Click Queries
Use this regex with an impressions sort and low-click review in GSC to isolate recurring high-visibility patterns that underperform on clicks.
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