Jazui sits between bots and your website: your server or CDN recognizes bots (Googlebot, GPTBot, WhatsApp…) and asks Jazui for the page, which opens it with a real browser, runs your JavaScript and returns the full HTML. People keep reaching your website as usual.
To get started you need five things: an account, your site added, proof that it's yours, the token and the integration on your server. This page walks you through each step and how to check that everything works.
1. Create your account
Go to app.jazui.com/register and sign up with your email and a password, or with your Google account. If you use your email, you'll get a code to confirm it.
Free trial: when you sign up you get a trial of a paid plan without a card (how many days and which plan, in Plans and limits). When it ends, the account moves to the free plan on its own unless you subscribe; you're not charged anything.
2. Add your site
In the dashboard, go to Websites and click Add. Type the domain without https:// or paths, for example mysite.com. The site is the center of everything in Jazui: its settings, rules, blog, metrics and AI bots belong to it.
How many sites you can have depends on your plan: see Plans and limits.
3. Prove the site is yours
Jazui only renders verified domains, so nobody can use the service with other people's websites. In the site list click Verify: you'll see a code unique to your site and two ways to use it. One is enough.
DNS TXT record (recommended)
At your domain's DNS provider (Cloudflare, GoDaddy, Namecheap, your hosting…), create a TXT record on the root domain with the value jazui-verification= followed by your code:
Tipo / Type: TXT
Nombre / Name: @ (misitio.com)
Valor / Value: jazui-verification=8f3a9c1e5b7d40f2a6c8e1b3d5f7a9c0<head>
<meta name="jazui-verification" content="8f3a9c1e5b7d40f2a6c8e1b3d5f7a9c0">
</head>Meta tag
If you can't change the DNS, add the tag above inside the <head> of your site's home page. Jazui looks for it at https://mysite.com/ and https://www.mysite.com/. It must be in the HTML the server returns, not added later with JavaScript.
When it's in place, click Check. DNS changes can take a few minutes to propagate; if it fails, wait a little and try again.
What does each method cover? With the DNS record, the domain and all its subdomains (www, blog, shop…) are verified. With the meta tag, only the exact host you verified.
4. Copy your token
The token is the key your integration uses to talk to Jazui. There are two kinds and you can use either:
| Token | Where it is | What for |
|---|---|---|
| Account token (JAZUI Token) | Home › Integration and settings | Works for all your verified sites. |
| Site token | Websites › Site token | Only works for that site and its subdomains. If it leaks, you regenerate or revoke it without affecting the others. Recommended if you have several sites. |
On Home you'll also see the PUBLIC Token: it's read-only and is used to read your blog from the browser (the public blog API). Don't use it in the integration.
Treat the token like a password: store it as a secret or environment variable and don't push it to a public repository. If you renew it, the old one stops working in less than a minute.
5. Connect the integration
The integration is a small snippet that sits in front of your website and decides which requests come from bots. Pick the one that matches where your website runs:
| Your website runs on… | Use |
|---|---|
| Any hosting behind Cloudflare | Cloudflare Worker (the simplest: you don't touch the server) |
| Vercel or Next.js | Vercel middleware |
| Netlify | Netlify Edge Function |
| A Node server with Express | Express middleware |
| ASP.NET Core (Blazor, Angular or React served by .NET) | Jazui.AspNetCore package |
| A server with nginx | nginx configuration |
| Windows with IIS | web.config with URL Rewrite and ARR |
| Apache or shared hosting with .htaccess | Apache .htaccess |
Each one has its own page with the full code and steps in the Integrations section of the menu. They all follow the same contract, explained in How it works.
6. Check that it works
Every integration treats the user agent integration-test as a bot, so you can test with it. Request your home page with it:
curl -I -A "integration-test" https://misitio.com/HTTP/2 200
content-type: text/html; charset=utf-8
x-jazui: true
x-jazui-cache: MISS
etag: "4812-638976215370000000"If you see x-jazui: true, the page was served by Jazui. The first time x-jazui-cache is MISS (it was just rendered); repeat the request and you'll see HIT, served instantly from the cache.
If the x-jazui header isn't there, the request went to your normal website. Check:
- That the site is verified.
- That the token is the right one and copied correctly (no spaces).
- That the integration is active on the path you're testing (in Cloudflare, the Worker route; in Vercel and Netlify, the
matcherorpath). - That the path doesn't end in a file extension (
.js,.png…): those never go through Jazui.
In the dashboard, under Cached pages, you'll see the page that was just saved, and under Bot traffic the integration-test request.
What's next?
With the integration connected, Jazui already serves your pages to bots. From here you can:
- See the SEO score of each page and fix what fails without touching your code, with rules.
- Decide which AI bots can read you and publish your
robots.txtandllms.txt. - Follow your bot traffic and the visits that come from AI answers.
- Connect Google Search Console.
- Write on the blog, with help from AI using your own key, and share each article on social networks.