Intro
Track ecommerce product-level searches in GSC so you can separate item-specific demand from category and buying-modifier traffic.
Use this regex to capture the modifiers that commonly appear in product-level ecommerce queries, especially around specifics and variants.
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 product-detail modifiers such as model, SKU, size, and colour.
- Surfaces product-level demand rather than broad category intent.
- Helps analyse how item-specific pages perform.
What it does not match
- office chair dimensions - Dimensions only matches if you use the variation.
- office chairs for sale - This is broader commercial demand, not a product-detail modifier.
Edge Cases
- Product-detail modifiers differ by vertical, so tune the list to your catalogue.
- Colour and size searches can still behave like category intent if the user has not chosen a specific item yet.
Example Matches Table
| Query | Match | Why |
|---|---|---|
| nike air max sku | Match | SKU is directly included. |
| office chair size guide | Match | Size appears in the grouped product-detail set. |
| office chair dimensions | No | Dimensions only matches if you use the variation. |
| office chairs for sale | No | This is broader commercial demand, not a product-detail modifier. |
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
- Separate product-detail traffic from broader category traffic.
- Audit whether product pages capture item-specific searches.
- Compare product-detail demand with high-intent modifiers.
Pro Tips
- This recipe works best when paired with page filters for product URLs.
- Add only the detail modifiers that matter in your catalogue.
- Review colour versus color depending on your target market mix.
- Use exports to see which product attributes matter most in search demand.
Variations
Include dimensions
Adds another common product-detail attribute to the ecommerce set.
Related Regex Recipes
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.
Regex for SKU / Model Numbers
Use this regex to isolate model-number style searches in GSC when users search with precise alphanumeric identifiers rather than descriptive product terms.
CTA
Building query segments manually in GSC works for one-off checks, but it breaks down across multiple sites and stakeholders. Spicy Metrics keeps those segments organised and easy to monitor.
Scale segmentation in Spicy Metrics