Rising-query miner
Each week a query miner reads your search performance for queries gaining impressions with no dedicated page, clusters them by intent, checks for cannibalization, and turns the winners into prioritized content briefs — you approve which briefs go into production.
Saves you ~4.9 h / week
How it works
- Trigger
- On the “Rising-query mining run” schedule.
- Job
- Mine rising queries from search performance, cluster them by intent.
- Outcome
- Prioritized content briefs for verified rising queries.
What it installs
Agents 2
-
Query Miner
Reads search performance for rising queries with no dedicated page and turns the winners into prioritized content briefs for human approval.
-
Rising-query miner Quality Reviewer
Checks primary evidence, domain controls, deliverable completeness, and communication quality, stopping the run when the work is wrong, unsupported, incomplete, or uncertain.
Teams 1
-
Rising-query miner quality team
The delivery agents produce the work while an independent quality reviewer checks each workflow handoff against explicit evidence, domain, and communication requirements before the run can continue.
Workflows 1
-
Mine, cluster, check, brief
Mine rising queries from search performance, cluster them by intent, check each cluster for cannibalization, write prioritized briefs, and hand them off for approval.
Documents 1
-
Query-opportunity log
The rolling log of rising query clusters — what was spotted, the verdict, the brief, and what happened after publication.
Goals 1
-
Rising demand captured before competitors
Keep a steady pipeline of approved briefs targeting queries whose demand is arriving now. Success looks like: Every weekly run ends with rising query clusters logged, cannibalization-checked, and turned into ranked briefs — with the approved ones in production while the queries are still climbing.
Skills 4
-
rising-query-mining
Mine search performance for rising queries through an eight-phase research flow — scope, seed discovery, modifier variations, intent classification, opportunity scoring, GEO-check, clustering, delivery — with every metric labeled by provenance. Adapted from aaron-he-zhu/aaron-marketing-skills/keyword-research.
-
query-intent-clustering
Group rising queries into clusters by shared search intent rather than string similarity, name each cluster by its head query, classify the intent type, and size clusters so one page can honestly satisfy the whole set.
-
cannibalization-check
Check each query cluster against the site's existing pages before recommending new content — find every page already competing for the cluster, and return a verdict: new page, strengthen existing, consolidate, or watch.
-
content-brief-writing
Turn a validated query cluster into a production-ready content brief and prioritize the batch — searchable before shareable, a weighted score across customer impact, content-market fit, search potential, and resources, buyer-stage mapping, and hub-and-spoke placement. Adapted from coreyhaines31/marketingskills/content-strategy.
Schedules 1
-
Rising-query mining run
Mines search performance for rising-query opportunities each week. ## Professional quality control Objective: complete the recurring Rising-query miner operating cycle and deliver a review-ready, evidence-backed result rather than merely report that the schedule ran. Start by fixing the review period, reading the current source records and prior run, confirming required access, and listing missing or contradictory inputs. Execute the bundle's full authored method in order, retaining source, calculation, command, or before/after evidence for load-bearing findings. Separate facts from interpretation, apply supplied policy without inventing thresholds, and stop any branch that requires missing authority or an unconfirmed human rule. Produce the complete named deliverable plus an evidence record, assumptions, exceptions, unresolved questions, and concrete next actions with owners where the method calls for them. Run the workflow's independent verifier checks and fix failures before requesting approval. The task is done only when every requested section and quality criterion passes or a blocker is explicit; silence, inaccessible data, or polished prose is not proof of completion. Verify current platform guidance, crawl or search evidence, measured versus estimated metrics, affected URLs, and the reader value behind each recommendation. Reject keyword-shaped filler, generic AI phrasing, stale rules, date-only refreshes, unsupported ranking claims, and content written for a crawler rather than a person. The human retains authority over publication, sending, spend, signing, merging, deployment, and other consequential external actions.
Connectors optional
-
Ahrefs
Connects to Ahrefs so the miner can confirm query volumes, difficulty, and competing pages behind each rising cluster.
-
Semrush
Connects to Semrush so the miner can confirm query volumes, difficulty, and competing pages behind each rising cluster.
Folders 1
-
Rising-query mining
Requirements
- Browser access to Google Search Console — The agent reads query and page performance in Google Search Console through its web interface in your browser and pauses for your approval before any action. Until you connect it, it works from attached performance exports and the query-opportunity log.
- Web search and fetch access for checking existing pages — The agent checks each query cluster against your existing pages through worker web search and fetch tools; it only reads public pages and never changes anything.
Setup guide
How to Mine Rising Search Queries
A practical guide to finding Search Console queries gaining impressions and turning the right clusters into approved content briefs.
Read the setup guideDon't see your workflow? Describe it.
A sentence or two about a recurring job is enough. We design the playbook that runs it and show you exactly what it saves.