SiteNexis is an AI Retrieval and Machine Trust Intelligence platform that models how AI systems — including ChatGPT, Gemini, Perplexity, and Claude — retrieve, interpret, trust, and recommend web content. It runs 16 intelligence agents across four layers and produces a 12-dimensional audit report with actionable recommendations.

How does SiteNexis improve AI visibility?

SiteNexis analyzes entity clarity, schema completeness, chunk extractability, semantic trust signals, and retrieval simulation across six stages. Each finding maps to a named issue with specific recommendations. Improvements to entity consistency, schema alignment, and content structure directly raise the probability of being retrieved and recommended by AI systems.

Which AI systems does SiteNexis analyze?

SiteNexis models retrieval behavior across Google AI Overviews, ChatGPT browsing and RAG modes, Perplexity, Gemini, Claude web search, voice assistants, and autonomous agents. Provider scoring weights are configurable and all scores are labeled as probabilistic estimates.

What is the Machine Trust Score?

The Machine Trust Score is a 0–100 composite that models AI system confidence in a website as a reliable source. It combines entity credibility consistency (30%), schema trust alignment (20%), external validation depth (25%), contradiction absence (15%), and trust degradation resistance (10%).

What is the Intelligence Report?

The Intelligence Report is a Grok-style editorial narrative generated for every audit. It synthesizes all twelve scores and the top issues into six named sections: a Signal Summary, SEO Posture, AI Visibility standing, Machine Trust analysis, Entity Health, and a Strategic Verdict with a composite X.X/10 score. Unlike dashboards that surface raw numbers, the Intelligence Report reads like a professional analyst's assessment — prose with precision.

What is the Decision Roadmap?

The Decision Roadmap is the output of the Decision Orchestrator — a v4 system that transforms a ranked issue list into an optimally sequenced action plan using Sequencing Value Score (SVS). It identifies the single best action to start with, groups subsequent actions into This Week, This Sprint, and Backlog bands, and calculates the projected score impact of completing each band. It also identifies parallel tracks for team-based execution.

SiteNexis has a free tier with 1 full AI visibility audit per month covering Layers 1–3. Layer 4 Machine Trust Intelligence — including Retrieval Simulation, Machine Trust Score, Temporal Authority, Recommendation Surface Mapping, and Synthetic Entity Detection — is available on Pro and Agency plans.

Back to Blog

DOM Forensics 6 min readJun 16, 2026

Part 8 of 10DOM Forensics series

Rendered vs Source HTML: Where AI Extraction Diverges

Source HTML and rendered HTML are two different documents. Understanding the difference between them reveals why content that exists "on the page" may be invisible to AI systems.

Source HTML is the HTML delivered by the server in the HTTP response. Rendered HTML is the DOM state after the browser has parsed the source HTML, executed all JavaScript, applied CSS, and completed all asynchronous data fetches. For modern web applications, these two documents can be dramatically different — and different AI crawlers read one or the other.

The Two Crawler Types

HTTP-based crawlers fetch the source HTML only. They receive the server response and parse it without JavaScript execution. Headless browser crawlers (like SiteNexis) launch a browser, navigate to the URL, and read the rendered DOM after JS execution. The content gap between these two methods depends entirely on how much of the page's content is JavaScript-rendered versus server-rendered.

What Exists Only in Rendered HTML

Content that typically exists only in rendered HTML (invisible to HTTP crawlers): product descriptions and pricing loaded from an API after page mount, review and rating content loaded asynchronously, personalized content (recommendations, recently viewed), tab content not in the active tab on initial load in CSR applications, infinite scroll content, and modal content loaded on user interaction.

What Exists Only in Source HTML

Content that sometimes exists only in source HTML (may disappear in rendered HTML): server-side rendered data that is overwritten by client-side hydration (hydration errors that clear SSR content), meta tags written by the server that client-side routing overwrites without proper SPA meta management, and structured data in script tags that dynamic rendering removes in certain configurations.

●The SiteNexis crawl captures rendered HTML. If you want to compare source vs rendered for a specific page: view-source: the URL (source HTML) and then use browser DevTools Elements panel (rendered HTML). Content that appears in DevTools but not in view-source is JavaScript-rendered. Content that appears in view-source but not in DevTools may have been overwritten during hydration.

DOM Forensics

JavaScript Rendering Blindness in AI Crawlers DOM Crawling Methodology: What SiteNexis Actually Reads Shadow DOM and AI Invisibility

DOM Forensics — Part 8 of 10

PreviousDOM Reading Order and AI Extraction Accuracy NextHeading Hierarchy and Semantic Chunk Boundaries

Tags: rendered HTML source HTML DOM forensics JavaScript Rendering

All articles Run free audit