Intro

Build a reusable low-CTR query slice in GSC so you can review weak click-through performance by intent pattern instead of scanning the full report manually.

Use this regex as a practical low-CTR triage segment in GSC after sorting by CTR and filtering for weak-performing query groups.

The Regex

\b(what is|how to|best|top|vs|review|price|pricing)\b

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 query modifiers that often deserve separate CTR review.
  • Creates a triage segment you can combine with a CTR sort or export workflow.
  • Helps you review under-clicked intent patterns rather than isolated keywords.

What it does not match

  • seo dashboard free - Free is not included in the base segment.
  • brand login - No grouped triage modifier appears.

Edge Cases

  • Regex alone cannot identify low CTR, so use it with metric sorting or exports.
  • This segment is meant to focus review, not replace threshold-based analysis.

Example Matches Table

Query Match Why
what is search intent Match Contains a grouped modifier useful for CTR triage.
best seo dashboard Match Contains best, which is included in the segment.
seo dashboard free No Free is not included in the base segment.
brand login No No grouped triage modifier appears.

How to Use This in Google Search Console

  1. Open Performance and go to Search results.
  2. Sort queries by CTR ascending after setting a sensible impressions floor.
  3. Click Add filter and choose Query.
  4. Select Custom (regex), paste the regex, and click Apply.

When to Use This

  • Review which query types underperform most on CTR.
  • Split low-CTR analysis by intent pattern instead of page alone.
  • Prioritise title and snippet updates on recurring weak segments.

Pro Tips

  • This recipe is a workflow aid, not a complete low-CTR detector by itself.
  • Always set an impressions threshold before judging CTR in GSC.
  • Compare date ranges after snippet changes to see whether CTR improves for the same segment.
  • Export the filtered set to cluster recurring SERP-messaging problems.

Variations

Include guide-led queries

\b(what is|how to|best|top|vs|review|price|pricing|guide)\b

Adds another common modifier for broader CTR triage coverage.

Related Regex Recipes

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