Interpret click, impression, position, CTR, query, and appearance incidents

Investigate daily rolling organic performance changes across pages, queries, templates, and result types.

Last checked 20 August 2026

Search Analytics incidents compare the latest stored rolling 7-day performance window with the corresponding 7-day window one week earlier. The compared periods do not overlap, so each result is a week-over-week comparison. A new rolling comparison can become eligible each day. The incidents identify rows that crossed TechDash's thresholds, but they do not prove why performance changed.

Open Incidents, select the incident, and review the affected values in its evidence before changing the site.

Page performance incidents

Page organic clicks dropped means a page row had at least 50 clicks in the prior window and its clicks fell by at least 30 percent. Check:

Whether impressions also fell, which can point to reduced visibility or demand
Whether average position worsened
Whether CTR fell while impressions remained
Recent title, content, canonical, redirect, or indexability changes
Matching availability or template incidents in TechDash

Page impressions dropped requires at least 200 prior impressions and a fall of at least 30 percent. This can follow ranking loss, deindexing, weaker query coverage, seasonality, or lower search demand.

Average position worsened requires at least 200 prior impressions and an increase of at least 3 in Google's average-position value. Higher position numbers are worse. Average position is an aggregate, so inspect the page and its queries in Search Console before treating it as one uniform ranking drop.

Click-through rate dropped requires at least 200 prior impressions and CTR at or below 80 percent of its previous value. Review title and snippet changes, position, intent, competing results, and new SERP features. Stable impressions do not guarantee the page appeared in the same positions or result layout.

Template incidents

Template organic clicks dropped groups page rows by the first one or two URL path segments. For example, /products/shoes/red contributes to /products/shoes. A group needs at least 50 prior clicks and a fall of at least 30 percent.

Treat the displayed path prefix as a cohort hint, not proof that all URLs use one technical template. Look for shared deployment, navigation, canonical, structured-data, rendering, or internal-link changes across the listed section.

Query incidents

Query organic clicks dropped applies the same 50-click and 30-percent thresholds to a query row.

Query impressions dropped applies the 200-impression and 30-percent thresholds.

The current check compares the top query rows returned by Google. It does not classify brand versus non-brand terms. Search Console can omit anonymized or lower-volume queries, so a missing row is not automatically a literal loss of every impression. Confirm important terms in Search Console with the same dates.

Search appearance incidents

Search appearance clicks or impressions dropped identifies a search appearance value, such as a product or rich-result category, that crossed either the click-loss or impression-loss threshold.

Correlate it with structured-data and template incidents. Also check whether Google renamed, reclassified, or changed eligibility for the appearance. TechDash requests search appearance as its own dimension, so the incident identifies the appearance type but does not provide a page-level breakdown.

Interpret the evidence carefully

The daily rolling requests use a 3-day reporting buffer and at most 1,000 rows per dimension. TechDash derives the requested labels from the UTC date, while Search Console interprets them in Pacific Time, so take care when recreating ranges near a day boundary. Google says Search Analytics returns top rows rather than a guaranteed complete export. Page and query grouping can also drop some data.

Before deciding that the site is broken:

Recreate the two 7-day ranges in Search Console.
Confirm the row still shows a material change.
Compare clicks, impressions, CTR, and position together.
Check seasonality, news, demand, country, device, and SERP changes.
Review TechDash incidents that opened around the same deployment or crawl.
Investigate affected URLs directly.

If the first run only stores a baseline, no performance-loss incident should open. Google API rate limits and quota errors are scheduler conditions and are not SEO incidents.

Resolve an incident only after the cause is understood or a later successful daily rolling comparison shows recovery. Do not use a single rolling change as proof that one technical fix caused the movement.