Pete Hahn

For 6/2/26, the update you provided was nearly an exact match. And to clear up one important detail, I was using Google Analytics as my comparison and NOT Google Search Console.

Yesterday GA reported 95 visitors and 125 page views. Koko reported 91 and 133. Nearly an exact match.

I’m sure when websites have very large traffic figures this issue is not even perceptible. It’s only when the traffic drys up to a trickle that things like this become more obvious. My site used to have really good traffic until the AI thing took over. Still struggling to find out how to operate a website in this new paradigm.

Thanks for working out those details and publishing that update. Seems to have resolved the issue. Until the AI bots find another way to screw something up.

Thanks for checking in on this topic. I understand your question regarding Google Search console, and I will explain a bit more detail. From the left-hand panel on Google Search Console you to to:

Life cycle –> Engagement –> Pages and screens

From there I am able to configure a report that shows me actual page views. This value has always been very closely correlated in the past. But in the past week or so I have seen a very large divergence. But as you mentioned, there is a chance this is showing only page views related to Google search activity and not total page view volume from all sources? However, when I compare these values to what I get from Google Analytics they tend to line up very closely. And GA is reading page views from all sources.

I can also view live traffic through the Wordfence plugin. And they are also having difficulty differentiating between bots and humans. But for them, that is not a mission critical issue. One of the most common things they miss is the “applebot” crawler. Wordfence counts all of those hits as humans. And the pattern typically results in a nearly equal number of “visitors” and “page views”. Because every hit from applebot comes from a different IP.

So that is part of the pattern as well. In the past whether using JetPack or Koko I typically get at least 3 times the pages views as visitors. But for the day of May 27th, 28th and 29th that ratio is not even close. As follows:

May 27th: Visitors = 169 and Page views 264

May 28th: Visitors = 168 and Page views 202

May 29th: Visitors = 165 and Page views 346

May 25th was the worst of the bunch, showing 97 visitors with only 105 page views.

When you examine the site traffic through any other tool those ratios are way off. My site typically gets at least 3-4 page views for each unique visitor.

And today’s traffic so far is more typical. Koko currently shows Visitors = 52 and Page view = 203

This stuff is really difficult to troubleshoot so I understand the challenge. But I hope you can identify something and find a way to refine it further.

This issue occurred again on 3/27/26

Google Search Console reports page views of 99

Koko reports page view of 264

Please let me know if I can provide any additional details to help you identify what is wrong. I’m certain this is happen to every other website using Koko. Probably has do with the filters used for determining bot/crawler versus human page views.

Yeah, it’s been a pretty strange rabbit trail for certain. I can block those bots by specific criteria. Seems there are bots that have a list of all my BuddyPress members, and they (several bots actually) just keep crawling every member profile. To what end? I have no clue. But I changed the settings so now only members who are logged in can view member profiles. So the bots only see “Member only area” when they try to access those pages. Bizarre stuff.

If anyone has some more insight into this I would love to get some details.

Thanks for trying to help. But unfortunately this only adds to the long list of features I have stopped using in the Jetpack plugin. It all started out great. But over time the Jetpack service has morphed into something that no longer adds any value to managing my website.

Update. As it turns out, this website field for the comments was being generated by the Jetpack plugin. Sorry for any confusion.

Thanks Danny @dvankooten for the very rapid and thorough solution. I saw your update posted this morning and I appreciate the clear instructions on how to correct the database records due to the glitch in the previous update.

Sorry to hear about your experience @macitpros

And nearly three weeks after posting my original question no one from support or sales has bothered to respond. I would say that puts the “final nail in the coffin” for this theme. Bummer. I’ve been using it since 2014. Time to move on.