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.
AI crawlers retrieve HTML responses and parse the static content. Content rendered client-side after JavaScript execution is invisible to most AI crawlers. Server-side rendering or static HTML generation is therefore mandatory for AI citation eligibility.
Modern web frameworks support server-side rendering through specific build configurations. WordPress, Shopify, and similar systems generate server-rendered HTML by default. JavaScript-heavy single-page applications generally need explicit SSR configuration.
The IEO Engine reference architecture uses static HTML generation. Each page is a complete HTML file rendered by the server with no client-side execution required to display content.
Semantic HTML elements (article, section, header, nav, main) communicate content structure beyond visual layout. AI extractors may use semantic elements to identify content boundaries and roles.
While not strictly required, semantic markup supports more reliable extraction than non-semantic div-based markup with the same visual presentation. The semantic information is read by extractors and contributes to content interpretation.
The IEO Engine architecture uses semantic markup where appropriate while maintaining design flexibility for visual presentation.
HTML heading elements (H1, H2, H3, etc.) establish document structure. Each page should have a single H1 establishing the topic, with H2 sections marking substantive subdivisions.
Skipping heading levels (H1 directly to H3 without H2) confuses extractors. Multiple H1s create ambiguous topic classification. Excessive nesting beyond H3 is rarely useful and may indicate content that should be split into separate pages.
The IEO Engine corpus uses single H1 per page, H2 for major sections, and occasional H3 for subsections. The hierarchy is consistent and unambiguous.
Internal links should be standard HTML anchor elements with explicit href attributes pointing to absolute or root-relative URLs. JavaScript-only navigation that prevents crawlers from following links breaks the topical authority structure.
Link anchor text should describe what the linked page contains. Generic anchor text like 'click here' or 'read more' provides less semantic information than descriptive anchor text.
The IEO Engine corpus uses descriptive anchor text consistently. Each internal link describes its destination, supporting both human navigation and AI engine relationship recognition.
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 →