## **📌 Overview**

Next.js sites can look unverified even when the OTTO Pixel or a Cloudflare worker is present. If you see ` `, that flag comes from the Cloudflare worker, not from the client-side snippet. It means the worker reached Search Atlas but got no page data back. This article explains the usual causes and how to fix them.

## **🧠 What enabled=false Means**

The OTTO Pixel and the Cloudflare worker both ask Search Atlas for optimizations for the current page. `enabled=false` is set by the worker when that request returns no page data. The usual case is that OTTO is installed but not engaged for the project. It can also mean the API failed or the result was cached. A project UUID that does not belong to the site is a different error, not `enabled=false`.

- A www versus non-www difference by itself does not disable OTTO. Search Atlas matches both forms of the same domain, and the installation scan retries the www address if the first fetch fails. The project must still be created for the same domain as the live site. A different domain, or a UUID from another project, is a real mismatch.
- OTTO does not apply changes until the project is engaged. Until you select Engage OTTO, the Cloudflare worker can report `enabled=false` even though the installation is present. Completing a scan is not what turns OTTO on.
- **Two install methods at once:** A Cloudflare worker and a client-side snippet are both active, and one of them uses the wrong project identifier.
- **Cached response:** Cloudflare or your hosting provider is serving an older copy of the page or script from before the project was configured.
- The OTTO Pixel must be in the shared site head so it loads on the homepage. The installation scan checks the live homepage first. A snippet that exists only on other pages, or that Next.js drops during client-side routing, is not detected.

## **✅ Before You Start**

- Confirm the exact address your visitors use, including whether it starts with www.
- Make sure you have access to your Next.js code and deployment process.
- If you use Cloudflare, make sure you can purge the cache.
- Open the OTTO installation guide for your project and copy the OTTO Pixel script from the Code Snippet steps under Manual Installation. Paste it unchanged so the `data-uuid` is this project's UUID.

## **🛠️ Step-by-Step Fix**

1. In the OTTO project, confirm the domain is the live site's domain, including https. You do not need a separate project for the www and non-www versions. Search Atlas treats those as the same site. Do not point the project at a preview or local address.
2. **Choose one install method.** Use either the Cloudflare worker or the client-side snippet. If you want to use the snippet, disable or remove the OTTO worker route for that domain first so the two do not conflict.
3. Add the OTTO Pixel once to the shared head, not to an individual page. In the Next.js App Router, put it in the root `app/layout` head. In the Pages Router, put it in the shared `\_document` or `\_app` head. It must be present on the homepage and remain after client-side navigation.
4. Paste the OTTO Pixel script exactly as copied into the shared ` `. Do not change its id, `data-uuid`, or script URL, and do not minify it. Do not rely on a deferred or per-page script load. The tag should be in the initial page head.
5. **Deploy your changes.** Publish to your live site. Verification checks the live address, not your local or preview environment.
6. **Purge the cache.** If you use Cloudflare, purge the cache for the homepage and for the OTTO script. If your host has its own cache, clear that too.
7. **Confirm the snippet is live.** Open your homepage in a private browser window, view the page source or use the browser developer tools Network tab, and look for the OTTO script. Check that it loads without errors.
8. Return to the OTTO installation guide and click Scan. If OTTO was just engaged or the site was just deployed, wait about 3–5 minutes so the cached worker and page-data responses expire, then scan again. Scan checks the published site.

## **🔎 How to Check the Result**

- Open the OTTO script request in the Network tab and look at the response.
- If it now shows **enabled=true**, verification should pass on the next check.
- If it still shows **enabled=false**, note the exact address that made the request and compare it with your project domain.

## **⚠️ Common Mistakes**

- Adding the snippet only to a single page instead of the shared layout.
- Testing on a preview or staging address that is not the project domain.
- Leaving a Cloudflare worker active while also adding the snippet.
- Forgetting to redeploy after editing the layout.
- Using a cached version of the page that does not include the new snippet.
- Redirects that send visitors to a different hostname than the one saved in the project.

## **💡 Tips for Next.js Sites**

- Server-rendered and static pages are both supported, as long as the script is included in the final HTML or loads in the browser.
- If your site uses a content security policy, allow the OTTO script source so the browser does not block it.
- Cookie or consent tools that delay scripts can also delay verification. Make sure the OTTO script is allowed to load before consent where possible.

## **💬 Still Not Verifying?**

If you have followed every step and the page still returns enabled=false, our support team can check the project settings on our side. To help us resolve it faster, include these details in your message:

- The exact project domain and the live address you are testing
- Which install method you are using (snippet, Cloudflare worker, or both)
- The time of your last deployment and cache purge
- A screenshot of the OTTO script response in the Network tab

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.