Intro
Track tool- and feature-led searches in GSC so you can isolate product capability demand that should map to feature or solution pages.
Use this regex to capture tool- and feature-style query modifiers in GSC when searchers are looking for product capabilities rather than help or educational content.
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 capability and product-feature modifiers.
- Creates a segment for solution-page and feature-page demand.
- Helps you compare capability-led searches against support and landing-page queries.
What it does not match
- seo platform - Platform only matches in the variation.
- how to build seo reports - This is educational workflow intent rather than a tool/feature modifier.
Edge Cases
- Some feature-like modifiers can overlap with commercial and product intent, so page analysis is important.
- This is a practical capability segment, not a complete representation of every feature-related search.
Example Matches Table
| Query | Match | Why |
|---|---|---|
| seo reporting tool | Match | Contains tool, which is a product-capability modifier. |
| rank tracker dashboard | Match | Contains dashboard, which often maps to a feature or solution page. |
| seo platform | No | Platform only matches in the variation. |
| how to build seo reports | No | This is educational workflow intent rather than a tool/feature 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
- Measure feature-led and capability-led query demand.
- Audit whether feature pages capture the right search modifiers.
- Compare product-capability queries against landing-page and support intent.
Pro Tips
- This segment is especially useful for SaaS and product-led sites with many feature pages.
- Capability modifiers can overlap with commercial-intent reporting, so compare both views.
- Use page filters to find feature-intent queries landing on general pages rather than solution pages.
- Add platform or solution wording only if that language matters in your market.
Variations
Include platform wording
Adds another common product-capability noun often used in B2B and SaaS queries.
Related Regex Recipes
Regex for Landing Page Queries
Use this regex to capture query patterns that commonly map to landing pages and conversion-focused destination pages in Search Console.
Regex for Documentation Queries
Use this regex to capture documentation-style query modifiers in GSC when users need structured reference or implementation guidance.
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