Which keywords should we actually target given intent and revenue?

This is a keyword and market research question — the kind that usually shows up from cMO, content lead, client kickoff. It rarely has a one-line answer, because the honest version of “Which keywords should we actually target given intent and revenue” is a shortlist of rival explanations, not a single cause. The job is to work through that shortlist with evidence and stop as soon as one of them is confirmed — not to write a report that mentions all of them.

The rival explanations

Direct answer: Five competing signals — attractive head terms, consolidatable long-tails, already-won branded terms, AI-Overview-covered informational queries, and internal CRM/search language — each argue for a different keyword map, and picking by volume alone ignores all four of the others.

Treat these as competitors, not a checklist. The point of naming five up front is to stop the first plausible-sounding one from becoming the story before the others have been checked.

• Head terms look attractive but the SERP is a different page type than we can ship.
• Long-tails map to existing URLs and should be consolidated, not new posts.
• High-volume branded terms are already won; growth is in mid-intent comparisons.
• AI Overviews cover informational queries; commercial queries still click through.
• Internal search / CRM language beats third-party volume lists.

What the evidence has to show

Direct answer: Sixteen months of GSC query-by-page data, third-party volume/difficulty/SERP-feature data, PAA/AlsoAsked cluster completeness, actual CRM and sales-call language, and a realistic briefs-per-month capacity model are what separate a keyword that can convert from one that only looks big.

None of the five above survives on a hunch. Here is what actually needs pulling before any of them can be ruled in or out:

• GSC query × page for 16 months; cluster by intent and landing URL.
• Keyword Planner + Semrush/Ahrefs: volume, KD, SERP features, parent topic.
• AlsoAsked / PAA for cluster completeness; AI Overview presence on the seed set.
• CRM / sales call language and top converting landing pages.
• Capacity: briefs per month × expected time-to-rank given rival link/content velocity.

The decision rule

Direct answer: A term enters the map only if (1) intent matches a page type we will maintain, (2) the SERP is winnable with this quarter’s capacity, and (3) there is a revenue or pipeline proxy. Volume alone is not a reason to target.

What to tell the people around you

Direct answer: Stakeholders need to see their 'must-rank' list converted into page types, owners, and an explicit kill list — not a bigger spreadsheet of the same terms with volume columns attached.

The analysis is not finished until it produces something a non-specialist can act on. That means naming the situation, the cost of getting the first move wrong, and a specific ask — not a summary of the investigation.

• Situation — Stakeholders have a list of ‘must-rank’ phrases. We are converting that list into a map of page types, owners, and no-compete terms.
• So what — Chasing vanity head terms burns writers and never moves pipeline. A shorter map with commercial intent compounds.
• The ask — Sign off the map (including the kill list). Protect writer capacity for the agreed clusters only.

SEO owns the map. Content owns briefs. Revenue ops validates the proxy.

How to act on this

1. Cluster 16 months of GSC query data by intent and landing URL, then layer in third-party volume, difficulty, and SERP-feature data per cluster.
2. Check PAA/AlsoAsked coverage and AI Overview presence on the seed set to see which clusters still reward a classic ranking play.
3. Pull real CRM and sales-call language, and the pages that already convert, to find revenue-adjacent terms no volume tool will surface.
4. Apply the three-part gate — matching page type, a winnable SERP within this quarter's capacity, and a revenue or pipeline proxy — before any term enters the map.
5. Publish the kill list alongside the map so writers and stakeholders both see which 'must-rank' terms were deliberately excluded, and why.

Frequently asked questions

Is a high-volume term ever worth targeting even without a clear revenue link?

Only if it feeds a page type you can maintain and a SERP you can realistically win — volume alone never clears the three-part gate on its own.

What happens to long-tail terms that already map to an existing page?

They get consolidated onto that page rather than spun into new posts — a fresh long-tail post competing with your own ranking URL is a self-inflicted cannibalization problem, not a growth opportunity.

How do we handle terms where an AI Overview already answers the query?

Informational queries with a satisfying AI Overview usually keep low click-through regardless of ranking; the map should weight those clusters toward genuinely commercial or comparison intent instead.

Who decides the kill list — SEO alone?

SEO proposes it from the evidence, but stakeholders sign off explicitly, since the kill list is what protects writer capacity from being reallocated back to vanity terms mid-quarter.

Should CRM language override third-party keyword-tool data?

Neither overrides the other — CRM/sales language surfaces real buyer phrasing that tools miss, while tools supply volume and difficulty; the map needs both to pass the revenue-proxy test.

How often should the keyword map be revisited?

At minimum quarterly — search behavior, AI Overview coverage, and your own capacity all shift, so a map built once and never revisited drifts away from the revenue signals that justified it.

Should seasonal keywords get a permanent spot on the map?

Only if they clear the same three-part gate every cycle — a seasonal term that reliably converts each year earns a place, but one that only spiked once shouldn't consume year-round writer capacity.

Sources

1. Beginner's Guide to SEO — Moz
2. SEO essentials — Search Central
3. Keyword research — Wikipedia
4. Search engine optimization — Wikipedia

Where nqzai fits

nqzai runs this same rival-hypothesis framework against your own connected Search Console, Analytics, and audit history, and returns a keep / change / stop decision with the evidence named — including which of the explanations above it could not test, and what to connect to close that gap. No extra cost for the analysis itself; it reads measurements already on file.

Ask nqzai: “Which keywords should we actually target given intent and revenue?”