Intro
Create a repeatable keyword-clustering workflow in GSC by grouping close intent modifiers, exporting the query set, and then clustering by topic or landing page.
Use this regex to pull one coherent evaluation-intent family from GSC, then cluster the exported queries into subtopics or page groups.
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 a tight family of evaluation and comparison modifiers.
- Creates a high-signal source set for clustering related query variants.
- Helps reduce manual query bucketing work.
What it does not match
- best ga4 dashboards - Best only matches if you use the broader variation.
- ga4 dashboard pricing - Pricing is a different commercial family.
Edge Cases
- The broader the source regex, the noisier the downstream clusters become.
- If clustering output feels messy, split the query families before exporting.
Example Matches Table
| Query | Match | Why |
|---|---|---|
| ga4 alternatives | Match | Alternatives is included in the evaluation set. |
| search console vs looker studio | Match | Vs is one of the grouped clustering modifiers. |
| best ga4 dashboards | No | Best only matches if you use the broader variation. |
| ga4 dashboard pricing | No | Pricing is a different commercial family. |
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.
- Export the filtered query set.
- Cluster the queries by repeated entities, modifiers, or landing pages.
- Use the clusters to refine page targeting, internal linking, or content consolidation.
When to Use This
- Group related comparison-style queries into manageable clusters.
- Spot subtopics that deserve dedicated pages versus consolidation.
- Reduce repeated manual clustering work in exports.
Pro Tips
- Regex is just the first pass: real clustering still happens after export by topic, entity, or landing page.
- Start with one intent family at a time so the clusters stay coherent.
- Review page overlap inside each cluster to spot consolidation or cannibalisation opportunities.
- Broaden to best and top only if you deliberately want to merge shortlist and comparison demand.
Variations
Include shortlist modifiers
Broadens the clustering source set to another close commercial-intent family.
Related Regex Recipes
Regex for Synonyms
Use this regex to capture several close synonym patterns around comparison intent so you can report on them as one group in Search Console.
Regex for Comparison Intent
Use this regex to focus on comparison intent in GSC when you want a tighter segment built around direct option-versus-option evaluation.
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