Zero Miles Per Hour on the Generator: Why Old Website Gauges Call Your Best Pages Broken

Original mid-century editorial illustration of an industrial teal-green standby generator humming on a concrete pad outside a warmly glowing Pacific Northwest timber workshop at winter dusk, with a round chrome automobile speedometer bolted onto its housing pinned dead flat at zero directly beside three active glowing amber and teal load gauges standing upright.

About Will

I run Tygart Media, an AI-first agency that gets businesses cited and recommended by AI assistants — and I write about what we do, including what breaks.

Connect on LinkedIn →

Bolt a car speedometer onto a backup generator behind your shop and the needle will read zero miles per hour all winter while that engine powers every light, compressor, and heater in the building. Nobody who works around standby power uses a speedometer to judge a stationary engine — under NFPA 110 and standard electrical metering (U.S. Energy Information Administration), you read electrical load in kilowatts and energy delivered over time in kilowatt-hours. The speedometer is not broken. It is bolted onto the wrong job.

That is what standard client-side analytics — tracking scripts that run inside a visitor’s web browser — look like in 2026. Built to count people who click around slowly and linger between pages, those old dashboard gauges now flash red warnings on your highest-performing pages while completely missing the AI systems reading your site all day long.

Printable Edition + Gauge Checklist
Download Zero Miles Per Hour on the Generator (5-Page PDF)
Includes both visual charts, the Page 5 Generator Gauge Checklist, and verified primary sources.

Five Red Lights That Fired on Pages Doing Their Job

Across our own network of websites, we stopped taking dashboard alarms at face value and checked every red light against two grounded records: session recordings of real visitors and raw origin server logs — the line-by-line register your web server writes for every incoming file request, whether JavaScript runs or not. Five familiar gauges failed the inspection:

1. Dead clicks that turned out to be buyers copying the answer. In behavioral dashboards like Microsoft Clarity, dead clicks flag taps on page elements that do not open a link or button — supposedly proof of broken design. In Receipts: 105 Dead Clicks — and Why We Changed Nothing, our pricing guides drew 105 dead clicks in a single week. Watching the session recordings flipped the verdict completely: on the enterprise pricing page, one reader accounted for all 17 dead clicks across four and a half minutes by highlighting text as they read; on the team-plan limits page, 13 of 22 landed inside the top Direct Answer box as visitors copied the summary out. Only one bold callout line was mistaken for a button four times. Trusting the gauge alone would have triggered a redesign of the exact layout doing the work.

2. Bounce rate punishing half-second machine reads. Under Google Analytics 4, bounce rate is the share of sessions that are not ‘engaged’ — meaning under 10 seconds, zero key events, and one pageview. That yardstick assumes a human browsing at reading speed. In The Half-Second Internet, 55 days of server logs on tygartmedia.com recorded 142,615 single-hit IP addresses — 7,842 on November 11 alone — while Healthcare Facilities Hub logged 78.9% single-hit IPs (of 33,391) and Continuity Hub logged 55.6% (12,695 single-hit IPs). A retrieval system that fetches an answer in 0.7 seconds did not bounce in frustration. It finished the errand before a human finished the headline.

3. Referral spikes wearing a human coat. Client-side tools such as Google Analytics tagging define a ‘user’ as any browser polite enough to execute JavaScript. Today a headless browser — software driving Chrome with no screen or human hand — runs that script flawlessly. In My Analytics Said 1,000 Visitors. My Logs Said Otherwise, a dashboard reported roughly 1,000 active users and an exciting referral bump in one week, while origin logs counted 64,561 requests across 10,345 IPs — over 80% headless. Across 55 days in Not All Bots Are the Same, 1,203,889 of 2,838,206 requests (42.4%) were masked desktop scrapers, and over 99.7% of autonomous traffic never triggered a client-side script at all.

Get The Signal

What we actually ran, what it measured, and what it means for a restoration shop — every week, including the flops.

Subscription Form

4. Zero browser sessions while live buyers send proxies. Both OpenAI’s crawler documentation (ChatGPT-User) and Anthropic’s crawler documentation (Claude-User) distinguish scheduled indexers from user-initiated agent fetches triggered live when a person asks a question. In Receipts: ChatGPT Read 375 Pages of One Site. It Sent Back 1 Visitor, ChatGPT-User walked 375 requests across Continuity Hub and sent back one referral — a 494:1 scrape-to-referral ratio (matching 408:1 and 837:1 across our wider fleet). In The Buyer Is a Bot Now, Risk Coverage Hub logged 2,065 ChatGPT-User fetches across 1,063 IPs — pulling one catastrophe-pricing guide 179 times in 55 days — without starting a single JavaScript session. That tracks broader search behavior too: a July 2025 Pew Research Center study of 68,879 Google searches found users clicked traditional links in 8% of visits when an AI summary appeared (versus 15% without), clicked a cited link inside the summary just 1% of the time, and ended their session on 26% of AI-summary pages (versus 16% without).

