Intro
Group equivalent modifiers across several languages in GSC so you can track international query intent without building separate filters for each language.
Use this regex to capture a controlled set of equivalent pricing words across multiple languages in one Search Console filter.
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 several language variants of the same pricing concept.
- Lets you report on one intent family across markets.
- Works best with a tightly controlled term list.
What it does not match
- prix outil seo - Prix only matches if you use the variation.
- best seo tools - No grouped pricing term appears.
Edge Cases
- This is a practical grouped-term recipe, not a full international keyword model.
- The chosen words depend on your target markets, so adapt the list before using it as a production report.
Example Matches Table
| Query | Match | Why |
|---|---|---|
| seo tool precio | Match | Precio is included in the multi-language group. |
| preise fur seo tool | Match | Preise is one of the listed variants. |
| prix outil seo | No | Prix only matches if you use the variation. |
| best seo tools | No | No grouped pricing term appears. |
How to Use This in Google Search Console
- Open Performance and go to Search results.
- Click Add filter and choose Query.
- Select Custom (regex).
- Paste the regex and click Apply.
When to Use This
- Create one pricing-intent view across several markets.
- Reduce the need for language-specific filters for simple reporting questions.
- Compare international demand for one modifier family.
Pro Tips
- Keep multi-language patterns narrow and concept-led rather than trying to cover every translation in one regex.
- Use page or country filters in GSC alongside the regex for cleaner market-level analysis.
- Review accents and character variants if they matter in your markets.
- Split languages back out when you need diagnostic analysis rather than high-level reporting.
Variations
Include French pricing
Adds another common pricing term for multilingual reporting.
Related Regex Recipes
Regex for Brand + Pricing Queries
Use this regex to isolate branded pricing demand in GSC when users already know the brand and want commercial information.
Regex for SaaS Pricing Queries
Use this regex to capture the core pricing modifiers that show up when SaaS buyers are evaluating cost and packaging.
CTA
Regex is powerful in GSC, but manual filtering still leaves you exporting, comparing, and rebuilding the same views. Spicy Metrics turns those segments into reporting your team can reuse.
Turn regex into repeatable reporting