Intro
Group overlapping query patterns in GSC when you want to review potential cannibalisation across similar intent families.
Use this regex as a practical cannibalisation review slice when similar modifiers are spread across multiple pages and need comparison.
The Regex
How This Regex Works (Explained Simply)
()
Parentheses group terms together so GSC treats them as one unit. That is what lets one regex cover several query variants in a single filter.
|
The pipe means OR. GSC will match any term on either side of the pipe, which is useful for variants, modifiers, or alternative phrases.
\b
Backslash-b marks a word boundary. It helps stop short terms from matching inside longer words in GSC queries.
GSC regex is case-insensitive by default, so capital letters do not need separate variants. GSC also uses partial matching by default, so the regex can match part of a longer query unless you anchor it with ^ or $.
What This Regex Does
- Matches recurring intent patterns often involved in cannibalisation reviews.
- Helps you isolate groups of similar queries that may split clicks across pages.
- Creates a workflow-friendly segment before deeper page comparison.
What it does not match
- canonical tag guide - Guide only matches in the variation.
- seo dashboard free - No grouped cannibalisation-review modifier appears.
Edge Cases
- Regex cannot prove cannibalisation on its own, because page overlap has to be examined separately.
- Some similar modifiers still map to legitimately different intents, so review carefully.
Example Matches Table
| Query | Match | Why |
|---|---|---|
| best seo dashboard | Match | Contains best, which often appears in overlapping commercial page sets. |
| what is canonical tag | Match | Contains what is, which can split across glossary and blog pages. |
| canonical tag guide | No | Guide only matches in the variation. |
| seo dashboard free | No | No grouped cannibalisation-review modifier appears. |
How to Use This in Google Search Console
- Open Performance and review queries with multiple relevant pages.
- Add a Query filter with Custom (regex).
- Paste the regex and click Apply.
- Compare the filtered query set against landing pages or exports.
When to Use This
- Review similar query families that may split across multiple pages.
- Organise cannibalisation checks by modifier or intent pattern.
- Support page-merging, consolidation, or internal-linking decisions.
Pro Tips
- Cannibalisation is a page-level issue, so regex is only the first filter, not the proof.
- Always compare multiple pages ranking for the same filtered query family.
- Use exports when you need to inspect page overlap at scale.
- Keep this segment narrow enough that the compared pages really share intent.
Variations
Include guide-led overlaps
Extends the overlap review set to another common content format.
Related Regex Recipes
Regex for Duplicate Intent Queries
Use this regex to organise duplicate-intent reviews in GSC by grouping common informational and evaluative formats that often overlap across content.
Regex for Overlapping Keywords
Use this regex to isolate overlapping keyword families in GSC when you want to review how related modifier sets distribute across pages.
CTA
Regex is only the first step. The real bottleneck is turning manual filters into a repeatable workflow your team actually uses. Spicy Metrics helps you move from ad hoc filtering to operational SEO workflows.
Move beyond manual regex work