Intro
Separate order-modified searches in GSC so you can track explicit fulfilment or purchase wording in one view.
Use this regex to isolate queries that include order when users signal direct intent to place a purchase.
The Regex
How This Regex Works (Explained Simply)
\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 the standalone word order in a query.
- Captures a direct transactional modifier that often appears late in the journey.
- Helps you separate order-led intent from broader commercial demand.
What it does not match
- preorder gaming console - Preorder is not the standalone word order.
- best dog food deals - No order modifier appears.
Edge Cases
- Preorder and ordered are excluded unless you explicitly broaden the pattern.
- Because the regex is not anchored, order can appear anywhere in the query.
Example Matches Table
| Query | Match | Why |
|---|---|---|
| order protein powder online | Match | Contains order as a standalone word. |
| where to order dog food | Match | Order appears directly in the query. |
| preorder gaming console | No | Preorder is not the standalone word order. |
| best dog food deals | No | No order modifier 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
- Measure strong fulfilment-led purchase intent.
- Compare order terms with buy and ready-to-buy segments.
- Check whether product pages capture direct purchase wording.
Pro Tips
- Word boundaries matter here because preorder and ordered can create noise.
- This tends to be a strong bottom-funnel signal, so review the landing pages closely.
- Compare device splits if mobile users behave differently on order-led queries.
- Add purchase only if you want a broader direct-intent segment.
Variations
Broaden to purchase wording
Adds another direct transaction term when order alone is too tight.
Related Regex Recipes
Regex for "Buy" Queries
Use this regex to capture queries that include the standalone word buy when you want the clearest direct-purchase intent signal in Search Console.
Regex for Purchase Stage Queries
Use this regex to capture purchase-stage queries in GSC when users are close to converting and are using clear action-ready language.
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