Skip to main content
Card class: HeroCategory: Search Performance
Total organic-search clicks across all queries, the first-line traffic-health signal. Drops here precede revenue drops by hours.

At a glance

The total number of clicks from Google’s organic results to your site over the period, summed across every query, page, country and device. This is the single most important Search Console number for an SEO or marketing team: it is the actual organic traffic Google sent you. Because organic visitors land before they browse and buy, a fall here is an early warning that visibly precedes any drop in on-site sessions or revenue, often by hours. The card compares Today, 7-day and 30-day totals against the matching prior period and fires when clicks fall more than 15% versus that prior period.
What it countsThe clicks metric from the Search Console Search Analytics API, summed over the selected window with no query, page, country or device filter. A click is counted when a user clicks a result that takes them to your site (and counts once per result, not per scroll).
Data sourceGoogle Search Console Search Analytics API (searchType=web by default), the same dataset behind Performance > Search results. Refreshed on the standard data pull; the underlying Google data is typically 2 to 3 days behind real time.
Time windowT / 7D / 30D vsP. Today, trailing 7 days and trailing 30 days, each shown against the immediately preceding period of equal length.
Alert triggerFires when Total Clicks drops more than 15% versus the prior period (drop >15% vsP). Sentiment key drives the red state on the card.
Why it leadsClicks are the closest Search Console signal to real organic traffic. A click drop shows here before the visitor reaches your analytics, your basket or your order table, which is why this is a hero card and a sensitivity-tracked alert.
What a drop usually meansRanking loss (positions slipping), index-coverage loss (pages dropped from the index), a Google algorithm or SERP-layout change, seasonality, or a tracking gap in the property itself (a removed verification, a property scope change).
CurrencyNot applicable. This card counts clicks, not money. Use the cross-channel revenue cards to translate clicks into pounds.
Rolesowner, marketing

Calculation

The value is a straight sum of the clicks metric returned by the Search Analytics API over the selected date range, with no dimension breakdown applied (the unfiltered property-level total). For each window the card requests the trailing period and the prior period of equal length, then computes the percentage change:
change% = (clicks_current − clicks_prior) ÷ clicks_prior × 100
The alert evaluates the 7-day and 30-day windows against their priors; if change% is below −15, the card turns red and the sensitivity rule fires. Note that the property-level total is queried without a query dimension, so it is NOT subject to the per-query anonymisation and 1,000-row cap that affect the breakdown cards. That makes Total Clicks the most complete click figure available from the API, which is exactly why it is the canary.

Worked example

A UK homeware retailer, Search Console connected, property https://www.thelinendrawer.co.uk/. The team is watching the 7-day window on 18 Jun 26.
WindowClicks (current)Clicks (prior)ChangeCard state
Today1,2101,460−17%Amber (intraday, incomplete)
7 days9,84012,180−19.2%Red, alert fires (>15% drop)
30 days47,30049,100−3.7%Green
Reading it:
  1. The 30-day window is calm, the 7-day window is not. That pattern, recent acute drop hidden inside a steady month, is the classic signature of a fresh ranking or indexing event rather than a slow seasonal decline. The 30-day average has not yet absorbed the last week’s loss.
  2. Triage order when this card fires. (a) Check Average Position and Position Change: if positions slipped, this is a ranking event. (b) Check Total Impressions: if impressions also fell, your visibility shrank (ranking or indexing); if impressions held but clicks fell, this is a CTR problem (a SERP-layout change, an AI overview eating clicks, or a title/meta regression). (c) Check Index Coverage Trend and Pages Not Indexed for a de-indexing batch. (d) Confirm it is real, not a tracking gap: a removed sitemap, a property re-verification, or a switch from URL-prefix to domain property all change the click base.
  3. For this brand the cause was impressions-stable, clicks-down. Impressions were flat week-on-week but clicks fell 19%. The drill-down showed a cluster of top non-branded queries that had gained a Google AI overview above the organic block, pushing the retailer’s result below the fold. No ranking was lost; the SERP simply changed shape. The fix was not a ranking fix but a content and rich-result play to compete for the new SERP real estate, tracked via CTR Opportunity Queries and Zero-Click Indicators.
  4. Why Today is only amber. The current-day figure is always incomplete because Google’s data lags 2 to 3 days, so the Today comparison is informational, not alert-grade. The hard alert is anchored to the 7-day and 30-day windows where the data has settled.
Rule of thumb. A red 7-day Total Clicks with steady impressions is a CTR or SERP-shape problem; a red 7-day Total Clicks with falling impressions is a ranking or indexing problem. Always read this card next to Total Impressions before deciding which.

Sibling cards merchants should reference together

CardWhy pair it with Total Clicks
Total ImpressionsThe visibility half of the pair. Clicks down + impressions down = ranking/indexing; clicks down + impressions flat = CTR/SERP shape.
Average CTRClicks ÷ impressions. Isolates whether a click drop is a visibility problem or a click-through problem.
Clicks TrendThe longitudinal view of this metric. Use to see whether a drop is acute or part of a longer slide.
Average PositionThe leading cause of click loss. Position slip almost always shows here first.
Top Queries by ClicksThe drill-down. Tells you which queries lost the clicks.
Pages Losing TrafficThe page-level drill-down. Pinpoints which URLs drove the total down.
Index Coverage TrendConfirms or rules out de-indexing as the cause of a click drop.
Organic-to-Revenue DivergenceThe downstream impact. Translates an organic-click change into revenue terms.

