The goal is the same for all four fixes: get the populated DOM into the initial HTTP response. The right one depends on change frequency and how much of the codebase you can touch.
Your recommendation appears here.
Matching the fix to your constraints
There is no single right answer to a rendering problem, only four patterns with different cost curves: server-side rendering (SSR), incremental static regeneration (ISR), static generation (SSG) and edge prerendering. Four of them solve the problem; only SSR requires rewriting application logic. This advisor maps your change frequency, codebase freedom and page-set size to the cheapest pattern that works.
How to use it
- Set how often the content changes, from real-time per-user data to rarely.
- Say whether you can change the application code, and whether the framework is modern or legacy.
- Set the page-set size, a handful of key pages or a large catalogue.
- Read the recommended pattern and the reason, then confirm against the remediation matrix in the article.
When should I use SSR versus SSG?
Use SSR (or ISR) when the content changes in real time or daily, like pricing pulled from a billing API or a personalised feed. Use SSG when the content changes weekly or monthly, like docs, blogs and most marketing pages, because building the HTML once at deploy time is the cheapest readable option.
What is edge prerendering and when is it the answer?
Edge prerendering is a CDN worker that intercepts crawler requests, serves them a cached rendered snapshot, and passes humans through to the normal app. It is the retrofit for a legacy codebase you cannot or will not rewrite this quarter, because it changes nothing about your origin or build, only what bots receive.
Is serving bots a prerendered snapshot cloaking?
Only if the snapshot differs from what humans see. Serve bots the same content, rendered, and you are compliant; serve them different content and it is cloaking, a policy problem with search engines. Keep the snapshot TTL shorter than your pricing change cycle so a stale plan never gets served.
Does this tool send my inputs anywhere?
No. The recommendation is computed entirely in your browser from the three answers. Nothing is uploaded or stored.