When traffic falls, the instinct is to change something at once. That often makes the cause harder to find. A short, orderly check usually points to the answer.

Confirm the drop is real

First check that analytics is still tracking. A removed or broken tag looks exactly like a traffic crash. Compare against Search Console clicks. If analytics fell and Search Console did not, the problem is likely measurement.

Find out when it started. Use a daily view and note the exact date. Then ask what happened on or just before that date: a site change, a deployment, a plugin update or a Google announcement.

Segment the loss

In Search Console, compare the period after the drop with the period before. Split by page, query, device and country. Is the loss spread across the whole site, or concentrated in a few pages or one section?

Rule out technical causes. Check for accidental noindex tags, blocked robots.txt, broken redirects, server errors, slow response, or a changed URL structure. Inspect a few affected URLs.

Consider demand and seasonality

Some topics have seasons or news cycles. Compare with the same period last year and check whether searches for the topic fell, using a trends tool.

Look at the search results themselves. Search for your main queries. Has the layout changed? Are there new features, such as answer boxes, that push organic results down? Have stronger pages arrived?

Review content and intent

Check whether the affected pages match what searchers want now, and whether competitors improved. A gradual decline often means the page has aged.

Questions to ask about the shape of the drop

  • Sudden cliff: suspect a technical error, tracking break or manual action.
  • Step down on a date: look for a site change or search update.
  • Gradual slide: suspect ageing content or stronger competitors.
  • Seasonal wave: compare with last year.
  • One section only: check changes to that section or its internal links.

Reactions that make it worse

Do not rewrite the whole site in a panic. Do not undo working changes without evidence. Do not trust one tool alone; compare Search Console, analytics and server logs. Keep a note of every change you make, so you can see what happened if numbers move again.

A sample diagnosis timeline

Day 1: confirm the drop in Search Console and analytics. Day 2: identify the date it began and list everything that changed around then. Day 3: segment by page and query and check technical issues. Day 4: review the search results for your main queries. Day 5: decide on one or two actions and write down what you expect to happen. Then wait at least two weeks before judging, because search data moves slowly.

The point of writing the plan down is to avoid reacting to every dip. If you act before you understand, you may make a harmless change look like the cause.

Checking whether Google had an update

Google publishes a Search Status Dashboard that lists ranking updates and incidents. Compare its dates with the start of your drop. If a core update lines up with your decline, read Google's guidance on helpful content and compare your pages with those that now rank above you. There is rarely a quick fix, so plan improvements to content quality over months, not days.

Keep a change log. A simple dated log of changes to your site makes future diagnoses much faster. Record deployments, template edits, plugin changes, redirects, title rewrites and large content updates. When a number changes, you can see at once what happened nearby.

Act on one hypothesis at a time

Fix the likely cause, note the date and watch the data for a few weeks. If a Google update coincides with the fall, focus on improving quality, since there is rarely a quick technical fix.