Intro
Create a repeatable cannibalisation workflow in GSC by filtering a shared intent family, then reviewing how many different pages receive impressions and clicks for the same query theme.
Use this regex to isolate one shared commercial-intent family, then inspect which pages are competing for overlapping queries inside GSC exports.
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.
?
The question mark usually makes the previous character or group optional. That is handy when a query modifier appears inconsistently.
\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 a query family that often triggers page overlap and cannibalisation.
- Creates a useful source set for overlap analysis.
- Helps standardise cannibalisation reviews around one repeatable process.
What it does not match
- ga4 reporting alternatives - Alternatives only matches if you use the variation.
- how to use ga4 reports - This is informational rather than shortlist or overlap-prone commercial intent.
Edge Cases
- A shared regex family only points you towards possible overlap; true cannibalisation needs page-level review.
- Some overlap is intentional, especially when different page formats target slightly different stages of the same topic.
Example Matches Table
| Query | Match | Why |
|---|---|---|
| best seo dashboards | Match | Best is one of the grouped overlap-prone modifiers. |
| ga4 reporting comparison | Match | Comparison is included in the cannibalisation source set. |
| ga4 reporting alternatives | No | Alternatives only matches if you use the variation. |
| how to use ga4 reports | No | This is informational rather than shortlist or overlap-prone commercial intent. |
How to Use This in Google Search Console
- Open Performance and go to Search results.
- Add a Query filter with Custom (regex) and paste the regex.
- Export the filtered queries with page data.
- Look for repeated query themes or exact queries associated with multiple pages.
- Review whether the overlap is intentional, then consolidate, retarget, or internally link as needed.
When to Use This
- Surface overlapping pages inside one intent family.
- Build a repeatable cannibalisation review process from GSC exports.
- Prioritise consolidation or retargeting work where multiple pages compete.
Pro Tips
- Regex does not prove cannibalisation; it narrows the query family before you inspect page overlap.
- Use exports with both query and page dimensions so you can actually see the competing URLs.
- Review whether the overlap is healthy intent coverage before treating it as a problem.
- Add alternatives if your commercial landscape relies heavily on that modifier.
Variations
Include alternatives overlap
Adds another overlap-prone commercial modifier to the workflow.
Related Regex Recipes
Regex for Keyword Cannibalisation Patterns
Use this regex as a practical cannibalisation review slice when similar modifiers are spread across multiple pages and need comparison.
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