Your Traffic Number Is Wrong This Month. What to Count Instead

Branded card for the article Your Traffic Number Is Wrong This Month. What to Count Instead on imivantan.com

Written by

in

Three things distorted your traffic number in the last ten days, and none of them was your site getting worse. Google undercounted impressions in its Search Console Generative AI report from 9 to 11 November, the November core update started inside that same gap, and a share of what your analytics calls “direct” was never a person. This month the session graph is a story about measurement, not demand — so read completed actions instead.

The short version

  • Google confirmed a logging error lowered impressions in the Search Console Generative AI performance report for 9–11 November. The data is missing; the visibility was not.
  • The November 2026 core update started on 10 November and should be finishing around now.
  • Google’s advice is to wait a full week after the rollout completes before comparing anything at all.
  • “Direct” in GA4 is the bucket for traffic with no referrer. It is not a channel and it never was.
  • For the next two weeks, count five completed actions a week and leave the session graph alone.

What actually broke, in order

9–11 November: a logging error. Google’s entry on its data anomalies page reads: “A logging error caused a decrease in impressions on the Generative AI performance report in Search for data from November 9 – November 11, 2026. This issue affects data logging only.” That report shows impressions only and no clicks, so the damage is confined to one number on one screen. Annotate those three days in whatever dashboard you keep, because in six months the dip will look like a ranking event.

10 November: the core update started. Google described it as “a regular update designed to better surface relevant, satisfying content”, global and in all languages, with a rollout of up to two weeks. Glenn Gabe’s running notes put visible movement at around 13 November and kept repeating one thing: Search Console is the source of truth this time, because the visibility tools were struggling and because a wave of “phantom agent clicks” earlier in the month had slipped through Google’s systems. Two measurement systems were wobbling at once.

10 November, same day: a new counter appeared. OpenAI opened Business Hub in beta, where a business can claim its profile and see, for the past 28 days, how often ChatGPT mentioned it and how many website clicks it sent. Search Engine Journal claimed its own profile and reported 353,356 mentions against 2,663 website clicks for 14 October to 10 November. Look at that ratio. A lot of mentions, a small number of clicks is exactly what being quoted in an AI answer looks like from the inside.

Late November: the calendar. Thanksgiving, Black Friday and Cyber Monday fall inside the first clean comparison week, so any retail site comparing that week to an ordinary one is comparing two kinds of behaviour, not two versions of its content.

Why “direct” is not a channel

GA4 files a session as direct when there is no referrer it recognises. That covers someone typing your domain, a bookmark, an email client that strips the referrer, an RSS reader, a preview bot fetching your page for a link card, and an AI assistant opening your page to answer a question. All of it lands in one column labelled direct, and that column is usually the biggest one on a small site.

One founder published his own split on Indie Hackers this month: 46 Organic Search sessions against 491 Direct sessions from 25 October to 11 November. He was careful about it in a way I respect — he wrote that he could not point at a day with 79 total sessions and claim SEO brought 79 visitors. The channel pie on a site this size tells you almost nothing: the sample is tiny and the buckets are unreliable.

So stop optimising the pie. Pick the action that proves a person got value, and count that instead.

Five completed actions worth counting

Action What it proves Where to capture it
A tool run finishes Someone used the thing, not just loaded it One custom event on the result state
A file download The output left your site Automatic file_download, filtered to real formats
A form or email reply A human typed something Your inbox, no analytics needed
A click from a post to your paid page Intent survived the read One event on that link
A second visit within seven days Habit, not a one-off A user-scoped exploration

Two are enough for a one-person site: the tool-run event and the form submission, because one measures the product and the other measures the person. If your site is a blog, swap the first row for “read to the end of a post” — an event at 90 per cent scroll depth separates a reader from a bounce in a way average engagement time never does.

A ten-minute Monday log

The reason a bad week confuses you is that you compare it to a number you half-remember. Keep the number somewhere you can see it, in the same shape every week:

week:        2026-11-16 .. 2026-11-22
core update: in progress / finished
tool runs:   ___
downloads:   ___
forms:       ___
GSC clicks:  ___
one line:    what changed, and the reason I think so

Five numbers and one sentence, ten minutes a week. Six weeks of it tells you more than any dashboard, because the sentence forces you to write down the cause instead of guessing later.

Once a month, also check how much of your server log is agents rather than people. On a Plesk server the access log sits at /var/www/vhosts/<domain>/logs/proxy_access_ssl_log; on cPanel look under ~/logs. This counts the crawler families that matter by name:

grep -Eio 'gptbot|oai-searchbot|chatgpt-user|claudebot|perplexitybot|ccbot|google-extended' access.log | sort | uniq -c | sort -rn

A training crawler reading every post is a cost. A search crawler indexing your tool pages is the reason anyone finds them at all. A user-triggered fetch — ChatGPT-User or Perplexity-User — is a person on the other end of a question, and it is the one kind of agent traffic that can turn into a sale.

What to ignore until the rollout ends

  • Title rewrites. Mid-rollout you cannot tell whether a change helped or the update did.
  • Deleting pages after a three-day dip. Three days of a two-week rollout is noise, and a deletion is permanent.
  • Week-over-week comparisons that straddle 9 November. One analysis of the anomalies page suggests comparing 14 days before 9 November with 14 days after 11 November instead, and using main-report clicks as the steadier signal.
  • “We lost 40 per cent of AI impressions” taken from the Generative AI report. That report counts impressions only, and it was undercounting for three of those days.

None of this is a reason to stop working, only to stop reacting for two weeks. The pages still need writing; you just cannot grade them yet.

Checklist for the next two weeks

  • Annotate 9–11 November on every dashboard you keep.
  • Write down today’s tool runs, downloads and form counts, so next Monday has a baseline.
  • Check that your analytics fires one completion event, and that it survives a bot visit — most do not.
  • Run the log filter once and note the agent share. That number explains a lot of “direct”.
  • If you run a real business, claim your ChatGPT business profile and screenshot the 28-day baseline.
  • Set a reminder for one week after Google marks the rollout complete, not before.

The update will finish, the logging gap will close or it will not, and the session graph will go back to being roughly true. What survives is the habit of measuring the five things only a person can do on your site. That habit works in a quiet month and in a month like this one, when every number moved for reasons that had nothing to do with you.

For the other half — why a page can be indexed and still never rank — see 88 tools, 8 organic sessions. And if you have not yet decided which crawlers you are letting in, the file agents read before they touch your site is the place to start. The core update itself I covered the week it began, in what to do while it rolls out.

Comments

Leave a Reply

Your email address will not be published. Required fields are marked *