🛠️ Fix OTTO Changes Not Showing on GoHighLevel

🔍 What This Issue Looks Like

You deploy a change in OTTO and the platform shows it as Deployed. But when you open your GoHighLevel website, or inspect the page, the change is not there. This is usually a setup, publishing, or caching issue, not a failed deployment. The steps below walk you through the most common causes.

💡 Why This Happens

OTTO applies changes to your site through its installed script. A deployed status means OTTO has the change ready on the Search Atlas side. The change only appears on your site if the page loads the OTTO script and the page is not serving an old, saved copy. On GoHighLevel, the most common reasons are:

• The OTTO script is missing from the page. GoHighLevel sites, funnels, and individual pages can each have their own tracking code settings.
• The GoHighLevel page was not re-published after the script was added.
• Caching. Your browser, GoHighLevel, or a CDN may be showing an older version of the page.
• Domain mismatch. The domain connected in OTTO may differ from the live domain, for example www vs non-www, or a GoHighLevel preview URL vs the custom domain.
• You are checking the wrong view. Some changes are applied after the page loads, so they may not appear in View Page Source.
• The URL is not covered. The change may be deployed to a different page than the one you are checking.

✅ Step 1: Confirm the Deployment in OTTO

1. Open your project in OTTO.
2. Find the change you deployed and confirm its status is Deployed.
3. Check the exact page URL the change applies to.
4. Make sure the URL matches the live page you are testing, including https, www, and any trailing slash.

🧩 Step 2: Check That the OTTO Script Is Installed

1. Open the live page in your browser.
2. Right-click and choose View Page Source.
3. Search for the OTTO script from your project's installation instructions.
4. If you cannot find it, the script is not loading on that page.

If the script is missing, add it again in GoHighLevel using the tracking code or header code area for the correct level. This might be site-wide settings, funnel settings, or the individual page settings. Add the same script exactly as shown in your OTTO installation instructions, and do not edit it.

🚀 Step 3: Re-Publish the GoHighLevel Page

GoHighLevel often needs a fresh publish before code changes go live.

1. Save the settings where you added the script.
2. Open the page in the GoHighLevel builder.
3. Click Save, then Publish.
4. Wait a few minutes and reload the live page.

If you manage several pages or funnels, check that each one has the script and has been re-published.

🧹 Step 4: Clear Caches and Re-Test

1. Open the page in a private or incognito window.
2. If the change is still missing, do a hard refresh. Use Ctrl + Shift + R on Windows or Cmd + Shift + R on Mac.
3. If you use a CDN or caching service in front of GoHighLevel, clear its cache for the affected page.
4. Test on a different device or network to rule out local caching.

🔎 Step 5: Inspect the Page the Right Way

Some OTTO changes, such as titles, meta descriptions, headings, or schema, may be applied after the page loads. This means they can look different depending on how you check.

• View Page Source shows the original code the server sends. It may not show changes applied afterward.
• Inspect (Developer Tools, Elements tab) shows the page as the browser finally displays it. Use this view to check for OTTO changes.

To check, right-click the page, choose Inspect, and search the Elements tab for the text or tag you changed. Then compare it with the change shown in OTTO.

🌐 Step 6: Verify the Domain and URL

• Make sure the domain in your OTTO project is the same one visitors use to view the site.
• Test the custom domain, not a GoHighLevel preview or staging link, unless the script is installed there too.
• Check that the page URL has not changed since the change was created, for example after a slug edit or redirect.

📋 Quick Checklist

• The change shows as Deployed in OTTO.
• The OTTO script appears in the live page source.
• The GoHighLevel page was saved and re-published after the script was added.
• You tested in an incognito window after clearing the cache.
• You used Inspect, not only View Page Source.
• The domain and page URL match your OTTO project.

🛟 When to Contact Support

If you have worked through the steps above and the change still does not appear, gather these details to speed things up:

• The page URL where the change should appear
• The change you deployed in OTTO and when you deployed it
• Whether the OTTO script appears in the page source
• Whether the page uses a GoHighLevel site, funnel, or custom domain
• A screenshot of the OTTO deployment status and the inspected page

If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.