π Why the project still says it cannot see OTTO
A beacon response of 204 only means the pixel request reached Search Atlas and the server had nothing further to return. It does not, by itself, mark the project installed or active. The project stays on We can't see OTTO while pixel_tag_state is not_installed, is_active is false, and processing_status is PENDING. Those fields update only after verification matches the live site to that exact project.
Customers cannot flip these statuses manually. Verification has to observe the pixel on the public site that belongs to the project.
π Where to Find It
UI path: Left sidebar β OTTO SEO β Installation Guide
β Check that the pixel is on the correct live site
- Open the OTTO project and confirm the domain matches the public site exactly, including https and whether the site uses www.
- Open the homepage and one inner page in a private window with extensions disabled.
- View the page source and confirm the OTTO pixel snippet from this project is present. A snippet from another project, a staging site, or an old container will not activate this project.
- In the browser network log, reload the page and confirm the pixel script loads and the beacon request completes. A 204 is a good sign, but note the final page URL that sent it.
- If the tag is injected by a tag manager, publish the latest container version and confirm the trigger runs on a normal page view for the production hostname.
π οΈ Remove blockers that keep verification pending
- Cache or CDN: purge cached HTML so visitors and our checker receive the page that includes the pixel.
- Consent banner: if the tag waits for consent, accept cookies in a test session. Verification cannot see a tag that never runs.
- Blockers: ad blockers, privacy tools, and some security plugins can stop the script in your browser even when the snippet is in the HTML.
- Wrong environment: a pixel that loads only on localhost, a password-protected page, or a preview URL will not verify the production project.
- Redirects: if the project domain redirects to another host, install and test the pixel on the final public host and make sure the project uses that host.
After fixing the site, load the public homepage once in a normal browser, wait a few minutes, then refresh the OTTO project. Repeat on one inner page so the signal is not limited to a single URL.
π Reinstall the pixel before escalating
- In the OTTO project, copy the current pixel snippet again. Do not reuse an older copy from notes or a previous site.
- Replace the existing snippet in the site template or tag manager, then publish.
- Clear the site cache and confirm the new snippet is visible in the public page source.
- Reload the site and confirm the beacon still returns 204 from the production domain.
- Return to the project and refresh the status. Allow time for processing_status to leave PENDING.
If the page is correct but the project still shows not_installed and is_active false, the project needs a fresh verification from our side. Do not keep creating duplicate projects for the same domain.
π¬ Ask for a manual verification check
Contact support when the public site clearly contains this project's pixel, the beacon returns 204 on the production domain, and the status remains unchanged after a fresh install and cache clear. Include the project domain, the page URL you tested, and a short note that pixel_tag_state is not_installed, is_active is false, and processing_status is PENDING.
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.