Why Did My Organic Traffic Drop? A Diagnosis Checklist for IT Company Websites

Before you rewrite a page, rule out the ordinary causes of an organic traffic drop in this order: broken tracking, a technical fault, a site move, seasonality, a Google update, then lower demand.

Forty-person IT services firm. New website goes live on a Friday. By the next Wednesday, organic traffic is off by about a third and two people in the leadership meeting are sure they know why. One says Google changed something. The other says the new menu confuses visitors. Nobody has opened Search Console yet. The firm is invented, but I suspect you’ve heard this argument before.

The theory is rarely the expensive part. The fix that follows it is. Roll back a redesign that was fine, or delete the old posts that quietly feed the pricing page, and a small dip can turn into a bigger one. So the boring checks go first.

What follows runs from cheap and likely to slow and rare. Each step rests on Google Search Central, web.dev or a crawler vendor’s own documentation, because forum advice is where the deleting usually starts.

Confirm the Organic Traffic Drop Is Real

Start with the data, not the site. Open Search Console and your analytics side by side. They count different things. Search Console reports impressions and clicks on Google while your analytics reports visits, which means that if one fell and the other didn’t, you have a tracking question rather than a ranking question. Data first. Theories later.

Google’s guide to debugging drops in Search traffic says to check the Search Console Data Anomalies page for a change in data processing or a logging error. Do that first. It takes a minute. Nothing else matters if the chart is wrong.

Then widen the window. In the Performance report, set the date range to the last 16 months, which is how Google suggests separating a real drop from one that happens every year, and then use the compare tab to set the drop period against the previous period and against the same months a year earlier. A dip every November is a calendar, not a crisis.

Check the other channels too. If paid, direct and referral traffic fell on the same day, search probably isn’t the culprit. That’s our read, not Google’s. It saves hours.

One more test for demand. Take the queries that lost the biggest share of clicks and run them through Google Trends. The same guide recommends it. If interest fell across the web, your site didn’t fail. The market moved. Different problem, different fix.

Read the Shape of the Drop

Google’s debugging guide pairs sketches of traffic lines with likely causes, so a broad fall can come from an algorithm update or a site-wide security, spam or technical issue, while a repeating dip is seasonality and a single odd day may be a reporting glitch. The table below turns that into a first move.

Read impressions and clicks together. Google says that when both fall, you work through the cause list. When impressions hold and only clicks fall, look at your titles and snippets first, because searchers may not understand what the page offers or may simply prefer the richer result a competitor is showing.

Then ask which pages lost the traffic. Sort the Pages table by clicks difference. One page, a group of pages or the whole site? A site-wide fall sends you to the Page indexing report, and a group of pages sends you to the URL Inspection tool, where you check a few URLs one at a time.

Technical Faults That Cause an Organic Traffic Drop on IT Company Sites

Technical faults are the cheapest to check and the fastest to fix, so they go before any theory about Google. Cheap checks first. Google lists server availability, robots.txt fetching, “page not found” errors and misplaced noindex tags, and points to the Crawl stats and Page indexing reports for a spike. IT company sites have a few favorites.

Staging rules come first. Developers often block crawling while a new site is built. Google’s site move guidance warns that owners who do this must prepare what the live robots.txt and noindex rules should look like before the move starts, and if nobody wrote that list, the block ships with the launch. One line in a text file can stop Google crawling a whole site. Check it in thirty seconds. Seriously.

Redirects are second. A migration changes URLs, and Google says a medium-sized site can take a few weeks or more before the new URLs replace the old ones in results. A dip in that window is expected. A dip that isn’t recovering is not. Boring, common, fixable. The usual faults are missing permanent redirects, chains of several hops and old URLs left to 404. Our website migration SEO checklist covers the full list.

This next one will feel familiar to an IT audience. A web application firewall, a CDN rule or a security plugin gets tightened and starts challenging crawlers. Humans never notice. Server errors in the Crawl stats report do. Look there. Ask your host or security vendor to confirm that requests really coming from Google are let through.

