Intro
Track landing-page style searches in GSC so you can isolate conversion-oriented query formats from editorial and support demand.
Use this regex to capture query patterns that commonly map to landing pages and conversion-focused destination pages in Search Console.
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 landing-page and conversion-entry modifiers.
- Creates a cleaner segment for signup, pricing, and demo-style demand.
- Helps you compare landing-page intent against product, support, and blog queries.
What it does not match
- seo dashboard free trial - Free trial only matches in the variation.
- what is search console regex - This is informational, not landing-page led.
Edge Cases
- Landing-page intent overlaps with commercial and decision-stage demand by design.
- The best segmentation comes from combining query modifiers with page filters.
Example Matches Table
| Query | Match | Why |
|---|---|---|
| seo dashboard pricing | Match | Pricing is a common landing-page modifier. |
| request demo seo dashboard | Match | Contains request demo, which strongly signals a landing-page path. |
| seo dashboard free trial | No | Free trial only matches in the variation. |
| what is search console regex | No | This is informational, not landing-page led. |
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 conversion-entry demand in one segment.
- Audit whether landing pages capture the right query modifiers.
- Compare landing-page intent against product and support demand.
Pro Tips
- This segment is useful when your site has multiple conversion-entry pages with different jobs.
- Keep free trial in a variation if you want a slightly tighter landing-page view.
- Use page filters to validate that demo and pricing searches land on the intended pages.
- Compare branded and non-branded landing-page demand separately.
Variations
Include free-trial intent
Broadens the landing-page segment with another strong conversion-entry modifier.
Related Regex Recipes
Regex for Product Page Queries
Use this regex to isolate product-page style demand in GSC when users search with modifiers that imply a specific product detail page.
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.
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