Search Console Regex Filters: 2026 Guide
Imagine the SEO lead at a US retailer on a Monday in December. The marketing director wants one answer before lunch: how did the Black Friday landing pages do against last year? The lead opens the Performance report. The default chart shows the whole site for the past three months, which the Search Console Help overview names as the default view. The answer lives behind two features that are easy to skip, filters and compare mode. This guide explains both, with the Search Console regex filter at the center, for in-house teams and agencies working across the United States, Europe, and South Korea.
Why does the filtered table never add up to the chart?
The Search Console Help overview says chart data is aggregated by property, while table data grouped by Pages or Search appearance is aggregated by page. The advanced filtering page adds that filtering by query or URL "can affect the report totals due to data truncation and the omission of anonymized queries", so filtered numbers are real but filtered.
The overview gives a concrete case: if two results from the same site appear for one query, the chart counts a single impression, so a Pages table can count an impression on each URL's row. The April 7, 2021 Search Central Blog post by Ziv Hodak adds that some queries and pages "are not available in the reports to protect user privacy or due to storage limitations". It also says a reminder appears each time you apply a query or page filter.
What can you filter in the Performance report?
The Search Console Help overview lists the dimensions as Queries, Pages, Countries, Devices, Search appearance, and Dates. The advanced filtering page says you can filter by several dimensions at once, add a filter with the + Add filter label or by clicking any table row, and remove one with the x beside it. The Search type and date filters can never be removed.
Google's own example on the advanced page is a query view filtered to country='USA' AND device='Mobile'. For a broader tour of the report's neighbors, our practitioner's guide to Google Search Console covers indexing, URL Inspection, sitemaps, and a weekly monitoring routine. For a lighter summary, the Search Console Insights report guide explains that Insights is a summary rather than a diagnostic tool.
When is a containing filter enough, and when do you need a Search Console regex?
The advanced filtering page says a containing filter takes a single substring, and that the match is "not case-sensitive, but is otherwise exact, including any spaces". Use it when every item you want shares one identical string. Use a Search Console regex when the items differ, such as brand misspellings, several folders, or a list of question words with nothing in common.
Ziv Hodak's Search Central Blog post of April 7, 2021 says filters had supported "three patterns: containing a string, not containing a string, and exactly matching a string". Regex arrived that day with a revamped comparison mode. Daniel Waisberg's follow-up of June 2, 2021 added the negative match, which he says appears "through a secondary dropdown" after you pick Custom (regex).
How do you build a Search Console regex filter step by step?
Follow the steps on the advanced filtering Help page: click + Add filter, choose Queries or Pages, choose Custom (regex), type the expression, pick Matches regex or Doesn't match regex, and click Apply. For several values, the page says to separate them with a vertical bar and surround the whole expression with parentheses. That is the entire mechanic of a Search Console regex filter.
- Open the Performance report for Search results and click + Add filter in the filters row.
- Choose Queries to match search terms, or Pages to match URLs.
- Choose Custom (regex) from the dropdown.
- Type your expression, and for a list wrap it in parentheses with a vertical bar between the values.
- Keep the default Matches regex to see only what matches, or choose Doesn't match regex to see everything else.
- Click Apply, then read the reminder about missing queries before you trust the total.
Which four regex rules trip people up?
Matching is a "partial match" by default, so a pattern matches anywhere unless you anchor it with ^ or $. Matching is not case-sensitive unless you prepend (?-i), and the syntax is RE2. Several values take a vertical bar, wrapped in parentheses on the Help page, and the RE2 reference adds that a metacharacter such as a dot is matched by escaping it with a backslash.
For example, a short brand like ace under Matches regex also keeps "face" and "space", because the pattern matches anywhere in the string. The fix is either ^ace$ with the anchors the Help page describes, or \bace\b, which the RE2 reference defines as an ASCII word boundary on each side. The RE2 syntax reference marks lookahead, lookbehind, and possessive quantifiers as not supported, so a filter that tries to match a word only when another word follows it will fail. Every row in the table below is taken from the Search Console Help page.
| Pattern | What it does | Source example |
|---|---|---|
| . | Matches any single character | "m.n" matches "men" and "man" but not "meen" |
| [ characters ] | Matches any single item inside the brackets | "c[aie]t" matches "cat", "cit", and "cet" |
| * | Matches the preceding item zero or more times | "fo*d" matches "fd", "fod", and "food" |
| + | Matches the preceding item one or more times | "fo+d" matches "fod" and "food" but not "fd" |
| | | OR operator, matches the expression before or after it | "New York|San Francisco" matches "I love New York" and "I love San Francisco" |
| \d | One digit 0-9 | "\d\d\d abc" matches "123 abc" |
| \D | Any non-digit | "\D\D\D 123" matches "aaa 123" but not "123 123" |
| \s | Any whitespace (tab, space) | "1\s2\s3" matches "1 2 3" |
| (?-i) | Case-sensitive matches for all following characters | (?-i)AAA matches https://example.com/AAA but not https://example.com/aaa |
| ^ | Limits matches to the start of the target string | "^example" matches "example" but not "an example" |
How do you write a brand regex for US, UK, German, and Korean brands?
Start from Google's own example. Daniel Waisberg's June 2, 2021 post suggests willow tree|wilow tree|willowtree|willowtee for a company called Willow Tree, and explains that "the | metacharacter represents an OR statement". List every spelling, spacing, and script your customers use, then run the pattern once under Matches regex and once under Doesn't match regex.
For example, imagine a UK tea brand called Hartwell whose customers type it as one word or two. The pattern hart\s?well covers both, because \s is whitespace in the Help table and the RE2 reference defines x? as zero or one x. Imagine a German site called Grünwald, where grünwald|gruenwald catches both the umlaut and the ae form. Imagine a Korean brand written in Hangul and in Roman letters, where 하늘가구|haneul gagu keeps both scripts in one view. Once the split works, the SEO reporting guide on KPIs that prove ROI shows how to turn a branded and non-branded split into the chart leadership reads.
How do you filter one site section with a page regex?
Switch the filter from Queries to Pages and describe the URL path. Waisberg's June 2, 2021 example is shoes/.*/green for a URL structure of example.com/[product]/[brand]/[size]/[color], where ".* matches any character any number of times". Anchor with ^ when you want a whole path prefix, and escape the dot in the domain with a backslash.
For example, ^https://example\.com/ko/ isolates a Korean section. The shorter /blog/ is enough for a blog folder, because the partial match finds it anywhere in the URL. Clean folders make these filters trivial, which is one more reason to follow the site architecture guide on readable subfolders and crawl depth. If your markets live under /de/ or /ko/, the hreflang and international SEO guide explains why subfolders are the easiest structure to manage. The same report also exposes competing URLs: filter a query, switch to the Pages tab, and look for two rows on one term. That is the pattern the keyword cannibalization guide teaches you to diagnose and fix.
How do you separate question queries from buying queries?
Use the two intent patterns from the June 2, 2021 Search Central Blog post. A query filter of what|how|when|why surfaces question searches, which Waisberg says might indicate "your content should easily answer questions, maybe through an FAQ". A filter of buy|purchase|order surfaces transactional searches and, in his words, might show "which product names are more commonly or rarely used".
Question queries are the raw material for the answer boxes covered in our featured snippets and People Also Ask guide, and the intent types they hint at are mapped in the search intent and micro-intents guide. For a US retailer, I would add a seasonal set such as black friday|cyber monday under Queries and compare this year to last year. The seasonal SEO planning guide warns that peak dates move each year, so treat calendar-date comparisons with care.
How does compare mode work, and where does it stop?
The advanced filtering page says you can compare two values in any one grouping dimension, such as USA versus France, and a Difference column then appears in the table. You can have only one comparison at a time, and a new one replaces the old. Rare values show ~ (not available), and comparing by page or search appearance can change how the metrics are calculated.
For date ranges it recommends the Weekly or Monthly granularity, because that neutralizes the "day-of-the-week" effect of comparing a Monday with a Saturday. Comparing whole weeks rather than single days is the same patience the SEO A/B testing guide asks for with a live control group. Whole-week compares also sharpen the refresh-or-prune calls in the content refresh and decay guide. One catch remains, because the Search Console annotations guide explains that annotation markers do not show in comparison mode, so write down the date before you switch.
How do you compare countries and markets?
Country is a grouping dimension, so the two-value rule applies. Google's advanced filtering page uses USA versus France as its example, and a UK team can run United Kingdom versus Germany the same way. The Help page also says that several countries at once require a comparison "limited to two items", so a three-market view means two compares run one after another.
Keep one fact in mind: the Help overview says the report shows how your site performs in Google Search results, so Naver traffic never appears here, which is why our Naver SEO guide for Korean search exists. In Europe, a sudden shift in one country deserves a country compare before anyone blames rankings. The DMA search changes analysis shows how to segment EU markets by country to measure exposure. When a drop is real, the organic traffic drop decision tree orders the checks from cheapest to rarest.
What does the AI-powered configuration tool do, and should you trust it?
The advanced filtering page describes an experimental tool that opens from the filter icon in the report header into a side panel. You type a request, it suggests filters, comparisons, and metrics, and you "must then confirm" before anything applies. Each user is limited to 20 requests per day, and it is visible only to a small percentage of Search Console users.
The page warns that it may generate filters that do not match your request, so you should always review the filters applied. My contrarian take is that this is a filter typist, not an analyst. It saves clicks for people who already know what a Search Console regex should say. It cannot tell you which question is worth asking.
When should you leave the Performance report interface?
Leave when you need to hand the view to someone else, keep the numbers, or work beyond the table. The Help overview says the Share button grants access only to the current view of the report, and that values shown as ~ or - become zeros in the downloaded data. For very large sites, the BigQuery bulk export is the next step.
When the filtered table stops answering questions, the Search Console BigQuery export guide covers who needs it, the Google Cloud setup, and what the exported tables contain.
What should you build first with Search Console regex?
Build two filters this week. First, a brand regex in the Willow Tree style that lists every spelling your customers use. Second, a page regex for your most important section, anchored with ^ and with the domain dot escaped. Run each under Matches regex and Doesn't match regex, save both Share links, and you own a repeatable view.
The right answer for the retailer is a page regex for the Black Friday URLs, a date compare on Weekly granularity, and a clear note that the figure is filtered. None of that needs a new tool, only the Search Console regex filter and the advanced filtering and comparison Help page open in a second tab, with Waisberg's quick tips post and the RE2 syntax reference as backup. Now you know the mechanic, so which filter will you build first?
Frequently asked questions about Search Console regex filters
What is a Search Console regex filter?
A Search Console regex filter is a Performance report filter that uses a regular expression instead of a plain substring. Daniel Waisberg's June 2, 2021 Search Central Blog post defines a regular expression as "a sequence of characters that specifies a search pattern". You reach it by choosing Custom (regex) under a Queries or Pages filter, as the advanced filtering Help page describes. One filter can then cover brand misspellings, several folders, or a list of words, which a containing filter cannot do because that option accepts only a single substring.
Is regex in Search Console case-sensitive?
Not by default. The advanced filtering Help page says default regex matching is not case-sensitive, and that you can prepend (?-i) to the beginning of your expression for case-sensitive matches. Its example is that (?-i)AAA matches https://example.com/AAA but not https://example.com/aaa. The plain containing filter behaves the same way, since the page describes that match as "not case-sensitive, but is otherwise exact, including any spaces". My advice is to leave case off unless your URLs really differ by letter case, since the default already ignores it.
Why does my regex match queries I did not want?
Because matching is partial by default. The Help page states that your expression "can match anywhere in the target string unless you use ^ (start of string) or $ (end of string)". For example, the pattern ace also keeps "face" and "space" in the table. Anchor it as ^ace$ to match only that exact query, or use \bace\b, which the RE2 reference defines as an ASCII word boundary, so "ace hardware" still matches while "space" does not. Read the filtered list before you report anything from it.
Which regex syntax does Search Console use?
The advanced filtering Help page says "The RE2 syntax is used". Waisberg's June 2, 2021 post points readers to the RE2 syntax reference for all metacharacters supported by Search Console. In practice that means the common tools work: the dot, square brackets, star, plus, the vertical bar, \d, \s, ^ and $. The RE2 reference also lists features that are not supported, including lookahead, lookbehind, and possessive quantifiers. If a pattern copied from another tool fails in Search Console, one of those unsupported features is a likely culprit.
How do I exclude queries with regex in Search Console?
Choose Custom (regex), type the pattern, then pick Doesn't match regex from the secondary dropdown. The advanced filtering Help page puts it this way: "If you want to see all values except the specified values, choose Doesn't match regex", while Matches regex is the default. This negative option arrived with Daniel Waisberg's June 2, 2021 announcement, after what he describes as many requests to complete the picture. A common use is a brand pattern under Doesn't match regex, which leaves only non-branded demand in the table.
Why do the chart totals and the filtered table disagree?
Two documented reasons. The Search Console Help overview says the chart is aggregated by property while tables grouped by Pages or Search appearance are aggregated by page, so one query with two ranking URLs counts once in the chart and can appear on each URL's row in a Pages table. The advanced filtering page adds that filtering by query or URL "can affect the report totals due to data truncation and the omission of anonymized queries". Neither is an error, so label filtered numbers as filtered and the disagreement stops mattering to anyone reading your report.
Can I compare more than two countries or devices at once?
No. The advanced filtering Help page says that to see data for multiple devices, Search types, countries, or Search appearance types you must use a comparison "limited to two items". It also states you can have only one comparison at a time, and that adding a new comparison filter replaces the existing one. For three markets, run two compares one after another and note both results. If one value is very rare in a group, the page says that row shows ~ (not available) for that group.
Should I compare date ranges daily, weekly, or monthly?
Weekly or Monthly for anything longer than a few days. The advanced filtering page recommends those granularities when comparing two date ranges, because aggregating by week or month neutralizes the "day-of-the-week" effect of lining up a Monday against a Saturday. The Help overview adds that Weekly and Monthly smooth out daily fluctuations like those caused by weekends or holidays. My advice is to match the days of the week exactly for short compares and to wait before judging any change from a single week.
Does the AI-powered configuration tool replace learning regex?
No, and Google's own description explains why. The advanced filtering Help page calls it experimental, limits each user to 20 requests per day, and says it is visible only to a small percentage of Search Console users. It suggests filters that you must confirm, it cannot sort or export, and the page tells you to always review the filters applied, so you need to read the regex it writes. You still need to know what a good pattern looks like in order to check its work.
Where does a Search Console regex stop being enough?
When the table cannot hold your data or your team needs the raw rows. The Help overview says the Share button grants access only to the current view, and that exports turn values shown as ~ or - into zeros, so a download loses some meaning. For large sites, our BigQuery export guide linked above describes the bulk export as the route past the interface. Until you reach that point, one brand regex and one section regex answer most of the questions a marketing director will ask.