Why did my organic traffic drop?
First establish what fell: analytics sessions, Google clicks, impressions, or rankings. Then isolate the affected pages and queries using comparable periods. A traffic drop can have several causes; the graph alone does not tell you whether to change content, fix indexing, or investigate measurement.
On this page
The first useful action is to localize the loss. Rewriting twenty pages before you know whether the drop is in Google clicks or analytics tracking can make the investigation harder and introduce new problems.
Use the diagnostic below to choose the next evidence to collect. It works without signing in; it does not fetch your website or claim to know what happened to it.
Find your first check
Establish the baseline before making an edit.
- 1Open Search Console → Performance → Search results and use Web search.
- 2Compare two equal, complete periods, then sort Pages by lost clicks.
- 3Choose one important losing page and check its queries before investigating the whole site.
This checklist uses the pattern you select. It has not accessed or diagnosed your website.
Investigate my Search Console data with PercyEstablish a clean comparison
Record the date you first noticed the change and where you saw it. Keep a separate note of recent releases, migrations, analytics changes, and business events. A release on the same date may be relevant, but timing alone is not proof.
Compare complete periods of equal length. A seven-day emergency check can help you localize a sudden outage; a longer comparison is usually more informative for a gradual decline. Keep the weekday mix and reporting filters consistent, and consider whether a seasonal comparison is more meaningful.
Google's traffic-drop documentation recommends investigating patterns across pages, queries, search types, and longer-term demand. It also identifies technical issues, ranking changes, and data anomalies as possibilities. Use those possibilities as an investigation checklist rather than assigning a cause from the shape of the chart.
Separate analytics losses from Google search losses
An analytics session and a Search Console click are different measurements. They should not be expected to match one-for-one. The useful question is whether their trends changed together for the same relevant landing pages.
If analytics sessions fall while Google clicks remain broadly steady, check the journey after the click. Does the landing page load? Was the tracking script changed? Did consent behavior change? Does a redirect lose attribution? Did the report switch channels or include a different set of pages?
If Google clicks also fall, continue the search investigation. Keep the analytics question open if its decline is disproportionately large; more than one problem can happen at once.
Identify the pages responsible for the loss
In Search Console, compare the periods under Performance → Search results and inspect Pages. Focus first on the pages contributing the largest absolute loss that matter to your business.
This illustrative example shows why a percentage-only ranking is misleading:
| Page | Earlier clicks | Later clicks | Change |
|---|---|---|---|
| Service guide | 600 | 420 | −180 |
| Small glossary entry | 4 | 1 | −3 |
| Product explanation | 120 | 105 | −15 |
The glossary lost 75%, but it explains very little of the overall loss. The service guide is the useful first investigation. These numbers illustrate the method; they are not a Percy customer result.
Select the important page and inspect its queries. Keep its page filter while comparing devices or countries. Look for a specific set of lost searches, not just an average position for the whole domain.
Test the explanation against another page
Choose a comparable page that held steady. This gives you a useful reference point:
- Did both pages use the same template and release?
- Did they have similar indexing and canonical behavior?
- Did their main queries have similar seasonal demand?
- Is one page informational while the other supports a buying decision?
The comparison does not create a controlled experiment, but it can rule out an explanation that should have affected both pages equally.
For suspected indexing problems, inspect the affected URL and its live response. Our guides explain crawled but not indexed, robots.txt blocks, and Google choosing a different canonical. A legitimate exclusion on an unrelated URL does not explain the loss on your money page.
What the common patterns do and do not establish
Clicks down, impressions similar: investigate query mix, rankings, and the actual search result. An inaccurate title may deserve correction, but stable aggregate impressions do not isolate its effect.
Clicks and impressions down: investigate both visibility and demand. A page can lose impressions because it appears less often, because fewer people search, or because the mix of searches changes.
A different page now receives the query: check whether the new page satisfies the same intent and whether combined performance suffered. Two pages appearing for a query is not automatically harmful. Use the cannibalization investigation.
The decline coincides with an update: record the timing and inspect the pattern. Do not turn a correlation into a penalty diagnosis. Likewise, seeing an AI answer in today's results does not prove it caused a historical loss without a meaningful comparison.
Turn the investigation into one next action
Write the conclusion in three parts: what changed, what supports the explanation, and what remains unknown. Then pick the next action that resolves the biggest uncertainty.
For example: “The service guide lost clicks from two commercial queries. Its live page and canonical are unchanged. We do not yet know whether competitors better satisfy the request. Compare those results and the page's coverage before changing the title.”
If a technical error is confirmed, fix and verify that error. If the page is healthy but its answer is weak, make a focused improvement. If the evidence is sparse, collect more comparable data. Once the issue is understood, the quick-win workflow helps you prioritize the work.
Investigate your site in Percy
Use the prepared prompt to bring the page and query comparison into your connected SEO workspace. You can edit it to specify the dates you care about. Percy uses Search Console and page research; you may still need to check analytics or deployment records separately.
Investigate this site's Google organic traffic. Compare the last 28 complete days with the previous 28 and identify the pages and queries contributing most to lost clicks. Check relevant page evidence and separate observed changes from possible causes, including query mix and seasonality. Do not infer an algorithm penalty or an AI Overview effect from dates alone. If there is no meaningful decline, tell me. End with the first check or action worth taking.