Intro
Capture category-style searches in GSC so you can monitor broader browse intent that should map to collection or category pages.
Use this regex to isolate category-page style demand in GSC when users search with broad browse-oriented modifiers rather than item-level terms.
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 common browse and collection modifiers.
- Separates category-style demand from specific product-page demand.
- Supports cleaner reporting for ecommerce and listing-based sites.
What it does not match
- browse office furniture - Browse only matches in the variation.
- buy office chair - This is item-level transactional intent rather than category-page phrasing.
Edge Cases
- Category-style demand can overlap with ecommerce browse intent from Cluster 4.
- Many category-page queries do not use explicit browse modifiers, so combine this with landing-page analysis.
Example Matches Table
| Query | Match | Why |
|---|---|---|
| running shoes collection | Match | Contains collection, which is a category-style modifier. |
| shop office furniture | Match | Contains shop, which often aligns with category or browse pages. |
| browse office furniture | No | Browse only matches in the variation. |
| buy office chair | No | This is item-level transactional intent rather than category-page phrasing. |
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
- Measure browse-style demand separately from product-detail demand.
- Audit whether category pages capture the right generic search formats.
- Compare shop and collection modifiers against product queries.
Pro Tips
- Category intent is often clearer when paired with page filters for collection or listing URLs.
- Keep browse as a variation if you want the base segment to stay tighter.
- This is especially useful for ecommerce, directories, and marketplaces.
- Compare category-style demand against product-page demand for merchandising priorities.
Variations
Include browse modifiers
Adds another broad browse-style modifier often seen in listing intent.
Related Regex Recipes
Regex for Product Page Queries
Use this regex to isolate product-page style demand in GSC when users search with modifiers that imply a specific product detail page.
Regex for Product Queries
Use this regex to isolate product-level queries in GSC when you want a clear segment built around specific items rather than category or intent modifiers.
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