Search console regex filters let you slice the Performance report in ways the normal "contains" filter cannot: all question queries, all long queries, every misspelling of your brand, or every page in one folder. This tool builds the pattern for you from a preset, tests it on queries you paste, and warns you about syntax that Search Console refuses.
Why use regex in Search Console?
The Performance report shows the queries and pages that bring clicks and impressions. With a plain filter you can ask for queries that contain one word. With a custom regex you can ask for many patterns at once:
- Question queries such as "how to submit a site to bing": good ideas for FAQ sections and new articles.
- Long queries of six words or more: the long-tail searches that small sites can actually win.
- Brand queries, including typos, so you can split brand traffic from the rest.
- A group of topics, such as price, cost or cheap.
- A folder of pages, such as everything under /blog/.
My own site is small and gets only a few clicks a day from search, so I lean on these filters more than on totals: they show which questions people actually typed before they found a page.
How regex filters work in Search Console
Four rules explain almost every surprise:
- RE2 syntax. Google uses its RE2 engine. It is fast and safe, but it leaves out some features: lookahead
(?=...), negative lookahead(?!...), lookbehind and backreferences such as\1. Patterns with them are refused. - Partial match. The pattern only has to appear somewhere in the query or URL.
seomatches "free seo tools". Use^for "starts with" and$for "ends with". - Case. Matching is case-sensitive unless the pattern starts with
(?i). Queries in the report are lowercase, so this matters mostly for page URLs. - Length. A filter can be up to 4,096 characters.
A few symbols do most of the work: | means "or", ^ and $ mark the start and end, \b marks a word edge so "cost" does not match "costume", \s is a space, and {5,} means "five times or more". A dot matches any character, so escape it as \. when you mean a real dot in a URL.
For "everything except", you do not need lookahead: choose "Doesn't match regex" in the filter menu instead.
How to use the search console regex builder
- Pick what you want to find. Each preset writes a pattern. You can also type your own.
- Fill in the value. Extra question words, the minimum number of words, your brand names, a word list or a folder.
- Paste test lines. Export queries or pages from Search Console and paste them, one per line. Matches turn green, and the counts show how much the filter catches.
- Read the check line. It says whether the pattern is valid for Search Console, or names the part RE2 will refuse.
- Copy it into Search Console. Performance, then + Add filter, then Query or Page, then Custom (regex).
Patterns worth saving
| Goal | Pattern | Filter on |
|---|---|---|
| Question queries | ^(who|what|when|where|why|how|which|can|does|is|are)\b | Query |
| Six words or more | ^(\S+\s+){5,}\S+$ | Query |
| Brand with a space or dash | (blog[ -]?hints|bloghint) | Query |
| Buying words | \b(price|cost|cheap|best|review)\b | Query |
| One folder | ^https?://[^/]+/blog/ | Page |
| Two folders | /(tools|basic)/ | Page |
The brand preset also adds each version of the name with one letter missing, because those are the most common typos. Check the test list: a short brand can collide with ordinary words, and then you should remove a few variants by hand.
What to do with the results
- Question queries with impressions but few clicks often mean the page answers the question too late. Put a short direct answer near the top.
- Long queries that land on the wrong page point to a missing article or a page that needs a clearer heading.
- Brand versus non-brand clicks tell you whether people find you through search or already know you.
- Folder filters show which section grows and which one stalls.
Compare date ranges with the same filter, for example the last 3 months against the 3 months before, and watch the trend rather than single days.
Limits to keep in mind
Search Console hides some rare queries for privacy, so a filter never sees every search. The report also shows at most 1,000 rows in the browser; use the export or the API for more. And a regex only filters what is there: it cannot tell you about searches where you have no impressions at all.
Build the pattern here, test it on a real export, then paste it into the search console regex filter and save the view you use most.
Frequently asked questions
Why does Search Console say my regex is invalid?
Most often the pattern uses something RE2 does not support, such as lookahead (?!...), lookbehind or a backreference like \1. Other causes are an unclosed bracket or a pattern over 4,096 characters. The tool names the part that fails.
Is the Search Console regex filter case-sensitive?
Yes, unless you start the pattern with (?i). Queries are shown in lowercase, so it rarely matters for queries, but page URLs can contain capitals.
How do I exclude queries with regex in Search Console?
Write a pattern for what you want to remove, then choose "Doesn't match regex" in the filter menu. You do not need a negative lookahead, which RE2 does not support anyway.
