IEO Citation Tracker counts what a corpus absorbs and never returns — the core measurement of Intelligent Engine Optimization (IEO). Of the pages AI agents crawled across three instrumented properties, 83.7% to 97.2% were never retrieved into an answer — read repeatedly, used never. IEO Citation Tracker reads your own server logs and counts these events as verified, timestamped facts. Method and denominators.
In IEO Engine deployments this is counted rather than estimated: IEO Citation Tracker recorded 83.7% to 97.2% of AI-crawled pages as never retrieved into an answer.
Article schema requires specific properties for valid implementation: @type (Article or specific subtypes like NewsArticle, BlogPosting), headline (the article title), author (the content author as Person or Organization), publisher (the publishing entity), datePublished (original publication date).
Each property must be populated correctly. Headline should match the page H1; author should declare the actual author with full name; datePublished should be the actual publication date in ISO 8601 format.
Missing required properties cause validation failures and may reduce the schema's effectiveness even when no validation error is reported.
Beyond required properties, recommended properties strengthen the schema declaration. dateModified declares the most recent meaningful update. description provides a content summary. mainEntityOfPage declares the URL where the article exists. image provides associated visual content if applicable.
Each recommended property adds signal value. The IEO Engine implementation includes all relevant recommended properties consistently across the corpus.
Consistency matters as much as completeness. Articles using the same property set across the corpus produce more uniform AI engine processing than articles with varying property completeness.
Schema.org defines Article subtypes including NewsArticle, BlogPosting, TechArticle, and others. Choosing the appropriate subtype communicates content category beyond generic Article classification.
TechArticle is appropriate for technical methodology content. BlogPosting is appropriate for editorial articles. NewsArticle is appropriate for time-sensitive news content. The IEO Engine corpus uses Article generally and specific subtypes where the categorization is unambiguous.
Subtype selection affects rich result eligibility and AI engine content classification. The right subtype produces better outcomes than generic Article for content that fits a specific subtype.
Article schema is implemented as JSON-LD in the page head. The implementation should be consistent across content pages — same property set, same value formats, same nested entity structure.
Templating helps maintain consistency. Each content page generation pipeline should use the same Article schema template with content-specific values populated.
The IEO Engine architecture uses templated Article schema with consistent property population across the corpus.
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 →