GSC Regex Examples: 10 Search Console Filters You Can Reuse

Google Search Console regex filters are useful when one query or page filter is too narrow, but a giant export is too broad. A single expression can group brand variations, URL folders, product families, or query patterns so you can compare the segment that actually matters.

Search Console uses RE2 syntax for custom regex filters. Google currently documents three behaviors that are easy to miss:

• matching is partial by default;
• matching is case-insensitive by default;
• ^ and $ anchor a match to the start or end of the value.

You can build and test the examples below with the free KairoxBuild GSC Regex Builder & Tester before pasting them into Search Console.

1. Group several brand variations

Suppose people search for a brand with spaces, hyphens, or shorthand:

(?:kairoxbuild|kairox build|kairox)

Because Search Console uses partial matching by default, this can match longer queries such as kairoxbuild seo tools as well as the short brand terms.

This is useful when you want a branded query segment without maintaining several separate filters.

2. Match only exact brand queries

If the previous filter is too broad and you only want exact brand terms:

^(?:kairoxbuild|kairox build|kairox)$

The anchors change the behavior:

• ^ means the match must start at the beginning;
• $ means it must end at the end.

kairoxbuild matches. kairoxbuild tools does not.

Use this when you want a clean core-brand baseline rather than every query containing the brand.

3. Build a non-brand report

You do not need a different regex for non-brand analysis. Build the brand expression first, then choose Doesn't match regex in Search Console.

Example pattern:

(?:kairoxbuild|kairox build|kairox)

Filter mode:

Doesn't match regex

That keeps the logic readable: one maintained brand pattern, with Search Console deciding whether to include or exclude matches.

4. Group several informational query modifiers

To review queries that often signal a learning or research intent:

(?:how to|guide|tutorial|examples?)

The ? after s makes the final s optional, so example and examples both match.

Do not assume every matched query has identical intent. Regex creates a segment; it does not replace reading the actual queries.

5. Find comparison-style queries

A reusable comparison cluster:

(?:vs\.?|versus|alternative|alternatives|compare|comparison)

This can help isolate queries where users are comparing products, approaches, or tools.

The escaped dot in vs\.? means the literal period after vs is optional, so both vs and vs. can match.

6. Group URL folders

For page filters, you may want to analyze several site sections together:

^https://example\.com/(?:blog|guides|resources)/

This matches URLs beginning with:

https://example.com/blog/
https://example.com/guides/
https://example.com/resources/

The dots in the hostname are escaped because an unescaped . means “any single character” in regex.

For your own site, replace the hostname and folder names with the real canonical URL structure.

7. Match one exact URL folder

If you only want a single folder and everything below it:

^https://example\.com/blog/

This is often clearer than an overly clever expression. Regex is useful when it reduces repetitive filtering, not when it makes a simple rule harder to understand.

8. Group file or page endings

To find URLs ending in several common document types:

\.(?:pdf|docx?|xlsx?)$

This can match endings such as:

• .pdf
• .doc
• .docx
• .xls
• .xlsx

Use this only if those file types actually exist in your Search Console data. It is a segmentation example, not a recommendation to index documents by default.

9. Force case-sensitive matching

Search Console regex matching is case-insensitive by default. Google documents (?-i) as the prefix for case-sensitive matching.

Example:

(?-i)^API$

This can distinguish API from api when that distinction genuinely matters.

Most SEO segmentation does not need case-sensitive matching, so leave the default behavior alone unless you have a specific reason.

10. Group repeated naming patterns safely

Imagine a site has product pages with predictable paths:

^https://example\.com/tools/(?:seo|analytics|content)-[a-z0-9-]+$

This can match URLs such as:

https://example.com/tools/seo-audit
https://example.com/tools/analytics-dashboard
https://example.com/tools/content-brief

The important idea is not the exact expression. It is to model a stable URL naming rule rather than paste dozens of individual URLs into separate filters.

A practical workflow for building GSC regex filters

A safe workflow is:

1. Write down the exact queries or URLs you want included.
2. Decide whether the rule is partial, starts-with, ends-with, or exact.
3. Escape literal regex characters such as . when they should not act as operators.
4. Test the expression against both positive and negative examples.
5. Paste it into Search Console and verify the resulting rows before using the segment in a report.

The GSC Regex Builder & Tester automates the repetitive part: paste one value per line, choose the match mode, then test the generated expression against sample queries or URLs.

Common mistakes

Forgetting that partial matching is the default

This expression:

seo

can match any value containing seo, not only the exact query seo.

Use:

^seo$

when you truly mean an exact value.

Forgetting to escape dots in URLs

This:

example.com

uses . as a wildcard.

This is more precise:

example\.com

Building one enormous expression

A huge regex that mixes brand, country, template, intent, and product logic becomes difficult to review. Prefer several understandable filters if the segments answer different questions.

Assuming a browser regex tester is identical to RE2

JavaScript regex engines support constructs that RE2 does not. KairoxBuild blocks common unsupported constructs such as lookarounds and backreferences, but Search Console remains the final validator.

Which filter should you build first?

For most SEO reviews, start with one of these:

• branded vs non-branded queries;
• one important URL folder;
• comparison or informational query modifiers;
• a product or service family with several naming variations.

Then compare clicks, impressions, CTR, and trend direction inside that segment instead of staring at one site-wide average.

If the next problem is deciding which queries or pages deserve optimization first, use the GSC Opportunity Finder or read How to Find Striking-Distance SEO Opportunities in Google Search Console.

If one query keeps surfacing multiple URLs, that is a different review problem. Use the Keyword Cannibalization Checker with combined query + page Search Console data before consolidating or redirecting anything.

Sources

Google documents Search Console custom regex behavior, RE2 syntax, partial matching, include/exclude filters, anchors, and case sensitivity in its advanced filtering guidance and Search Console performance report documentation.