What's new (2026.08.17) - Admin dashboard themes · Hub navigation
Read the changelogRender Engine
The Commerce SDK renders your store with JavaScript. Search engines, social apps, and chat unfurls cannot always run that. The Render Engine serves pre-rendered HTML to those crawlers so every product, collection, and page can be indexed, shared, and previewed.
The Problem
Google can render JavaScript, but it is slow and unreliable. Facebook, LinkedIn, Slack, iMessage, and most other crawlers never run JS at all. Without pre-rendering, shared links look empty and products may never appear in search.
How It Works
The Render Engine sits between your website and the visitor. Crawlers get HTML. Humans get the interactive SDK experience.
A visitor or crawler hits your website. The Render Engine inspects the user-agent header.
Search bots, social scrapers, and chat unfurlers receive a fully pre-rendered HTML snapshot. That includes Google, Bing, Facebook, LinkedIn, X, Slack, iMessage, and more.
Real visitors get the fast, interactive SDK experience. Crawlers get clean HTML with meta tags, structured data, and all product content.
Who it serves
One pre-render path covers the crawlers that actually hit a storefront.
Google, Bing, DuckDuckGo, and other indexers get product HTML, sitemaps, and JSON-LD.
Facebook, Instagram, LinkedIn, X, Pinterest, and TikTok get Open Graph cards when someone shares a link.
Slack, iMessage, WhatsApp, and similar apps can show a title, image, and description instead of a blank URL.
Features
Bot detection, pre-rendering, structured data, social cards, caching, and sitemaps. All automatic.
Cache is refreshed when products, collections, or pages change. No manual purging required.
Detects search crawlers (Google, Bing, DuckDuckGo) and social crawlers (Facebook, Instagram, LinkedIn, X, Slack, iMessage, WhatsApp, Pinterest, TikTok) by user-agent. Shoppers still get the live SDK.
Open Graph and Twitter cards so a shared product URL shows the right title, image, and price in feeds, DMs, and unfurls.
Rendered pages are cached at the edge for fast bot responses. Cache TTLs are configurable per content type.
Dynamic title tags, meta descriptions, Open Graph images, and Twitter cards are injected per page.
Serves a fully rendered HTML snapshot to any crawler that cannot run your JavaScript. Every product, collection, and page is crawlable.
Automatic XML sitemaps with all products and collections. Submit once to Google Search Console and forget about it.
JSON-LD Product, BreadcrumbList, and Organization schemas so search results can show rich snippets with price and ratings.
Lesuto-hosted stores include bot routing. On your own site, add a Cloudflare Worker or Apache/nginx rule so crawlers receive pre-rendered HTML.
Setup
The Render Engine is included with the Commerce SDK. Self-hosted sites also need a short bot-routing rule so crawlers hit it.
Embed Lesuto with a single script tag and a Commerce SDK site key. Catalog pages still render in the browser for shoppers.
On a Lesuto-hosted store this is already on. On your own host, add a Cloudflare Worker or Apache/nginx rule.
Read the install guideOpen the Studio SEO tab, then confirm Google Rich Results, Facebook Sharing Debugger, and LinkedIn Post Inspector see title, image, and structured data.
Better Together
The Render Engine is the SEO and sharing layer under everything you build on Lesuto.
Shoppers get the fast, interactive SDK. Crawlers get the prerendered HTML of the same page.
See and verify the metadata Lesuto injects for each page, live, with no guesswork.
AI-written product copy and articles ship with meta tags and JSON-LD the engine serves to crawlers.
Included with the Commerce SDK. Self-hosted sites need about 15 minutes of Worker or Apache config.
Get Started Free