Search Atlas Help Center
Troubleshooting

πŸ› οΈ Fixing Failed OTTO Schema Deployments

Camilo Aponte

Camilo Aponte

Last updated on Nov 19, 2026

πŸ” Overview

Sometimes a schema shows as deployed in OTTO, but you cannot find it on the live page. This can affect page-level schemas, including FOUND schemas. This article explains what to check and when to contact support.

🧩 Replacement vs. Insertion

OTTO can add schema to a page in two ways:

  • Insertion: OTTO adds a new schema block to the page. It does not depend on anything already being there.
  • Replacement: For a FOUND schema, OTTO prepares a replacement using the originally detected markup and the updated schema. A deployed status does not by itself confirm that the replacement appeared on the live page.

OTTO prepares FOUND schema replacements using the original detected markup. A replacement may not appear if the installation cannot apply it or if the page markup no longer corresponds to what OTTO detected. Check the live page and contact support if it remains missing.

❓ Why a Replacement May Not Appear

  • The original ImageObject may have changed or may be generated dynamically by a theme, plugin, page builder, or script. Compare the current page markup with the schema OTTO detected and share any differences with support.
  • The page was cached. Your site, CDN, or caching plugin may still be serving an older version of the page.
  • If the page was updated after OTTO detected its schema, the image or markup shown in OTTO may no longer match the live page. Compare the current markup with the FOUND schema and contact support if the deployment is missing.
  • A page may contain more than one ImageObject. Review the schema markup on the live page and compare it with the FOUND schema in OTTO. If you cannot identify the intended schema or the deployed change is missing, contact support.
  • Check that the OTTO installation or connected deployment method is working on the affected page. If it is missing or blocked, changes delivered through it may not appear.

βœ… Step-by-Step: Check Your Deployment

  1. Open the page in a private or incognito browser window so you see the version visitors see.
  2. Right-click the page, choose View Page Source, and search for application/ld+json. Look for the ImageObject and check whether it matches the schema shown in OTTO.
  3. Clear any caches: your site cache, caching plugin, and CDN. Then reload the page and check again.
  4. Test the URL with a schema validation tool, such as Google's Rich Results Test or the Schema Markup Validator. This shows the schema a search engine would read.
  5. Confirm in OTTO that the deployment status for that page and schema is marked as deployed, and that OTTO is active on the site.
  6. If the schema is still missing, check the affected schema and its deployment status in OTTO. If appropriate, redeploy that schema, allow time for processing, and check the live page again. Contact support if it remains missing.

πŸ”„ Can the Schema Be Applied as an Insertion Instead?

If a replacement does not appear, contact support to review the affected schema and deployment method. Support can investigate the replacement and advise whether adding a separate schema is appropriate, including whether it could duplicate existing markup. **Code references:** Page-level insertion and replacement preparation: content-assistant/app/ca/models/otto\_url.py:746–805, 998–1004, 1064–1073. The browser pixel skips unsupported header replacement types, including scripts: customer-frontend/public/scripts/dynamic\_optimization.js:1583–1597; it processes header replacements at lines 1979–1986. This is evidence about that code path, not proof of the behavior of every installation.

Keep in mind that adding a new ImageObject while the original still exists can create duplicates. Duplicate schema is not always harmful, but it is cleaner to have one accurate version per image. Check the page source after any change.

πŸ›‘οΈ Tips to Prevent Failed Deployments

  • Deploy schema after you finish editing the page, not before.
  • Clear your caches after every deployment and after major page changes.
  • Avoid having multiple plugins output ImageObject schema on the same page.
  • Recheck important pages after theme or plugin updates.
  • Validate key pages periodically, especially those with many images.

πŸ’¬ What to Include When Contacting Support

Sharing these details helps us resolve the issue faster:

  • The full URL of the affected page
  • The schema type (for example, ImageObject) and whether it was deployed as a replacement
  • The approximate date and time of the deployment
  • A screenshot of the deployment in OTTO
  • A screenshot or copy of the page source section where you expected the schema
  • Whether you cleared caches and retested in a private window

πŸ™‹ Need More Help?

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.

Was this article helpful?