When traffic drops, the instinct is to start rewriting posts. Sometimes the readers never left: the tracking broke, the comparison was unfair, or a bot that used to inflate the numbers stopped coming.

Work through the checks in order. The early ones take a minute and rule out the cases where nothing needs fixing.

1. Check that tracking still works

A site that stopped recording looks exactly like a site nobody visited. Rule that out before anything else.

  • Open your site in a private window and view the page source. Your analytics script should be there. In Vireo it’s tracker.js.
  • Think back to the day the drop started. A new theme, a page builder update, a caching or optimisation plugin, or a consent banner can all stop a tracking script from loading or running.
  • Clear your page cache after any of those changes. Cached pages keep serving whatever HTML they were built with.

Vireo checks some of this for you. If no pageviews were recorded yesterday on a site that was busy the week before, the Overview says so in What changed: “No pageviews were recorded yesterday, but this site was busy the week before. Tracking may have stopped.” Tools, Site Health also gets a test called “Vireo Analytics is recording visits”, which turns into a critical issue if the job that records visits stops running or the database refuses writes. The troubleshooting page lists every message and what to do about it.

2. Check whether the counting changed

If tracking works, ask whether you’re measuring the same thing as before.

  • Did you switch analytics tools? A tool that filters bots will show fewer visits than one that doesn’t, for the same readers. Why your analytics tools show different numbers covers the usual gaps.
  • Did you add an excluded IP range, path or country? Exclusions apply from the moment you save them.
  • Did a bot stop visiting? If your old numbers included a scraper or a monitor that ran JavaScript, losing it looks like losing readers.
  • Did you add a consent banner, or change its settings? A tool that waits for consent counts fewer people.

3. Compare like with like

A fair comparison rules out a lot of false alarms.

Compare whole weeks. Most sites have a weekly rhythm, and a range that swaps a Saturday for a Tuesday can move the total on its own.

Then check the season. Many topics have a yearly cycle. Gardening posts peak in spring, and anything work-related dips over the summer holidays. A hypothetical recipe blog could easily see December at twice the traffic of January, every year, with nothing wrong.

Vireo’s comparison is against the period of the same length just before, so a December-to-January drop will look like a drop. To check the season, open the Year in review for last year and look at pageviews by month. If last January fell by a similar share, you’re looking at the calendar. You can also set a Custom range to the same dates last year and compare the figures by hand.

4. Find where the readers went

A real drop usually comes from a few pages or sources. Find them before you change anything.

The summary line at the top of Vireo’s Overview names the cause when one is big enough. If a single page or source accounts for a large part of the fall, you’ll see a line such as “Most of the drop is traffic that stopped coming from news.example.com.” Below it, What changed lists the pages and sources that Lost the most against the previous period.

Then narrow it down with the Source filter. Set it to Search, then to Social, then to Other sites, and see which one fell. Each answer points to a different fix.

5. If search fell, open Search Console per post

A drop in search traffic has three common shapes, and Search Console tells them apart. For each post that lost readers, look at its searches:

  • Position fell. The post ranks lower for the searches that used to bring readers. Someone published something better, or the post went out of date.
  • Position held, impressions fell. Fewer people are searching for the topic, which is the season again, or interest is fading.
  • Position and impressions held, clicks fell. People see the post and don’t choose it. Google may be showing more above it on the results page, or a competing result has a better title.

In Vireo, open a post’s stats from Top pages and look at “Searches that found this post”, with clicks and average position for each search. Hover over a click count to see how many times the post was shown. Set the range before and after the drop and compare. Connecting Search Console is a one-time setup, and Vireo can fetch the last 90 days once it’s connected.

If many posts fell on the same day, check the Google Search Status Dashboard for a ranking update around that date. A site-wide shift after an update is a different problem from one post slipping.

When the lost traffic came from one site, click it in Where visitors come from. Its own screen shows a daily chart and “Posts it sent people to”, so you can see when it stopped and which post it was linking to. Then go and look. The link may have been removed, or it was in a newsletter that went out once.

7. Check for broken pages

A changed permalink or a deleted post turns every link and every search result pointing at it into a 404. If 404 errors jump, What changed warns you with a line naming the path that gets hit most, such as “404 errors are up 80%, mostly on /old-guide/” (the figure there is made up). The Issues tab lists broken links. Redirect the old address to the closest live page.

8. Write down what you found

Once you know the cause, pin it to the date with a Note at the foot of the Overview, such as “Link from the partner site removed”. The note puts a pin on the traffic chart, so in six months the dip still has its explanation. Add one when you make a fix as well, and you’ll be able to see whether it worked.