Intro
Surface question-led queries in GSC so you can measure informational demand that starts with clear question intent.
Use this regex to isolate question keywords in GSC and see how well your content captures query-led informational demand.
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.
.*
Dot-star means any characters can appear here. In GSC it is commonly used when you want to allow extra words before or after a core phrase.
^
The caret anchors the regex to the start of the query. Use it when you want to match terms only if they appear first in GSC.
\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 queries that begin with a core question word.
- Keeps the segment tight by anchoring the pattern to the start of the query.
- Helps you benchmark educational visibility separately from commercial demand.
What it does not match
- search intent guide - Contains informational intent, but it does not begin with a question word.
- best seo reporting tools - This is a modifier-led query, not a question-led query.
Edge Cases
- This pattern misses question intent that starts with other words such as can, should, or is. Add them in a variation when needed.
- The anchor keeps matching tight, so a query that contains a question word later in the string will not match.
Example Matches Table
| Query | Match | Why |
|---|---|---|
| how to segment gsc queries | Match | Starts with how, so it matches immediately. |
| what is search intent | Match | Starts with what, which is included in the grouped options. |
| why does branded ctr drop | Match | Starts with why, so it stays inside the question segment. |
| search intent guide | No | Contains informational intent, but it does not begin with a question word. |
| best seo reporting tools | No | This is a modifier-led query, not a question-led query. |
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 question demand before and after publishing FAQs or guides.
- Benchmark question-led CTR against non-question informational queries.
- Identify question clusters that need richer snippets or clearer answers.
Pro Tips
- If your market uses which heavily, add it as a grouped option in the regex.
- Compare question-led visibility against page types such as blog or documentation pages.
- Look at rank position and CTR together, because question queries often underperform on clicks even with strong visibility.
- Export matched queries and cluster them into answer themes before writing content.
Variations
Add which queries
Expands the question group to include which-led searches.
Focus on how and what only
Useful when you want the highest-volume question formats without the full question set.
Related Regex Recipes
Regex for Informational Intent
Use this regex to isolate informational intent terms in GSC and measure awareness-stage SEO performance with less noise.
Regex for Non-Brand Queries
Use this regex with the Doesn't match regex query filter in GSC to exclude brand terms and leave non-brand demand behind.
CTA
Regex is powerful in GSC, but manual filtering still leaves you exporting, comparing, and rebuilding the same views. Spicy Metrics turns those segments into reporting your team can reuse.
Turn regex into repeatable reporting