A drop-in replacement for prerender.io. Renders your pages in headless Chromium,
waits for readiness, strips scripts, and caches the payload — served in milliseconds.
Free plan · no credit card · set up in about five minutes
By the numbers
12 mstypical cache hit
50+crawlers recognized
100kfree renders / month
~5 minto integrate
What do bots see on your site?
Google, ChatGPT, and Perplexity don't wait for your JavaScript. Paste any URL and compare what crawlers get today with the fully rendered version snapcache would serve them — free, no signup required. Test your URL free.
Know exactly which bots read your site
Search engines, social preview fetchers, SEO tools, and the new wave of AI crawlers — snapcache identifies each one, tracks hit rates and trends, and keeps a searchable request log. Per-bot render counts and week-over-week trends, with AI-crawler traffic broken out from classic search.
Every snapshot, scored and inspectable
Browse every cached page, open the exact HTML bots receive, and see a 0–100 SEO score per snapshot — missing titles, thin content, and broken metadata surface themselves. One-click recache when a page changes; filter to weak pages site-wide.
Prove the gap before you sign up
Paste any URL and get a side-by-side comparison: the bare HTML crawlers fetch today versus the fully rendered version snapcache would serve — each scored, with word counts, metadata, and shareable results. Run a free test.
And the rest of the toolbox
Millisecond cache hits
Cached snapshots are served immediately. Search bots never wait on Chrome.
Stale-while-revalidate
Expired entries serve stale content instantly while a background re-render freshens the cache.
Durable render queue
Recaches, sitemap warming, and live misses run through a persistent job queue with retries — a slow origin never loses a render.
Sitemap warming
Point snapcache at your sitemaps and it pre-renders your pages before the first crawler ever arrives.
API key auth
Issue per-tenant API keys. Each key is hashed and tracked — create, rotate, or revoke anytime.
Team access & alerts
Invite teammates to your console and get email alerts before you hit your monthly render quota.
Drop it in front of your site in minutes
Route bot user-agents to snapcache from nginx, a Cloudflare Worker, or Express middleware — copy-paste snippets live in the dashboard. Humans keep getting your normal app; crawlers get pre-rendered HTML. Full API docs built into the console, an instant recache API for on-demand updates, free vs billable usage tracked per billing period, and SSRF-safe rendering: private and internal addresses are always refused.
Is prerendering cloaking? Will Google penalize it?
No. Serving bots a pre-rendered copy of the same content your users see is the “dynamic rendering” pattern Google itself documented for JavaScript-heavy sites. The HTML snapcache serves is produced by loading your real page in a real browser — same content, same URLs, just rendered ahead of time. Cloaking means showing bots different content than users; snapcache exists to show them the same thing.
How is snapcache different from prerender.io?
The render API is drop-in compatible, so existing prerender.io middleware works unchanged. On top of that you get a full console: crawler analytics with AI-bot breakouts, a browsable cache with per-page SEO scores, sitemap warming, a durable render queue, and a free tier of 100,000 renders a month. See the full comparison.
Do I need to change my application code?
No. You add one routing rule at your edge — nginx, a Cloudflare Worker, or our Express / Next.js middleware — that sends bot user-agents to snapcache and everyone else to your app. Copy-paste snippets for each are in the console, and your application code never changes.
How fresh is the cached HTML?
Every page has a TTL, and expired entries are served stale instantly while a background render refreshes them — bots never wait. Deploying something new? Hit the recache API for an instant update, or let sitemap warming re-render your pages proactively. Pages that fail to render correctly are never cached as complete.
What happens when I go over my plan?
You get email alerts as you approach your monthly quota. On the Free plan, rendering simply pauses at the limit — there is never a surprise bill. On paid plans, overage is a flat $0.01 per render, tracked live on your usage dashboard.
Which bots get the prerendered HTML?
Over 50 recognized crawlers: search engines (Googlebot, Bingbot), social preview fetchers (X, Facebook, LinkedIn, Slack), SEO tools, and AI crawlers like GPTBot, ClaudeBot, and PerplexityBot — a list we keep current as new bots appear. Human visitors are never affected; they keep getting your normal app.
Stop letting crawlers see an empty page.
Rendered HTML for every bot, a cache that answers in milliseconds, and a console that shows exactly what Google, ChatGPT, and Perplexity read on your site. Start on the free plan — 100,000 renders a month, no credit card.