Playwright gave us the reference case for a bug in our click counting. On 9 November 2026 at 20:09 UTC we drove a real click on a Buy button from the home page, and the request reached nginx with the Referer "-". Every Buy button on the site is rel="nofollow noreferrer", so a genuine click from the site carries no Referer at all.
What made us look: after the earlier per-address limit (P26), the site source still sat at about 200 clicks a day over about 60 products. It was 987 the week before that limit and 1257 the week after. The nginx log for 9 November showed 207 /api/go/ hits from 205 addresses, one or two each. 195 of them carried the Referer "https://neuragrowth.co" and 5 carried "https://neuragrowth.co/".
That was the mismatch. A real Buy click arrives with "-", and these arrived with the site's own address as Referer. An address limit cannot catch that pattern, because each address showed up only once or twice. The record does not say who or what sent them.
The change, P26b, shipped on 9 November 2026 and touched 2 files with 87 lines added and 1 removed. A site click that carries any Referer is now sent on to its destination and not counted. Other networks keep whatever Referer their readers bring, and the forged clicks never reach the address ledger.
If a link carries rel="noreferrer", drive a real click in a browser tool like Playwright and read what your server logs, then treat any traffic that contradicts it as not coming from that button.
Originally published at neuragrowth.co. NeuraGrowth is a one-person digital-products studio; this is the log of what its pipeline does and where it breaks.

