Search Console Regex Filters: Practical RE2 Patterns
Quick answer: Search Console regex filters use RE2 syntax. Add a Query or Page filter, choose Custom (regex), and decide whether results should match or exclude the pattern. Matching is partial and case-insensitive by default. Use ^ and $ for whole values, escape literal dots in URLs, and test included and excluded rows before reporting a total.
One contains filter works for one spelling. Real reports usually need a group: a brand and its misspellings, two content folders, or several question words. Regex puts those variants into one repeatable Search Console filter.
A short expression can also create a very confident wrong segment. Search Console uses partial matching by default, and punctuation such as a dot has a special meaning. Start with a small pattern, inspect the rows it includes, and test the excluded rows before reporting a total.
SEARCH CONSOLE
Search Console Regex Filters: Practical RE2 Patterns
PRIMARY KEYWORD
Search Console regex filters
READ TIME
8 minutes
Apply a custom regex filter in the Performance report
Open the Search results Performance report, select Add filter, and choose Queries or Pages. Select Custom (regex), leave Matches regex selected for the included group, then apply the expression. Use Doesn't match regex for the complementary group.
Google documents RE2 as the supported syntax. Regex matching is case-insensitive and partial by default, so “acme” can match any query containing those letters. Add ^ for the start and $ for the end when the expression should cover the entire query or URL. A case-sensitive report is possible with the documented “(?-i)” prefix, though query analysis rarely needs it.
Group brand names and common variations
A practical brand pattern is “(acme|acme app|akme)”. The vertical bar means “or,” and the parentheses keep the alternatives together. Because the default match is partial, the pattern also catches longer queries such as “acme pricing” and “acme reviews.” Replace the example terms with the real brand, product names, former names, and misspellings visible in the query table.
If only exact brand queries belong in the group, use “^(acme|acme app|akme)$”. Run the pattern once with Matches regex and once with Doesn't match regex to inspect the split. Search Console omits anonymized queries, so the two visible groups do not create a complete classification of every impression in the property total.
Filter complete page folders without catching similar URLs
For a site whose content lives under two folders, “^https://(www\.)?example\.com/(blog|guides)/” matches full URLs beginning with either folder. The optional “(www\.)?” covers both host variants in the example, while the escaped dots mean literal dots rather than any character.
Match the expression to the canonical URLs that appear in the Pages table. Protocol, hostname, subdomain, trailing slash, and folder spelling all matter once the pattern is anchored to the start. Test a known URL inside the folder and a similar URL outside it, such as “/blogroll/”, before trusting the total.
- Use ^ to anchor the protocol and hostname
- Escape each literal dot as \.
- Put folder alternatives inside parentheses
- End the folder with / to avoid a similar prefix
Find queries that begin with question words
The pattern “^(how|what|why|when|where|who|can|do|does|is|are|should)\s” finds queries that begin with one of those words followed by whitespace. The start anchor prevents a phrase in the middle of a query from entering the group, and \s prevents a word such as “island” from matching the “is” alternative.
Treat this as a research slice rather than a complete list of informational intent. Some questions do not begin with a question word, and some matching queries may have commercial or navigational intent. Review the rows and landing pages before turning the group into a content brief.
Test the included and excluded rows before reusing a pattern
Apply the expression to a long enough date range to produce a useful table, then scan rows near the top and bottom. Switch to Doesn't match regex and look for expected values that leaked into the other group. Add one alternative or boundary at a time so an invalid or overly broad expression is easy to diagnose.
Save the pattern, property, dates, search type, and other filters with the analysis. SEO Receipts can keep bounded Search Console windows and source-backed opportunities together, but it does not make regex results exhaustive, reveal privacy-hidden queries, or provide live rankings. The native table remains the place to validate the rows selected by a pattern.
TAKEAWAY CHECK
What belongs on the validate a search console regex filter?
- 01Choose Query or Page before entering the expression.
- 02Confirm whether partial or whole-value matching is intended.
- 03Use parentheses around alternatives separated by |.
- 04Escape literal dots and check URL host variants.
- 05Inspect known matches in the filtered table.
- 06Switch to Doesn't match regex and inspect expected exclusions.
- 07Save the exact expression with the report scope.
- 08Account for anonymized queries and bounded table rows.
What else do people ask about Search Console regex filters?
Which regex syntax does Search Console support?
Google documents RE2 syntax for Search Console regex filters. Patterns copied from another regex engine can use features RE2 does not accept. Start with the operators in Google's Search Console guide and test the expression in the report before building a recurring analysis around it.
Are Search Console regex filters case-sensitive?
They are case-insensitive by default. Google's documented “(?-i)” prefix turns on case-sensitive matching for the text that follows. Query groups usually benefit from the default because capitalization rarely represents a meaningful intent difference.
Why does a regex match more queries than expected?
Search Console uses partial matching by default. A simple term can match anywhere inside a query or URL. Add start and end anchors when the whole value must match, use a whitespace or folder boundary where appropriate, and remember that an unescaped dot matches any single character.
Can a regex split every query into branded and non-branded groups?
It can split the query rows Search Console exposes under that scope. It cannot classify anonymized queries that are omitted for privacy, and detailed tables are bounded. Document the regex and describe the result as a split of visible query data rather than every search impression.
Which primary sources support this guide?
Product behavior and metric definitions change. These are the official Google references used for this article and checked on July 26, 2026.
- 01Google Search Console: advanced filtering and comparison
Official guidance for date comparisons, query and page filters, and RE2 regular expressions in the Performance report.
- 02Google Search Console Performance report
Official guidance on filters, dimensions, date ranges, and reading the report.
- 03Search Console dimensions and data groupings
Official rules for queries, pages, dates, countries, devices, and time granularity.
- 04About Search Console data
Google's documentation on freshness, privacy omissions, row limits, time zones, and discrepancies.
PUT THE CLAIM ON THE RECORD
Your SEO result deserves a source, not a trust-me caption.
Connect an owner-level Search Console property, choose what stays public, and get a receipt with a stable share link.