Intro
Isolate blog-style searches in GSC so you can measure demand that leans towards articles, posts, and editorial content formats.
Use this regex to capture blog-style query modifiers in GSC when users appear to be looking for editorial or article-led content.
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 editorial-format terms such as blog, post, and article.
- Creates a practical segment for article-style content demand.
- Helps you compare editorial queries against support, docs, and product-led page types.
What it does not match
- seo reporting news - News only matches in the variation.
- search console pricing - No blog-style page-type modifier appears.
Edge Cases
- Many blog-driven queries do not use explicit blog-style modifiers, so treat this as one useful segment rather than the whole picture.
- Article and post can occasionally appear in non-content contexts, so review matched queries.
Example Matches Table
| Query | Match | Why |
|---|---|---|
| search console regex blog | Match | Contains blog as an editorial-format modifier. |
| seo reporting article | Match | Contains article, which is in the grouped terms. |
| seo reporting news | No | News only matches in the variation. |
| search console pricing | No | No blog-style page-type 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
- Track article-led demand separately from product and support traffic.
- See whether blog content attracts the right query formats.
- Compare editorial modifiers against documentation and FAQ demand.
Pro Tips
- This is a proxy for content format intent, not a guarantee that the SERP prefers blog pages.
- Use page filters to see whether blog-like queries actually land on article pages.
- Split news into a variation if you want a stricter blog-only segment.
- Editorial-format modifiers can be low volume, so compare over longer date ranges.
Variations
Include news-led queries
Adds another editorial-format modifier often used in content-led searches.
Related Regex Recipes
Regex for Documentation Queries
Use this regex to capture documentation-style query modifiers in GSC when users need structured reference or implementation guidance.
Regex for FAQ Queries
Use this regex to isolate FAQ-style query modifiers in GSC when users are looking for direct answers rather than long-form guidance.
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