Fill in these first
- Brand names and misspellings: [e.g. examplename, example name, exmplename]
- Topics to group: [e.g. pricing, comparisons, how-to, city names]
- Sample queries from the report: [paste 30 to 100 queries]
- Questions to answer: [e.g. how much traffic is non-branded, which question searches show us but get no clicks]
- Language of the queries: [e.g. English, Hinglish mixed with English]
Task
Write one regular expression per reporting need, using the syntax the Search Console filter accepts, and prove each one against the sample queries.
Output format
- | Need | Regex | Filter setting: matches regex or does not match regex | What it catches |
- For each regex, three sample queries it matches and two it correctly leaves out, taken from the inputs.
- A short note on how to save the view or compare date ranges with the filter.
Patterns to include
- Questions: queries starting with or containing who, what, when, where, why, how, which, can, does, is, should.
- Branded: every brand spelling given, with optional spaces.
- Non-branded: the branded pattern used with "does not match regex".
- Long-tail: queries of five words or more.
- One pattern per topic group.
Rules
- The filter uses RE2 syntax: no lookaheads or lookbehinds. Use the setting "does not match regex" for exclusions instead.
- Start each pattern with (?i) so it ignores capital letters either way.
- Keep each pattern under the filter's length limit and readable; split very long ones.
- Flag any sample query that the patterns sort into the wrong group.
Example
Long-tail: ^(\S+\s+){4,}\S+$






