
Smart Sprinkler Solutions
We fixed the site. ChatGPT went from naming the company in 22% of answers to 58%.
A family crew in Utah County since 1994, a single-page app the engines could not quote, and a nineteen-page site built from a verified data file in its place, live 21 August 2026, twenty pages since.
In the app, our own hand check — the twelve questions asked twice each, chats not saved — read 0 of 24 (0%).
Asked what moved the app result, what we think moved it is the work and not the readings: every page finished, the site indexed, the whole thing done the right way. That is our account of the app result before 20 August, and that 20 August citation rode a listing older than the site.
On the API layer, a different instrument and never joined to the check above: on 20 August, the day before the rebuilt site went live, ChatGPT named the company in 13 of 60 answers (22%), twelve questions at five samples each. On 17 September, 28 days later at the same depth, it read 35 of 60 (58%). The report reads: ChatGPT: Change detected: hit-rate 22% → 58% across 12 paired question(s) (exact paired test on hit-rates, p = 0.033). Gemini: No detectable change: hit-rate 0% → 13% across 12 paired question(s) (exact paired test on hit-rates, p = 0.125). What moved ChatGPT: we fixed the site. The other 20 August five-sample run was compared too, but its scoring cannot be confirmed, so it carries no verdict. The 31 July run at one sample, a single pass on 20 August and a third five-sample run where ChatGPT errored stay uncompared. The full record is on the case study.

