Intro
Track feature-led SaaS searches in GSC so you can isolate product-capability demand from broader educational or pricing queries.
Use this regex to capture common feature and capability modifiers that appear in SaaS product evaluation searches.
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 SaaS capability words such as features, integrations, and automation.
- Surfaces product-led demand rather than broad informational traffic.
- Helps report on which features pull organic visibility.
What it does not match
- rank tracker workflow - Workflow only matches if you use the variation.
- rank tracker pricing - Pricing is a separate intent and not in the feature set.
Edge Cases
- Some terms such as reporting can also appear in educational queries, so review landing pages before classifying every click as product-led.
- This recipe is best for SaaS products with clear capability language in the query set.
Example Matches Table
| Query | Match | Why |
|---|---|---|
| seo reporting dashboard features | Match | Features and dashboard are both in the grouped set. |
| rank tracker integrations | Match | Integrations is explicitly included. |
| rank tracker workflow | No | Workflow only matches if you use the variation. |
| rank tracker pricing | No | Pricing is a separate intent and not in the feature set. |
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 which capabilities attract organic demand.
- Compare feature-led traffic with pricing and comparison demand.
- Audit whether feature pages and product pages rank for the right terms.
Pro Tips
- Keep the feature list aligned to the capabilities users actually search for, not every internal product label.
- Use page filters to see which features deserve dedicated landing pages.
- Compare branded and non-branded feature demand separately.
- Expand the term list gradually so the segment stays interpretable.
Variations
Include workflow wording
Adds another SaaS capability term often used in product-led searches.
Related Regex Recipes
Regex for Tool / Feature Queries
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.
Regex for SaaS Pricing Queries
Use this regex to capture the core pricing modifiers that show up when SaaS buyers are evaluating cost and packaging.
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