Search Console regex filters: find questions and brand searches
Short answer: In the Performance report, add a Query filter, choose Custom (regex), and paste a pattern. A question filter like ^(how|what|why|when|where|who|which|can|do|does|is|should) shows the searches you could answer with content, and a brand pattern with "Doesn't match regex" shows how people find you without knowing your name. Search Console uses RE2 syntax, matches anywhere in the query by default, and ignores case unless you say otherwise.
The default Queries table in Search Console is a long, unsorted list. Regex filters turn it into answers to specific questions: what are people asking, how much traffic depends on our name, which towns are we showing up in. Below is a worked example using a fictional business, followed by a pattern table you can copy.
The rules Search Console applies
From Google's help page on advanced filtering, as of November 2026:
- Syntax: RE2.
- Partial match by default: the pattern can match anywhere in the query unless you anchor it with
^(start) or$(end). - Not case-sensitive by default. Add
(?-i)at the start if you ever need case-sensitive matching. - Two modes: "Matches regex" (the default) and "Doesn't match regex".
- Totals can shift: filtering by query can affect report totals because of data truncation and anonymized queries that are left out.
One RE2 limitation catches people who copy patterns from elsewhere: RE2 doesn't support lookaheads or lookbehinds such as (?=...) or (?!...). Use the "Doesn't match regex" option to exclude instead.
The worked example: a fictional plumber
Hypothetical business: Ridgeline Plumbing, a four-van plumbing company serving Austin and Round Rock, Texas. The owner wants to know three things: what questions people ask before calling, how dependent the site is on people already knowing the name, and whether the water heater pages show up for both towns.
Question 1: What are people asking?
Filter: Query → Custom (regex) → Matches regex:
^(how|what|why|when|where|who|which|can|do|does|is|should|will)
The trailing space stops "whole" or "isolation" from matching. In this example, results might include "how long does a water heater last", "why is my water heater making noise", "can a slab leak be fixed without breaking concrete".
What the owner does next: sorts by impressions, picks questions with plenty of impressions but low clicks, and checks whether the page Google shows actually answers them. Several become short sections on existing service pages; one becomes its own article.
Question 2: How much traffic comes from the brand?
Brand pattern:
ridgeline|ridge line|ridgelineplumbing
Google's own announcement of regex filters used the same idea: a company called "cats and dogs" capturing its variants with cats and dogs|cats & dogs|c&d.
Include common misspellings you see in the table. Apply it once with "Matches regex" to see branded clicks, then switch to "Doesn't match regex" to see everything else.
What the owner learns, in this hypothetical: most clicks come from branded searches, which means existing customers and referrals find the site easily, but new customers searching "plumber Round Rock" mostly don't. That points the next month's work at local service pages, not the homepage.
Question 3: Service plus town
Pattern:
(water heater|tankless|hot water).*(austin|round rock)
The .* allows anything in between, so "water heater replacement round rock" and "tankless water heater install austin tx" both match.
Add a Page filter alongside it, such as URL containing /water-heater, to see whether the right page is the one getting those impressions. If the homepage keeps appearing instead, the service page probably isn't clear enough about the town or the service.
To compare towns, run the pattern once for each, or use the comparison mode with two date ranges to see whether a page update helped.
Ready-made patterns
| Goal | Pattern | Mode |
|---|---|---|
| Question searches | ^(how|what|why|when|where|who|which|can|do|does|is|should|will) |
Matches |
| Brand searches | yourbrand|your brand|yourbrnd |
Matches |
| Non-brand searches | same brand pattern | Doesn't match |
| Cost and price intent | cost|price|how much|cheap|quote |
Matches |
| Urgent intent | emergency|24 hour|24/7|same day|tonight |
Matches |
| "Near me" searches | near me|nearby|close to me |
Matches |
| Long searches (7+ words) | ^([^ ]+ ){6,}[^ ]+$ |
Matches |
| One town | round rock |
Matches |
| Comparison intent | vs | versus |or |
Matches |
| A section of the site (Page filter) | /services/|/blog/ |
Matches |
In the table, \| is just the pipe character | written so it displays; type a plain | in Search Console.
The long-query pattern uses RE2's counting form {6,}, meaning "six or more repeats". Long searches are often very specific problems, the kind a short FAQ or a paragraph on a service page can win.
Making it a monthly habit
- Keep a pattern library. Store your patterns in a shared note so you can paste them in seconds each month.
- Compare date ranges. Use the comparison mode with the last 28 days against the previous period on your question filter to see whether new content is gaining impressions.
- Export. Use the export button to pull filtered results into a sheet and tag questions by topic.
- Agree definitions. Whoever checks next month should use the same brand, town and service patterns, or the numbers won't be comparable.
Common mistakes
- Pasting lookaheads from other regex tools. RE2 rejects them; use "Doesn't match regex".
- Forgetting the brand misspellings, which makes non-brand look bigger than it is.
- Anchoring by accident.
^plumberonly matches queries that start with "plumber", not "emergency plumber". - Reading totals as exact. Filtered totals can differ from unfiltered ones because some queries are anonymized or truncated.
FAQ
Is Search Console regex case-sensitive?
No, not by default. Google's help page says to prepend (?-i) for case-sensitive matches.
Why doesn't my pattern with (?!...) work?
Search Console uses RE2, which doesn't support lookaheads or lookbehinds. Write the pattern for what you want to exclude and choose "Doesn't match regex".
Can I combine a query regex with a page filter?
Yes. Filters on different dimensions stack, so you can see question searches for one section of the site.
How often should I check?
Monthly is enough for most small businesses, with a quick look after publishing or updating important pages.
When you'd like your Search Console patterns turned into a short monthly content list, send us the questions you keep hearing on the phone.