Guide 09
How to Use Regex Filters in Search Console for Rank Tracking
Ready-to-paste RE2 patterns for questions, brand terms, long-tail queries and page groups.
Short answer
In the Performance report choose Add filter, then Query or Page, then Custom (regex), and paste an RE2 pattern; matching is partial and not case-sensitive by default, and you can switch to Doesn't match regex to exclude terms.
Key takeaways
- Search Console regex filters use Google's RE2 syntax and work on the Query and Page dimensions.
- Matching is partial by default, so add ^ and $ when you need the whole query or URL to match.
- Matching ignores case by default; start a pattern with (?-i) when case matters.
- Doesn't match regex is the quickest way to strip branded searches out of your rank tracking.
The Queries table in Search Console gets long fast. Even a small site can show hundreds of searches, most of them variations of the same few ideas. Regex filters cut that list into groups you can actually track: questions, branded searches, long phrases, one section of the site. You do not need to be a programmer to use them. A few patterns cover most of what a small site needs.
How do you add a regex filter in Search Console?
Open Performance, click Add filter, pick Query or Page, then choose Custom (regex) and paste your pattern.
- Go to Performance and then Search results.
- Click + Add filter and choose Query (or Page for URLs).
- Open the dropdown and pick Custom (regex).
- Choose Matches regex or Doesn't match regex.
- Paste the pattern and click Apply.
The chart and every tab update to show only the matching data. Google's help page on advanced filtering lists these options and notes that regex works on the Query and Page dimensions.
What rules does the regex follow?
Search Console uses RE2 syntax, matches any part of the text by default and ignores letter case unless you tell it otherwise.
Three rules explain most surprises:
- Partial match. The pattern
pricematches "price", "prices" and "laptop price list". Use^to anchor the start and$to anchor the end. - No case sensitivity.
seoandSEOmatch the same queries. Put(?-i)at the start if you need an exact case. - RE2 only. Lookaheads and backreferences are not supported, so patterns copied from other tools sometimes fail.
The | character means "or", which is the one you will use most.
Which patterns are useful for rank tracking?
Start with a few groups: questions, non-branded searches, long-tail queries, comparisons and site sections.
Question searches (Query, Matches regex):
^(how|what|why|when|where|which|who|can|does|is|are|should)\b
Non-branded searches (Query, Doesn't match regex):
tweeted ?ranks|tweetedranks
Long-tail queries of five words or more (Query, Matches regex):
^(\S+\s+){4,}\S+$
Comparison searches (Query, Matches regex):
\bvs\b|versus|compare|alternative
One site section (Page, Matches regex): /blog/
Replace the brand pattern with your own name and its common misspellings. If your brand is two words, the ? after the space makes the space optional, so both "tweeted ranks" and "tweetedranks" are caught.
How do these filters help you track rankings?
They turn a noisy site-wide average into a few stable groups whose average position you can log every week.
Site-wide average position mixes your brand name, where you rank first, with hundreds of queries where you rank 40th. A single new low-ranking query can drag the average down without anything getting worse. Filtering removes that noise:
- The non-branded filter shows how you rank for people who did not already know your name.
- The question filter shows how your guides perform, since most guides answer questions.
- The long-tail filter often reveals pages that rank well for specific phrasing, a hint about what to write next.
- A Page filter on one folder shows whether a section is gaining or losing after you update it.
Write each group's average position into the free rank log as if it were a keyword, for example "non-branded" or "questions". After a few weeks you get a trend line for each group, which is far easier to read than one line for everything. Our weekly rank report guide shows how to fit this into a 15-minute routine.
What mistakes should you avoid?
The big ones are forgetting that matching is partial, mixing branded and non-branded data, and comparing groups built with different filters.
- A pattern like
aimatches "email", "paint" and "detail". Wrap short words in\bword boundaries:\bai\b. - An unanchored Page filter such as
/blogalso matches/blog-archive/. Use/blog/with the trailing slash. - Changing the pattern halfway through a month breaks the trend. Keep a note of the exact pattern for each group.
- Comparing a filtered week against an unfiltered week is meaningless. Keep the country, device and search type filters identical too.
Can regex help when you check positions by hand?
Yes, indirectly: it tells you which queries are worth checking, so your manual searches go where they matter.
A manual search shows one snapshot that depends on your location and device. Use the regex groups to find the handful of non-branded queries with the most impressions, then check those by hand now and then. If you have not set up Search Console yet, start with our guide on checking rankings for free with Search Console.
Questions
- What is RE2?
- RE2 is the regular expression library Google uses in Search Console and other products. It supports the common building blocks such as |, ^, $, character classes and counted repeats, but leaves out some features found elsewhere, such as backreferences and lookaheads.
- Can I combine a regex filter with other filters?
- Yes. A regex on Query can sit alongside filters for country, device, page or date range. Each filter narrows the data further, so remove the ones you do not need before comparing results.
- Why does my regex return no rows?
- The usual causes are an unsupported feature such as a lookahead, an anchor that is too strict, or a pattern that expects capital letters after you added (?-i). Test the pattern on a few real queries from the table first.
- Can I save a regex filter?
- There is no saved-filter button. Filters generally carry over in the report's page address, so a bookmark of the filtered report often works; keep your patterns in a note as well so you can paste them again.
Sources
- Search Console Help: Advanced filtering and comparison
- Search Console Help: Performance report (Search results)
- RE2 syntax reference (Google, GitHub)
Read next
- How to Check Your Google Rankings for Free with Search ConsoleSet up Search Console, open the Performance report and read your positions query by query.
- How to Build a Simple Weekly Rank ReportA 15-minute routine and a one-page template that turns Search Console numbers into a report you'll actually read.