Intro
Track product-detail style searches in GSC so you can measure query formats that should map directly to a specific item or detail page.
Use this regex to isolate product-page style demand in GSC when users search with modifiers that imply a specific product detail page.
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 detail-page modifiers such as specs, model, and sku.
- Separates product-detail demand from category and editorial intent.
- Helps you compare item-level traffic against broader browse or content traffic.
What it does not match
- office chair dimensions - Dimensions only match in the variation.
- best office chairs - This is a broader commercial query, not a product-page format.
Edge Cases
- This segment is still a proxy, so combine it with page filters for cleaner product-page reporting.
- Specs and features can overlap with research-stage comparison behaviour.
Example Matches Table
| Query | Match | Why |
|---|---|---|
| ZX500 specs | Match | Contains specs, which is a product-detail modifier. |
| buy office chair model a12 | Match | Contains buy and model, both of which suggest product-page demand. |
| office chair dimensions | No | Dimensions only match in the variation. |
| best office chairs | No | This is a broader commercial query, not a product-page format. |
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 detail-page demand separately from category or listing demand.
- Audit whether product detail pages capture the right query modifiers.
- Compare model and specs searches against general product searches.
Pro Tips
- This is best used as a format proxy alongside product-noun or SKU segments.
- If your products are technical, specs and dimensions may be especially valuable.
- Use page filters to make sure detail-page queries do not land on category pages.
- Keep the grouped terms close to the language your catalogue actually uses.
Variations
Include dimension-led queries
Adds another common detail-page modifier often used in product research.
Related Regex Recipes
Regex for Category Page Queries
Use this regex to isolate category-page style demand in GSC when users search with broad browse-oriented modifiers rather than item-level terms.
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
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