Speed matters less than owners fear, but check it. web.dev sets the Core Web Vitals targets at the 75th percentile of page loads. Largest Contentful Paint within 2.5 seconds. Interaction to Next Paint of 200 milliseconds or less. Cumulative Layout Shift of 0.1 or less. Those are targets for a good experience, not a ranking formula. Treat a miss as one more fix, and as the explanation only if the timing matches the drop.

Last, a newer mix-up. Owners who block AI crawlers sometimes worry they just cut off Google. Google says its Google-Extended token doesn’t impact a site’s inclusion in Google Search and isn’t a ranking signal. OpenAI says its OAI-SearchBot and GPTBot settings are independent of each other, one for ChatGPT search results and one for model training. A rule aimed at Googlebot, or at every crawler, is a different matter.

Our technical SEO checklist for MSP websites goes deeper on every row of that table.

Update, Penalty or Demand: Sorting the Slow Causes

If the data is real and the technical checks come back clean, the cause is slower and harder to prove. Three suspects remain.

The first is a core update. Google makes several broad changes a year and lists them on its Search Status Dashboard. Its core update guidance is specific. Wait at least a full week after the update finishes rolling out, then compare that week with the week before the update began, because comparing a half-finished update with last month proves nothing. Patience is cheap.

Then look at position for your top pages. A slide from position 2 to 4 is small. Google says not to take drastic action and to avoid changing content that already performs. A fall from position 4 to 29 across a wide range of terms is large, and for that Google asks you to assess the whole site, not single pages, for whether it is helpful, reliable and people-first.

The second suspect is the word everyone reaches for. Penalty. Open the Manual actions report and the Security issues report in Search Console. If both are empty, you don’t have a manual action. The cause sits elsewhere. Google also says content can rank lower for breaking its spam policies even when no manual action exists, so read those policies once and check your own site against them honestly.

The third is demand. Searches that used to send a click now end on the results page, a shift we cover in our post on zero click searches. It looks exactly like this in the data: impressions hold, clicks fall, rankings look fine. Weak titles and snippets produce the same pattern. Test both before you decide.

What to Fix First, and What to Leave Alone

Fix the foundation first. In this order:

1. Confirm the data. Tracking, the Data Anomalies page, the other channels and the 16-month view.
2. Rule out the cheap faults. Robots.txt, noindex, redirects, server errors. Fix what you find today.
3. Open the Manual actions and Security issues reports. Ten minutes, and a clean result closes a whole branch of the tree.
4. Line up the dates. Set the start of the drop against your launch log, plugin updates, CDN changes and Google’s update list.
5. Measure position on your top pages, then decide whether the fall is small enough to wait out.
6. Write down every change with its date. You can’t judge a fix you can’t date, and Google says some changes show up in days while others take months.

Now the part that saves money. Don’t delete content because traffic fell. Google calls deletion a last resort, for content that can’t be salvaged. Don’t rewrite a page that still ranks well, since Google recommends avoiding radical changes to a page that already performs and a rewrite is the easiest way to lose a position you were holding. Don’t make a quick fix because a forum said some page element was bad for SEO.

And don’t accept a promised recovery date from anyone. Google says plainly that nothing you change on your site is certain to move results. If Google won’t promise it, a vendor can’t sell it honestly. We don’t promise one either. Nobody should.

When to Bring Someone In

You can run the first four steps yourself in an afternoon. Some findings need more than an afternoon. Here’s when.

• Search Console shows a manual action.
• The fall in position is large, covers the whole site and has lasted for weeks.
• A migration was done months ago and the line never came back.
• You can’t reconstruct what changed and when. That one is common, and it is a process failure, not a search failure.

Ideas are cheap. Execution wins. If the finding is a technical fault, your developer can fix it. Done. If it’s a penalty or a site-wide quality problem, our penalty recovery services are built for that, and our SEO, AEO and GEO services cover the long-run work of keeping the line from falling again. To go through your own numbers with us, book a strategy call.