How to use Search Console regex to find content opportunities
Use regex filters to find questions, comparisons, objections, and other searches your existing pages are already showing up for.
4 min read
Search Console contains queries your pages already appear for but may not answer particularly well.
Regex makes those queries easier to find.
You can filter for questions, comparisons, objections, and other patterns, then combine those filters with page URLs to see what people are searching before they land on a specific page.
The useful part is not the regex itself. It is what you do with the queries you find: improve an existing answer, add missing information, create a new page when the intent is distinct, or leave it alone.
How do you use regex in Search Console?
In Performance → Search results, add a Query filter.
Change the match type to Custom (regex) and enter the expression you want to use.
You can also use regex with the Page filter. Combining Query and Page filters is especially useful when you want to understand the searches associated with a specific page or section of the site.
Which Search Console regex filters are useful?
You do not need dozens of regex patterns. A few cover most of the research I actually use Search Console for.
Questions
Find queries phrased as questions:
This is useful for finding searches beginning with terms such as who, what, when, where, why, how, can, does, is, and are.
Comparisons
Find searches where someone is comparing options:
These can reveal comparison pages you are missing or comparison criteria that belong on an existing page.
Objections and concerns
Find searches that suggest hesitation, problems, or objections:
These are particularly useful on commercial pages because they can expose the questions someone needs answered before choosing.
Non-branded queries
Exclude your own brand when you want to focus on non-branded discovery:
How do you turn Search Console queries into content updates?
Say a software comparison page appears for:
“does [product] charge for guest users”
The query has strong impressions, but the page ranks near the bottom of page one and receives very few clicks.
First, check the page.
If guest-user pricing is already answered clearly, the problem may not be missing content.
If the information is buried in a large pricing section, make the answer easier to find.
If the page never answers it, determine whether the question belongs on that page. For a software comparison, it probably does.
You do not automatically need a new article called Does [product] charge for guest users?
The query identifies the question. The page and intent determine what you do with it.
Want to check yours?
Run the FAQ writer →
Which Search Console queries should you act on?
Finding a query does not mean it deserves content.
Look at the query together with:
Impressions: Is there enough recurring demand to matter?
Position: Is the page already reasonably competitive for the query?
Clicks and CTR: Are people seeing the result but not choosing it?
Existing page: Does the page actually answer the query?
Intent: Does the question belong on this page at all?
A few useful patterns:
Impressions + reasonable position + weak answer
Strong candidate for a content update.
Impressions + low CTR + good answer
Look at the SERP, title, snippet, and competing results before adding content.
Impressions + poor position + dedicated section already present
Missing content may not be the problem.
Very low impressions + tangential query
Probably not worth changing the page for.
Search Console gives you evidence of demand. It does not make the content decision for you.
How do you find questions for a specific page?
Combine a regex Query filter with a Page filter.
For example, filter queries to questions, then filter Page to one important product, category, guide, or landing page.
Now you have the questions that specific page is already appearing for.
Review them against the page itself:
already answered clearly → leave it alone
answered but buried → improve placement or clarity
relevant and unanswered → add it
distinct intent → consider another page
irrelevant → ignore it
This is much more useful than turning every query into another heading.
What are the limitations of Search Console regex research?
Regex only finds patterns you tell it to look for.
A question does not need to begin with “how” or “what” to express a question. Searches such as standing desk height for 6 foot person or Asana guest pricing may represent exactly the kind of information you want and never match a question-word filter.
Search Console also does not show every query, and low-volume or anonymized queries may be omitted.
Finally, impressions are not the same as demand. One query can generate multiple impressions for the same user, and rankings affect how often your result is eligible to appear.
Use regex to surface patterns worth investigating, not as a complete keyword dataset.
What date range should you use in Search Console?
Start with enough data to prevent a handful of searches from driving the analysis.
Three months is a reasonable starting point for many sites. Lower-volume sites may need six months or more.
Then compare periods when the topic is seasonal or changing.
A query growing meaningfully over the last three months may deserve more attention than a larger query whose demand is declining.
Use the time range to understand whether the pattern is persistent, seasonal, growing, or temporary.
When should you export the Search Console queries?
Export when you have enough rows that reviewing them individually in Search Console becomes slow.
In a spreadsheet, add columns for:
query type
landing page
impressions
clicks
CTR
position
already answered?
action
Your action column can stay simple:
Keep / Improve answer / Add answer / New page / Investigate / Ignore
That turns a regex export into a working content queue instead of another keyword spreadsheet.
What should you do with the queries you find?
Do not default to creating more content.
For each useful query, decide:
Improve the existing answer when the right page already exists but the information is weak or incomplete.
Move or clarify the answer when the information exists but is difficult to find.
Add a section or FAQ when the question belongs on the page and adds information the main content does not already cover.
Create a new page when the query represents a distinct intent that deserves its own answer.
Do nothing when the page already answers the query well or the opportunity is too small to matter.
The goal is not to turn Search Console queries into pages. It is to use the searches you already appear for to find where your site is failing to answer demand it can already see.
How should Search Console query research fit into your content workflow?
Use regex as a discovery step.
Find the query patterns that matter, connect them to the pages already appearing for those searches, and determine what is actually missing.
From there:
use the FAQ Writer for legitimate follow-up questions
use the Content Brief Builder when the opportunity requires substantial new content
use the Article Structure tool when a distinct query deserves its own page
use the traffic-opportunity methodology when you need to prioritize opportunities by potential impact
Then return to Search Console after the change to see how the page performs for the queries that prompted it.
Regex helps you find the questions. The useful work is deciding which ones deserve an answer and where that answer belongs.
Keep reading
