Intro
Isolate documentation-style searches in GSC so you can track queries that should map to technical docs, setup guides, and reference material.
Use this regex to capture documentation-style query modifiers in GSC when users need structured reference or implementation guidance.
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 common technical-documentation modifiers.
- Creates a clean segment for reference-led content demand.
- Helps you compare documentation intent against support, FAQ, and tutorial traffic.
What it does not match
- developer regex guide - Developer only matches in the variation.
- regex tutorial - Tutorial is educational, but it does not use a documentation-style modifier.
Edge Cases
- Documentation intent can overlap with support and tutorial demand, especially on technical topics.
- Docs and api terms are useful proxies, but reference-style searches can use many other words too.
Example Matches Table
| Query | Match | Why |
|---|---|---|
| search console api docs | Match | Contains docs and api, both of which fit documentation-style intent. |
| regex manual for gsc | Match | Contains manual, which is included in the grouped documentation modifiers. |
| developer regex guide | No | Developer only matches in the variation. |
| regex tutorial | No | Tutorial is educational, but it does not use a documentation-style modifier. |
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 technical reference demand in one segment.
- Audit whether docs and developer content capture the right queries.
- Compare documentation demand against support and tutorial traffic.
Pro Tips
- Docs-style queries often deserve stronger internal linking between reference and tutorial content.
- API modifiers can behave differently from general manual or docs searches, so split them later if needed.
- Use this with page filters to catch documentation-intent queries landing on blog posts instead.
- Keep developer wording in a variation if you want the base segment to stay focused.
Variations
Include developer wording
Broadens the docs-style segment with another common technical modifier.
Related Regex Recipes
Regex for Support / Help Queries
Use this regex to capture support and help-oriented queries in GSC when users are trying to solve a problem rather than evaluate or buy.
Regex for Tool / Feature Queries
Use this regex to capture tool- and feature-style query modifiers in GSC when searchers are looking for product capabilities rather than help or educational content.
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