Intro
Find cause-and-effect searches in GSC so you can measure diagnostic question demand around problems, drops, and unexpected behaviour.
Use this regex to isolate why does queries in GSC when users are trying to understand a cause, problem, or change in behaviour.
The Regex
How This Regex Works (Explained Simply)
.*
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 why does.
- Surfaces diagnostic search behaviour rather than generic learning intent.
- Works well for troubleshooting, support, and performance-investigation content.
What it does not match
- why is my traffic down - This would only match if you use the broader variation.
- how to fix indexing issues - This is an action-led query, not a why-does query.
Edge Cases
- This is intentionally narrow. Many diagnostic queries begin with why is or why do instead.
- If you want all why queries, broaden the grouped phrase rather than dropping the anchor.
Example Matches Table
| Query | Match | Why |
|---|---|---|
| why does ctr drop | Match | Starts with why does, so it matches. |
| why does gsc show delays | Match | Uses the exact diagnostic phrasing. |
| why is my traffic down | No | This would only match if you use the broader variation. |
| how to fix indexing issues | No | This is an action-led query, not a why-does 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 diagnostic search demand around SEO problems.
- Spot recurring troubleshooting topics for support content.
- Measure whether problem-led content is improving visibility.
Pro Tips
- Broaden this to why do or why is if your audience uses more conversational wording.
- Pair this with support pages to see whether users land on the right answers.
- Review impression growth because these queries often appear before users know the fix.
- Cluster matched queries by root cause to prioritise help content.
Variations
Capture broader why phrasing
Adds common variations so you capture more diagnostic demand.
Related Regex Recipes
Regex for Question Keywords
Use this regex to isolate question keywords in GSC and see how well your content captures query-led informational demand.
Regex for Educational Queries
Use this regex to capture a wider educational query set in GSC when you want a practical top-of-funnel segment that includes multiple informational modifiers.
CTA
Regex is only the first step. The real bottleneck is turning manual filters into a repeatable workflow your team actually uses. Spicy Metrics helps you move from ad hoc filtering to operational SEO workflows.
Move beyond manual regex work