{
  "schemaVersion": "crawler-atlas-1",
  "atlasVersion": "atlas-2026-07-28-v1",
  "canonical": "/atlas/client-rendering",
  "title": "Client-rendered content",
  "category": {
    "slug": "rendering",
    "title": "Rendering and client execution"
  },
  "definition": "Client rendering creates important content or navigation only after JavaScript runs.",
  "mechanism": "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.",
  "validation": "Compare links and visible facts in the raw HTML with a deterministic rendered snapshot, including the time at which late content appears.",
  "commonFailure": "Assuming every crawler renders can make central pages invisible to fast HTML-only fetchers and delay discovery even for capable engines.",
  "related": [
    "/atlas/server-rendering",
    "/atlas/hydration"
  ],
  "modified": "2026-07-28"
}