Works on websites that can have Cloudflare in front of them, such as custom-built websites — not on Wix, Squarespace, GoDaddy Website Builder, Framer or Shopify. Your website stays exactly where it is: only its traffic passes through Cloudflare, where a tiny worker serves your haAplo fixes automatically and counts real AI-bot visits. You do this once — or send this page to whoever manages your website.
⏱ Total time: 30–60 minutes, once — in two sittings: there is a waiting pause in the middle, and Cloudflare emails you when to come back.
Every screen name below was verified on Cloudflare's real interface on 25 August 2026; the AI-bot lines of the domain step were updated on 27 September 2026 from Cloudflare's own changelog (from 15 September 2026 new domains block Training and Agent bots on pages with ads), not from the screen. Cloudflare changes its screens without notice: if what you see does not match, write to [email protected] — we fix the guide, not you.
Connect with one click. Sign in to Cloudflare, pick your account and allow haAplo. Nothing changes yet. Back here, you see your AI-bot settings today and what haAplo will set. Then you install with one more click. Your domain must already be on Cloudflare. If it isn't, add it first with the guide below, up to the Active email.
Cloudflare's free Workers plan covers 100,000 requests a day. haAplo keeps the worker off your static folders (on PrestaShop: img, themes, modules, js). A page view costs one request for the page, plus one per product image it shows. Up to about 3,000 page views a day, the free plan is enough. Above that, Workers Paid ($5 a month) removes the daily limit. Past the limit, with the Fail open setting on its routes, the worker steps aside: your website keeps working, only the fixes pause until the next day. haAplo sets Fail open when it installs; if Cloudflare does not let it, this page tells you how to set it by hand.
Before we install: your AI-bot settings on Cloudflare. Nothing has changed yet.
| Setting | Today | After haAplo |
|---|
AI Training bots (the ones that learn from your pages): — your call; haAplo does not score it either way.
Google's training is not a crawler: Cloudflare can't block it. It's a line in robots.txt (Google-Extended): with block, haAplo puts it in the robots.txt it serves for you; if your website serves its own robots.txt instead, add it there. Blocking it also keeps you out of the Gemini app's answers.
Bot Fight Mode, firewall rules and rate limits stay as they are. Disconnect puts these five settings back exactly as they are today.
One step left, at your domain registrar: replace the nameservers with these two. When Cloudflare emails you that the domain is Active, come back and press Check now: haAplo finishes the installation.
Before you change them: if DNSSEC is on at your registrar, switch it off first. On GoDaddy the change asks for a code sent by email — it is valid for 60 minutes, and three wrong tries lock the change for 24 hours: copy and paste it.
Connected through Cloudflare. The worker is installed and updates itself every hour; new versions are published by us.
The worker is installed in your Cloudflare account, but haAplo has not seen it answer on your website in the last day, so it cannot confirm your fixes are live. haAplo looks again at each hourly sync. If this stays, check in Cloudflare that your domain is Active and that its DNS rows for your website (the domain and www) are Proxied, with the orange cloud.
One setting Cloudflare would not let us set from here: on each of the two routes, Fail open (proceed) under the request limit — open Workers Routes and set it, so your website never waits on us.
Cloudflare did not confirm the AI-bot settings: open your domain's Overview and check that Search and Agent are on Allow.
Shopify does not allow Cloudflare in front of a store, so this road is not for you and we won't send you down it. Your road is the haAplo Shopify app: use it instead →.
haAplo does not connect these websites through Cloudflare, so this road is not for you and we won't send you down it. There is no automatic installation on this platform: get the fix files from your website's page in haAplo and add them by hand, with the steps in the guide inside the ZIP.
Questions? Write to [email protected].
On WordPress? Use our plugin instead — one upload, no Cloudflare needed →
Go to cloudflare.com and create a free account — the Free plan is enough. Already have one? Log in.
Cloudflare will sit in front of your website and run a tiny helper (a "worker") that serves your haAplo fixes and counts AI-bot visits. A huge part of the internet already runs behind Cloudflare — your website stays exactly where it is.
In the left menu click Domains → Overview, then the blue Add domain button (top right).
On the "Add a website" page pick the first card: Connect a domain.
In the "Domain name" box type only your domain — yourdomain.com, without www.
Below the box, Additional configuration is already open. Four lines matter — set them like this, whatever Cloudflare pre-selected (since 15 September 2026 new domains start with Training and Agent blocked on pages with ads):
Search bots are the ones that put you in AI answers; Agent bots are the live assistants that fetch your page while a customer is asking about you. Blocked at the network edge, they would silently fight the work haAplo does — so they must be allowed. Training bots feed the models themselves: letting them in or keeping them out is a legitimate choice that is yours, and if you block them, do it on this line rather than in robots.txt, so haAplo can keep your robots.txt correct.
You land on "DNS management for yourdomain.com" — a search box, an Add record button, and at the bottom Continue to activation. One rule before that button:
A (or AAAA) rows whose Name is your bare domain (often 2 of them);www row — yes, www stays ORANGE, even though it is a CNAME: it is your website too.For each other orange row: click Edit → click the Proxy status switch (orange "Proxied" becomes grey "DNS only") → Save.
Orange = the traffic passes through Cloudflare. Grey = just an address entry. Rows like autodiscover, email, sip, lyncdiscover, msoid, _domainconnect are your email and services — grey keeps them pointing at their own servers, not through Cloudflare.
Rows of type MX, TXT and SRV have no cloud to change: leave them alone, but do check at least one MX row exists — it is what delivers your email. You can redo this step at any moment, before or after the nameserver switch, from DNS → Records.
Warning triangles next to some rows, or a "Recommendations" banner suggesting to proxy more records or add DMARC? Ignore both — that is Cloudflare being cautious, not an error.
Final check: count the orange clouds — normally exactly 3 (two A + www). All good? Click Continue to activation.
One too few? You probably turned www grey by mistake: click its Edit → switch Proxy status back ON (orange "Proxied") → Save.
One too many? Go back one step (← Back) and re-read the rule: only your bare domain's A rows and www stay orange.
Cloudflare now shows two nameservers of its own — two names like ada.ns.cloudflare.com (yours will be different). Keep this tab open: you will copy them one at a time in the next steps.
The next change happens in the panel of the company where your domain is registered. Not sure which company that is? The nameservers you are about to replace give it away: domaincontrol.com = GoDaddy · aruba.it = Aruba · register.it = Register.
If your domain is at GoDaddy (the most common case): go straight to account.godaddy.com/products and scroll to the Domains section. Next to your domain there are two buttons, DNS and Manage — click DNS.
Landed on a page that offers to build you a website ("What's next — Customize a website")? That is GoDaddy's venture dashboard, a dead end. Go back to account.godaddy.com/products.
Your domain is somewhere else? The path is similar everywhere: in your domain's settings look for DNS or Nameservers, choose "use my own / custom nameservers", paste Cloudflare's two names, save — then skip ahead two steps.
You are on your domain's control page (tabs: Overview · DNS · Registration Settings…). In the DNS tab open Nameservers → button Change Nameservers.
In the Edit nameservers window select I'll use my own nameservers. Paste Cloudflare's first name into Nameserver 1 and the second into Nameserver 2 — if the second box is missing, click the Add Nameserver link to add it. Then click Save.
A warning that changing nameservers "is risky"? That is GoDaddy's standard text. Optional extra safety: click download inside that text to save a backup copy of your DNS. Then click Continue.
You are done here when the page shows "Using custom nameservers".
Back on Cloudflare your domain shows a yellow pending banner until the change spreads across the internet. Cloudflare sends you an email when it becomes Active — you can close this page: it remembers where you left off. Don't want to wait? The same screen has a Check nameservers now button that forces the check.
If Cloudflare has all your DNS records, your website and your email usually keep working while you wait. While you wait you can still fix any cloud you missed (DNS → Records) — and you can even prepare the worker in the next steps: it just won't serve anything until the domain turns Active.
Still pending after a few hours? Re-check the two nameservers at your registrar (typos happen). It usually takes a few hours, sometimes up to a day — that is the internet, not you.
When the Active email has arrived, back on Cloudflare: if you are inside your domain, first click ← Back to Domains at the top of the left menu — the next entry lives at account level, not inside a domain. Then: left menu → Compute → Workers & Pages → Create application → under Workers choose Start with Hello World!.
Can't find Compute? It sits in the Build section of the left menu, together with AI, Storage & databases and Media.
Ended up on the "Workers Routes" page inside your domain? Do NOT click "Add route" — a route needs a worker, and the worker does not exist yet. Click Manage Workers (top right) instead: it takes you to the right place. The routes come at the end.
Ended up on Domains → Transfers, with a price and a Continue button? That page transfers your domain registration to Cloudflare — money, and nothing to do with the worker. Go back.
Name it haaplo-proxy — and at the bottom of this panel, leave "Protect with Cloudflare Access" OFF. Then click Deploy — the sample code is fine for now, you replace it in the next step.
"Protect with Cloudflare Access" puts a login wall in front of the worker. It looks harmless now, but once the routes are connected that wall lands in front of your whole website, and every visitor gets asked to authenticate. Off means off for good.
Click Edit code, select ALL the sample code and delete it, then paste ours. To publish, open the arrow next to Deploy and click Deploy — "immediately deployed to 100% of your audience".
This tiny worker serves your haAplo files (llms.txt, Markdown pages, robots.txt, structured data), counts AI-bot visits, and lets everything else through. It is deliberately simple: if haAplo is ever unreachable, it keeps using the last fixes it received, and your pages keep reaching your visitors.
Open the worker's Settings tab. Under Variables and Secrets click Add: name HAAPLO_KEY, value = your key:
Already saved it as Text? Don't redo it: in the Type column pick Secret from the menu, then Deploy. The value stays.
This key only opens your own website — treat it like a password. It is the only secret in the whole setup, and it never gives access to anything else.
Variables and Secrets → Add again: name HAAPLO_API, value https://haaplo-app-production.up.railway.app. This one is not a secret — leave the checkbox alone. Finish with Add 1 variable.
First, create the storage box. Left menu → Storage & databases → Workers KV → + Create Instance → name it haaplo-payload → Create.
Then connect it to the worker. Go back to the worker (Compute → Workers & Pages → haaplo-proxy) and open the Bindings tab — it is a top tab of the worker, next to Deployments, NOT inside Settings. Click Add binding → KV namespace → Variable name PAYLOAD → in the menu pick haaplo-payload → Add Binding.
A small storage box where the worker keeps a copy of your fixes — so it can serve them instantly, even when haAplo is not reachable. It must exist before it can be connected: that is why this step is two places, in this order.
On the worker: Settings → Trigger events → Cron triggers → + Add. Stay on the Schedule tab and set Execute Worker every → Hour(s) → 1.
Below, Cloudflare prints the next run times. If you read whole hours (10:00, 11:00, 12:00…), it is right — you can see you did it well instead of hoping.
Back to your domain: Cloudflare home → your domain → left menu Workers Routes → blue Add route. In the Route box type yourdomain.com/* — it must END with /*. In the Worker dropdown pick haaplo-proxy.
Then Save. Before adding the second route: open your website in a new tab and check it looks normal. It should be identical to before.
"Could not understand route pattern"? The /* at the end is missing — the box wants a URL pattern, not a name.
The route tells Cloudflare: "let this worker handle my website's traffic". Without it, the worker exists but never runs.
Click Add route again: this time type www.yourdomain.com/*, pick the same worker haaplo-proxy — and set "Request limit failure mode" to Fail open (proceed) again: the setting is per route, and this one starts back on Fail closed. Then Save.
Open yourdomain.com/llms.txt — within the first hour it starts serving your haAplo content. Your website page in the haAplo dashboard shows connected once haAplo sees the worker answer on your website, and the "AI bots are reading you" graph starts filling as crawlers visit.
Last look, ten seconds: on your domain's Overview page, right panel, Manage AI bot access must show Search and Agent on Allow (Training as you chose), and Manage your robots.txt must be disabled — exactly how you set them at the start.
Want new versions to install themselves? On your website page in the dashboard, press Connect with Cloudflare: one consent, and haAplo takes over this same worker and installs every future version. Or skip it: the service works the same, we'll simply tell you when an update exists and you paste the new code from this page.
On AI Crawl Control you see "Markdown for Agents" greyed out with "Upgrade plan"? It is a Cloudflare Pro feature — nothing you need and nothing you did wrong: haAplo already serves Markdown versions of your pages itself.
If anything ever looks off: when haAplo is unreachable, the worker keeps using the last fixes it received. Removing it (delete the two routes) takes the worker off your website: your pages then reach visitors without it.
haAplo now serves and updates your fixes automatically, hour by hour — and counts the AI bots reading you.
Go to your dashboardDone: the owner of this website sees it connected in haAplo.