Intro
Find purchase-stage searches in GSC so you can isolate the strongest conversion-ready demand in your query set.
Use this regex to capture purchase-stage queries in GSC when users are close to converting and are using clear action-ready language.
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 strong bottom-funnel modifiers associated with purchase or sign-up intent.
- Creates a narrower high-intent segment than the broader transactional view.
- Helps teams report on the search demand closest to revenue.
What it does not match
- best seo reporting software - This is still consideration-stage evaluation.
- gsc dashboard pricing - Pricing is late-stage, but it is not as explicit as a purchase action.
Edge Cases
- If your market uses request demo rather than buy language, add those terms separately.
- This is intentionally narrow, so broader commercial or pricing queries stay out of the segment.
Example Matches Table
| Query | Match | Why |
|---|---|---|
| buy seo reporting software | Match | Buy is a direct purchase-stage modifier. |
| start trial for gsc dashboard | Match | Start trial shows clear sign-up intent. |
| best seo reporting software | No | This is still consideration-stage evaluation. |
| gsc dashboard pricing | No | Pricing is late-stage, but it is not as explicit as a purchase action. |
How to Use This in Google Search Console
- Open Performance and go to Search results.
- Click Add filter and choose Query.
- Select Custom (regex).
- Paste the regex and click Apply.
When to Use This
- Track the query segment closest to revenue or sign-up.
- Measure whether product, signup, and checkout pages capture bottom-funnel traffic.
- Compare purchase-stage search demand with broader transactional demand.
Pro Tips
- Keep this narrower than your transactional segment so you can separate action-ready demand from general conversion interest.
- Subscribe can matter for SaaS and media, so add it only if it fits your model.
- Review branded vs non-branded purchase-stage queries separately for clearer reporting.
- Use this segment to prioritise landing-page CRO work on SEO traffic with the highest intent.
Variations
Include subscribe intent
Adds one more bottom-funnel action for subscription-led products.
Related Regex Recipes
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.
Regex for Decision Stage Queries
Use this regex to isolate decision-stage queries in GSC when searchers are validating the final details before taking action.
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