🔍 What Is Causing the 404 Errors?
The OTTO pixel fires on every page where it is installed, including pages marked with a noindex directive. When OTTO attempts to track or process a noindex page, it may send a request that returns a 404 (Not Found) response. This happens because noindex pages are often intentionally excluded from public-facing content — they may lack canonical URLs, be behind access controls, or simply not resolve as expected by the pixel's endpoint.
The result is harmless to your live site, but it creates noise in your error logs and can make genuine issues harder to spot.
📋 Common Noindex Pages That Trigger This Issue
- Thank-you and confirmation pages
- Search results pages (e.g., /?s=query)
- Login, account, and checkout pages
- Tag and author archive pages set to noindex
- Staging or draft pages accidentally published
- Paginated pages beyond page 1 (e.g., /blog/page/2/)
⚙️ How to Exclude Noindex Pages from the OTTO Pixel
The recommended fix is to add a script exclusion rule so the OTTO pixel does not fire on noindex pages. The two approaches below cover the most common implementation methods. If you are unsure which method applies to your setup or cannot locate the relevant setting in Search Atlas, contact our support team for guided assistance.
🚀 Option 1 — Request a Script Exclusion via Search Atlas Support
If your OTTO pixel is managed through Search Atlas, script exclusions for noindex pages can be configured at the account or session level. Because the exact location of exclusion settings may vary depending on your plan and OTTO version, the most reliable path is to contact the support team and request that noindex page patterns be added to your pixel's exclusion rules. When you reach out, have the following ready:
- Your Search Atlas project name or domain
- The specific URL patterns or page types generating 404 errors (e.g., /?s=*, /page/2/, thank-you pages)
- A sample from your error logs showing the 404 responses
🛠️ Option 2 — Conditionally Load the Pixel in Your Theme or Tag Manager
If you manage the pixel code directly, wrap it in a condition that checks for the noindex meta tag before firing. This approach works for WordPress themes, custom CMS setups, and Google Tag Manager.
WordPress (functions.php or a custom plugin):
- Use the wp_head hook and check is_singular() combined with your noindex logic before outputting the pixel script tag.
- Exclude template types such as search pages (is_search()), 404 pages (is_404()), and any archive marked noindex.
Google Tag Manager:
- Create a new Trigger of type Page View.
- Add a trigger condition: fire only when the robots meta tag variable does not contain****noindex.
- Attach this trigger to the OTTO pixel tag so it fires only on indexable pages.
✅ How to Verify the Fix Is Working
After applying either option, monitor your error logs over the next 24–48 hours. The 404 entries tied to noindex pages should stop appearing. You can also use your browser's developer tools (Network tab) to confirm the pixel does not fire on a known noindex page.
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.