Prerender

A single-page app renders to an empty shell until its JavaScript runs, which is nothing for a crawler or a link unfurler to read. For routes opted into prerendering, the platform serves a cached headless snapshot to bots while real visitors still get the live app. This surface inspects and manages those snapshots. pages lists what is stored for the live release, each with its path, render time, and byte size, and view returns the stored HTML for one path as JSON rather than rendering it, so nothing in the snapshot executes.

invalidate purges snapshots, by path or all at once, so the next crawler visit re-renders from live data; a deploy already does this automatically, so invalidate is for content that changes between deploys. get fetches a path the way a crawler does, with a bot user agent, to confirm the end-to-end serve path: a warm path returns the snapshot, a cold one returns the live app and triggers a render.