Search Atlas Help Center

⚙️ Update OTTO Schema and Descriptions

Open in
View as Markdown Open in ChatGPT Open in Claude
Camilo Aponte

Camilo Aponte

Last updated on Oct 8, 2026

🔍 Overview

OTTO can update your website’s cloud schema and meta descriptions. After changes are created or published, the live site may continue showing older data temporarily because deployment, page caching, or content delivery networks can delay the update.

🚀 Start an OTTO update

  1. Open OTTO SEO from the left sidebar.
  2. Select the relevant project and review its current status.
  3. Use Create to generate or update recommendations for schema and meta descriptions.
  4. Use Scan when you need OTTO to recheck the current site content before making changes.
  5. Review the proposed updates and follow the available publishing or deployment prompts.

📊 Check deployment status

After publishing, allow the deployment to finish before checking the live site. A completed action in OTTO does not always mean that every cached version of the page has refreshed.

  • Confirm that the correct project and domain are selected.
  • Check whether the update is still processing, queued, or complete.
  • Verify that the intended URL is included in the project and is accessible to search engines.
  • Wait for deployment and caching to complete before comparing the page again.

🧪 Verify schema and meta descriptions

  1. Open the affected live URL in a private browser window.
  2. View the page source or inspect the rendered HTML.
  3. Search for the updated meta description and relevant JSON-LD properties, such as Product or hasProduct.
  4. Compare the live output with the latest version shown in OTTO.

Search results may not update immediately after the page source changes. Search engines can retain previously crawled descriptions until they recrawl the page.

🛠️ Troubleshoot stale live data

  • Deployment is incomplete: Wait until the update finishes, then verify the URL again.
  • Page or CDN cache is stale: Purge the relevant cache if your hosting or caching setup provides that option.
  • Multiple schema sources exist: Check whether your CMS, theme, plugins, or another SEO tool is adding older Product or hasProduct JSON-LD.
  • The wrong page was checked: Confirm the URL, canonical address, language version, and project domain.
  • Source and rendered HTML differ: Check the page after JavaScript loads, since some sites add metadata dynamically.
  • Search results still show old text: This can be normal until the page is crawled again; it does not necessarily mean the deployment failed.

✅ Best practices

  • Change one set of metadata at a time and record the affected URLs.
  • Keep only one trusted source for each schema property where possible.
  • Recheck both the page source and the rendered page after deployment.
  • Do not repeatedly republish while an earlier deployment is still processing.

💬 Get 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.