Audit JavaScript Websites with Rendered Crawling
Compare source HTML with LLMIC's rendered capture to find content, links and metadata that depend on JavaScript.
A browser can display content that is absent from the first HTML response. Comparing both layers shows what changed and what evidence is incomplete.
Build availability: This guide describes the September 2026 development workflow. Some controls may not yet be included in the public installer. Check the release notes and your app version before following the steps.
Evidence flow
- Capture source HTMLRecord the server response before scripts run.
- Render the pageUse the supported rendered-crawl setting.
- Compare layersInspect content, links, headings and metadata.
- Review failuresKeep timeouts and incomplete rendering visible.
This visual explains the review sequence. It is not a performance forecast or a set of measured customer results.
Start with a clear question
Open the relevant LLMIC dashboard only after loading the crawl, property or saved observation needed for this review. For JavaScript SEO, record the website, date, filters and document layer before interpreting a result. This keeps the work reproducible when another team member reviews it later.
Read the evidence before the recommendation
Open the affected page or row and inspect the retained evidence. Counts help you find patterns, but the page-level source explains what was actually measured. When coverage is partial, a response failed, or a legacy crawl omitted the required field, keep that state visible. Do not turn unavailable evidence into a failed check.
Choose the smallest useful action
Write an instruction that names the exact URL, observed condition and intended result. Preserve intentional behavior and review shared patterns before applying a site-wide change. If a suggestion creates new wording, markup or redirects, a person should approve the facts and destination before publication.
Understand the limits
Rendered crawling costs more time and memory than HTML-only crawling. Use it where JavaScript changes important evidence, and keep source and rendered findings labelled throughout comparisons and exports.
Quick reference
| Evidence or state | How to use it |
|---|---|
| Source only | Confirm whether the rendered capture failed or content disappeared. |
| Rendered only | Decide whether critical information should be server delivered. |
| Both layers | Compare meaning and destination, not just counts. |
| Not measured | Do not infer absence from legacy or failed captures. |
Check the result
After the reviewed change is deployed, collect fresh evidence with a compatible configuration. A task marked complete records workflow progress; it does not prove the live page changed. Save the verification time and result, then use Verify SEO Fixes for supported checks or run a complete follow-up audit.
Continue your workflow
Return to the documentation home, learn how to interpret audit results, or organize reviewed work in the Action Queue and Fix Generator. Remove private information before sharing exports, and contact LLMIC support with a sanitized example when a result cannot be explained.
Frequently asked questions
Compare source HTML with LLMIC's rendered capture to find content, links and metadata that depend on JavaScript.
Load a completed crawl that includes the pages you need to inspect. Confirm the crawl scope, capture time, rendering choice, and any filters before interpreting the result.
Review the affected URL, measured field, source or rendered evidence, and the rule that raised the item. Inspect nearby pages and templates because one shared component can create the same pattern across many URLs.
Create a task with the affected URL, observed evidence, intended outcome, smallest safe change, owner, and verification method. Keep the measured finding separate from the proposed fix.
Publish the approved change, run a fresh compatible crawl, and compare the new evidence with the saved result. A resolved local finding confirms the implementation changed; search performance requires separate observation over time.
The check cannot guarantee rankings, indexing, traffic, conversions, inclusion in an AI answer, or a future search-engine action. Interpret it with site context, search performance, and editorial judgment.
Save or export the evidence, assign the approved action, and use the related guides linked on the page for the next check. After implementation, repeat the same workflow against a fresh crawl so the result is comparable.