# Your organic traffic dropped: how to find the cause by date

Your search traffic fell. Use dates to trace the cause. You will compare periods in Search Console, match them to updates and deploys, and check the results page for changes.

Updated 2026-09-14 · Source: https://porteur.ai/guides/organic-traffic-dropped

## Start with dates in Search Console

Confirm the drop is from Google search, not all channels. In Search Console, open Performance. Switch Search type to Web. Set the date to the last 28 days compared to the previous period.

1. **Pick the right property** Use the domain property if you have it, so www and non-www, http and https, and subpaths are covered. A URL-prefix view can miss traffic.
2. **Use the comparison view** Click the date filter, choose Compare, select Last 28 days vs Previous period. Remember, Search Console data lags about two days.
3. **Split by page first** Click Pages. Sort by Clicks difference. Note the pages with the biggest losses. Export them if it helps you work.
4. **Then split by query** Click a losing page, then Queries. Sort by Clicks difference. This shows which searches fell for that page.
5. **Check positions and impressions** Toggle Average position and Impressions. If position worsened, it is ranking. If impressions fell but position is steady, demand or coverage changed.

The query table omits rare and anonymised searches, so its totals will be less than the page totals. Use it for direction, not a strict sum.

## Decide: ranking drop or demand drop

- Ranking drop: average position moved down, impressions steady or up. Fix the page, links, or intent match.
- Demand drop: impressions down, position steady. Check seasonality, brand interest, and results page features that absorb clicks.
- Coverage drop: impressions and clicks down for a page, and fewer queries show. Check indexation, canonicals, redirects, and robots.

Example: /guides/getting-started lost clicks. Impressions are flat. Average position on “getting started with yourproduct” fell. That is a ranking drop.

## Match the date to Google updates

Open the Google Search Status Dashboard. Look at the dates of core and spam updates. Do they overlap the fall? Expect volatility during an update and shortly after.

If your losses cluster on helpful guides or reviews, and they line up with a core or reviews-related change, treat it as a quality and intent problem, not a technical fault.

Google’s systems, as of 2026, pick and order results by relevance, quality, usability and context, across crawling, indexing and serving. There is no fee to appear. A core update shifts those signals, so your positions can move without any site change on your side.

## Rule out manual actions and security issues

1. **Open Security & Manual Actions** In Search Console, check Manual actions and Security issues. You will see a clear message if Google applied one.
2. **If you have a manual action** Read the examples in the notice, fix the issues on the listed pages, then file a reconsideration request. Be specific in what you changed and where.
3. **If you have security issues** Clean the hack or malware, close the hole, then request a review. Do not restore from a backup until you are sure the entry point is fixed.

If both sections are empty, carry on. Your drop is not a manual penalty.

## Check your deploys on those dates

Many traffic drops are self inflicted. A release added noindex, changed canonicals, broke internal links, or redirected key URLs. Trace what shipped on the day the graph turns.

1. **Diff the templates** Check head tags on a losing page. Look for meta robots, canonical, hreflang, and structured data changes.
2. **Test the URL** Use the URL Inspection tool on a loser. Confirm Google can crawl, sees the canonical you intend, and the page is indexed.
3. **Check redirects** Hit the URL with a redirect checker. A 301 to the wrong place or to a 404 will sink clicks overnight.
4. **Scan robots and sitemaps** Open robots.txt and your sitemap. A disallow on a key path or a stale sitemap can slow discovery after a move.
5. **Compare internal links** Did you remove the only link to /pricing from the header? Check click depth and nav changes that hide pages.

> The classic cause: a staging noindex shipped to production. Search for “noindex” across your templates before you deploy.

In the Page indexing report, “Alternate page with proper canonical tag” means Google agreed with your canonical to a different URL and left this one out. It is only a problem if the canonical is wrong.

## Check seasonality and brand demand

Compare the same 28 days last year in Search Console. If impressions fell in the same weeks then, the drop is seasonality, not a penalty.

Open your analytics and look at Organic Search sessions by week. If search clicks fell but Direct rose, some users now type your URL or use bookmarks. That is not a ranking issue.

Brand queries can move. Check clicks to your brand name query on the Site view. If that falls while generic queries are flat, run brand work, not only SEO fixes.

## Inspect the results page on key queries

1. **Search in the right country** Use an incognito window and a search location that matches your users. Results vary by location and history.
2. **Note the layout** Count how many organic links appear above the fold. A featured snippet, a local pack, or an AI Overview can push links down.
3. **Spot new rivals** Did a well known domain ship a better guide last month? Compare their page to yours for depth, freshness and examples.
4. **Check your snippet** Is your title truncated? Rewrite to about 60 characters. If your meta description is dull, write one that matches the search.

Example: yesterday “how to export data from yourproduct” gained an AI Overview that answers the steps inline. Impressions are flat, CTR halved, position steady. You will need to target a clickworthy gap, like edge cases, formats, or versions.

## Recheck coverage on the top losers

1. **Inspect the URL** In URL Inspection, confirm Indexing allowed, User declared and Google selected canonical match, and the last crawl is recent.
2. **Open the Page indexing report** Filter for the losing URL or path. Watch for Page with redirect, Excluded by ‘noindex’ tag, and Duplicate without user selected canonical.
3. **Fetch the HTML** View source and ensure the primary content and title exist without client side rendering. Google renders in a second wave, so delays can bite thin pages.
4. **Check server health** Look for spikes in 5xx or timeouts in your logs or uptime monitor on the dates. Serving issues drop clicks without any ranking change.

