AI doesn’t run JavaScript
GPTBot, ClaudeBot or PerplexityBot read the HTML as it comes. If your SPA adds the content, the page is empty to them: they can’t cite or recommend you.
How it works
How Jazui works
Your server recognizes bots and asks Jazui for the page. Jazui renders it in a real browser, caches it and returns complete HTML to them.
Why it matters
If your site is built with JavaScript, many bots see it empty
Angular, React, Vue or Blazor build the page in the browser. People don’t notice, but many bots only read the HTML your server returns.
Neither do social networks
Link previews on WhatsApp, LinkedIn, X or Telegram come from the HTML. Without a title, description and image, your link is shared without a card.
Google does, but later
Google renders JavaScript in a second pass, when it has resources to spare. With full HTML it indexes sooner, crawls more pages and doesn’t depend on your JavaScript loading well.
<html>
<head>
<title>My store</title>
</head>
<body>
<div id="app"></div>
<script src="main.js"></script>
</body>
</html>A page with no text, no useful title and nothing for the preview.
<html lang="en">
<head>
<title>Trail running shoes | My store</title>
<meta name="description" content="Light, great grip…">
<meta property="og:image" content="…/trail.jpg">
<script type="application/ld+json">…</script>
</head>
<body>
<h1>Trail running shoes</h1>
<p>Light and made for the mountains…</p>
<a href="/deals">See deals</a>
</body>
</html>The same page a person sees, already rendered: text, metadata, structured data and links.
Under the hood
The journey of a request
Your server decides who goes to Jazui. People still go straight to your site and, if Jazui doesn’t answer, so do bots.
BotGooglebot, GPTBot…
Your server or CDNThe integration recognizes the bot
JazuiCache or render with Chrome
Complete HTMLContent, metadata and links
People
Your server or CDN
Your SPAAs always
1. Your server recognizes bots
The integration compares the user agent with Jazui's bot list and only redirects those requests.
- Search engines, social networks, SEO tools and AI bots.
- Files (images, CSS, JavaScript…) are never redirected.
- Ready-made integrations for Cloudflare, Nginx, Apache, IIS, Node, Vercel, Netlify and ASP.NET Core.
2. Jazui renders the page
The first time a URL is requested, Chrome opens it, runs your JavaScript and waits for it to finish loading.
- With the mobile or desktop view depending on the bot.
- With a maximum wait time that you choose.
- Rules decide which URLs get rendered and which don't.
3. The cache stays up to date
Later requests are served from the cache instantly, and pages are re-rendered automatically.
- Automatic recaching every so many days, per site or per rule.
- Instant recaching from the dashboard or through the API when you publish.
- A warning if the cache no longer matches your live site.
4. You control what bots see
Every render is checked, and from the dashboard you see which bots visit you and what they get.
- SEO score per page and broken link checks.
- A policy per AI bot, with automatic robots.txt and llms.txt.
- Bot traffic, Google Search Console and a weekly report.
5. Privacy and security
Jazui only sees the bot requests your server sends it, always with your account's token.
- Your users never go through Jazui.
- Only domains you have verified get rendered.
- You can delete the cache and your account whenever you want.
Getting started
Up and running in minutes
- 1
Add your site
Create your free account, add your domain and verify it with a DNS record or a meta tag.
- 2
Connect the integration
Copy the snippet for your server or CDN (Cloudflare, Nginx, Apache, IIS, Node, Vercel, Netlify or ASP.NET Core) with your account token.
- 3
Check the result
From the dashboard you see what each bot gets, the SEO score of every page and your bot traffic from day one.
How does AI see you today?
Scan your site for free, no sign-up needed: in under a minute you see what AI, Google and social networks read, and what would change with Jazui.