Intro
Capture location-plus-service searches in GSC so you can report on the strongest structured local intent in one reusable segment.
Use this regex to isolate location-plus-service searches in GSC when users combine a place and a service type in the same query.
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.
.*
Dot-star means any characters can appear here. In GSC it is commonly used when you want to allow extra words before or after a core phrase.
\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 queries containing both a grouped service term and a grouped location term.
- Works whether the service appears before or after the location.
- Creates a very practical local-intent segment for service-area reporting.
What it does not match
- leeds locksmith - This only matches in the broader variation.
- best plumber near me - Contains a service term, but no grouped city name.
Edge Cases
- This is a template pattern, so both the service list and the location list should be customised.
- Longer grouped lists can become hard to maintain, so split them into smaller regional packs when needed.
Example Matches Table
| Query | Match | Why |
|---|---|---|
| plumber london | Match | Contains a grouped service term and a grouped city term. |
| manchester dentist | Match | Matches because the city comes before the service term. |
| leeds locksmith | No | This only matches in the broader variation. |
| best plumber near me | No | Contains a service term, but no grouped city name. |
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
- Track the clearest local service-intent combinations.
- Benchmark local landing pages against their actual place-plus-service demand.
- Find gaps where important service-location pairs have weak visibility.
Pro Tips
- This is a strong workflow recipe because it combines two grouped sets in one view.
- Keep the service and city lists small enough to stay maintainable and accurate.
- Expand carefully because each added service or location multiplies the query space.
- Use this to prioritise the next local landing pages you build or improve.
Variations
Add more services and cities
Expands both grouped sets so you can cover more location-service combinations.
Related Regex Recipes
Regex for City-Based Queries
Use this regex to isolate city-based searches in GSC when your reporting needs to focus on explicit city modifiers in the query.
Regex for Local Service Queries
Use this regex to isolate local service-type searches in GSC when you want a service-category segment that can be combined with location filters later.
CTA
Manual regex checks in GSC are useful, but they do not scale well across properties, date ranges, and recurring reporting. Spicy Metrics turns repeat regex workflows into faster monitoring and clearer action.
See how Spicy Metrics scales this