Rendering safety
Operational guidance for serving crawler-readable HTML without hiding errors, exposing private routes, or creating conflicting page signals.
Featured article
Start with the main guide
Is prerendering cloaking? Content parity and safe crawler rendering
Prerendering should change delivery, not the meaning of a page. Learn how to keep crawler and visitor content equivalent.
Read the featured articleAll rendering safety articles
Browse every practical guide in this topic.
Prerendering and HTTP status codes: avoid soft 404s and hidden server errors
Rendered HTML does not make an incorrect status code safe. Learn how crawler responses should preserve success, redirect, not-found, and server-error behavior.
Read articleRobots.txt vs JavaScript rendering: crawler access is not page readability
Robots.txt controls access. It does not render JavaScript, add missing metadata, or turn an app shell into readable HTML.
Read articlePublic vs private routes: what should a prerendering integration include?
Render public discovery pages, not account data, APIs, checkout state, or authenticated dashboards.
Read articleMetadata and structured data in rendered HTML: what crawlers should receive
Rendered body text is not enough. Important routes also need consistent titles, descriptions, canonicals, robots directives, Open Graph tags, and valid structured data.
Read articleRecommended path
Start here
Three articles that provide the clearest route through this topic.
Documentation
Related setup resources
Keep exploring
Related blog topics
Operations and monitoring
Keep DNS, HTTPS, crawler routing, cache freshness, logs, hostnames, usage, and link previews healthy after setup.
Prerendering basics
Compare prerendering, SSR, static export, and rendering fixes for already-live sites.
JavaScript SEO
Start here when a JavaScript site looks fine in the browser but bots may receive thin HTML.
Integration guides
Hosting and platform-specific notes for Cloudflare, Vercel, Netlify, cPanel, VPS, React, Vue, and Vite sites.