# Client-rendered content

Canonical HTML: /atlas/client-rendering
Atlas version: atlas-2026-07-28-v1
Category: Rendering and client execution

## Definition

Client rendering creates important content or navigation only after JavaScript runs.

## How it works

A rendering crawler must allocate a browser, execute scripts, wait for useful completion, and inspect the DOM. This costs more and is often scheduled after the initial HTML fetch.

## How to validate it

Compare links and visible facts in the raw HTML with a deterministic rendered snapshot, including the time at which late content appears.

## Common failure

Assuming every crawler renders can make central pages invisible to fast HTML-only fetchers and delay discovery even for capable engines.

## Related topics

- [Server-rendered content](/atlas/server-rendering)
- [Hydration](/atlas/hydration)