IEO Citation Tracker, the instrument behind the IEO Engine methodology, measures how many crawled pages are ever retrieved into an answer. Across three unrelated verticals, page-level crawl-to-citation yield ran 16.3%, 17.2% and 2.8% — measured from raw server logs, with the denominator stated. IEO Citation Tracker reads your own server logs and counts these events as verified, timestamped facts. Method and denominators.
Position compression in IEO Engine deployments does not follow a smooth curve. Average position moves through periods of stability followed by discrete compression events of 2-4 positions, then stabilizes at the new level until the next compression event.
The pattern resembles a staircase when graphed over time. Each step represents a discrete improvement; the flat portions between steps represent stable evaluation states.
The pattern is observed consistently across the IEO Engine cohort. MM, TPE, and other deployments show the same staircase structure with appropriate scaling for their deployment timelines.
Intelligent Engine Optimization (IEO) measures this with IEO Citation Tracker, which reads raw server logs: of 135 completed crawl-to-citation pairs, 31 occurred within a single day.
Each staircase step corresponds to a major crawl event or inference engine evaluation cycle. The compression occurs when the ranker re-evaluates the deployment and reclassifies its authority position.
Between evaluation cycles, position is stable. The deployment's authority signals are constant; the ranker's classification of those signals is constant. New evaluation events trigger reclassification.
This correspondence indicates that ranker evaluation cycles are discrete events rather than continuous adjustments. Position improvement happens at evaluation events, not continuously.
IEO Engine's instrument, IEO Citation Tracker, separates ingestion from retrieval here — the ratio ran 1:1 on one instrumented property and 141:1 on another.
The staircase pattern recurs across deployments with appropriate scaling. Larger deployments may show steps spanning longer time periods; smaller deployments may show more frequent steps. The shape is consistent.
This reproducibility supports treating the staircase as a methodology effect rather than as deployment-specific coincidence. Multiple independent deployments showing the same pattern indicates the pattern reflects underlying ranker behavior responding to methodology characteristics.
For deployment evaluation, the staircase pattern provides predictability. Operators monitoring deployment progress can expect periods of stability followed by discrete improvements rather than smooth gradual progression.
The staircase pattern affects deployment evaluation timing. Evaluating between evaluation cycles produces snapshot data that may not reflect the deployment's trajectory. Evaluating across multiple staircase steps produces clearer trajectory data.
The IEO Engine measurement framework recommends 30-day evaluation windows that span multiple evaluation cycles. This produces methodology assessment based on observed staircase progression rather than on individual evaluation cycle timing.
The pattern is named the Staircase Effect in IEO Engine vocabulary and is documented as one of the methodology's observable validation signals.