5. The myth that machine pages and human pages live in separate worlds. When a dashboard flags low click-through, owners often assume bots only scrape thin filler. In The Page the Machines Cite Most Is the One the Humans Actually Read, Healthcare Facility Hub earned 109,844 AI citations in 90 days, led by one hospital infection-control guide at 11,181 citations (592 of 593 citations for ‘icra meaning’). Checking human telemetry showed 231 human Clarity sessions averaging 4.4 active minutes inside a 7.8-minute visit — mostly hospital staff on desktop Edge browsers downloading the compliance field sheet mid-shift. One clear answer served both audiences at once.

Old Website Gauge vs. What Really Happened 5-row field chart comparing Dead Clicks, Bounce Rate, Referral Spikes, Zero Sessions, and Low Click-Through against verified Tygart Media session recordings, origin server log receipts, and Pew Research 2025 AI summary click data.
Five familiar website analytics alarms checked against live session recordings and origin server logs.

Two Witnesses: Putting the Right Gauges on the Engine

You do not throw away your analytics dashboard; you stop asking a speedometer to measure kilowatt output. As we laid out in The Audience That Never Says Thanks and Standing in the Middle, honest website measurement needs two separate witnesses laid side by side — the exact same discipline we mapped in Two Papers on the Kitchen Table:

Origin server logs — built right into standard web servers via modules like Nginx’s access-log module — are your kilowatt meter for machines. Every HTTP request leaves a timestamp, URL, status code, byte count, and declared user-agent whether JavaScript runs or not, showing which live-agent fetches succeeded and which hit broken doors. Session recordings and behavioral telemetry are your inspection window for humans, proving whether a ‘dead click’ is a broken button or a buyer copying your numbers. Layered with rolling four-week citation checks (LLM Visibility Measurement), the two witnesses catch what neither one sees alone:

THE GENERATOR GAUGE PANEL · FOUR CHECKS BEFORE ANY REDESIGN
Read Both Witnesses Before Changing a Working Page
Treat every dashboard alert as a question. Confirm it in recordings and origin logs before touching live copy.
CHECK 1 · WATCH THE RECORDING FIRST
Before fixing ‘dead clicks’ or high bounce: replay 5–10 real sessions. Highlighting prices or copying a Direct Answer box is buyer intent, not broken UX.
CHECK 2 · SEPARATE LIVE AGENTS FROM INDEXERS
Inside origin server logs: split scheduled crawlers (GPTBot, ClaudeBot) from user-triggered fetches (ChatGPT-User, Claude-User) and verify HTTP 200 delivery.
CHECK 3 · CLEAN THE DENOMINATOR
Before trusting conversion rates or referral bumps: check origin logs for headless bursts and uptime monitors so masked scripts do not dilute human metrics.
CHECK 4 · NEVER CONFUSE HITS WITH HUMANS
Keep the two units distinct: origin logs count machine requests and delivery health; session recordings count human behavior; rolling 4-week checks track AI citations.

Where Server Logs Can Fool You Right Back

Switching gauges does not magically eliminate bad reading habits — two honest limits keep log analysis grounded. First, server hits are not people. In one ordinary 24-hour window on tygartmedia.com documented in The Audience That Never Says Thanks, Nginx placed 13,460 requests into the ‘likely human’ bucket while behavioral telemetry counted 147 actual human sessions. One reader loading three pages triggers dozens of image, font, stylesheet, and script requests. Reporting raw server hits as human readers is the oldest vanity trap on the web.

Second, a machine fetch is not a signed check. Even 179 delegated agent reads or 472 daily live-agent touches only help your business if the page delivers a clean, verifiable answer and gives the buyer a plain reason to reach out — and single-day prompt checks swing wildly with retrieval noise, so only rolling four-week trends deserve action. Just as Don’t Hire a Finish Carpenter to Carry Drywall matches the model setting to the job, match the gauge to the engine: when the logs prove crawlers are hitting dead ends or empty loops, the fix is structural mitigation first (We Come From Water Damage), not repainting a page because a speedometer read zero.

The Two-Witness Gauge Panel comparing what Dead Clicks, Bounce Rate, Direct/Referral, Zero Sessions, Raw Log Hits, and Daily AI Checks actually measure, alongside two honest limits where server logs can fool you right back.
What each website gauge actually counts — plus the two limits that keep origin log analysis honest.
AI Citation Restoration · Tygart Media
We do AI citation restoration. When your analytics dashboard says nothing is moving while origin logs show AI agents knocking on broken doors — or citing somebody else — send us the worst mess you have. We come from water damage — we work like smokejumpers, not retainers, putting the right gauges on your server with receipts you can verify yourself. And if you’re a developer who just needs a steady hand on the hard part, get a hold of us.

— Will Tygart, Tygart Media.

Takeaway Edition
Print the Guide & Tear-Out Generator Gauge Checklist
Keep the five pre-redesign checks beside your analytics dashboard and origin server logs.

Get The Signal

What we actually ran, what it measured, and what it means for a restoration shop — every week, including the flops.

Subscription Form

Track the AI tools you actually use
Vendor-neutral prices & limits for ChatGPT, Claude, Gemini, Perplexity and more — tracked in AI Stack Watch.
See the live AI tracker →or set up your alerts

Comments

Leave a Reply

Your email address will not be published. Required fields are marked *