Reconciling against the source

Where to look in Search Console:
Performance > Search results, with the Total clicks tile selected, the Search type set to Web, and the date range matched to the card’s window. The headline number on that tile is the direct counterpart to this card.
The same total is available programmatically from the Search Analytics API (searchanalytics.query) with no dimensions array, summing clicks over the range. The unfiltered property query is the most complete figure Google will give you. Why our number may legitimately differ from the Search Console UI:
ReasonDirection of divergence
Data freshness lag. Google’s Search data is typically 2 to 3 days behind. If we pull before Google has finalised a day, our recent-day clicks read low until the data settles.Our recent days read low until finalised
Search type scope. The card counts Web results by default. The Search Console UI lets you add Image, Video, News and Discover, which would raise the total.UI higher if extra search types are included
Date boundary and time zone. Search Console reports in Pacific Time (America/Los_Angeles) day boundaries. If your window is aligned to a different zone, day edges shift.Marginal, at the window edges
Property scope. A domain property aggregates all subdomains and protocols; a URL-prefix property does not. Mismatched property type changes the base.Domain property reads higher
Anonymisation (breakdowns only). This is a property-level total, so it is NOT reduced by per-query anonymisation. Your per-query cards will under-sum versus this total.Total higher than the sum of query rows
Cross-connector reconciliation:
CardExpected relationshipWhat a divergence means
google_analytics Organic trafficGA4 organic sessions track Search Console clicks closely but are usually lower (some clicks bounce before GA4 fires, some are blocked by consent or ad-blockers).A widening gap suggests a measurement issue in GA4 (consent banner, broken tag), not a real organic loss.
shopify.total_revenueOrganic clicks lead revenue by hours. A Total Clicks drop is usually followed by an organic-attributed revenue dip.Revenue down without a click drop = a checkout or conversion problem, not a traffic problem.
Branded Search Cannibalisation (GSC vs Google Ads)If branded organic clicks fall while branded paid clicks rise, paid may simply be eating organic, not net-new traffic loss.Use it to avoid mis-reading a paid-cannibalisation shift as an organic regression.
This card is not a real-time alarm. Because Google’s data lags 2 to 3 days, Total Clicks confirms an organic trend rather than catching a live outage. For minute-level outage detection use the analytics-side real-time cards; use Total Clicks to confirm whether the cause was organic.

Known limitations / merchant FAQs

The card shows a drop but my Search Console Performance tab looks fine. Why? Almost always data freshness. Google finalises Search data 2 to 3 days after the fact, so the most recent day or two read artificially low until they settle. Re-check the same window in two days; if the UI now agrees, it was a lag, not a real drop. Also confirm both views use the Web search type and the same property. Clicks dropped but impressions are flat. Is that good or bad? Bad, but a different kind of bad. Flat impressions with falling clicks means your visibility is intact but fewer people are clicking, so this is a click-through-rate problem: a SERP-layout change, an AI overview pushing you down, a competitor’s richer snippet, or a weakened title and meta description. Investigate via Average CTR and CTR Opportunity Queries, not via ranking work. The sum of my Top Queries by Clicks is lower than Total Clicks. Is one wrong? Neither. Total Clicks is the unfiltered property total. The per-query breakdown drops rare, anonymised queries to protect user privacy and the UI caps at 1,000 rows, so the query-level rows will always sum to less than the property total. The gap is your anonymised long tail, and it is normal for it to be 10 to 30% of the total. Why is the alert anchored to 7-day and 30-day, not Today? The Today figure is structurally incomplete because of Google’s 2 to 3 day lag, so an intraday comparison would fire false alarms every morning. The hard alert uses the settled 7-day and 30-day windows; Today is shown for context only and stays amber rather than red. Could a click drop be a tracking artefact rather than a real loss? Yes, and you should rule it out first. Re-verifying the property, switching from a URL-prefix to a domain property, losing a sitemap, or a temporary verification lapse can all shrink the click base without any real ranking change. Check the property settings and verification status in Search Console before assuming an SEO cause. Does this include clicks from Google Images, Discover or News? By default the card counts Web search clicks only. Image, Video, News and Discover are separate search types in Search Console and are not summed in here unless explicitly included. If your business depends on Discover or Image traffic, read those search types in the Search Console UI separately. Why doesn’t a 15% drop always mean something is broken? Seasonality and the calendar move organic clicks materially: a bank holiday, the end of a sale, or a category going out of season can all produce a genuine, expected 15%+ swing. Read the alert next to Clicks Trend and last year’s same-period shape before treating it as a regression. The alert is a prompt to look, not a verdict.

Tracked live in Vortex IQ Nerve Centre

Total Clicks 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 or book a demo to see this metric running on your own data.