Find low-hanging-fruit keywords

Low-hanging-fruit queries are relevant searches where an existing page already has meaningful reported visibility and a realistic, valuable improvement path. They are not simply every query with an average position between 11 and 20.

A defensible opportunity combines:

• Enough impressions to matter.
• A page that already serves—or can credibly serve—the need.
• A position or CTR pattern with room to improve.
• Business and audience relevance.
• A feasible change.
• Acceptable risk to the page’s existing performance.

Search Console provides the performance evidence. It does not provide keyword difficulty, total market search volume, competitor authority, or guaranteed upside.

There is no universal striking-distance position

Ranges such as positions 4–20 are useful starting filters, not rules.

Why a rigid range fails:

• Average position is impression-weighted, not a fixed rank.
• Query, page, country, device, and result layout all affect the average.
• Position 5 can already be a major opportunity for a high-value query.
• Position 18 can be unrealistic if the page serves the wrong intent.
• A low-volume position 8 row may matter less than a high-volume position 25 cluster.
• Property-level query position can reflect several pages.

Use page-query rows and prioritization evidence, not position alone.

Create the source dataset

Interface workflow

1. Open Performance → Search results.
2. Select Web or the relevant Search type.
3. Use at least 3 complete months; add year-over-year context for seasonal sites.
4. Turn on Clicks, Impressions, CTR, and Average position.
5. Open Queries.
6. Export the table.

For a small manual analysis, click promising queries and open Pages. For repeatable analysis, use the Search Analytics API with Query and Page dimensions. For large sites, use BigQuery bulk export.

The interface shows a limited number of rows, and the API returns top rows rather than every underlying query. Bulk export offers the most complete available dataset while preserving privacy protections.

Work at query-page level

A query-only row can hide which page earns the impressions. Add or look up the page before prioritizing.

Minimum useful fields:

Field	Why it matters
Query	Reported search phrase
Page	Existing destination
Clicks	Current traffic outcome
Impressions	Opportunity scale
CTR	Click behavior
Average position	Visibility context
Country/device	Segment mix
Query family	Stable user need
Business value	Organization-specific priority
Intended page	Content decision, not a GSC field

Most Performance data is credited to Google’s selected canonical URL. Confirm the canonical when the page is unexpected.

Apply minimum evidence thresholds

Remove rows that are too small for the site’s decision process. Example starting thresholds might be:

• At least 100 impressions in 90 days.
• At least 20 impressions in two or more separate weeks.
• Average position between 4 and 25.
• A query clearly relevant to the site.

These are examples, not Google recommendations. A large ecommerce site may need thousands of impressions; a specialized B2B site may reasonably act on fewer.

Require persistence. One-day visibility from a news event is not low-hanging fruit for an evergreen page.

Group close variants before ranking opportunities

Users phrase the same need in many ways. A cluster can be material even when no individual query passes the threshold.

Example family:

• search console regex
• gsc regex filter
• google search console regular expressions
• regex in search console

Preserve modifiers that change intent, including free, buy, vs, login, location, model, and year.

Google’s language systems understand variations without exact repetition. A cluster is for analysis and content planning, not a reason to make one thin page per phrase.

Classify the opportunity type

CTR opportunity

Signals:

• Meaningful impressions.
• Competitive position for comparable queries.
• CTR below an appropriate peer group.
• Page intent is already correct.

Possible work: improve title, result summary inputs, page promise, structured-data eligibility, or intent clarity.

Visibility/relevance opportunity

Signals:

• Meaningful impressions.
• Weak but sustained position.
• Page broadly fits the need.
• Clear content, evidence, or internal-link gaps.

Possible work: strengthen the page’s useful coverage, originality, evidence, and relevant internal links.

Wrong-page opportunity

Signals:

• An unsuitable page earns impressions.
• A better page exists but is missing or weak.
• Several pages switch for the query family.

Possible work: fix indexing/canonicals, differentiate pages, consolidate overlap, or strengthen the intended page and internal architecture.

New-content opportunity

Signals:

• Relevant query family has sustained impressions.
• Existing pages only partially satisfy a distinct user need.
• The site has expertise and can add original value.

Possible work: create one complete resource for the distinct intent. Do not create a page for every wording variation.

Demand-only observation

Signals:

• Position is already strong.
• Impressions remain low.
• No meaningful CTR or page problem exists.

Action: monitor or use broader market data. A better ranking cannot manufacture query demand.

Irrelevant visibility

Signals:

• Query does not fit the audience, product, expertise, or page purpose.

Action: do not chase it merely because it has impressions.

Use position as a bucket, not a promise

A practical set of diagnostic buckets:

• Positions 1–3: defend; CTR/result representation may be the larger opportunity.
• Positions 4–10: often material click upside, but inspect result features and intent.
• Positions 11–20: common “striking distance” pool; prioritize only relevant, well-matched pages.
• Positions 21–50: usually requires a stronger relevance/content/page selection case.
• Beyond 50: treat as discovery evidence, not a quick win.

