## **🔍 Confirm the change was deployed**

Open **OTTO SEO** from the left sidebar, then review the affected project, page, and recommendation. Confirm the edit shows as deployed, not drafted, pending, or awaiting approval.

If you changed schema or another item after the original deployment, deploy the updated change again. Editing a previously deployed item does not always publish the new version automatically.

## **🔗 Check the connected delivery method**

OTTO delivers changes through the connection configured for your project, such as the OTTO WordPress plugin. Confirm the connection is active and installed on the same website and environment as the affected page.

For a Go High Level website, verify that the connected delivery setup is attached to the correct domain and that the page is published in Go High Level. Also confirm the page was not replaced, duplicated, or moved to another funnel or subdomain after the OTTO edit was deployed.

## **⚙️ Verify project engagement**

Make sure the project is engaged and that OTTO is enabled for the affected site. If the project or delivery connection was recently paused, reconnected, or changed, deploy the edit again after confirming the current configuration.

## **🧹 Clear caching and conflicting changes**

Caching can make an older version of a page appear live. Clear or bypass caches in Go High Level, your CDN, hosting layer, browser, and any SEO or optimization tools. Then open the page in a private browser window.

Check for other tools or custom code that may overwrite title tags, meta descriptions, schema, or page content after OTTO applies its changes. Temporarily disable conflicting automation only if it is safe for your site, then test the page again.

## **🧪 Verify the live page directly**

Do not rely only on the status shown in the OTTO dashboard. Open the affected URL on the public site and inspect its live HTML source. Search for the expected title, meta description, schema, or other deployed content.

Compare the live HTML with the intended OTTO edit. If the expected code is present but the dashboard reports that it is not live, the status may be inaccurate. If it is absent, continue checking the delivery connection, page URL, and caching layers.

## **📄 Check the exact URL and page version**

- Confirm the deployed URL matches the live canonical URL, including protocol, subdomain, path, and trailing slash.
- Make sure redirects are not sending visitors to a different page.
- Check that the page is published and accessible without a login or preview link.
- Confirm the live page is not using a different template or location than the page selected in OTTO.

## **✅ When to contact support**

Capture the affected URL, the OTTO edit, deployment time, delivery method, and a copy of the live HTML showing the missing change. This information helps the team determine whether the issue is caused by delivery, caching, a conflicting tool, or an incorrect live-status report.

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.