Add to Preferred Sources
A search console regex guide for SEO cuts straight to the problem: Google Search Console gives South African businesses thousands of queries in the Performance report, and "contains" filters can handle one word at a time. Regular expressions — regex — let you match entire families of queries in a single pattern, turning an overwhelming data dump into actionable segments you can act on this week. If you are already using SEO in South Africa as a growth channel, mastering GSC's regex filter is the fastest free upgrade available.
This search console regex guide for seo covers the filter mechanics, the seven patterns that surface real opportunities, and the South Africa–specific variants — city modifiers, pricing intent, local qualifiers — that generic tutorials skip entirely.
Quick Answer
Google Search Console's Custom (regex) filter, found under Performance → Search Results → +New filter → Query or Page, lets you match multiple search terms at once using RE2 syntax. A solid search console regex guide for SEO starts with seven patterns: question queries, local intent, transactional intent, comparison intent, long-tail queries, informational intent, and parameterised URL detection. All query data in GSC is lowercase, so patterns are case-insensitive by default. Test every pattern on regex101.com (Golang flavour) before applying it in Search Console.
Jump to a Section
Not Sure What Your GSC Data Is Telling You?
Send us your domain and we will walk through the top query segments your current filters are missing — no tools subscription required.
Get a Free GSC ReviewWhat Is Regex in Google Search Console?
Regex in Google Search Console is a custom filter mode that uses regular expressions — pattern-matching syntax — to group or exclude queries and page URLs that share a structure, rather than an exact string. Where a standard "contains" filter finds queries with the word johannesburg, a regex pattern finds every query containing any of six city names simultaneously, giving you a single chart for all local-intent traffic.
GSC uses RE2 syntax — Google's own regex engine, which is close to but not identical to Python or JavaScript regex. The practical differences: RE2 does not support lookaheads, lookbehinds, or backreferences. Everything else you are likely to need — anchors, character classes, quantifiers, alternation with the pipe character — works as expected. The filter accepts patterns up to 4,096 characters, which is large enough to list every city modifier in South Africa and still have room to spare.
Key Limitation to Know
Regex filters apply only to the Query and Page dimensions in the Performance report. You cannot apply regex to Country, Device, or Search Appearance. When you add any filter, GSC excludes some anonymised queries from the total — so filtered impression and click counts will be lower than the unfiltered baseline. This is expected behaviour; it is not a data error.
How to Access the Regex Filter in Google Search Console
The regex filter is buried two clicks deep in the Performance report. Here is the exact path:
- Open Search Console and click Performance in the left sidebar.
- Click Search results (the default tab).
- Click + New above the chart.
- Select Query (to filter by search term) or Page (to filter by URL).
- In the dropdown, choose Custom (regex).
- Choose Matches regex or Doesn't match regex — the "doesn't match" version is useful for excluding branded queries or irrelevant sections of the site.
- Type or paste your pattern, then click Apply.
The chart and table update immediately to show only data matching your pattern. Google's official documentation on Search Console advanced filtering and comparison covers all filter types, including how to layer multiple filters — for example, Country = South Africa AND Query matches a regex pattern — for precise market-level analysis.
A Note on Case
All query data in Search Console is stored in lowercase. Your patterns are
effectively case-insensitive for Query filters. If you need explicit
case-sensitive matching (for URL filters where casing matters), prepend (?-i) to your pattern. To force case-insensitivity
explicitly, use (?i) at the start.
Search Console Regex Guide for SEO: 7 Proven Patterns
The table below covers the seven patterns with the highest practical return for South African sites. Each can be copied directly into the regex filter field. The SA-specific column shows how to adapt the pattern for the local market — city modifiers, pricing language, and market-specific qualifiers are the three main levers.
| # | Pattern | What It Matches | SA Application |
|---|---|---|---|
| 1 | ^(what|how|why|when|where|who|can|is|are|does|should) | Question-form queries | Find featured snippet and FAQ content opportunities |
| 2 | (johannesburg|joburg|cape town|durban|pretoria|sandton|south africa) | Local intent queries with SA city or country modifier | Measure city-level performance; see which locations drive traffic vs. which need pages |
| 3 | (price|cost|how much|buy|order|cheap|affordable) | Transactional and pricing intent | Identify buyers reaching top-of-funnel content; redirect them to pricing or product pages |
| 4 | (best|vs|versus|compare|alternative|alternatives|review) | Comparison and commercial investigation | Spot demand for comparison content you have not yet written |
| 5 | (\w+\s){4,}\w+ | Long-tail queries with five or more words | Surface highly specific intent; long-tail queries typically attract visitors closer to a decision, and competition in SA niche markets is lower |
| 6 | (guide|tutorial|tips|checklist|how to|examples) | Informational and educational intent | Identify informational queries your blog should be ranking for; cross-reference against topical authority gaps in your content cluster |
| 7 | (page=\d+|filter=.+|\?.*=) | Parameterised and faceted URLs | Technical audit: find paginated or filtered URLs appearing in organic results — a common crawl budget issue on SA ecommerce sites |
Building the South Africa City-Modifier Pattern
South African sites often rank for the same service across multiple cities without knowing which location drives the most organic demand. Paste this pattern into a Query filter to see all city-intent impressions in one view:
(johannesburg|joburg|cape town|durban|pretoria|sandton|centurion|bloemfontein|port elizabeth|gqeberha)Sort the resulting query table by Impressions descending. Cities near the top but with low CTR are underserved by your current page titles and descriptions — a fast win that does not require new content.
They add a separate "contains" filter for each city — seven separate sessions in Search Console, no combined view, no easy comparison. The alternation pipe in regex eliminates all of that in a single pattern.
Combining Patterns with Alternation
The pipe character | means OR in RE2 syntax. You can chain
as many alternatives as the 4,096-character limit allows. To find every
question-form query that also contains a city name, layer two separate
filters: one regex filter for the question pattern, a second for the
city-modifier pattern. GSC applies them with AND logic — you will see
only queries that satisfy both.
How to Filter Page URLs with Regex in Search Console
Query filters tell you what people searched for. Page URL filters tell you which pages attracted those searches. Used together, they give you a complete picture of any segment. For South African sites with a blog, product catalogue, or service page hierarchy, page-level regex cuts analysis time significantly when you are tracking declining pages or auditing a specific section of the site.
| Use Case | Pattern | What It Isolates |
|---|---|---|
| Blog performance only | ^https://yourdomain\.co\.za/blog/ | All blog posts; exclude service and home pages from the view |
| Service pages only | ^https://yourdomain\.co\.za/(services|service)/ | Service directory pages for conversion-focused analysis |
| Parameterised URLs | \?.*= | Any URL with query parameters — flag for canonicalisation review |
| Exclude utility pages | terms-of-service|privacy-policy|contact (as "doesn't match") | Focus the report on pages that drive organic value |
| Faceted navigation | (page=\d+|filter=.+|sort=.+) | Ecommerce filter/sort URLs that may be accumulating clicks |
The parameterised URL pattern is particularly relevant for South African ecommerce stores running on WooCommerce or Shopify, where faceted navigation (colour, size, brand filter pages) can generate thousands of indexable URLs. If these URLs appear in Search Console's Page report with clicks, they are either receiving traffic you did not intend, or competing with canonical product pages. This connects directly to crawlability and crawl budget — every parameterised URL Google indexes is a page it might not crawl instead.
How to Test Your Regex Patterns Before Applying Them
GSC applies regex patterns live — there is no preview mode. A pattern with a syntax error returns no results (not an error message), making it easy to assume your data is genuinely empty when the pattern is simply malformed. Test first. If you would rather hand Search Console analysis to a specialist, our founder-led SEO support starts with a free audit and runs on a flat monthly retainer.
The recommended tool is regex101.com — set the flavour to Golang, which uses RE2, the same
engine GSC uses. Paste a few sample queries into the test string field and
confirm your pattern matches what you expect before copying it into the
filter. For URL patterns, the dot in your domain name needs to be escaped as \. — an unescaped dot in regex matches any character, so example.co.za would also match exampleXcoYza.
Three Common Regex Mistakes in GSC
- Unescaped dots in URL filters: Always write
example\.co\.za, notexample.co.za. - Using lookaheads or lookbehinds: RE2 does not support them. If a pattern works in Python but not GSC, this is almost always why.
- Expecting anchors by default: Without
^(start) or$(end), GSC does a partial match. The patternseomatches "seo", "seo agency", "local seo tips", and anything else containing those three letters. Add anchors when you need precision.
Once your patterns are validated and running in GSC, combine them with date comparison to track how a segment moves over time — regex filter plus date comparison is the core of any structured SEO rank tracking workflow that does not rely entirely on third-party rank trackers.
Spending Hours in GSC Without Clear Answers?
We can set up a structured query segmentation framework for your domain — intent buckets, city-modifier views, and URL-level filters — so you leave every GSC session with an action list, not just a chart.
Book a GSC Strategy SessionHow Regex Findings Feed Into Real SEO Decisions
A useful search console regex guide for seo does not stop at syntax — every filter you run should connect to a specific decision. Here is how the seven patterns above map to concrete actions:
- Question queries with low CTR: You rank for the question but your title is not phrased as an answer. Rewrite the meta title to mirror the question. If the page already has a solid answer, adding structured FAQ markup can push it into the featured snippet position.
- City modifiers with high impressions, low clicks: Google is matching the page but the title and description do not signal local relevance. Add the city name to the meta title or create a dedicated city-specific landing page.
- Transactional queries landing on blog posts: You are capturing commercial intent on informational pages. Either add a conversion-focused section to the post or create a separate service or product page and internally link to it.
- Comparison queries you do not rank for at all: Zero impressions means you have no page targeting that intent. Build a content brief for a dedicated comparison or "vs" post.
- Parameterised URLs appearing with clicks: Audit canonicalisation and either block the URLs in robots.txt or add canonical tags pointing to the primary page. Log this as a task in your SEO fix priority framework.
- Long-tail queries with page 2–3 rankings: These are the lowest-effort ranking improvements available. The page already exists and Google considers it relevant — a targeted content expansion or internal link from a higher-authority page is often enough to push it to page one. This is core to diagnosing keyword cannibalisation too, because long-tail regex views reveal when two pages split the same intent.
Ready for a Full Organic Opportunity Audit?
We will review your Search Console data, build a segmented query framework, and return a prioritised list of ranking improvements — timed against realistic South African traffic timelines.
Request an Organic AuditWhy South African Businesses Choose Growth Pulse Media for SEO
GPM was founded by Dirk, who scaled a South African ecommerce business from scratch before building the agency. That background means every analytical technique — including GSC regex segmentation — gets applied with an operator's eye: what does this data mean for a South African buyer, and what is the cheapest path to a better outcome?
We work with a deliberately limited number of clients at any one time, which means senior attention on every account. When we build a regex framework for a client's Search Console, it is not a template — it accounts for their specific URL structure, the city modifiers relevant to their market (whether that is Sandton professional services or Cape Town hospitality), and the intent patterns their target buyers actually use.
South African search behaviour is not a copy of UK or US behaviour. Local phrasing, Rand-based pricing queries, and city-level competition dynamics require patterns built for this market — not patterns imported from a global tutorial.
Our SEO South Africa service covers the full stack — technical audit, content strategy, and performance tracking through structured Search Console segmentation — not a tool subscription with auto-generated recommendations.
Who This Approach Is NOT For
Regex segmentation requires enough data for patterns to be meaningful. If your total organic click volume is small, splitting it further will produce segments too thin to act on — a handful of impressions in a pattern tells you almost nothing. Build overall organic traffic first; segment analysis is a scale tool.
Every regex pattern surfaces an insight that requires a content or technical change to act on. If your team does not have the capacity to implement updates, building elaborate query filters only adds complexity. Prioritise execution bandwidth before analytical sophistication.
URL-level regex filtering is most powerful on sites with clear directory structures — /blog/, /services/, /products/. On a site where all pages live in the root directory with no logical hierarchy, the URL patterns in this guide will not segment usefully. Fix the URL structure first.
Search Console regex shows you what Google has already indexed and what queries are driving impressions. It does not reveal crawl errors, indexation gaps, or structural problems that prevent pages from ranking. Pair it with a technical SEO audit for a complete picture.
Frequently Asked Questions
Does Google Search Console regex use the same syntax as Python or JavaScript?
No. Search Console uses RE2 syntax, Google's proprietary regex engine. RE2 supports most common operators — anchors, character classes, quantifiers, alternation — but explicitly does not support lookaheads, lookbehinds, or backreferences. Test your patterns on regex101.com with the Golang flavour selected, which runs the same RE2 engine.
Can I use regex to filter by country or device in Search Console?
No. The regex (Custom) filter is available only for the Query and Page dimensions in the Performance report. Country and Device filters use standard dropdown selectors, not regex. To combine geographic and query analysis, apply a Country filter using the standard selector alongside a regex Query filter — GSC will apply both with AND logic.
Why do my click and impression totals drop when I apply a regex filter?
This is expected. When you apply any filter in Search Console — regex or otherwise — GSC excludes some anonymised query data from the results. The filtered total will therefore be lower than the unfiltered baseline even if your pattern is theoretically matching everything. Use the unfiltered total as context, not as a number to reconcile exactly.
How do I use a regex pattern to find keyword cannibalisation in Search Console?
Apply a Query filter matching the focus keyword of the page you are
investigating — for example, .*plumber johannesburg.* — then
switch the grouping to Page. If more than one URL appears with meaningful
impression share, you have a cannibalisation signal. Review both URLs to
determine which page Google should canonically own the term, then consolidate
or differentiate content accordingly.
What is the character limit for a regex pattern in Search Console?
Search Console accepts regex patterns up to 4,096 characters. In practice,
even a comprehensive SA city-modifier pattern — all major cities, common
abbreviations, and common misspellings — stays well under 500 characters.
If you are approaching the limit, use shorter alternation forms where
possible: example.co.za/(aa|bb) instead of separate full
URL patterns for each path.
Get Senior SEO Attention on Your Search Console Data
Growth Pulse Media works with South African businesses that are serious about organic growth — not just ranking reports. We build structured query frameworks using the exact techniques in this guide, tailored to your URL structure, city footprint, and content gaps.
No obligation — we will get back to you within 24 hours.
Talk to a South African SEO Strategist