## **🔍 What Is Happening?**

Some websites use a Web Application Firewall (WAF) or bot protection service to filter out automated traffic. When OTTO crawls your site or sends requests to your WordPress API, the firewall may mistake those requests for a bot attack. Instead of the real page or data, it returns a verification challenge, usually with an **HTTP 202** status code.

OTTO cannot complete a challenge meant for a human visitor, so the request does not succeed. The result is that OTTO cannot read your pages or apply optimizations to your WordPress site.

## **⚠️ Common Signs**

- OTTO shows errors or stalls when connecting to your WordPress site.
- Your firewall or security logs show challenged or blocked requests to your site, often to the **/wp-json/** path.
- Requests return an HTTP 202 status with a short page asking to verify you are human, instead of your normal content.
- Changes that OTTO should apply do not appear on your live site.
- The issue started after you enabled or tightened a security plugin, CDN rule, or hosting-level firewall.

## **🧠 Why It Happens**

Bot protection tools look at things like request frequency, missing browser behavior, and the source of the traffic. OTTO is an automated service, so it can look like a bot. This is a security setting on your side, not a fault in OTTO or in WordPress.

WordPress API requests are often protected even more strictly, because attackers commonly target them. That is why you may see challenges on API calls even when regular page visits work fine.

## **🧰 Before You Start**

- Find out which security layers protect your site. This could be a CDN or firewall service, a WordPress security plugin, or a firewall provided by your host.
- Make sure you have admin access to those tools, or ask your developer or hosting provider to help.
- Have a recent request from OTTO in your logs if possible. It helps you create a precise rule.

## **✅ How to Fix It**

1. **Check your firewall logs.** Look for challenged, blocked, or flagged requests that match the time OTTO tried to connect. Note the rule that triggered, the request path, and the source IP address or user agent.
2. Create an allow rule for OTTO. In your WAF or bot protection settings, add an exception (often called an allowlist, bypass, or skip rule) so that OTTO requests are not challenged. Do not rely on IP addresses, because OTTO traffic comes from changing addresses. Base the rule on the user agent you see in your logs (the OTTO crawler identifies as "SearchAtlas Bot"; WordPress API calls identify as "content-assistant"). You can also ask Search Atlas support to enable the X-SearchAtlas-Token header for your site and allow requests that carry it.
3. **Limit the exception to what is needed.** Where possible, apply the rule only to the WordPress API path (**/wp-json/**) and to normal page requests rather than your entire site.
4. **Skip bot challenges for that rule.** Make sure the rule bypasses the bot challenge, rate limiting, and managed rule checks that triggered the HTTP 202 response, not just one of them.
5. **Check every security layer.** If you use more than one (for example a CDN and a WordPress security plugin), add the exception in each. One layer can still block the request even if another allows it.
6. **Clear any cache or block lists.** If OTTO was already flagged, remove it from temporary block lists and purge firewall caches so the new rule takes effect.
7. **Test the connection again.** Retry the action in OTTO and confirm in your logs that the requests now return a normal response instead of a challenge.

## **🔐 Tips for Common Setups**

- **CDN or cloud firewall:** Look for custom rules, security rules, or IP access rules. Create a rule that allows or skips bot checks for OTTO traffic.
- **WordPress security plugin:** Check the firewall, rate limiting, and blocked requests sections. Add OTTO to the allowlist and review any settings that restrict the REST API.
- **Hosting-level firewall:** Some hosts apply protection you cannot edit yourself. Ask your hosting provider to allow OTTO requests and explain that they are being challenged with an HTTP 202 response.

## **🚫 What to Avoid**

- **Do not turn off your firewall completely.** This leaves your site exposed. A targeted allow rule is safer and works just as well.
- **Do not allow broad traffic ranges** that you cannot identify. Only allow what you have confirmed in your logs.
- **Do not disable the WordPress REST API** unless you are sure nothing else needs it, because OTTO relies on it.

## **🛠️ Still Seeing the Challenge?**

- Confirm the allow rule is active and placed above the rules that trigger the challenge, since many firewalls apply rules in order.
- Check that the rule matches the exact IP address, user agent, or path shown in your latest logs. These details can change.
- Look for a second layer of protection you may have missed, such as a plugin, a host firewall, or a server-level rule.
- Wait a few minutes after saving changes, then try again, as some services take time to apply updates.

## **💬 Need More Help?**

If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

To help us resolve it faster, include your website URL, the security service or plugin you use, and the time of a recent failed request. A screenshot of the matching firewall log entry is also very useful.