🔍 What Deployed Means in OTTO
When OTTO shows an edit as deployed, Search Atlas has published that change to the OTTO installation connected to your site. Deployed does not always mean your browser, a content delivery network, or a page cache is already serving the newest version. Compare the live page with the exact URL listed in OTTO, including https, www, and any trailing slash.
⚠️ Why the Live Page Can Look Unchanged
Most cases come from a saved copy of the page, not from a failed deploy. Check these causes before you redeploy the same edit:
- Browser cache: your browser may still show an older copy of the page.
- Site or host cache: a caching plugin, server cache, or CDN can keep the previous HTML.
- Wrong page: the live URL may differ from the URL OTTO updated, such as a trailing slash, www, or a similar slug.
- Different field: OTTO may have changed a title, meta description, heading, or schema item that is not obvious in the page design.
- Script not loading: the OTTO script may be missing, blocked, or not included on that template.
- Static build: OTTO does not rewrite your site's saved HTML files. On a static site the edit appears only when the OTTO script loads in the browser, so you do not publish a new HTML build to make a deployed edit show. If the script is missing from that page, install it in the site template instead.
🛠️ Check the Live Page Step by Step
- In OTTO, find the deployed edit in its issue table and use the PAGE URL column. Click the path to open that live page, and compare it with the path shown, including www and any trailing slash.
- Note what changed, such as the title, meta description, heading, alt text, or internal link.
- Open that same URL in a private or incognito window.
- Use your browser view-source tool and search for the new text. Do not rely only on the visual design.
- If the new text is in the source but not on screen, clear the browser cache and check any on-page script or styling that hides it.
- If the new text is missing from the source, purge your site cache, host cache, and CDN, then recheck the source.
- Confirm the OTTO script is present in the page source on that URL. If it is missing, the install may not cover that template.
- After caches are cleared, reload the live page. If the source still shows the old content, return to OTTO and confirm the edit still says Deployed. Clicking Deployed undeploys it, so only click Deploy again if the edit has been undeployed.
🧹 Clear Cache Before You Retest
Wait a few minutes after a purge, then reload the exact URL in a private window. If your host or CDN has a separate purge for HTML and for images, purge HTML first. A hard refresh on one computer is not enough when a CDN still holds the old page for other visitors.
✅ Confirm the Right Change and URL
Match the live result to the field OTTO edited. A new meta description will appear in the page source and in search results later, but it may not change the visible layout. Also confirm you are checking the production domain, not a staging copy, and that no firewall, consent tool, or optimization app is blocking the OTTO script on that page only.
💬 When to Contact Support
Contact support if the exact URL matches, caches are purged, the OTTO script is present, and the new text is still missing from the page source. 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.