Serve fully rendered HTML to search engine and AI crawlers — without SSR or code changes.
$0/month · Pay only for what you use
Often nothing. Here's what happens every time a bot visits a client-rendered site.
Bot visits your page
A search engine bot opens your URL
Server sends an empty page
Instead of content, it sends instructions: "run this JavaScript code to build the page"
Code needs to run
Your browser would run the code — but the bot can’t or won’t wait
Bot sees nothing
It records a blank page and moves on
Bot visits your page
A search engine bot opens your URL
Server sends an empty page
Instead of content, it sends instructions: "run this JavaScript code to build the page"
Code needs to run
Your browser would run the code — but the bot can’t or won’t wait
Bot sees nothing
It records a blank page and moves on
Your page is invisible in search results
See what crawlers actually receive — free tool.
Crawl budget wasted
Bots spend your crawl budget waiting for JS to render instead of indexing content
Pages skipped entirely
Complex SPAs/PWAs often return empty HTML shells that bots can't parse
No rich snippets
Without rendered meta-tags & structured data, you get plain blue links at best
Broken link previews
Shared links on Slack, WhatsApp, Facebook show blank cards — zero engagement
Check which search engines and AI bots can actually read your pages.
Which bots can actually see your JavaScript-rendered pages
| System | Type | Runs JS? | Details |
|---|---|---|---|
| 🔍 Google (Googlebot) | 🌐 Search Engine | Yes | Full Chrome (Evergreen). Renders everything, but JS content is indexed with delay (second wave).Prerendering recommended |
| 🔎 Bing (Bingbot) | 🌐 Search Engine | Yes | Can render JS but less reliably than Google. Heavy scripts often take longer to process.Prerendering recommended |
| 🟨 Yandex (YandexBot) | 🌐 Search Engine | Partial | Renders only key pages. Deeply nested JS content often drops from index.Prerendering recommended |
| 🦆 DuckDuckGo | 🌐 Search Engine | No | Relies on Bing’s index. Does not render JS on its own.Prerendering recommended |
| 🍎 Apple (Applebot) | 🌐 Search Engine | Partial | Renders some JS for Siri and Spotlight. Limited compared to Googlebot.Prerendering recommended |
| 🤖 OpenAI (GPTBot) | 🤖 AI Bot | No | Collects raw HTML only. If your content isn’t in source code, GPT models won’t learn it.Prerendering recommended |
| 💬 ChatGPT (Browse) | 🤖 AI Bot | No | When ChatGPT "visits a site", it fetches raw HTML (like curl). Does not wait for React to render.Prerendering recommended |
| 🔎 Perplexity AI | 🤖 AI Bot | No | Fetches static page snapshots extremely fast. Dynamic content is often invisible.Prerendering recommended |
| ✨ Google Gemini | 🤖 AI Bot | Yes | Has direct access to Google’s pre-rendered page cache from Search. |
| 🟠 Claude (ClaudeBot) | 🤖 AI Bot | No | Crawls raw HTML for training data. JS-rendered content is invisible.Prerendering recommended |
| ⚡ Grok / xAI | 🤖 AI Bot | No | Collects raw HTML. No JS execution engine.Prerendering recommended |
Bots get a fully rendered HTML version of your page. Users get your normal app.
Full HTML Snapshot
Rendered in a real browser. No empty shells.
Users See Nothing Different
Only bots get the snapshot. Your app stays untouched.
No Code Changes
Works as a lightweight proxy. Connect once — done.
Setup time: ~15 minutes. Verify your prerendering is active with our free checker.
Your visitors notice nothing. Bots get the full picture.
Delivered Instantly
The ready-made page is served from a server close to the bot — in milliseconds
Complete Page Copy
The snapshot includes everything: text, images, titles, and descriptions
Always Fresh
Pages are automatically updated on a schedule you control
50%+ traffic boost
Pages that were invisible to Google start ranking. More pages indexed = more organic traffic. Run a quick SEO audit to see technical issues. Results typically visible within days.
3—5× crawl efficiency
Bots process lightweight static HTML instead of executing heavy JS. Your crawl budget goes dramatically further.
Rich snippets enabled
Structured data, Open Graph, Twitter Cards delivered perfectly every time. Higher CTR from beautiful search results.
Core Web Vitals ↑
TTFB, LCP, INP, CLS metrics improve for bot-facing requests — directly impacting your Lighthouse & PageSpeed scores.
Perfect link previews
Every shared link on Slack, WhatsApp, Facebook, iMessage, Telegram shows rich image + title + description.
AI search visibility
ChatGPT, Gemini, Perplexity, Grok, Claude bots crawl like Google. If they can read your page, you show up in AI answers.
Real Google Search Console data from production websites
14,000+ property pages · Next.js + Lovable
2,000+ exercise lessons · Mixed stack
450,000+ pages · 30 languages · WordPress
No subscriptions · No commitments · Pay only for what you use
Quick estimate for your site type
3,000 renders/mo · $0.0010 per render
Every account includes 1,200 free renders · Auto-recache included
Paste any URL — we'll fetch it as Googlebot and confirm the x-prerender-id header is set.
No account, no credit card · Works on any site, not just ostr.io
Prerendering serves optimized pages to 20+ search engines and AI crawlers. See how they view your site.
Choose your integration
NPM middleware · CloudFlare Worker · Nginx config · Meteor package — pick what fits your stack
Add the snippet
Copy-paste the middleware or config block. Set your auth token. That's the entire “migration.”
Watch traffic grow
Bots start getting served from co-located CDN immediately. Monitor everything in real-time analytics. Results in days, not months. Then verify with our prerender checker.
Technology-agnostic · Zero lock-in · 0 dependencies
React
Vue
Angular
Svelte
Meteor
Next.js
Ember
Backbone
Nginx
Apache
CloudFlare
Node.js
JavaScript
TypeScript
PHP
Python
Ruby
GoES6 / ES7 Ready
ECMAScript 2015 & 2017 support built-in
AMP Compatible
.amp. and /amp/ URLs auto-detected
CSP Compatible
Works with Content-Security-Policy headers
“Will this affect what my users see?”
No. Prerendering acts as a transparent proxy that detects bot User-Agent strings (Googlebot, GPTBot, ClaudeBot, and others) and only intercepts those requests. Human visitors get your normal JavaScript app, untouched. Bots receive a pre-rendered static HTML snapshot of the same page — identical content, served in a format crawlers can read.
“Is this considered cloaking by Google?”
No. Google's official documentation explicitly recommends pre-rendering as a valid solution for JavaScript-heavy sites. Cloaking means showing different content to bots vs. users; pre-rendering serves the same content in a different format (rendered HTML vs. JavaScript bundles). Google rewards this approach, and Bing, Yandex, and AI crawlers consume the same snapshot.
“What if it breaks my site?”
Zero risk to human visitors. Pre-rendering runs as middleware that only activates on bot User-Agent matches — your app code, deployment pipeline, and human user experience stay untouched. If the prerender layer misbehaves, bot traffic falls back to your origin automatically. You can remove the middleware in one config line with no rollback work.
“We already have SSR set up.”
Pre-rendering still helps even when SSR is in place. SSR re-renders on every request and uses your origin compute; pre-rendering caches one render per URL on a CDN co-located with the bot. That is roughly 10× faster TTFB, dramatically cheaper, and adds reliable link-preview generation plus access for AI bots that often fail on SSR-only sites.
“How do I know it's working?”
Three ways. The real-time analytics dashboard logs every crawl, cache hit, status code, and response time per bot. Our free Prerendering Checker tool fetches your URL as Googlebot and confirms the x-prerender-id response header is present. And Google Search Console will show your indexed-pages count climb within days of activation.
“What about data freshness?”
Configurable TTL from 2 hours up to 31 days, set per route or globally. Auto-recache refreshes pages automatically when they expire, so nothing goes stale on its own. For major content changes (product launches, breaking news), an instant purge clears the cache for one URL or your whole site in seconds.
Ostrio Systems, Inc
Registered company, operating since 2015
Open Source Core
BSD-3-Clause · 253 commits · Full TypeScript
5.0 Rating
AppSumo verified · GDPR compliant
7 global regions · 5.0 on AppSumo · Trusted since 2015. Start free, pay only when bots crawl past your free quota.
1,200 free renders/month · No credit card · 15-minute setup · Cancel anytime