Skip to content
Lesuto Render Engine

Rendering for JavaScript sites

JavaScript For Visitors
HTML For Crawlers

Search engines, social networks and AI assistants often see an empty shell when your site is built with JavaScript. Render Engine hands them the finished page, so you get indexed, shared and cited. Your visitors keep the live site.

Start on the Free plan. No card needed.

The Render Engine overview with crawler visits, pages served from cache, fresh renders and renders used this month

How it works

One URL
Two Right Answers

Your routing rule looks at who is asking. Crawlers get finished HTML; people get your app.

  1. A Request Arrives

    Someone or something asks for a page on your site.

  2. Your Rule Checks Who

    A rule in your CDN, server or framework looks at the user agent and picks the path.

  3. Crawlers Get Full HTML

    The request goes to Render Engine, which renders the page in a headless browser or serves the cached snapshot, with content, meta tags and structured data in the source.

    People Get The Live Site

    Visitors go straight to your app, exactly as before. Render Engine never sees them.

Activity

See Every
Crawler Visit

Know which crawlers came, what they asked for and what they got.

  • Search, social and AI crawlers, each named and counted by day.
  • Served from cache, rendered fresh, refused or failed, side by side.
  • Fake crawlers and floods of random addresses are stopped and never use your renders.
  • SEO audit tools are recognized and kept off your plan.
Render Engine crawler activity for 30 days: served from cache, rendered, refused and failed, with protection totals

Pages

Every Page Crawlers
Asked For, In One List

Check a page, render it again or clear it from the cache in one click.

  • Each page with its status, last render and how often crawlers asked for it.
  • Render a page again or purge it after you publish a change.
  • Keep pages cached from an hour to seven days, per domain or per path.
  • Read your sitemap so new pages are ready before crawlers arrive.
Cached pages in Render Engine with status, when each was rendered and how often crawlers asked for it

What you get

Complete Pages
On The First Fetch

A headless browser runs your page, waits for the content, and returns real HTML that crawlers can read.

Pricing

Pay For Renders
Not For Visitors

Pages served from cache are free. Plans are sized by fresh renders and the domains you connect.

  • Free

    $0per month

    20,000a monthPage renders

  • Starter

    $29.99per month

    100,000a monthPage renders

  • Growth

    Recommended

    $59.99per month

    300,000a monthPage renders

  • Pro

    $99.99per month

    750,000a monthPage renders

  • Business

    $149.99per month

    1,250,000a monthPage renders

Questions

Common Questions

Does it work with my framework?

Yes. Any JavaScript frontend on a connected domain works the same way: React, Vue, Next, Angular, custom builds, and sites that load content with scripts.

Will my visitors ever see the snapshot?

No. Your routing rule checks the user agent and only sends matching crawlers to Render Engine. People always get your live site.

Which crawlers get rendered HTML?

Search engines, social and chat unfurlers, and common AI crawlers. Every setup snippet lists them, and you can add or remove any user agent in your rule.

How fresh is the HTML?

The first crawl of a URL renders it live. Successful snapshots stay cached for the time you set per domain (24 hours by default), and you can purge a page or a whole domain whenever it changes.

What happens if a render fails?

Your routing rule serves your normal page instead, so crawlers are never left with an empty error page.

How long does setup take?

Plan on about 10 to 15 minutes: verify your domain, create an API key, and paste the snippet for your host. Book a free call and we will set it up with you.

Get Your JavaScript Pages
Indexed And Shareable

Keep the site your visitors love and give every crawler a page it can read.