Search Console regex filters: find queries in bulk
Regex filters in the Search Console performance report let you group question queries, brand terms, and URL folders. Here are patterns to copy and traps to avoid.
The Search Console performance report shows thousands of queries and pages. Most people scroll through them one row at a time. Regex filters let you ask a sharper question: show me every query that starts with a question word, or every page inside one folder. It takes a few minutes to learn and saves hours.
What regex filters do
Regex is short for regular expression. It is a pattern that matches text. In the performance report, you can apply one to the Query filter or the Page filter. Instead of typing one word, you describe a shape, and Search Console keeps only the rows that fit.
To use it, click the Query or Page filter, then change the match type from the default to a custom regex option. You can choose to include rows that match, or exclude rows that match. Google uses the RE2 syntax, which is a simpler flavor than what some programming languages offer. Features like lookaheads are not supported.
Without regex, you only get a few match types, such as contains or exact. Those are fine for one term. They break down when you want to group many terms at once.
Patterns worth copying
You do not need to be fluent in regex. A handful of patterns cover most real work. Here are the ones that earn their keep.
Question queries
Use a pattern that starts with a caret, then lists question words separated by a pipe, such as who, what, when, where, why, and how. The caret means the query must begin with those words. This gives you every question people typed. Those are good candidates for a direct answer block, and they are the queries AI answer engines tend to fan out into.
Long conversational queries
Match queries with at least five words by repeating a word-and-space group. Longer queries often signal a more specific need. Compare their click-through rate and position against short queries. The gap tells you where your content is too generic.
Brand versus non-brand
List your brand name and its common misspellings, separated by pipes. Apply it as an include filter to see branded traffic. Apply the same pattern as an exclude filter to see everything else. Misspellings matter, because people mistype brand names often.
One folder of your site
On the Page filter, match URLs that contain a folder path, such as the blog or a product category. This is the fastest way to judge one section without exporting data. Add the pipe to compare two folders at once.
Traps to avoid
- Case matters. RE2 is case-sensitive unless you add the case-insensitive flag at the start of the pattern. Search Console queries are usually lowercase, but page URLs are not always.
- Special characters need escaping. A dot matches any character, so to match a literal dot in a URL, put a backslash before it. The same goes for question marks and plus signs.
- A bare word matches anywhere. The word "seo" will also match "seoul". Use anchors or word boundaries when you need an exact term.
- Regex cannot find what Google hides. Anonymized queries, the rare ones that only a few users typed, never appear in the report, so your counts will undercount long-tail demand.
- Filters reset. If you leave the page, you lose the pattern. Keep a note of the ones you rely on.
Turning filters into decisions
A filter alone is just a view. The value comes from comparing two views. Here is a simple routine that works.
- Filter to question queries and sort by impressions.
- Pick the ones where you rank between positions 5 and 20. You already have some relevance there.
- Open the matching page and check whether it answers the question in its first paragraph or under a clear heading.
- Add or tighten the answer, then note the date so you can compare the same filter a few weeks later.
Treat the result as a hint, not proof. Position and impressions shift for many reasons, and a single edit rarely explains a change on its own. Look for a trend across several pages before you call something a win.
Search Console also lets you compare date ranges. Combine that with a regex filter to see whether your question queries grew faster than the rest of your traffic. If they did, your answer-style content is probably working.
What to do next
Open the performance report today and apply one pattern: question queries, excluding your brand. Sort by impressions, and pick the top three pages sitting between positions 5 and 20. Rewrite the opening of each so it answers the question in two or three plain sentences. Then re-run the same filter in a month and compare.