TRAFFIC & RANKINGS · FIELD GUIDE

Organic traffic dropped: what to check first

By SEO Orbiter · Updated

First confirm that completed Search Console days show a decline in Google search clicks. Then separate losses of visibility from lower click-through rates and isolate the pages responsible. An analytics-session drop alone does not establish a Google ranking problem.

Confirm the same thing is being measured

Write down the property, search type, filters and completed date range before exporting anything. Compare equal-length periods with the same weekday mix. If your analytics sessions fell but Search Console clicks did not, first investigate tracking or attribution rather than rewriting pages.

  • Exclude incomplete recent days; keep missing days separate from zero clicks.
  • Compare the same country, device and search type.
  • Check reporting incidents and whether a property or analytics configuration changed.

Find the pages carrying the loss

Sort page changes by lost clicks, not percentage alone. Group related URLs into useful sections such as product pages, help articles and the homepage. A large percentage on a tiny page is a different priority from a modest decline across your main acquisition pages.

Worked example

Illustrative calculation: a page goes from 400 to 260 clicks (−140), while another goes from 10 to 2 (−8). Investigate the first page before the larger percentage loss. Do not expect visible query rows to explain every site-level click.

Read clicks, impressions and position together

Falling impressions can reflect lost visibility, a change in search demand or a different query mix. Compare matching queries and pages before interpreting average position. If impressions remain similar but clicks fall, investigate CTR. If a URL no longer appears, check indexing and its canonical target.

  • Similar positions, fewer impressions: inspect demand and query composition.
  • Worse positions on matching queries: follow the ranking-drop investigation.
  • One section disappears: sample HTTP responses, indexing directives and redirects.

Build a dated evidence trail

Record the first completed day of the loss, deployments, redirects and observed page changes. Check Google’s published update and incident information as context. Timing alone does not show that an update or a title edit caused the loss. Do not undo several unrelated changes at once.

Choose one action and define the follow-up

For a confirmed technical fault, record the exact URL, observed response, intended behavior and the person responsible. After a fix, verify the response again and follow subsequent completed search data. For an unexplained decline, preserve the hypothesis and next check instead of recording an invented cause.

Worked example

Investigation note: “Three product URLs return noindex after Monday’s release. Intended: indexable pages. Remove the accidental directive, verify a fresh response, then check Google’s next reported crawl.” Recovery may lag and is not guaranteed.

Browse all diagnosis guides

Primary references

These references describe Google’s reporting and crawling behavior. The worked examples above are illustrative, not customer results.