Google’s own documentation says an AI Overview occupies a single position in Search results. On the query I’ve been tracking, the result Google reports as third sits roughly 1,640 pixels below the top of the page — about 1.7 screens. One position, one full screen of distance. That gap is where the measurement problem starts….
Quick Context: I have been measuring AI search visibility for a few months, first badly and then slightly less badly. The first version of this post was the bad version: it treated “AI visibility” as one number, borrowed a screenshot from a tool, and called the numbers traffic. This version separates four metrics that get…
Quick Context: I spent the last few months assuming my AI visibility problem was a content problem — that my pages were too thin, too new, or too boring to be quoted. Then I pulled eight days of raw server logs for this blog. GPTBot requested my site 14 times and got a rate-limit error…
Quick Context: This is the first part of a three-part tracking note, published on my personal blog, BenchJournal. When I started, I thought I already knew how to measure SEO: open Search Console, screenshot the graph, feel good about it. Then I ran three very different page types — an informational blog post, a product…
Quick Context: I run a small B2B PVC film export site, and last time I wrote about testing Surfer SEO on one of my product pages. This isn’t a strict experiment — just an early, honest look at how the same page performs across two very different search surfaces: traditional Google Search and Google’s newer…