> ## Documentation Index > Fetch the complete documentation index at: https://docs.vortexiq.ai/llms.txt > Use this file to discover all available pages before exploring further. # Clicks Trend, Google Search Console > Tracks the day-by-day shape of organic-search clicks so SEO teams catch drops, recoveries and seasonality early. How to read it, why it matters, and how to act on it. **Card class:** [Sensitivity](/nerve-centre/overview#card-classes-explained) • **Category:** [Search Performance](/nerve-centre/connectors#connectors-by-type) > The day-by-day line for organic clicks from Google Search results, with an alert that fires when the period total drops more than 15% against the prior period. ## At a glance > **Clicks Trend** plots the daily count of organic-search clicks Google Search Console attributes to your verified property over the selected window, defaulting to the trailing **90 days (`90D`)**. A click is recorded when a user clicks a link in Google Search results that takes them to your site. The card is the canonical health line for organic demand: when it bends, something in your rankings, indexing or SERP presentation has moved, and the **drop >15% vs prior period** alert is the trip-wire that surfaces it. | | | | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | **What it tracks** | The daily `clicks` metric from the Search Console Search Analytics API, summed by date across the property, then drawn as an area chart over the selected window. The card also shows the period total and the change against the prior equal-length period. | | **Data source** | Google Search Console Search Analytics API (`searchanalytics.query`) with `dimensions: ["date"]`, `type: "web"` by default. Property = the verified domain or URL-prefix property connected to Vortex IQ. | | **Time window** | `90D` by default. The window is selectable; the prior-period comparison always uses the immediately preceding equal-length window (so 90D compares against the 90 days before that). | | **Alert trigger** | `drop >15% vs prior period (vsP)`, sentiment\_key `gsc_clicks_trend`. Fires when the current period click total is more than 15% below the prior equal-length period. | | **Anonymisation** | GSC drops clicks on rare queries (anonymised queries) from query-level reports, but the date-dimension total used here includes those clicks, so the trend line is the most complete click count GSC exposes. | | **Data freshness** | GSC data is typically **2 to 3 days delayed**. The last 2 to 3 days of the line are partial and will fill in on later refreshes; do not read the tail as a real drop. | | **Roles** | owner, marketing | ## Calculation The card calls the Search Analytics API with the `date` dimension only and the `clicks` metric, for the selected window. Each row is one day; the value is the count of clicks Google attributes to your property's results in Search for that day. Vortex IQ sums the daily values for the period total, then runs the same query over the immediately prior equal-length window for the comparison base. ``` period_total = Σ clicks[d] for each day d in the selected window prior_total = Σ clicks[d] for each day d in the prior equal-length window change_vs_prior = (period_total − prior_total) ÷ prior_total alert_fires when change_vs_prior < −0.15 ``` Two grounding notes. First, the line uses the **date dimension**, not the query dimension, so it is not subject to the row cap or the rare-query anonymisation that thins query-level reports: it is the truest click total GSC will give you. Second, `clicks` here is **search type `web`** by default; image, video and news search are separate search types in GSC and are not added in unless the property profile asks for them. ## Worked example A UK home-fragrance brand runs an URL-prefix property `https://www.scenthaus.co.uk/` in Search Console, connected to Vortex IQ. The window is `90D`. On 18 Apr 26 the card flips to an alert. | Period | Window | Organic clicks (sum) | vs prior | | ----------- | -------------------------------- | -------------------- | ----------------------- | | Prior 90D | 19 Jan 26 to 18 Apr 26 (prior) | 184,200 | baseline | | Current 90D | 19 Apr 26 to 17 Jul 26 (rolling) | 152,900 | **−17.0%, alert fires** | Reading the daily line told the team more than the headline number: 1. **The drop was a step, not a slope.** Daily clicks held around 2,050 per day through to 02 May 26, then fell to roughly 1,500 per day from 05 May 26 onwards and stayed there. A step change points at a discrete event (a Google core update, a site migration, a robots or canonical regression), not gradual decay. A slope would have pointed at slow ranking erosion or seasonality instead. 2. **Impressions held while clicks fell.** Cross-checking [Impressions Trend](/nerve-centre/kpi-cards/google-search-console/impressions-trend) showed impressions roughly flat across the same step. Clicks down with impressions flat means **CTR fell**: the site still appeared in results but won fewer clicks. That reframed the investigation away from "we lost rankings" toward "our SERP presentation got worse", confirmed on [CTR Trend](/nerve-centre/kpi-cards/google-search-console/ctr-trend). 3. **The cause was a title-tag template change.** A theme update on 03 May 26 had appended the brand name twice to every page title, pushing the descriptive part of the title past Google's display truncation. Titles still indexed fine, so impressions were unaffected, but searchers saw a worse snippet and clicked less. Reverting the template recovered daily clicks to \~2,000 within nine days. 4. **The last three days of the line were ignored.** On 18 Apr 26 the final two days read low (1,180 then 640). That was the standard GSC 2 to 3 day data lag, not a second drop; both days filled in to \~1,500 on the 21 Apr 26 refresh. **Never trust the tail of the GSC line.** **Rule of thumb.** A step down with impressions flat is a CTR or snippet problem; a step down with impressions also down is a rankings or indexing problem; a smooth seasonal dip that matches last year is usually nothing to fix. ## Sibling cards merchants should reference together | Card | Why pair it with Clicks Trend | | ------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------- | | [Total Clicks](/nerve-centre/kpi-cards/google-search-console/total-clicks) | The single-number companion. Clicks Trend is the shape; Total Clicks is the headline figure for the window. | | [Impressions Trend](/nerve-centre/kpi-cards/google-search-console/impressions-trend) | The numerator's partner. Clicks down with impressions flat = CTR problem; both down = rankings or indexing problem. | | [CTR Trend](/nerve-centre/kpi-cards/google-search-console/ctr-trend) | Confirms whether a click drop is presentation-driven. Clicks ÷ impressions = CTR; this card isolates that ratio. | | [Average Position](/nerve-centre/kpi-cards/google-search-console/average-position) | If clicks fell because rankings slipped, average position will have risen (worse) over the same window. | | [Clicks by Device](/nerve-centre/kpi-cards/google-search-console/clicks-by-device) | Splits the drop by device. A mobile-only click drop points at a mobile-specific snippet or usability regression. | | [Pages Losing Traffic](/nerve-centre/kpi-cards/google-search-console/pages-losing-traffic) | Pinpoints which URLs drove the trend so you can target the fix. | | [Ranking-Drop Alert](/nerve-centre/kpi-cards/google-search-console/ranking-drop-alert) | The rankings-side trip-wire. If it fired around the same date, the click drop is rankings-led. | | [Organic-to-Revenue Divergence](/nerve-centre/kpi-cards/google-search-console/organic-to-revenue-divergence) | Cross-channel: ties an organic click drop to downstream revenue impact. | ## Reconciling against the source **Where to look in Google Search Console:** > **Performance → Search results report.** Tick the **Total clicks** metric, set the same date range, and read the chart. The Vortex IQ line should match the GSC clicks chart day for day, because both pull the date-dimension total from the same Search Analytics data. To export the underlying daily numbers, use the Performance report's export, or query the **Search Analytics API** (`searchanalytics.query`) directly with `dimensions: ["date"]` and `type: "web"`: that is exactly what this card does. **Why our number may legitimately differ from a manual check:** | Reason | Direction of divergence | What to do | | -------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------- | ----------------------------------------------------------------- | | **Data lag.** GSC data is 2 to 3 days delayed; the last days of the line are partial. | Tail reads low, then fills in | Compare only fully settled days; ignore the trailing 2 to 3 days. | | **Search type.** This card defaults to `web`. The GSC Performance report lets you switch to Image, Video, News or Discover, which would show different totals. | Variable | Set the GSC search-type filter to Web to match. | | **Period boundary.** The card uses a rolling window in the property time zone; a manual GSC check may use a different calendar range. | Variable | Match the exact start and end dates. | | **Property choice.** Domain properties aggregate all subdomains and protocols; URL-prefix properties do not. | Domain property reads higher | Reconcile against the same property type connected to Vortex IQ. | | **Filters.** A query, page, country or device filter applied in the GSC UI narrows the total; this card is property-wide and unfiltered by default. | GSC filtered view reads lower | Remove filters in GSC for a like-for-like total. | **Cross-connector reconciliation:** GSC clicks are organic-search clicks only and will not match GA4 "Organic Search" sessions exactly. GSC counts clicks on the SERP; GA4 counts sessions that land and fire the tag. Click-to-session shrinkage from bounces before the tag loads, ad blockers and consent declines means **GA4 organic sessions usually run below GSC clicks**. Use [Impressions Trend](/nerve-centre/kpi-cards/google-search-console/impressions-trend) and the GA4 organic cards together rather than expecting a clean tie-out. For divergence investigations, use Vortex Mind. ## Known limitations / merchant FAQs **Why does the most recent day always look low?** Because GSC data is 2 to 3 days delayed and the latest days are partial. The tail of the line fills in on later refreshes. Read the alert against settled days only, never against the last 2 to 3 days. **The alert fired but my rankings look fine. What happened?** A click drop with rankings (average position) and impressions both stable is almost always a **CTR or snippet problem**: a title or meta-description change, losing a rich result, or a SERP-feature pushing your listing down the visible fold. Check [CTR Trend](/nerve-centre/kpi-cards/google-search-console/ctr-trend) and [Title/Meta Optimisation Candidates](/nerve-centre/kpi-cards/google-search-console/titlemeta-optimisation-candidates). **Does this include image, video and Discover clicks?** No, by default it is search type Web only. Image, Video, News and Discover are separate search types in GSC. If your property leans heavily on image search, ask for a profile that adds those types; otherwise the Web line is the right organic-demand signal. **Why is the alert vs the prior period and not vs last year?** A prior-period comparison catches acute regressions quickly (a migration, a core update, a robots slip). It does not account for year-on-year seasonality, so a genuine seasonal trough (post-Christmas, summer lull) can trip a false alert. Confirm against the same period last year before treating a seasonal dip as a fault. **My clicks dropped but impressions rose. Is that bad?** Usually yes for CTR. Rising impressions with falling clicks means you are appearing for more queries while winning a smaller share of clicks, often because you have started ranking on page two for broad terms. Segment with [CTR by Position Bucket](/nerve-centre/kpi-cards/google-search-console/ctr-by-position-bucket) to see whether the new impressions are low-position, low-CTR placements. **Why doesn't this match my GA4 organic sessions?** GSC counts clicks on the search result; GA4 counts sessions that land and fire the analytics tag. Bounces before the tag loads, consent declines and ad blockers all shrink clicks into fewer recorded sessions, so GA4 organic typically runs below GSC clicks. Treat them as correlated, not equal. **Can I change the 15% alert threshold?** Yes. The drop threshold is configurable per profile in the Sensitivity tab. Set it to match your normal volatility: a high-traffic property can use a tighter threshold, a low-traffic property a looser one to avoid noise. *** ### Tracked live in Vortex IQ Nerve Centre *Clicks Trend* is one of hundreds of KPI pulses Vortex IQ tracks across Google Search Console and 70+ other ecommerce connectors. Nerve Centre runs the detection layer; Vortex Mind investigates the cause when something moves; Ask Viq lets you interrogate any number in plain English. [Start for free](https://app.vortexiq.ai/login) or [book a demo](https://www.vortexiq.ai/contact-us) to see this metric running on your own data.