These bands are workflow conventions. Modern Search layouts and compound elements make “page one” language imprecise, and average position can cross bands because the query mix changed.

Estimate click opportunity directionally

Use a reference CTR from comparable rows at similar positions, devices, countries, brands, and result types.

estimated additional clicks = impressions × (reference CTR - current CTR)

Cap negative values at zero for an opportunity list.

Example:

• 10,000 impressions.
• Current CTR: 1.5%.
• Comparable reference CTR: 2.5%.
• Directional opportunity: 10,000 × 1% = 100 clicks.

This is not a forecast. The page might not achieve the reference CTR, impressions may change, and result layouts differ.

Do not apply one sitewide CTR curve to every query. Brand, device, country, intent, and search appearance can produce very different normal rates.

Add business and feasibility scoring

Performance opportunity is only one component. Score each cluster on explicit fields:

• Reported impression scale.
• Directional click opportunity.
• Relevance to the site’s purpose.
• Business value or conversion evidence.
• Existing page fit.
• Feasibility of a substantive improvement.
• Competitive/result-quality gap.
• Confidence in the data.
• Risk to existing valuable traffic.

Example transparent model:

priority = opportunity score × business value × feasibility × confidence

Keep every component visible. Avoid a black-box score that produces false precision.

Find the correct page for each query

Filter to a query or family and inspect Pages.

Classify the leading page:

• Correct: directly satisfies the need.
• Partial: relevant but missing a necessary distinct section or evidence.
• Wrong: another site page is more suitable.
• Overlapping: several pages serve essentially the same need.
• None: a distinct, relevant need lacks an appropriate resource.

When multiple pages appear, determine whether they are complementary before consolidating. The table covers a period and does not prove simultaneous competition.

Prioritize changes to existing pages

For the correct or partial page:

1. Verify indexability and selected canonical.
2. Compare the page with the query’s dominant user need and result types.
3. Improve the answer, structure, evidence, accuracy, and usefulness.
4. Add relevant sections only when they belong on the page.
5. Improve title and snippet inputs to represent the content accurately.
6. Strengthen crawlable internal links from relevant pages.
7. Check mobile experience and structured data where applicable.

Google recommends people-first content and says there is no preferred word count. Do not convert the query list into keyword-stuffed headings.

Segment before changing the page

Check whether the opportunity exists only for:

• Mobile or Desktop.
• One country.
• Branded or non-branded demand.
• Web, Image, Video, or News.
• A specific search appearance.
• A short seasonal window.

A pagewide rewrite may be the wrong response to a country-specific or device-specific result difference.

Automate the opportunity report

With the Search Analytics API:

1. Request a complete finalized date range.
2. Group by Query and Page.
3. Page through rows up to the available top-row boundary.
4. Apply minimum impressions and position buckets.
5. Join business value and page-type data.
6. Cluster close query variants.
7. Calculate directional click opportunity.
8. Flag multiple-page query families.
9. Store the extract and taxonomy version.

The API allows up to 25,000 rows per request but does not guarantee all data. Do not present the output as a complete keyword universe.

Common mistakes

• Treating positions 11–20 as automatically easy.
• Using property-level query position without identifying the page.
• Prioritizing percentage change over absolute opportunity.
• Ignoring tiny or one-day samples.
• Assuming impressions equal search volume.
• Applying a universal CTR benchmark.
• Chasing irrelevant queries.
• Creating one page per keyword variation.
• Ignoring page competition and canonical attribution.
• Promising clicks from an uplift estimate.

Validate the work

Before changing a page, save:

• Query/family definition.
• Page-query baseline.
• Country/device scope.
• Intended change and hypothesis.
• Control pages if suitable.

Add an annotation, verify recrawling, and compare equal complete periods. Review total family clicks/impressions and previously strong queries, not only the target phrase. Use GA4 or business systems to confirm the additional traffic was valuable.

What GSC can and cannot answer

It can help identify:

• Visible query-page pairs with impressions and room to improve.
• Which page appears for a query.
• Whether position, CTR, or page selection deserves investigation.
• Which segments contain the opportunity.

It cannot provide:

• Keyword difficulty.
• Complete search volume.
• Competitor backlink/content data.
• Guaranteed ranking or clicks.
• Every query due to privacy and top-row limits.

Opportunity checklist

• Minimum impression and persistence thresholds are defined.
• Page-query data is used.
• Query variants are clustered carefully.
• Position is treated as context, not a guarantee.
• Relevance and business value are required.
• CTR references use comparable cohorts.
• The intended page is verified.
• Technical, content, snippet, and overlap opportunities are separated.
• Estimates are labeled directional.
• Changes are measured against a saved baseline.

Official sources

• Performance report: common tasks and use cases
• Performance report: dimensions and data groupings
• Performance report: about the data
• Clicks, impressions, and position methodology
• Search Analytics API query method
• SEO Starter Guide
• Creating helpful, reliable, people-first content