## **📌 When the pixel is only on local pages**

Franchise accounts often control only local landing pages, not the main brand website. If the Search Atlas pixel is installed on those pages, Search Atlas can detect it when the project URL matches a page where the pixel actually loads. Seeing the pixel in your browser inspect tool confirms the code is present. It does not always mean the connected project is checking that same URL.

## **✅ Confirm the pixel on the landing page**

Open the exact local landing page in a browser, not the brand homepage.

1. Right-click the page and choose **View page source** or use Inspect.
2. Search for the Search Atlas pixel or OTTO script.
3. Confirm the script is in the page HTML and is not blocked by a consent banner, tag manager rule, or error in the console.
4. Repeat this on every local URL you expect Search Atlas to use. A pixel on one landing page does not cover other franchise pages.

Use the full public URL, including **https**, the correct subdomain, and any path. A small difference such as www versus non-www, or a trailing slash, can point Search Atlas at a page that does not contain the pixel.

## **🔗 Align the project with that URL**

In Search Atlas, open the site or project connected to this franchise location.

1. Set the website URL to the local landing page where you confirmed the pixel, if you do not control the brand homepage.
2. Save the change, then run or wait for the next site check or crawl.
3. Give detection a short time to refresh. A newly added script may not appear immediately.
4. If you manage several locations, keep each location’s landing page tied to its own project or property so pixels are not mixed across franchises.

Search Atlas looks for the pixel on the URL connected to the project. If that URL is the corporate homepage and you only installed the pixel on a local page, the project will not see it.

## **🛠️ Fix common reasons detection fails**

- **Wrong page:** The pixel is on a campaign URL, but the project still points to the homepage.
- **Script not executed:** The tag exists in a tag manager but the trigger never fires on that landing page.
- **Blocked loading:** A consent tool, ad blocker, firewall, or content security policy stops the script.
- **Duplicate or old code:** An outdated snippet is present, or the page is served from cache.
- **Noindex or login wall:** The landing page is not publicly reachable, so the check cannot load it.

After correcting the URL or the installation, reload the landing page, confirm the script still appears, and recheck the project in Search Atlas.

## **💬 When to contact support**

Contact support if the pixel is visible on the exact public landing page, the project URL matches that page, and Search Atlas still does not detect it after a fresh check. Include the full landing page URL and the project name. 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.