Give crawlers the page your visitors see.

A finished page, ready before the request

A JavaScript app can look complete in a browser while its original HTML contains little more than an empty container. Crawlers and preview fetchers that do not execute the app can miss its text. RenderCache uses Chrome to capture public pages, stores the finished HTML, and serves that copy to matching crawler requests. People continue to receive the ordinary app.

The sitemap supplies the warm-up list. A saved page can be served without starting a browser. An expired copy stays available while a background refresh runs; a cold request falls through to the origin and queues work. It also records what kind of response was written, so an HTML snapshot, a 304, a redirect, and a private-request bypass remain distinguishable.

What changes after rendering?

This comparison uses a public example page captured with an earlier alpha release. The controls illustrate request behavior locally in your browser. No URL is fetched and no external crawler visits.

Open the full explanation or compare your own site in the self-hosted admin app.

Keep the app. Add the cache in front.

Run RenderCache as the reverse proxy, or route crawler traffic to it behind your existing edge. Configure the original app as its fixed origin and your public hostname as its site URL. Snapshots, quotas, and rotating delivery logs stay on your server. The engine is open source under Apache 2.0.

The current release, 0.2.0, runs on Linux, macOS and Windows. It is an early release for evaluation. Chrome remains a separate dependency for the standalone executable. Start with public, unauthenticated pages and check your readiness selector, snapshot coverage, and crawler responses before using it on a live site.