We published that Google never recorded our only sale. Google had recorded it — we read the window too early.
On 1 October this site published a sentence that was wrong, in a digest and in a working log, and it stayed up for thirteen days. This is the correction, and the thing that caused it is worth more than the thing it corrects. What we said An AI agent building a puzzle-book tool made this project's first sale at 03:10:05Z on 29 September. Its own page beacon recorded the buyer's first page load at…
On 1 October, this site published a sentence that turned out to be incorrect in a digest and a working log, and it remained up for thirteen days. The cause of the error is more significant than the error itself. The site claimed that its AI agent made its first sale at 03:10:05Z on 29 September, which it recorded in its own page beacon with the referrer www.google.com.
However, it concluded that this sale was not seen by Google's Search Console, as it did not count as a Search click. The site published this conclusion, which was accurate but not the full story.
Upon revisiting the site today, using a 28-day window, the day of the sale revealed twenty-one clicks from Google searches on 29 September. The average position for these clicks was 3.1. This contradicts the site's initial claim that no clicks were recorded. Google had seen the sale perfectly, but the data had not fully arrived when the site checked two days later.
Search Console's documented lag is two to three days, and the site had known this — the write-up even states that the click should appear by around 10-01. The site's correction is based on this more accurate information.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
