Intro
Create a repeatable intent-segmentation workflow in GSC by grouping informational, commercial, and purchase modifiers into separate filtered views.
Use this regex as a starter set when building an intent workflow in GSC, then split the output into clearer informational, commercial, and purchase views.
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 a mixed set of modifiers that span multiple stages of search intent.
- Creates a starter source set for intent workflow design.
- Helps standardise how teams segment queries inside GSC.
What it does not match
- search console overview - No grouped intent modifier appears.
- compare seo dashboards - Compare only matches if you use the variation.
Edge Cases
- One regex cannot perfectly segment intent on its own, so use this as a workflow seed rather than a final taxonomy.
- Mixed-intent modifiers will always need human review when the stakes are high.
Example Matches Table
| Query | Match | Why |
|---|---|---|
| what is search console regex | Match | What is is one of the grouped informational modifiers. |
| buy seo dashboard trial | Match | Buy and trial are included in the mixed intent set. |
| search console overview | No | No grouped intent modifier appears. |
| compare seo dashboards | No | Compare only matches if you use the variation. |
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.
- Use the result as a baseline source set, then create narrower regex views for informational, commercial, and purchase intent.
- Compare performance across the intent views using the same date range.
- Document the intent rules so the workflow stays consistent over time.
When to Use This
- Standardise query segmentation by intent.
- Build repeatable informational, commercial, and purchase reporting views.
- Compare where SEO growth is happening across the funnel.
Pro Tips
- This starter regex is intentionally broad; the workflow value comes from splitting the stages into separate saved filters afterwards.
- Do not treat the mixed set itself as one final report unless you only need a rough intent-screening view.
- Keep the downstream intent definitions stable so trend reporting remains comparable.
- Add compare if your commercial stage relies heavily on explicit evaluation language.
Variations
Include comparison intent
Adds another common mid-funnel modifier to the starter intent workflow.
Related Regex Recipes
Regex for Informational Intent
Use this regex to isolate informational intent terms in GSC and measure awareness-stage SEO performance with less noise.
Regex for Transactional Intent
Use this regex to isolate transactional intent in GSC when searchers are signalling they want to take action rather than keep researching.
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