GSC Regex Tester
Test Search Console regex filters against your own URLs or queries, with RE2 rules applied.
Runs locally in your browser. Your input is never sent anywhere.
How Search Console actually matches
Search Console uses RE2, not JavaScript regex, and two of its defaults surprise people. This tool applies both, so what you see here is what GSC will do.
- Case-insensitive by default.
/GUIDES/matches/guides/foo. Prefix the pattern with(?-i)to force a case-sensitive match. - Partial match by default. The pattern can match anywhere in the
value. Use
^and$to anchor it to the start or end.
What RE2 will not run
RE2 has no lookaheads ((?=…), (?!…)), lookbehinds,
backreferences (\1) or atomic groups. JavaScript accepts all of them,
so a tester built on JavaScript alone would happily show you results that Search
Console can never reproduce. This one refuses those patterns instead, and tells you
which character is the problem.
Filtering pages or queries
The same regex works for both. In the Performance report, add a filter, choose Page or Query, then Custom (regex). Paste a sample of real URLs or queries above to check the pattern catches what you expect before you commit to it.
Examples
| Pattern | Matches |
|---|---|
/guides/ | any URL containing that path segment |
^/news/ | paths beginning /news/ |
\.html$ | URLs ending in .html |
/(guides|reviews)/ | either section |
^(who|what|how)\b | question-style queries |
(?-i)AAA | AAA but not aaa |