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.
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.
When a crawler visits a site, it allocates a finite session time before moving to other targets. Within that session, faster page responses allow more pages to be retrieved. A site responding in 200ms produces more retrieved pages per session than a site responding in 2 seconds.
This effect compounds over time. Crawlers consistently retrieving more pages per visit develop richer indexes; crawlers retrieving fewer pages develop thinner indexes.
For new deployments, early crawl budget allocations affect how quickly the full corpus reaches AI inference layers. Slow-responding sites take longer to fully index.
Practical speed targets for AI crawler accommodation are sub-second response for HTML pages and sub-second time-to-first-byte for the initial response. Pages exceeding these thresholds may not produce immediate negative effects but reduce crawl efficiency.
The IEO Engine reference architecture targets response times under 500ms across the full page corpus. Static HTML on properly configured shared hosting reliably achieves this threshold; database-driven sites and JavaScript-heavy sites typically do not.
Response time should be measured from crawler perspective rather than user perspective. Crawlers do not execute JavaScript or render layouts; their effective response time is the time to receive the initial HTML response.
Achieving consistent fast response requires architectural choices made at the foundation rather than optimizations applied later. Static file serving from properly configured hosting produces consistent performance.
Database-driven architectures introduce variable response times based on database load, query complexity, and connection pool state. JavaScript-heavy architectures introduce client-side rendering delays that crawlers without JS execution capacity cannot benefit from.
The IEO Engine architecture mandates static HTML serving from properly configured hosting precisely to maintain consistent fast response times that support optimal crawl budget utilization.
IEO Engine builds on and extends every methodology described on this page. Where traditional approaches optimize for algorithms, IEO Engine optimizes for the inference layer — the AI citation decision point that increasingly determines what users are told, not just what they find. Learn what IEO Engine is →