Crawler coverage
Rich Previews And Results
Wherever Links Travel
The crawlers that decide how your pages look in search and in shared links all get the finished page.
Who Gets
Rendered HTML
Search Engines
Google, Bing, DuckDuckGo, Yandex and Baidu.
Social Networks
Facebook, LinkedIn, X and Pinterest.
Chat Apps
Slack, WhatsApp, Discord and Telegram.
AI Crawlers
GPTBot, ChatGPT, Claude, Perplexity, Apple and Amazon crawlers are in every setup snippet.
Link Previews
That Look Right
Social and chat apps read your tags from the HTML they fetch. With Render Engine, the tags are there.
- The page title and description you set, not a generic fallback.
- Your Open Graph image, so shared links show the product or article.
- Twitter card tags for posts on X.
- JSON-LD structured data in the source, ready for rich results.
<title>Linen Throw, Natural</title>
<meta property="og:image" content="/linen.jpg">
<script type="application/ld+json">{"@type":"Product"}</script>
<h1>Linen Throw, Natural</h1>Renders Go To
Crawlers That Matter
- Every crawler visit is recorded per crawler, such as Googlebot, GPTBot, ClaudeBot or Perplexity, and grouped as search, social, AI or SEO tool.
- SEO audit tools are recognized and counted, so they do not use up your renders.
- Your routing rule decides exactly which crawlers are sent to Render Engine.

Questions
About Crawlers
Which crawlers does the setup snippet include?
Search engines (Google, Bing, Yandex, DuckDuckGo, Baidu, Apple), social and chat unfurlers (Facebook, X, LinkedIn, WhatsApp, Telegram, Slack, Discord, Pinterest) and common AI crawlers.
Can AI crawlers get rendered pages too?
Yes. Every setup snippet includes common AI crawlers. Remove any you do not want from the list in your rule.
Do SEO audit tools count against my renders?
No. Audit tools are recognized and counted in your activity, and they are not rendered.
Keep Going
See how a render works, how caching keeps crawls fast, and how to set it up.
How it works
Your rule spots crawlers, Render Engine renders the page, people keep the live site.
Caching
Fresh renders on the first crawl, cached snapshots for as long as you choose, purges on demand, safe fallbacks always.
Setup
A checklist, then one guide per stack: Cloudflare, nginx, Apache, Caddy, Next.js, Express, WordPress or any other server.
Make Every Shared Link
Look Its Best
Add one rule and your previews carry the right title, image and description.