🗺️ Overview
Search Atlas currently offers a pre-configured native integration for Contentful. If your site runs on a different CMS — such as Flexo, a headless CMS, or a fully custom-built system — you can still connect it using the manual or API-based setup path described in this article. This article also explains the difference between OTTO Pixel status states, which is a common source of confusion after installation.
❓ Why Is Only Contentful Available in the Integration Menu?
Contentful is the only CMS with a one-click native connector in Search Atlas at this time. This is because native integrations require platform-level API agreements and validated data-mapping configurations that are built and tested by our engineering team before release.
Support for additional CMS platforms is on our roadmap. In the meantime, any CMS that allows you to inject custom scripts or access a public API can be connected using the manual setup steps below.
🛠️ How to Integrate a Custom CMS (e.g., Flexo)
Follow these steps to connect a non-Contentful CMS to Search Atlas:
- Install the OTTO Pixel script. Navigate to Left sidebar → OTTO SEO → All Sites (SEO Automation) (URL: /seo-automation-v3). Open the OTTO setup panel and copy your unique Pixel script tag.
- Paste the script into your CMS. In your CMS admin panel, locate the section that controls global HTML output — this is typically called Head Scripts, Custom Code, or Site Settings → Head. Paste the Pixel script before the closing
</head>tag so it loads on every page. - Publish or deploy the change. Save and publish your changes. If your CMS uses a build or deploy pipeline (common in headless setups), trigger a new build so the script appears in the live HTML output.
- Verify the script is live. Open your website in a browser, right-click anywhere on the page, and select View Page Source. Search for your Pixel script tag to confirm it is present in the rendered HTML.
- Return to OTTO and check the Pixel status. Go back to Left sidebar → OTTO SEO → All Sites (SEO Automation) and refresh the OTTO panel. Status should update within a few minutes of the script being detected on your live site.
If your CMS does not support direct script injection, contact your CMS provider or developer to request access to global head injection. Most modern CMS platforms, including headless and custom-built ones, support this capability.
📡 OTTO Pixel Status Definitions
After installing the Pixel, you may see one of the following status labels in the OTTO panel. Each means something different:
- Not Installed — The Pixel script has not been detected on your site. The script is either missing, not yet published, or placed in a location that prevents it from loading on all pages.
- Engaged — Search Atlas has made contact with your domain and the setup process has been initiated, but the Pixel script has not yet been confirmed as active on your live pages. This often appears immediately after you begin the OTTO setup, before the script is deployed.
- Installed — The Pixel script has been detected loading on your site. Search Atlas can now begin crawling and collecting data from your pages.
- Verified — The Pixel has been detected, confirmed across multiple page loads, and OTTO has successfully completed its initial site scan. This is the fully active state and means OTTO is running normally.
**Key point:**Engaged does not mean the Pixel is working. It only means the setup flow was started. You must reach Installed or Verified status for OTTO to function correctly.
🔍 How to Troubleshoot an 'Engaged but Not Installed' Status
If your OTTO status shows Not Installed and does not progress to Installed, work through the following checks:
- Confirm the script is in the live HTML. Use View Page Source (not browser DevTools Elements panel, which can show injected code) to check the raw HTML your server delivers. Search for your Pixel tag.
- Check that the script loads on all pages, not just one. The Pixel must be present site-wide. If it only appears on the homepage, OTTO cannot fully verify installation.
- Confirm the page is publicly accessible. OTTO cannot detect the Pixel on pages behind a login, staging password, or IP restriction. Test on your public-facing production URL.
- Clear your CMS cache and CDN cache. Many CMS platforms and CDNs aggressively cache page output. After adding the Pixel, purge all caches so the updated HTML is served to external requests.
- Wait up to 10 minutes and refresh the OTTO panel. Status checks do not happen in real time. Allow a short window after deployment before concluding there is a problem.
- Re-copy and re-paste the Pixel script. If you manually typed or edited the script tag, it may contain a typo. Return to the OTTO setup panel, copy the script fresh, and replace the existing one in your CMS.
💬 Still Need Help?
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.