Discovery and Expansion · Lesson 6 of 17 · 13 min
Search Console Keyword Mining
Use Search Console query and page evidence to choose useful content improvements, accounting for average positions, missing queries and reporting limits.
Video walkthrough coming soon
This lesson is fully written below. The recorded walkthrough for “Search Console Keyword Mining” will appear here once it is published.
Performance model
Keyword Research Mastery Discovery and Expansion
Stage 1
What Search Console data can
Stage 2
Find candidates without treating averages
Stage 3
Expand an answer only when
Want to earn a Rankar Academy certificate?
This lesson is free to read in full. Join the Academy to track your learning, complete courses and sit the certification assessment.
Join the AcademyWhat Search Console data can establish
The Performance report describes clicks, impressions, CTR and average position for your verified property in the selected search type, dates and filters. It is evidence about your own observed search visibility, not a complete list of every query or a third-party traffic estimate.
Some queries are anonymised for privacy and report tables have limits. Totals can differ from visible query rows, and filtering can change the data included. Record the property, search type, date range, country and device; an absent row is not proof of zero demand.
Find candidates without treating averages as fixed ranks
Enable the relevant metrics, select a page or query and compare like-for-like periods and segments. Export the query table if you want to screen rows by numeric position ranges in a worksheet. An average position between 11 and 20 is a screening choice, not proof that a page always sits on a second results page.
Average position describes the average topmost result from your property under the report’s counting rules. It varies across contexts and result types. A low CTR may reflect layout, intent, brand recognition or position as well as the title; it does not diagnose a weak meta description by itself.
- Review relevant query/page combinations, not sitewide averages alone
- Inspect the current results in the intended market and device
- Identify unanswered needs or inaccurate information, not a word-count deficit
- Choose changes you can substantiate and record the evidence
Expand an answer only when it serves the visitor
Unexpected relevant queries can reveal an unanswered question worth covering on an existing page. Use a separate resource only when it supports a distinct task. Avoid adding irrelevant phrases simply because they appear in a report. No small edit, new link or added heading guarantees a ranking improvement.
Keep a measured change and review record
Record the target URL, query, observation date, proposed change and review date. Add selected queries to RankTracker with consistent engine, location and device settings, then compare its checks separately from Search Console averages.
After editing, review comparable periods and relevant business outcomes. Seasonality, competing pages and other changes can affect results; timing alone does not prove that your edit caused a gain. Leave failed or missing observations unavailable.
Why this lesson matters
Use Search Console query and page evidence to choose useful content improvements, accounting for average positions, missing queries and reporting limits.
Keep the decision grounded in evidence
The Performance report describes clicks, impressions, CTR and average position for your verified property in the selected search type, dates and filters. It is evidence about your own observed search visibility, not a complete list of every query or a third-party traffic estimate.
After editing, review comparable periods and relevant business outcomes. Seasonality, competing pages and other changes can affect results; timing alone does not prove that your edit caused a gain. Leave failed or missing observations unavailable.
Do it now
Apply this lesson to a real page or research task without inventing missing observations.
- Record report filters and privacy limits
- Treat average position as an aggregate, not a fixed ranking
- Investigate the actual visitor need before editing
- Compare consistent evidence without promising or inventing gains
Key takeaways
- Record report filters and privacy limits
- Treat average position as an aggregate, not a fixed ranking
- Investigate the actual visitor need before editing
- Compare consistent evidence without promising or inventing gains
Practise it now in RankTracker
Use a relevant seed, public question sources and available search evidence to prepare a reviewed candidate list. Record sources and missing data, group related needs and propose useful target pages without a fixed keyword quota.
3h 54m of material in this course · 17 lessons