Prerender JavaScript pages for search engines and AI crawlers.
Renderlix renders your React, Vue, Angular or SPA pages in a real browser, caches the HTML and serves it to bots. Plug it into nginx - your app and your users stay exactly as they are.
- No frontend rebuild
- Works with your existing nginx
- Static files never leave your server
- Now in public beta
- Free plan available
What is Prerendering?
<div id="app"></div> <!-- Bots see nothing -->
<html>
<head>
<title>Your Page Title</title>
<meta name="description" ... />
<script type="application/ld+json">
{ structured data }
</script>
</head>
<body>
<h1>Full page content</h1>
<nav>...</nav>
<main>All your JS content</main>
</body>
</html>Prerendering is the process of loading a web page in a headless browser environment - executing all JavaScript - before delivering the resulting HTML to a crawler or AI bot that needs a fully-rendered version.
A typical client-side app initially returns an empty shell. The meaningful content only appears after JavaScript executes. Renderlix loads the page, runs the JS, waits for all content to appear, and captures the resulting HTML - then caches and serves it instantly to every crawler.
- Page copy and headings
- Internal links and navigation
- Product and category content
- Metadata and structured data
- Dynamically loaded elements
- All JS-generated content
Simple pricing that scales with your crawl.
Pay for renders, not for bot hits served from cache. Start free, upgrade when your traffic grows. Overages are capped, so a crawl spike never turns into a surprise bill.
| Compare plans Everything you need to render at any scale. | |||||
|---|---|---|---|---|---|
| Renders / month | 5,000 | 30,000 | 150,000 | 600,000 | 2,000,000 |
| Extra renders | — (stale-serve) | $2.00 / 1k | $1.50 / 1k | $1.00 / 1k | $0.80 / 1k |
| Overage cap | — | Up to 2× plan price | Included | Included | Included |
| Projects | 1 | 3 | 10 | Unlimited | Unlimited + client sub-accounts |
| TTL min–max | 24h–7d | 12h–30d | 6h–30d | 1h–30d | 1h–90d |
| URL TTL overrides | — | 3 rules | 10 | 50 | Unlimited |
| Sitemap revisit | — | 7 days | 24 hours | 1 hour | 1 hour |
| Bot logs Daily statistics; individual requests up to 90 days | 7 days | 30 days | 90 days | 1 year | 2 years |
| Bot groups | Fixed list | Enable / disable groups | + custom patterns | + custom patterns | + custom patterns |
| Deploy invalidation Webhook + purge API | — | 1 per project | Unlimited | Unlimited | Unlimited |
| Cache warming | — | — | Included | Included | Included |
| Seats | 1 | 1 | 3 | 10 | Unlimited |
| White-label reports | — | — | — | — | Included |
| Support | Community | Email · 48h | Email · 24h | Priority · 8h | Priority + onboarding |
A render is one page rendered in our browser. Cached responses don't count. Rendering both desktop and mobile counts as two renders.
How Renderlix Prerendering Works.
Renderlix acts as a rendering layer between selected crawler requests and your JavaScript application - invisible to your users, essential for bots.
Verify your domain.
Add one TXT record to your DNS. It proves you control the domain and doesn't route any traffic.
Create a token.
Generate a project token in the dashboard. We show it once and store only a hash.
Paste the nginx config.
Three short snippets: one in http {}, one in server {}, one line in your location / {}. A built-in check confirms everything is wired up.
Nginx checks the user agent.
Googlebot, Bingbot, GPTBot and other crawlers go to Renderlix. Real visitors, and every static file, are served by your own server as usual.
Cached? Served instantly.
If the page is in cache, the crawler gets the HTML right away.
Not cached? We render it.
Renderlix loads the page in a headless browser, waits until it's ready, saves the HTML and returns it.
Anything goes wrong? Your page still loads.
If we can't serve a request, nginx falls back to your own page. A Renderlix issue never takes your site down for crawlers.
Ready for search engines and AI crawlers alike.
Switch without touching your app.
Renderlix already understands window.prerenderReady, so pages tuned for Prerender.io render correctly from day one. Swap the nginx snippet, verify your domain, and you're done.
- Same readiness signal — no code changes
- Regex include/exclude rules and ignored query parameters
- Bot logs and render history on every plan, including Free
- Clear overage pricing with a cap, so a crawl spike can't blow up your bill
Everything you need to control what crawlers see.
See every bot visit
Which crawlers came, which pages they asked for, cache hit or miss, and the status code they got. Filter by URL, crawler or result up to 7 days back on Free, 30 on Starter and 90 from Pro.
Render history
Every render attempt with its time and outcome. Spot slow or failing pages before a crawler does.
Sitemap sync
Point us at your sitemap and new pages are rendered before the first crawler arrives, so it never waits. Sync by hand on any plan, automatically from Starter. From Pro we also re-render pages before their cache runs out.
Smart readiness detection
We wait for window.renderlixReady, a CSS selector of your choice, or the network to go quiet - so we capture the page when it's actually done, not half-loaded.
Precise cache control
Set cache TTL, include and exclude URLs with regex, strip tracking parameters like utm_* and gclid. Stale pages re-render in the background while crawlers still get the cached copy.
Desktop and mobile
Render the desktop version, the mobile version, or both. Mobile comes with every paid plan.
API and deploy webhooks
Purge or re-render pages from your CI the moment you deploy. Call the API or hit a webhook, and crawlers get the fresh version instead of waiting for the cache to expire. Available from Starter.
JavaScript Websites Are Powerful. Crawling Them Shouldn't Be Complicated.
Modern websites rely heavily on JavaScript. React, Vue, Angular, and other JavaScript frameworks make it possible to build fast interfaces, interactive dashboards, marketplaces, SaaS applications, ecommerce stores, and dynamic websites that would be difficult to create with static HTML alone.
But client-side rendering creates an additional step for crawlers. A browser can load your JavaScript, execute it, request data from APIs, update the DOM, and finally display the complete page. A crawler may process that workflow differently.
Google can execute JavaScript, but JavaScript pages still go through a rendering process and not every crawler handles JavaScript in the same way. Other search engines, SEO tools, social crawlers, and AI crawlers may execute only part of your scripts - or none at all.
That can leave them with an incomplete HTML response containing little more than an application shell.
Renderlix provides a simpler path.Instead of asking every crawler to execute your application, our prerender service creates a fully rendered HTML version of the page and makes that version available when supported bots request it.
A Prerender Service Built for JavaScript SEO.
JavaScript SEO becomes unnecessarily difficult when important content exists only after scripts execute. Renderlix helps bridge that gap.
Make Important Content Available in Rendered HTML
If product descriptions, category text, landing-page copy, links, or metadata are generated through JavaScript, they may not exist in the initial HTML response. Prerendering provides crawlers with the DOM after the page has rendered - making critical page content accessible without requiring each crawler to reproduce the entire browser-side rendering process.
Improve Crawlability of JavaScript Websites
Internal links are fundamental to crawling. If navigation or links appear only after JavaScript execution, some crawlers may have difficulty discovering them. A prerendered HTML response can expose those links directly in the rendered document, helping crawlers understand the full structure of your website.
Reduce Dependence on Crawler-Side JavaScript Rendering
Different crawlers have different capabilities. Instead of designing your SEO strategy around what every individual crawler may or may not execute, serve them a rendered HTML version of the page. It creates a more predictable response for JavaScript-heavy websites.
Search Engine and AI Crawler Rendering.
Their ability to process JavaScript varies. Every plan covers the crawlers on our list. From Starter you can turn groups of them on and off, and from Pro you can add your own User-Agents.
Serve rendered pages to selected search engine bots when your JavaScript content requires it.
Supported AI crawlers are on the list on every plan, so publicly accessible content can be returned as rendered HTML.
Pages with dynamically generated metadata can also benefit from rendering when preview crawlers need access to the final document.
Need to prerender pages for an internal crawler or specialized SEO tool? From the Pro plan, add its User-Agent as a custom pattern. You stay in control of which requests are sent through the rendering service.
One Prerendering Platform for Multiple Domains.
Managing several JavaScript websites? You shouldn't need a completely different rendering infrastructure for every project.
Use one Renderlix account to organize prerendering across your sites and applications.
- Agencies
- SEO teams
- Development companies
- SaaS portfolios
- Ecommerce groups
- Businesses operating multiple regional domains
Manage rendering, caching, and crawler access from one platform while keeping each website's implementation independent.
Frequently Asked Questions.
Everything you need to know about prerendering, JavaScript SEO, and how Renderlix works.
A prerender service loads a web page in a browser environment, executes its JavaScript, and produces rendered HTML. That HTML can then be cached and served to crawlers that need a completed version of the page. It is commonly used for JavaScript websites, SPAs, React applications, Vue websites, Angular applications, and other client-side rendered platforms.
In SEO, prerendering usually refers to generating the completed HTML version of a JavaScript page before delivering it to a crawler. The objective is to make important public page content, links, metadata, and other elements accessible in HTML without requiring the crawler to execute the full client-side application itself.
Yes. Google can execute JavaScript and uses a web rendering system to process JavaScript pages. However, JavaScript introduces an additional rendering step and other crawlers may have different JavaScript capabilities. Prerendering can therefore still be useful for websites that want to provide selected crawlers with a complete rendered HTML response.
No. No legitimate prerendering SEO software can guarantee search rankings. Prerendering addresses a technical accessibility and rendering problem. Rankings depend on many other factors, including content, relevance, internal linking, authority, competition, site quality, and technical SEO. The purpose of Renderlix is to make it easier for configured crawlers to access the content your JavaScript application already provides.
Yes. React prerendering is one of the most common use cases for crawler rendering. Renderlix loads the React application in a browser environment, executes the JavaScript, and generates the resulting HTML.
Yes. Vue pages can be rendered and cached so configured crawlers receive the completed HTML rather than relying entirely on client-side JavaScript execution.
Yes. Angular and AngularJS applications can also use a prerender service when public page content depends on JavaScript rendering.
No. Server-side rendering generates HTML as part of your application's normal server-side architecture. Prerendering can be added as an additional rendering layer, often specifically for crawlers, while the normal user-facing application continues to use client-side rendering.
No. Static site generation usually creates HTML files during a build process. A cloud prerender service renders URLs through a browser and can cache or refresh the resulting HTML independently of your frontend build.
Yes. Single-page applications are a common reason businesses use prerendering. It allows normal users to continue using the SPA while selected crawlers receive rendered HTML.
It can help crawlers that would otherwise receive incomplete HTML from a JavaScript application. Supported AI crawlers are on the list on every plan, and Renderlix can serve them the rendered public page instead of the original client-side application shell.
No. In a crawler-focused implementation, normal visitors continue accessing your existing website. Only configured crawler requests are routed through the prerender service.
No. One of the main reasons to use a prerendering service is to add crawler rendering to an existing JavaScript application without rebuilding the complete frontend architecture. Your exact integration depends on your server, CDN, framework, and deployment setup.
Renderlix integrates through nginx, on Debian, Ubuntu, RHEL, Alpine and the official nginx Docker images. Without nginx, use our SDK for Next.js and Express, a Cloudflare Worker for any site behind Cloudflare, or a few lines of code on anything built on the Fetch API. Running something else? Tell us what you use.
A TXT record proves you control the domain itself, not just whatever server answers today. It doesn't route any traffic and works even when your DNS is proxied through Cloudflare.
Nginx falls back to your own page. Crawlers get what they would have got without us, and your site stays up.
No. We support window.prerenderReady, so readiness signals you already have keep working.
Yes, from the Starter plan. Use the purge API or a deploy webhook from your CI, and the pages you changed are re-rendered right away. The number of webhook endpoints depends on your plan.
Only your domain. Only your token. Never your downtime.
DNS-verified domains
Every project is verified with a TXT record before it can be used. Until then, our gateway refuses all requests for that domain.
Tokens we can't leak
Tokens are shown once and stored only as a hash. A request is accepted only when the token and the Host header both match your project — a leaked token can't be used to render someone else's site on your plan.
Your server stays in charge
Static files never come to us. Excluded URLs — admin and cart pages, for example — stay on your server. If we refuse or fail a request, nginx serves your own page.
A renderer you can identify
Our browser announces itself as Renderlix, so you can allow it through Cloudflare or any other bot protection with one narrow rule.
Run several sites? Add each domain as its own project under one account — separate settings, tokens and logs, one bill. Built for agencies, SaaS portfolios and multi-region stores.
We're new. That works in your favor.
Renderlix is in public beta. Early users talk directly to the people building it, and the features they ask for go to the top of the list.
- Direct line to the founders — not a ticket queue
- Help with your nginx setup if you get stuck
- Your feature requests shape the roadmap
Let every crawler read your site.
Verify your domain, paste the nginx config, and watch the first bots come in. Free plan, no card required.