🔍 What this article covers
After OTTO deploys schema and internal links, you can confirm the change on the live site and in the project. This guide explains how to check a deployment (for example on your own domain), why markup may not show in raw source, and what happens to deployed content when a project is unbound.
⚙️ Check status inside the project
Open the site project in Search Atlas and go to OTTO. Review the deployment or changes list for the page you updated.
- A Deployed or equivalent completed status means OTTO finished sending that change.
- Pending, failed, or paused items are not live yet. Open the item for the error or wait until the status completes.
- Confirm the target URL matches the page you are checking, including https, www, and trailing slash.
- Confirm the OTTO installation (pixel or supported integration) is still connected for that domain.
📄 Confirm schema on the live page
OTTO often adds schema through its installed script, so it appears in the rendered page, not always in the server’s raw HTML.
- Open the exact deployed URL in a private window so cached pages do not mislead you.
- View the rendered page (browser developer tools, Elements panel) and search for application/ld+json or the schema type OTTO added.
- If you only use View Source, the block may be missing even when deployment succeeded. Check the rendered DOM before treating it as a failure.
- Hard-refresh the page. If a CDN or cache plugin is active, purge that URL and check again.
- Optional: test the same URL in Google’s Rich Results Test. Processing can lag behind a successful deploy.
Schema that is missing from both the rendered page and a completed OTTO status usually means the install is absent, blocked, or the change targeted a different URL.
🔗 Find the deployed internal link
Internal links are placed in the page body or in an OTTO-managed block, depending on the recommendation.
- On the live URL, use the browser Find tool for the anchor text or destination path OTTO listed.
- Search the rendered HTML, not only the CMS editor. Links injected by the script will not appear as a saved CMS edit.
- Check the same URL variant you deployed. A www and non-www page are different targets.
- Give caches a few minutes, then recheck. A failed or rolled-back item will not show the link.
🧹 If schema or the link is still missing
- Recheck that OTTO shows the item as deployed for that exact URL.
- Confirm the OTTO script loads on the page and is not blocked by consent tools, ad blockers, or a firewall.
- Purge CDN, server, and plugin caches for the URL.
- Compare the public page with the page OTTO edited. Drafts and noindex duplicates will not match.
- Redeploy the item from OTTO if status is failed or the install was fixed after the first attempt.
📦 Unbinding a project
Unbinding or disconnecting the project stops OTTO from serving its injected changes. Schema and internal links that exist only through the OTTO installation are removed from the live page. That is expected, not a partial rollback of your CMS history.
- Content OTTO injected via the script disappears after the project is unbound and the script no longer runs.
- Copy you manually saved in the CMS stays unless you delete it yourself.
- Rebinding and redeploying is required to publish those OTTO changes again.
- Search engines may keep an old cached copy until they recrawl the URL.
💬 Need more help
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.