--- type: "Index" title: "Pre-rendering guides - choose by symptom, bottleneck, and operating stage" description: "Operational pre-rendering guides for crawl-budget loss, stale snapshots, large-site routing, render-cost modeling, hydration failures, and other production SEO bottlenecks." resource: "https://prerender.info/guides" tags: [guides, prerendering] timestamp: 2026-04-21T00:00:00Z --- # Pre-rendering guides - choose by symptom, bottleneck, and operating stage Use this hub when the architecture is already plausible and the real question is operational. The issue is usually one of five things: crawlers are wasting budget, snapshots are stale, render cost is climbing, parity is breaking between cached HTML and the live app, or the URL set has grown past the point where defaults still work. Start with [crawl budget fundamentals](/guides/crawl-budget.md) when you still need the baseline diagnosis. Move to [expand crawl budget](/guides/expand-crawl-budget.md) when the problem is confirmed and you need sequencing. Use [pre-render cache headers](/guides/prerender-cache-headers.md) when freshness and invalidation are the real bottlenecks. Use [large sites (100k+ pages)](/guides/large-sites-100k-pages.md) when scale itself is now the main constraint. The advanced guides are for narrower cases such as hydration drift, paywalled content, shadow DOM, or headless-browser ownership. If you are still deciding what kind of site pattern you have, step back to [use cases](/use-cases/index.md). If you are already choosing tooling, move forward to [compare](/compare/index.md). ## Operational pre-rendering guide An operational pre-rendering guide explains how to diagnose and fix one production bottleneck in the rendering layer: crawl waste, stale snapshots, weak recrawl, scaling cost, or parity failures. The point is not generic SEO theory. It is a repeatable workflow with measurement and decision boundaries. ## Topics - [Crawl budget fundamentals](/guides/crawl-budget.md) — Start here if the diagnosis itself is still fuzzy. Best for teams that know indexing is weaker than it should be but have not isolated whether crawl waste is the real cause. - [Expand your crawl budget](/guides/expand-crawl-budget.md) — Use this when crawl-budget waste is already established and you need the next sequence of changes: canonical compression, sitemap structure, and template prioritization. - [Fix the 80% crawl-budget loss](/guides/crawl-budget-80-percent.md) — Best when pages exist but indexing still stalls. This guide is built around the classic render-queue and wasted-fetch pattern on JavaScript-heavy sites. - [Large sites (100k+ URLs)](/guides/large-sites-100k-pages.md) — The right path when the site has already crossed into six-figure URL territory and selective rendering, shard logic, and economics matter more than defaults. - [Pre-render cache headers](/guides/prerender-cache-headers.md) — Choose this when freshness, TTL design, purge triggers, and stale-snapshot risk are the operational bottlenecks rather than raw crawl discovery. - [Crawl frequency signals](/guides/crawl-frequency-signals.md) — Useful when crawlers are not coming back quickly enough after updates and the team needs a clearer model for recrawl cues and false positives. - [JavaScript rendering cost](/guides/javascript-rendering-cost.md) — Use this when the main question is economic: what rendering actually costs at 10k, 100k, and 1M URLs, and where build-vs-buy math changes. - [Advanced: paywalled content](/guides/advanced/prerender-paywalled-content.md) — Read this only when the crawler-visible surface sits behind subscription boundaries and parity or anti-cloaking risk needs careful control. - [Advanced: hydration failures](/guides/advanced/hydration-failures-seo.md) — The right guide when the pre-rendered snapshot and hydrated app disagree, especially after deploys, experiments, or partial component failures. - [Advanced: headless browser overhead](/guides/advanced/headless-browser-overhead.md) — Choose this when the problem is operational ownership itself: CPU, RAM, queue pressure, crash handling, and the threshold where buying beats building. - [Advanced: shadow DOM and SEO](/guides/advanced/shadow-dom-seo.md) — Useful for web-component heavy teams that need to know what crawlers can actually see and what pre-rendering can or cannot rescue. ## FAQ ### Where should we start if we are not sure what the bottleneck is? Usually with [crawl budget fundamentals](/guides/crawl-budget.md). It gives the cleanest baseline model for diagnosis. If the site is obviously stale rather than undiscovered, start with [pre-render cache headers](/guides/prerender-cache-headers.md) instead. ### How do we choose between a guide and a use-case page? Choose a guide when the problem is cross-vertical: crawl waste, stale cache, weak recrawl, render cost, or parity drift. Choose a [use-case page](/use-cases/index.md) when the problem is strongly tied to one inventory or URL pattern such as job expiry, route/date fanout, or seller-generated facet sprawl. ### When do the advanced guides matter? Only when the core operating model is already clear and the site is hitting a narrower edge case. Most teams should solve crawl budget, freshness, scaling, and cost before spending time on shadow DOM or paywalled-content edge cases. ### What usually changes first after implementing the right guide? Usually crawl behavior and crawler-facing HTML quality change first: faster recrawl, cleaner canonical sets, lower stale-snapshot rates, or better first HTML completeness. Ranking and traffic improvements usually follow after those technical signals stabilize. ### When should we leave this hub and move to compare pages? Move to [compare](/compare/index.md) once the operational problem is clear and the team is deciding which vendor or build path can handle it. The guides tell you what has to be fixed. The compare pages tell you who is better equipped to do it. ## Related - [Use cases - diagnose by vertical failure pattern](/use-cases/index.md) — Go here when the operational problem is tightly coupled to a specific industry or inventory model. - [Compare - choose tooling after the ops model is clear](/compare/index.md) — Use the comparison hub once you know which constraints the vendor has to handle. - [Technology - how the rendering layer works](/technology/index.md) — Read this if terms like crawler routing, snapshot cache, and invalidation still need a clearer mental model. ## Source Generated from prerender.info editorial content (single source of truth). The canonical, always-current version is the `resource` URL above. Claims reflect prerender.info / ostr.io editorial guidance and are not confirmed from third-party public documentation unless explicitly linked. ## In this section - [Crawl budget fundamentals for JavaScript sites](/guides/crawl-budget.md) - [Expand your crawl budget — 7 levers that actually work](/guides/expand-crawl-budget.md) - [The 80% crawl-budget loss on JavaScript sites — and how to fix it](/guides/crawl-budget-80-percent.md) - [Pre-rendering at scale — large sites with 100k+ pages](/guides/large-sites-100k-pages.md) - [Pre-render cache headers - Cache-Control, Vary, invalidation](/guides/prerender-cache-headers.md) - [Crawl frequency signals - what makes crawlers come back](/guides/crawl-frequency-signals.md) - [JavaScript rendering cost - headless browsers at 10k, 100k and 1M URLs](/guides/javascript-rendering-cost.md) - [Pre-rendering paywalled content — Flexible Sampling without cloaking](/guides/advanced/prerender-paywalled-content.md) - [Hydration failures and SEO — detect and fix snapshot drift](/guides/advanced/hydration-failures-seo.md) - [Headless browser overhead — CPU, RAM, and operational cost at scale](/guides/advanced/headless-browser-overhead.md) - [Shadow DOM and SEO — web components and what crawlers see](/guides/advanced/shadow-dom-seo.md)