Intro
Identify SKU- or model-like queries in GSC so you can separate precise product lookups from generic product demand.
Use this regex to isolate model-number style searches in GSC when users search with precise alphanumeric identifiers rather than descriptive product terms.
The Regex
How This Regex Works (Explained Simply)
[]
Square brackets match one character from a set. They are useful for small spelling or formatting variations without writing every full word.
?
The question mark usually makes the previous character or group optional. That is handy when a query modifier appears inconsistently.
{n,m}
Curly braces control how many times something can repeat. Use them when you need tighter matching than * or + gives you.
\d
Backslash-d matches a digit. It is useful for years, model numbers, and numeric modifiers in GSC queries.
\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 many common letter-number product code formats.
- Surfaces very specific product lookup demand that often converts well.
- Separates exact model searches from broader category and feature searches.
What it does not match
- running shoes for men - No model-like alphanumeric code appears.
- cheap laptop deals - This is generic product demand, not a model lookup.
Edge Cases
- This is a best-effort template pattern, not a universal model-number detector.
- Very short product codes can create false positives, so tighten the pattern if needed.
Example Matches Table
| Query | Match | Why |
|---|---|---|
| ab-1234 review | Match | Fits the grouped letter-number model pattern. |
| ZX500 running shoes | Match | Matches the alphanumeric model format. |
| running shoes for men | No | No model-like alphanumeric code appears. |
| cheap laptop deals | No | This is generic product demand, not a model lookup. |
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 exact product lookup demand with high purchase intent.
- Audit whether product detail pages capture model-number searches.
- Find inventory and indexing gaps for code-based products.
Pro Tips
- Model-number formats vary a lot by catalogue, so test this against your real query data before relying on it.
- Keep the regex narrow enough to avoid matching ordinary short alphanumeric strings.
- Pair this with page filters to catch misrouted model searches landing on categories.
- If your store uses SKU labels explicitly, add them in a grouped variation.
Variations
Include explicit SKU phrasing
Broadens the pattern to include searchers who use SKU terms directly.
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 High Intent Keywords
Use this regex to capture a broad mix of ecommerce high-intent modifiers in GSC when you want one practical late-funnel reporting segment.
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