π What this article covers
If you manage a franchise and only control local landing pages, Search Atlas can only detect the OTTO Pixel on pages where the pixel script actually loads. This article explains how to check those pages, fix the most common gaps, and confirm detection.
π Before you start
You need the public URL of each local landing page and permission to view or edit that pageβs header, tag manager, or theme. If a corporate or agency team owns the site template, you may only be able to request the change rather than install it yourself.
- Open the local page in a normal browser window, not only inside a page builder preview.
- Use the live URL customers see, including the correct domain and path.
- Disable aggressive ad blockers for this test, because they can hide the pixel from your browser.
π οΈ Check that the pixel is on the page
- Open the local landing page.
- View the page source or use your browserβs developer tools and search for the OTTO Pixel script provided in Search Atlas.
- Confirm the script is in the page head or loads through a tag that fires on that exact URL.
- Reload the page once and check the Network tab for a request from the pixel. A blocked or failed request means the page is not sending data.
- Repeat the check on at least one other local page. A script on the homepage does not cover franchise pages unless those pages use the same template.
If you cannot find the script, the pixel is not installed on that landing page. Search Atlas cannot detect a pixel that never loads.
βοΈ Why detection often fails on franchise pages
- Template gap: The main site has the pixel, but local landing pages use a different header or builder.
- Tag rules: A tag manager fires only on the corporate domain or homepage, not on local URLs.
- Wrong property: The script belongs to another Search Atlas project or an old install.
- Caching: A CDN or page cache is still serving an older version without the script.
- Consent or blockers: A cookie banner or security tool stops the script before it runs.
- Draft versus live: The pixel was added in a draft, but the published page was not updated.
β Confirm detection in Search Atlas
- Publish the page after the script is added.
- Clear the site cache if your platform or CDN caches HTML.
- Open the live local URL and load it fully.
- In Search Atlas, open the OTTO Pixel or installation status for the project tied to that site.
- Wait a short time, then refresh the status. Detection follows a real page view that successfully loads the pixel.
Check the exact URL you tested. A visit to a different city page, a staging link, or a URL with a typo will not verify the page you care about.
π‘ What to send your web team
If you cannot edit the template, ask the team that controls the franchise pages to add the OTTO Pixel script from your Search Atlas project to every local landing page template, then publish and clear cache. Ask them to confirm the tag fires on the live local URLs, not only the main website.
π¬ Still not detecting
If the script is visible on the live page, the page has been published, cache has been cleared, and Search Atlas still does not detect it, gather the live page URL and a short note that the script is present. 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.