Intro
Track ecommerce category-level demand in GSC so you can separate broad browse intent from product-specific searches.
Use this regex to capture the modifiers that signal category and browse-level ecommerce intent.
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 common category and browse modifiers.
- Surfaces broader shopping intent than product-detail recipes.
- Helps analyse category-page SEO performance.
What it does not match
- running shoe styles - Styles only matches if you use the variation.
- running shoe size 9 - This is more product-detail-led than category-led.
Edge Cases
- Range and collection can show up in brand messaging as well as ecommerce search behaviour, so review actual query examples.
- Category intent is often broader and earlier-stage than explicit buy intent.
Example Matches Table
| Query | Match | Why |
|---|---|---|
| shop office chairs | Match | Shop is included in the grouped category terms. |
| running shoe collection | Match | Collection is one of the browse-level modifiers. |
| running shoe styles | No | Styles only matches if you use the variation. |
| running shoe size 9 | No | This is more product-detail-led than category-led. |
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-level ecommerce demand.
- Audit whether category pages rank for broad collection searches.
- Compare category intent with product-detail and high-intent segments.
Pro Tips
- This becomes much stronger when combined with page filters for category URLs.
- Keep category and product-detail recipes separate so you can compare behaviour properly.
- Collection can also appear in editorial contexts, so check landing pages before acting on the output.
- Use styles only when it fits the catalogue language in your niche.
Variations
Include style-led browsing
Adds another category-style modifier common in retail searches.
Related Regex Recipes
Regex for Category Queries
Use this regex to isolate category-style queries in GSC when users browse a broader product group rather than a single item.
Regex for "Shop" Queries
Use this regex to capture searches that include shop when users are explicitly looking for a place to browse or purchase products.
CTA
Regex is powerful in GSC, but manual filtering still leaves you exporting, comparing, and rebuilding the same views. Spicy Metrics turns those segments into reporting your team can reuse.
Turn regex into repeatable reporting