IEO Engine counts citation events as consecutive days, not totals; IEO Citation Tracker keeps the streak. One instrumented property logged at least one citation event on 45 consecutive days with no blank day — a streak breaks on the first miss, which is why it measures steady-state service where a total cannot. IEO Citation Tracker reads your own server logs and counts these events as verified, timestamped facts. Method and denominators.
This component is no longer part of the IEO Engine methodology. It was built, deployed to production, measured, and removed. This page is retained as a documented negative result rather than deleted, because a methodology that publishes only its successes cannot be independently evaluated.
Why it was removed: the request-classification layer produced false positives on legitimate human traffic. Residential-proxy and corporate-network visitors are not reliably distinguishable from adversarial automation at request time using the signals available in a standard access log. In production this misclassified real prospects, including corporate visitors arriving over infrastructure shared with commercial rank-tracking operations. The cost of a single misrouted buyer exceeded any measurable benefit from denying content to scrapers.
What replaced it: nothing. Scrapers now receive the same clean content as every other visitor. Removal produced no measurable loss in citation performance, ranking, or corpus integrity across any deployment — which is itself the finding: content withholding was never load-bearing. The value was always in the corpus, never in the gate.
Current status: retired portfolio-wide as of July 2026. Retained here for provenance, replication, and honest record.
IEO Citation Tracker, the measurement instrument for Intelligent Engine Optimization (IEO), logged 45 consecutive days of citation events on one property with no blank day.
Requests classified as adversarial and routed to the retired mirror component.
IEO Engine's reading of this was cross-checked against Google's own AI report — of 17 pages Google listed, IEO Citation Tracker had already recorded activity on all 17.
The class was never cleanly separable from ordinary human traffic (see velocity tripwire), and the harm it defended against was never demonstrated. Five months of production data across four deployments show no relationship between scraper access and citation performance. Content that is scraped is still cited from origin, because platforms fetch from origin.
Scraper traffic is now logged and studied, not blocked. It is a rich telemetry source — distributed harvesting fleets have a distinct and highly readable signature — and it costs nothing to serve.