Understand
Trends beside Search Console
Trends beside Search Console. Demand from the interest index, performance from your property, and a gap where interest rises and the fetched queries do not show a strong rank.
Understanding the labHow to use it and why you'd want to
Why you'd want to
A Trends spike is joined to the top query rows for this property, and a gap is labeled when interest is up and the query is missing or ranked worse than 10. After Accept the source word is queued, not the queries.
How to use it
- If the property is not set, Compare stops.
- Compare asks for the top queries.
- A gap needs the spike plus a missing or poorly ranked query.
- After Accept, the event carries the source, not the query text.
The join
Trends is demand in the sample Google publishes. Search Console is what this property earned: query, clicks, impressions, click-through rate, and average position. A gap on this page means the latest complete Trends point is at least 1.5 times the mean of up to four earlier points, and the query is missing from the fetched rows or its average position is worse than 10.
Both cutoffs are choices of this lab. They are printed here so the rule is visible. Search Console on this site returns the top 10 queries for a 28-day window. A query outside that list can still have impressions.
This property
sc-domain:blackboxpersonalization.com · 2026-10-18 – 2026-11-14 · top 10 queries. Live Trends for one term, worldwide, past 12 months.
| Query | Clicks | Impressions | CTR | Position |
|---|---|---|---|---|
| "black box" "google analytics" | 0 | 12 | 0.0% | 1.8 |
| api request | 0 | 2 | 0.0% | 84 |
| api requests | 0 | 2 | 0.0% | 85.5 |
| crear datalayer | 0 | 1 | 0.0% | 88 |
| custom campaign links | 0 | 5 | 0.0% | 90.6 |
| custom utm builder | 0 | 2 | 0.0% | 29.5 |
| datalayer | 0 | 14 | 0.0% | 73.3 |
| datalayer google | 0 | 6 | 0.0% | 76.8 |
| datalayer push | 0 | 10 | 0.0% | 77.6 |
| datalayer.push | 0 | 5 | 0.0% | 75 |
Labeled example
Example. Not a measurement from Google or from this site.
Interest is at the spike line, and this query is not in the rows below. That is a gap on this page’s rule. Missing from the list is not proof of zero impressions.
No example Search Console row for example alpha. Cutoff 10.
| Query | Clicks | Impressions | CTR | Position |
|---|---|---|---|---|
| example beta | 4 | 80 | 5.0% | 6 |
| example gamma | 1 | 20 | 5.0% | 18 |
Search Console query
The request this site already makes. Dates in the sample are placeholders for the window you choose.
# Search Console Search Analytics. The service account needs
# https://www.googleapis.com/auth/webmasters.readonly on the property.
# This site asks for the top 10 queries. Absence from that list is not
# proof of zero impressions.
POST https://searchconsole.googleapis.com/webmasters/v3/sites/{siteUrl}/searchAnalytics/query
{
"startDate": "YYYY-MM-DD",
"endDate": "YYYY-MM-DD",
"dimensions": ["query"],
"rowLimit": 10,
"dataState": "final"
}
# Each row has keys, clicks, impressions, ctr, and position.
# ctr is clicks divided by impressions. position is the average position.
Python · the join
Same rule as the buttons above.
"""Join a Trends series to Search Console query rows.
The 1.5 multiple and the position cutoff of 10 are choices of this lab.
A query missing from the returned rows can still have impressions.
"""
RATIO = 1.5
WINDOW = 4
RANK_CUTOFF = 10
def rising(values):
if len(values) < 2:
return None
latest = values[-1]
prior = values[:-1][-WINDOW:]
baseline = sum(prior) / len(prior)
if baseline == 0:
return latest > 0
return latest >= baseline * RATIO
def gap(term, values, rows):
flag = rising(values)
match = next((row for row in rows if row["query"].lower() == term.lower()), None)
if flag is None:
return "no-series"
if not flag:
return "not-rising"
if match is None:
return "no-row"
if match["position"] > RANK_CUTOFF:
return "weak-rank"
return "ranked"
WalkthroughHow we built itShowHide
Example vendor setup is marked below. eVar and event numbers are examples. This lab does not call Adobe.
The Search Console gap lab joins a Trends spike to the top query rows for this property and labels a gap when interest is up and the query is missing or ranked worse than 10. After Accept, Compare queues trends_gap_view with data_source, and the lab does not call Adobe.
Read the property or stop
The page calls inspectSearchConsole and, when it is ready, readSearchConsole. Without credentials the report stays disconnected and Compare does not fetch Trends.
Ask for the top queries
The Search Console query uses one date range and four requests: date, query with a row limit of 10, page with a row limit of 10, and the totals. A query outside those 10 rows can still have impressions.
Decide the gap from the spike and the row
classifyGap returns no-series when rising is null, not-rising when the spike is false, no-row when the query is absent, weak-rank when position is worse than the cutoff, and ranked otherwise. The cutoff is 10.
Queue the source word, not the queries
After Accept, a successful Trends response sets data_source to search_console. A failed Trends response sets unreachable. Clicks, impressions, and position are not parameters.
From the code
Recommended next
Why these picksReading path transitions…