# **🧭 Overview**

After pasting the OTTO Pixel into HubSpot, some users see a scan failure even though the code appears to be installed correctly. In most cases, the root cause is not the installation itself — it is a security layer on the hosting environment that blocks the Search Atlas crawler before it can verify the Pixel. This article walks you through a correct HubSpot installation and, critically, how to whitelist the Search Atlas crawler on servers and security tools that are **not** Cloudflare.

# **📋 Step 1: Install the OTTO Pixel in HubSpot**

1. In Search Atlas, go to **OTTO SEO → All Sites (SEO Automation)** using the left sidebar (URL: `/seo-automation-v3`).
2. Open your OTTO project and copy the full Pixel script snippet.
3. Log in to your HubSpot account and navigate to the **Settings** area, then look for the section where you can add custom tracking or header code to your site pages (the exact menu label may vary by HubSpot plan and version — consult HubSpot's current documentation if needed).
4. Paste the OTTO Pixel snippet into the header code field for your site, then save your changes.
5. Return to Search Atlas and trigger a new scan to confirm detection.

If the scan still fails after completing these steps, proceed to the crawler whitelisting section below.

# **🛡️ Step 2: Whitelist Search Atlas Crawlers (Non-Cloudflare Environments)**

If your client's site does not use Cloudflare, the crawler may be blocked by one of the following: a Web Application Firewall (WAF), a WordPress security plugin, a server-level firewall rule, or a CDN provider. Use the relevant section below to allow the Search Atlas crawler through.

# **🔎 Identify the Search Atlas Crawler Details**

Before whitelisting, you need the crawler's identifiers. Allow access for the following:

- **User-Agent string:**`SearchAtlasBot`
- **IP ranges:** To obtain the current crawler IP list, open the chat widget in the bottom-right corner of the platform and type **human teammate** — a member of our team will provide the up-to-date IP ranges, as they may be updated periodically.

# **⚙️ Whitelisting by Environment Type**

**WordPress Security Plugins (e.g., Wordfence, Sucuri, or similar WAF/security plugins)**

1. Open the plugin's settings dashboard in WordPress.
2. Locate the **Whitelisting**, **Allowlist**, or **Trusted Bots** section (the exact label varies by plugin).
3. Add `SearchAtlasBot` as a trusted User-Agent.
4. If the plugin allows IP-based rules, also add the Search Atlas crawler IPs obtained from the support team.
5. Save settings and re-run the OTTO scan.

**Server-Level Firewalls (Nginx, Apache, or similar)**

1. Access your server and open the relevant configuration file for your web server or firewall tool.
2. Add a rule to allow requests from the `SearchAtlasBot` User-Agent and from the Search Atlas crawler IP ranges.
3. Reload or restart the web server to apply the changes.
4. Re-run the OTTO scan in Search Atlas to confirm the crawler can now access the site.

If you are unsure which security layer is blocking the crawler, check your server or WAF access logs for blocked requests matching the `SearchAtlasBot` User-Agent — this will identify which tool needs to be configured.

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.