A Performance report can hold thousands of search queries, yet the rows that matter to your next content decision may be hard to spot. Google Search Console regex filters help group those rows by intent, brand, question format, word count, or page section without downloading and sorting every query manually.
For Malaysian business owners, this means clearer evidence for improving service pages, FAQs, blog topics, and conversion paths. Start with small patterns, verify the results, then use the findings to guide real website changes.
A direct answer for business owners
This feature lets you apply a custom regex rule to the Query or Page dimension in the performance report. Search Console uses RE2 syntax, which supports useful rules such as alternatives, word boundaries, anchors, and repetitions.
Use regex when a normal “contains” filter is too broad to isolate the intended search intent. For example, you can isolate every question-led query, remove searches for your own brand, or measure clicks to one site directory.
Search Console treats an unanchored regex as a partial match.
pricecan match anywhere in a query, while^price$matches the single-word query only.
This control matters when you use search data to decide which pages need expansion, consolidation, or clearer answers.
Apply a custom regex filter in the Performance report
Open Google Search Console and select Performance then Search results. Click + New, choose Query or Page, and select Custom (regex).
Next, choose either Matches regex or Doesn’t match regex, enter your pattern, and apply the filter. Google’s advanced filtering guidance confirms that these filters use RE2 and match partial strings by default.
Use the Query filter for customer wording and search intent. Use the Page filter when you need to compare a blog directory, product range, location pages, or service URLs.
Before you analyse clicks, impressions, CTR, and position, set a sensible date range. Digital marketers should use a three-month view, which often gives an SME a better sample than a seven-day snapshot. Then compare it with the preceding period only when seasonality does not distort the result.
RE2 syntax rules that prevent common errors
Regular expressions can look technical, but most SEO analysis uses a small set of metacharacters. A pipe | means “or”. Parentheses group alternatives. A caret ^ marks the beginning of text, while a dollar sign $ marks the end.
For example, seo|ppc matches a query containing either word. In contrast, ^seo$ matches only the one-word query “seo”. These metacharacters also affect pattern matching, so escape a dot as \. when matching a literal dot in a URL.
Quantifiers also help. Use + for one or more occurrences, * for zero or more, and {4,} for four or more repetitions of the item before it.
Search Console has a 4,096-character limit for a regex filter. However, short patterns are easier to test, explain, and maintain.
RE2 does not support lookaheads, lookbehinds, or backreferences. For negative matching, don’t build a complicated negative lookahead to exclude a brand. Choose Doesn’t match regex instead. Google’s Search Central update on negative regex matching confirms this inclusion and exclusion approach.
URLs are case-sensitive, so copy their structure carefully. Query data is generally shown in lowercase, but the (?i) flag can make a pattern case-insensitive where needed.
Regex patterns for useful SEO segments
These regex patterns are starting points for examining search intent. Check the filtered rows after every change because a valid expression can still group the wrong searches.
| SEO question | Regex pattern | How to apply it |
|---|---|---|
| Find question-led searches | `^(who | what |
| Identify purchase intent | `\b(buy | price |
| Exclude branded searches | `(?i)(pixelpro | pixel pro)` |
| Find five-word queries | ^(\S+\s+){4,}\S+$ | Query, Matches regex |
| Review a site section | ^https://pixelpro\.com\.my/services/ | Page, Matches regex |
Question queries often reveal a missing explanation or an FAQ gap, showing informational intent through long-tail queries. A Kuala Lumpur contractor, for example, may find searches beginning with “how” that point to concerns about project timing, materials, or permits. Those questions deserve direct, accurate answers on relevant service pages.
Patterns showing transactional intent can reveal visitors closer to a decision. The word “price” may signal a need for a pricing guide, quotation process, package comparison, or a clearer call button. Still, review each row before changing a page. Some terms can carry mixed intent.
For non-branded search analysis, exclude branded keywords and relevant keyword variations, including spelling variants, shortened business names, and product names only your company uses. That view shows whether your content attracts people who have not already chosen your business.
The page filter is equally useful. Change /services/ to /blog/, /products/, or a location folder to see which parts of your URL structure attract impressions and clicks.
Combine query and page filters for stronger findings
The best SEO analysis connects a query pattern to the pages receiving organic traffic. Use query and page filters to apply a question-query regex and a Page filter for /services/. This shows whether your commercial pages already answer customer concerns. If they do not, add concise answers near the relevant service details instead of publishing a disconnected blog post.
Likewise, apply a non-branded regex with a product or category-page filter. This separates existing customer interest from new demand and helps you judge whether category copy is doing its job.
For reliable data filtering, record every pattern in a shared measurement sheet with the date range, filters, clicks, impressions, CTR, and average position. Then export the filtered table to Google Sheets or CSV. If you build reports in Looker Studio, keep the exact regex beside the dashboard definition. Search Console interface filters do not automatically transfer into every dashboard connector.
These habits support more useful SEO services in Malaysia because recommendations can trace back to real search behaviour rather than a generic keyword list.
Use regex data to support AI SEO and answer-focused content
Regex does not create visibility in Google AI Overviews or other AI-powered search answers by itself. It reveals the questions, comparisons, and long-tail queries your audience already uses.
That insight can inform a clearer AI SEO content strategy alongside page structure, internal links, accurate entity references, technical SEO, and useful FAQ coverage. A page should identify the service, audience, location, and next step in plain language. For a Selangor clinic, education centre, B2B company, or eCommerce store, that clarity helps people and search systems understand the offer.
A trusted AI SEO agency should connect query patterns to business outcomes such as calls, WhatsApp enquiries, bookings, and sales. It should also show the limits of the data. Google Search Console tracks organic search performance, but it cannot prove a brand has appeared in every AI-generated answer.
For Malaysian firms, SEO Malaysia activity must remain grounded in measurable demand. A practical SEO audit checklist can help connect content gaps with technical issues, local landing pages, and conversion barriers.
Test and troubleshoot before reporting a result
Use a regex tester tool such as Regex101 to test a pattern against sample queries before applying it in Search Console. However, Regex101 may support advanced PCRE features that RE2 rejects.
Test the final expression in Search Console and inspect a sample of matching rows. When a pattern returns too much data, add anchors or word boundaries. When it returns nothing, check escaped characters, URL casing, spaces, and spelling variants. A literal dot in a domain must be written as \..
Keep each pattern focused on one decision. A huge expression may look efficient, yet it becomes difficult to audit when search performance changes.
Key takeaways:
- Start with question, transaction, brand, and page-section segments.
- Use
^and$when you need exact boundaries. - Choose negative matching for exclusions rather than unsupported lookaheads.
- Review the actual rows before turning regex findings into content changes.
Put query evidence behind your next SEO decision
Google Search Console regex filters turn a crowded report into smaller groups that answer practical questions. They can show where non-branded demand is growing, which service pages miss common questions, and whether long-tail queries justify a new content section.
If your business needs a clearer view of its website structure, content opportunities, and organic search data, speak with an SEO consultant about a practical review. Better analysis supports stronger pages, stronger enquiries, and more informed SEO decisions.
Frequently asked questions
How do I find the custom regex option in Search Console?
Go to Performance, open Search results, and click + New. Choose Query or Page, select Custom (regex), then choose Matches regex or Doesn’t match regex before applying the filter.
What regex syntax does Google Search Console use?
Search Console uses RE2 syntax. It supports anchors, alternatives, groups, character classes, and quantifiers. It doesn’t support lookaheads, lookbehinds, or backreferences.
How can I separate branded and non-branded traffic?
Create a Query filter with your business name and common variations, then select Doesn’t match regex. Review the remaining queries to understand non-branded search demand and identify content opportunities.
