Google Search Console keyword research is the practice of mining the Performance report for the real queries Google already shows your site for, then turning those queries into new pages or stronger versions of old ones. The short version: open Performance, then Search results, set the date range to the last 3 to 6 months, remove branded queries, sort by impressions and look for query clusters you have no dedicated page for. Those gaps are your next articles. The data comes from Google itself, and it costs nothing.
I’ve been doing SEO since 2018, and Search Console is still the first tool I open for a new client. Paid tools estimate. Search Console reports. That difference matters more than any feature list.
What Can Search Console Keywords Tell You That Paid Tools Can’t?
Search console keywords are queries where Google actually displayed one of your URLs. Every impression is a real person, in a real country, on a real device. A third-party tool guesses at that from clickstream panels and ranking scrapes, and the guesses drift.
The trade-off is honest limits. Google says the maximum you can export from the user interface is 1,000 rows of data, and queries typed by too few people are anonymized and never listed. You also only see queries you already appear for. So Search Console is brilliant at finding what you’re close to, and blind to topics you’ve never touched.
My take: use it as the source of truth for demand you’ve already earned, then use a keyword tool to expand from there.
The Four Things That Decide Your Path
Before you click anything, check these. They change what the workflow looks like for your site.
- Data volume. A site with a few hundred impressions a month needs a longer date range and more help from outside tools. A site with 50,000 impressions can work almost entirely inside Search Console.
- Page match. If a query already points at a relevant page, you update. If it points at the wrong page, or none, you write.
- Brand share. Branded searches inflate clicks and CTR. Strip them out or every number you read will look better than it is.
- Property type. Some newer features, such as the branded queries filter, only work on top-level properties with enough traffic.
How to Do Google Search Console Keyword Research in 7 Steps
This is how to use Google Search Console for keyword research with the interface as it looks in late 2026. The screenshots below are from our earlier walkthrough, so a few labels have changed. I’ll call those out as we go.
Step 1: Open the Search Results Performance Report
Sign in, pick your property, and open Performance, then Search results. If you haven’t verified your site yet, do that first. Nothing else in this workflow works without it.
You’ll also see a Generative AI performance report in the menu now. Google launched it in June 2026 and rolled it out to all websites by August 31, 2026, according to the Search Central announcement. It shows impressions, pages, countries, devices and dates for AI Overviews and AI Mode. It does not show queries. For keyword work, you stay in Search results.
Step 2: Set a Date Range That Smooths Out Noise
Click the date filter. The default is the last 3 months, and Search Console keeps 16 months of history.
I use 6 months for most sites. It’s long enough to flatten a random spike and short enough to reflect how Google treats the site today. For seasonal businesses, switch to Compare and put this year against the same period last year.
Step 3: Remove Branded Queries
Branded searches come from people who already know your name and were going to find you anyway, which makes them great for measuring brand demand and useless for discovering new topics. Skip them here. Google added a branded queries filter in November 2025 and opened it to all eligible sites on March 11, 2026; it splits queries into Branded and Non-branded using an AI-assisted classifier.
If you don’t see it, your property is probably a URL-prefix or subdomain property, or too small. In that case, click + Add filter, choose Query, and use “Queries not containing” with your brand name. Crude, but it works.
Step 4: Sort the Queries Tab by Impressions
Open the Queries tab and click the Impressions column header so the biggest numbers sit on top. Impressions tell you where Google already considers you relevant, even when nobody clicks yet.
Turn on Average CTR and Average position too. Here’s a real Google Search Console keyword research example from the site in our screenshots: the query “tilde key” earned 2,528 impressions and 0 clicks.
That pattern means one of three things. There’s no page targeting the query, the page’s title doesn’t earn the click, or the content misses the intent. Fixing weak pages is its own job, and I cover it in the guide to finding low hanging fruit keywords in Search Console. Here, we’re hunting for topics.
Step 5: Pull Question Queries With One Regex Filter
Question queries are the best raw material for new articles, because each one is already phrased as a heading. Click + Add filter (older screenshots label it + New), choose Query, then Custom (regex).
Paste this pattern and apply it:
^(how|what|why|when|where|who|which|can|does|is|are)\s
Search Console uses RE2 syntax, matching isn’t case-sensitive by default, and a pattern can match anywhere unless you anchor it with ^ or $. That single filter usually turns a messy list into a tidy list of reader questions.
I’m keeping regex to one step on purpose. You don’t need a library of 40 patterns to do good keyword research; you need one filter you’ll actually use every month. (If you do want more, I keep 20 tested patterns in Google Search Console regex.)
Step 6: Click a Query and Check Which Page Ranks
Click any promising query. The whole report filters. Now open the Pages tab.
This is the decision point. One relevant URL means you have a page to improve. Two or three URLs trading places means Google can’t tell which page you want to rank. No sensible URL at all means you’ve found a content gap.
Step 7: Expand the Seed Outside Search Console
Search Console gives you the seed keywords; it won’t give you search volume or difficulty for terms you don’t appear for. So take the query to Google itself. Type it in and watch the autocomplete suggestions.
Scroll down for related searches, which often reveal the problem behind the query.
Then run it through a free keyword tool for rough volume and difficulty. We used Ahrefs’ free keyword generator here: choose the search engine, set the country and click Find keywords.
At the time of the screenshot, “tilde key not working” showed a KD of 0 and about 30 searches a month. Small, yes. But it’s a real problem people type, and a site that already earns thousands of impressions for the parent term has a head start.
Should You Update an Existing Page or Write a New One?
Here’s the branch that most guides skip, and it’s where the ROI hides.
If one relevant page already ranks for the query, update that page. Add a section that answers the query directly, use the query’s wording in a subheading, and link to the page from two or three related posts. Writing a second page for the same intent splits your signals, so I work through my 9-step checklist for optimizing existing content instead.
If the ranking page is only loosely related, for example a product page showing up for a how-to question, write a new article. Then link from the old page to the new one so Google sees the relationship.
If several of your URLs rotate for the query, don’t write anything yet. Consolidate first. Adding more content to a split topic makes the split worse.
Turning One Query Into a Content Plan
Let me walk the tilde key data through the whole process. Examples beat theory. The site had 2,528 impressions and no clicks for the parent query. In our original walkthrough, the site had no article built for that term, so whatever Google tested for it was at best loosely related. That’s the second branch, and a new article is justified.
Step 7 then turned one seed into a small cluster. “Tilde key not working” is a troubleshooting post. “How to find the tilde key on my keyboard” is a quick answer that can live as a section inside it, since the intent overlaps. When two queries would be answered by the same page, I merge them; when the reader would need a different page to feel satisfied, I split them.
The last move is the one people forget. Annotate everything. After publishing, add a custom annotation in Search Console on the publish date. Search Console annotations hold up to 120 characters, and they save you from guessing six months later why impressions jumped. I check the new page’s Queries tab again after about 4 weeks to see which variations Google started testing it for, because that list usually suggests the next section to add.
This is the loop that makes Google Search Console keyword research compound over time. Every page you publish creates new impressions, and those impressions become the raw material for the next round.
What If Your Site Is New and the Report Is Nearly Empty?
When I start with a brand-new site, the Queries tab might hold 30 rows. That’s normal. Set the range to the full 16 months, check the Image search type as well as Web, and write down every query, even the weird ones.
Honestly, with a new site I’d lean on outside tools for the first 8 to 12 weeks and come back to Search Console once impressions build, because a report with 30 rows can make a random one-off search look like a trend worth chasing. Don’t chase it. The goal early on isn’t finding hidden gems. It’s confirming Google understands what the site is about.
Edge Cases That Trip People Up
- Totals don’t add up. The chart includes anonymized queries; the table doesn’t. Filtering by query drops them too, so filtered numbers always look smaller.
- Multimodal searches. Since September 24, 2026, Search Console reports searches made with Lens, Circle to Search and image uploads under a multimodal filter. For product and visual sites, check it separately.
- AI Overview impressions. They’re counted inside the normal Web numbers. Your query list already includes them; you just can’t isolate them by query.
- Query groups. Large sites get an AI-built Query groups card in the Insights report. It’s a quick way to spot topic clusters before you dig into single queries.
Update, Write or Skip: The Quick Matrix
| If the query… | And the ranking page… | Then |
|---|---|---|
| Has high impressions, some clicks | Matches the intent | Update and expand that page |
| Has high impressions, 0 clicks | Is off-topic or missing | Write a new, dedicated article |
| Shows several of your URLs | Rotates between them | Consolidate before writing |
| Has low impressions | Doesn’t exist yet | Validate volume in a keyword tool first |
| Contains your brand name | Any | Exclude it from research |
Where DIY Research Runs Out of Road
Search Console works best when you already have traffic and a clear topic. If you’re entering a new niche, building a topical map from scratch, or your queries are mostly anonymized, you need wider data than Google hands you. That’s when our keyword research service makes sense; you can try 5 keywords free before paying anything.
Frequently Asked Questions
Does Google Search Console Show Keyword Search Volume?
No. It shows impressions, which is how often your site appeared for a query, not how often people searched it. If you rank on page 5, impressions will be tiny even for a huge keyword. Use a keyword tool or Google Keyword Planner for volume estimates.
Where Did the Content Keywords Report Go?
Google removed it years ago. It listed words found on your pages, not searches people made, which confused a lot of site owners. The Queries tab in the Performance report replaced it and is far more useful for research.
How Many Google Search Console Search Terms Can I Export?
The interface exports up to 1,000 rows per view. To get more, export smaller slices (by country, device or page folder) or use the Search Analytics API, which Google says can return up to 50,000 rows per day per site per search type.
How Often Should I Repeat This Process?
Monthly for active sites, quarterly for small ones. I set a calendar reminder and use Search Console’s custom annotations to mark the date I published or updated each page, so I can see the effect later.
Last updated: September 2026 by Mizanur Rahman
