# **🔍 Overview**

When setting up OTTO, Search Atlas's AI-powered SEO automation tool, some websites are protected by **Cloudflare** — a popular security and content delivery network. This article explains whether access to a client's Cloudflare account is required and what steps may be needed to ensure OTTO can work properly on Cloudflare-protected sites.

# **⚙️ Is Cloudflare Access Required to Set Up OTTO?**

In most cases, **you do not need direct access to a client's Cloudflare account** to set up and activate OTTO. OTTO deploys optimizations directly through the connected website, so the standard setup process works independently of Cloudflare.

However, if a client's Cloudflare security settings are configured to block or challenge automated requests, OTTO's ability to crawl, deploy changes, or verify implementations may be affected. In these situations, a Cloudflare whitelisting step becomes necessary.

# **🚦 When Whitelisting Is Needed**

You may need to whitelist Search Atlas in Cloudflare if you notice any of the following:

- OTTO fails to crawl or index the site during setup
- Deployments are not applying correctly to the live website
- The site returns security challenge pages (e.g., CAPTCHA or "Checking your browser") when OTTO attempts to access it
- Cloudflare's **Bot Fight Mode** or **Super Bot Fight Mode** is enabled on the client's account
- Custom **WAF (Web Application Firewall)** rules are blocking automated traffic

# **✅ How to Whitelist Search Atlas in Cloudflare**

To allow OTTO to function without interference, ask your client (or log in if you have access) to complete the following steps in their Cloudflare dashboard:

1. Log in to the **Cloudflare dashboard** and select the relevant domain.
2. Navigate to **Security → WAF → Tools**.
3. Under **IP Access Rules**, add Search Atlas IP addresses with the action set to **Allow**. Contact our support team via the chat widget for the current list of IP addresses to whitelist.
4. If **Bot Fight Mode** is enabled, go to **Security → Bots** and consider temporarily disabling it during the initial OTTO setup, or create a bypass rule for Search Atlas traffic.
5. Save all changes and re-attempt the OTTO setup or crawl.

# **📋 Best Practices When Working With Client Sites**

- **Ask about Cloudflare upfront:** During onboarding, confirm whether the client's site uses Cloudflare and whether any strict bot protection rules are in place.
- **Request limited access if needed:** You do not need full admin access — read access to security settings and the ability to add IP allowlist rules is sufficient.
- **Document the changes:** Keep a record of any whitelisting rules added so they can be reviewed or removed if the client's security requirements change.
- **Re-enable security rules after setup:** If Bot Fight Mode was disabled temporarily, remind the client to re-enable it once OTTO is fully configured and verified.

# **🚀 Accessing OTTO in Search Atlas**

To get started with OTTO, navigate to **OTTO SEO** in the left sidebar of your Search Atlas dashboard, then open **SEO Automation** inside it, or go directly to **/seo-automation-v3**. From there you can connect a website, run the initial site audit, and begin deploying OTTO optimizations.

# **💡 Summary**

Cloudflare access is **not always required** to set up OTTO, but it becomes necessary when a client's security configuration actively blocks automated traffic. Whitelisting Search Atlas IPs and adjusting bot protection rules are the most common solutions. When in doubt, check Cloudflare settings early in the onboarding process to avoid delays.

If you need further assistance, open the chat widget in the bottom-right corner of the platform and type **human teammate** to be connected with a member of our team.