Built for a locked-down web
WAFs, CDNs and bot protection are now standard. We don’t try to sneak around them: your HEA works through your security layer, not against it.
The modern web is locked down, and that’s a good thing. HEA-World is built for that reality. A small, controlled whitelisting step gives your agent the safe key it needs to self-build, stay up to date, and answer from your own content.
WAFs, CDNs and bot protection are now standard. We don’t try to sneak around them: your HEA works through your security layer, not against it.
Whitelisting allows your agent to safely read your public pages, build itself from your site and stay in sync as you update your content — instead of endless copy-paste.
Our crawler is:
You decide which domains and paths are in scope, when to refresh, and when to pause or revoke. Your content powers your assistant — not someone else’s.
Cloudflare, SiteGround, WordFence, Sucuri, CDNs… we integrate cleanly with the tools your webmaster already uses. We’re the “good bot” your security team can approve in minutes.
Without controlled access, generic models will improvise answers for your brand. Whitelisting ensures your first-party AI actually knows your content and speaks with your voice.
Below is a step-by-step guide you can share with your webmaster, agency or hosting support.
It explains how to allow the HEA-Crawler/1.0 user agent on common platforms
(Cloudflare, SiteGround, Sucuri, WordFence and others).
After whitelisting, go back to your HEA backoffice and click “Refresh website content” to confirm that resources are discovered correctly.