A fixed page loads fast, returns 200, has one canonical to itself, is indexable, and is linked from your top pages.

## Pick fixes from the symptom table

| Cause | What you will see | What to do |
| --- | --- | --- |
| Core update reweights quality | Average position worsens across many guides, impressions steady or up | Improve pages to match intent, add original insights, update examples, prune thin pages. Expect months for movement. |
| Spam update or manual action | Message in Search Console, sharp site wide losses | Fix the issues in the notice, remove manipulative patterns, request reconsideration if manual. |
| Robots or noindex shipped | Clicks drop to near zero on a path overnight | Remove the block, redeploy, request indexing for key URLs, resubmit the sitemap. |
| Wrong canonical | Clicks shift to a different URL, loser shows as ‘Alternate page with proper canonical’ | Point canonical to the correct URL, align internal links and sitemaps, remove duplicates. |
| Broken or changed redirects | Top URL now 301s to the wrong place or a 404 | Fix the redirect map, keep a single 301 to the final URL, update internal links. |
| Navigation or internal link loss | Fewer impressions and queries for specific pages | Restore links from header, footer or hubs. Add contextual links using descriptive anchor text. |
| Content decay | Positions slide slowly over months, rivals fresher | Refresh the page: new steps, screenshots, clarified scope, recent dates. Merge overlapping pages if needed. |
| Results page features expand | Impressions steady, CTR halves, position steady | Target subtopics the feature does not cover. Improve titles and snippets for the remaining clicks. |
| Seasonality or brand drop | Same weeks fell last year, or brand queries down | Plan campaigns for peaks. Do not overhaul SEO for a calendar trough. |
| International or device mismatch | Losses in one country or on mobile only | Check the Country and Device tabs. Fix hreflang, mobile usability, or localise content. |
| Server performance | Crawl stats drop, spikes in 5xx, timeouts | Stabilise hosting, fix errors, reduce TTFB, keep Core Web Vitals healthy. |
| URL structure change | Many 404s, ‘Page with redirect’ spiking | Ship a complete redirect map, update sitemaps, keep old URLs live with 301s. |

## What a repaired week looks like

You roll back a noindex on /blog, request indexing on ten posts, and resubmit the sitemap. Within days, impressions recover, positions hold, and clicks return to the old range.

You update /pricing with clearer plan names, FAQs, and structured data. The snippet improves. Average position is unchanged, but CTR rises and clicks offset part of a market dip.

## Questions

### Is this a penalty or just a ranking change?

Check Manual actions first. If that is empty, it is not a manual penalty. A core or spam update can move your rankings without any action on your site. Match dates to the Search Status Dashboard to tell which it is.

### How long will recovery take after a core update?

There is no set timeline. If you improve content quality and intent match, movement can take months. Google has said SEO work can take four months to a year to show benefit, and updates roll out over weeks.

### Why are impressions down but average position is steady?

Demand likely fell or the results page added features that reduced link visibility. Check the same weeks last year for seasonality. Search your key queries to see if a featured snippet or AI Overview is taking clicks.

### Search Console clicks are down, but my analytics traffic is flat. Why?

Users might be coming direct or through other channels. Search Console counts Google search clicks. Your analytics counts all sessions by channel. Also, Search Console data lags about two days and filters some queries.

### Should I disavow links when traffic drops?

Not by default. Disavow is for clear cases where you control spammy links you cannot remove and you have a manual action for links. For most drops, improve pages and internal links instead.

### How many days should I compare to see a real change?

Use 28 days vs the previous 28 for enough data. Then compare the same 28 days last year for seasonality. For fast hits from deploys, a 7 day view can reveal an overnight drop.

## Read next

- [The Search Console performance report, column by column](https://porteur.ai/guides/search-console-performance-report): Every column in the Google Search Console performance report explained with the traps that trip small sites, and how to act on each.
- [How to find declining pages in Search Console before the traffic is gone](https://porteur.ai/guides/find-declining-pages-in-search-console): Use Search Console to compare periods, sort by click loss, read queries, and act before a page’s traffic is gone. Works for SaaS and small shops.
- [A Google core update hit your site: what it means and what to do](https://porteur.ai/guides/google-core-update): Dropped after a Google core update? Check the dates, rule out spam or manual actions, and work a focused content plan. Here is how recovery happens.
- [Google spam updates: the policies they enforce and how to stay clear](https://porteur.ai/guides/google-spam-update): See what a Google spam update enforces, the policies that trip small product sites, how to check your risk, and how to recover if you’re hit.
- [Manual actions and the reconsideration request](https://porteur.ai/guides/manual-actions-and-reconsideration): Tell a Google manual action from an algorithmic drop, fix the cause, use disavow only when needed, and write a clear reconsideration request.
- [Content decay: pages that earned more before, and the refresh](https://porteur.ai/guides/content-decay): See how to spot content decay in Search Console, why it happens, and a clear refresh method. When to merge instead, and how to measure recovery.
- [Organic traffic](https://porteur.ai/glossary/organic-traffic): Organic traffic is visits from unpaid search results. See how it is counted, where it differs from ads and direct, and what to do to grow it.

Paste your homepage and get a free Porteur check in about thirty seconds: it reads your site, the searches around it and the rivals on them, and shows three findings. Free check: https://porteur.ai/