\n for Search Console Performance reports, and we were delighted to see the community
\n reaction<\/a> to the announcement.\n<\/p>\n
\nWe were also interested in the feedback we received, as always, and we saw many requests to complete the picture by adding a negative match option
\n to the regular expression (regex) filter.\n<\/p>\n
\nThe good news is that starting today the Performance report filter supports both matching and not matching regex filters<\/strong>. The option \nWe also thought it would be helpful to provide some quick tips if you\u2019re just starting with regex.\n<\/p>\n \nFirst of all, what is<\/em> a regular expression? In a few words, it is a sequence of characters that specifies a search pattern. You can use it \nIf you\u2019re wondering when you should use regex as opposed to other filter types, here are a few examples when to use regex instead of other filters:\n<\/p>\n \nCheck the Search Console help center for common regular \nIf you have any questions or concerns, please reach out on the \n
\n is available through a secondary dropdown, which appears after picking the “Custom (regex)” option in the filter selector, as shown in the screenshot
\n below. Learn more about filtering search performance data<\/a>.\n<\/p>\n![\"Search](\"https:\/\/alienroad.com\/wp-content\/uploads\/kb-gorsel\/g-0411ff160b9d.png\" "\\"Search")
<\/p>\nQuick tips on using regex on Search Console<\/h2>\n
\n to create advanced filters to include or exclude more than just a word or a phrase. When using regex, you can use a number of metacharacters, which are
\n characters that have a special meaning, such as defining a search criteria. Check the RE2 regex
\n syntax reference<\/a> for a reference on all metacharacters supported by Search Console.\n<\/p>\n\n
\n including misspellings. This will inform you what type of queries each group is using and which section of your website is attracting each audience.
\n For example, if your company\u2019s names is Willow Tree<\/code><\/span>, you might want to create a filter for all variants like
\n this: willow tree|wilow tree|willowtree|willowtee<\/code><\/span> (the |<\/code> metacharacter represents an OR statement).<\/li>\n
\n understand what are common queries for each of your content areas. For example, if your URL structure is example.com\/\/[brand]\/[size]\/[color]<\/code><\/span>
\n and you’d like to view traffic leading to green shoes, but you don’t care about the brand or the size, you might use shoes\/.*\/green<\/code><\/span>
\n (.*<\/code> matches any character any number of times).<\/li>\n
\n For example, you might be interested in queries containing question words; a query filter what|how|when|why<\/code><\/span> might
\n show results that indicate your content should easily answer questions, maybe through an FAQ. Another example would be queries containing (or not)
\n transactional words such as buy|purchase|order<\/code><\/span>. This might also show which product names are more commonly or rarely used
\n with these expressions.<\/li>\n<\/ul>\n
\n expressions<\/a>. If you have any cool examples of what to use regex for, share them on Twitter using the hashtag #performanceregex<\/code>.\n<\/p>\n
\n Google Search Central Community<\/a> or on Twitter<\/a>.\n<\/p>\n