πŸ”„ Roll Back OTTO Deployments Safely

Camilo Aponte

Camilo Aponte

Last updated on Nov 5, 2026

⚠️ Why OTTO and Yoast can conflict

OTTO can update titles, meta descriptions, canonical tags, and schema, which may overlap with Yoast’s output. Disengaging OTTO temporarily stops its script-delivered changes from appearing while preserving saved fixes. Roll back approved fixes if you also want their deployment approvals withdrawn. Changes already written directly into your CMS need separate rollback verification. Check both the page source and rendered page before relying on Yoast alone.

πŸ›‘ Pause OTTO so nothing new goes live

  1. Open the website project in Search Atlas and go to OTTO.
  2. Turn off automatic deployment for the relevant fix types in OTTO settings. To stop script-delivered fixes from appearing on this site, turn off the Engaged switch and confirm Disengage OTTO. Disengaging also pauses new CMS syncing, but does not remove changes already written into the CMS.
  3. Confirm that the site’s OTTO switch shows Disengaged. Installation status is separate: the installation can still show Installed while OTTO is disengaged.
  4. Do not approve or deploy any pending recommendations while you are rolling back.

Pausing stops future publishes. It does not always remove changes that are already on the site. Complete the removal steps below as well.

🧹 Remove deployments that are already live

  1. In OTTO, open the list of deployed changes for the project.
  2. Select the deployed fixes you want to withdraw in each relevant issue category. For a full rollback, cover every category containing deployed fixes; do not assume selecting all rows in one view includes the entire project.
  3. Use the rollback control for the selected fixes, or Roll back all for the current category, and confirm when prompted. Wait for completion, verify that the fixes are no longer marked deployed, and check the live page. If CMS syncing is enabled, verify its rollback outcome separately.
  4. OTTO can run through the WordPress plugin or an installed site script. Disabling that delivery mechanism stops script-delivered fixes from being applied on subsequent page loads, but does not necessarily undo CMS-written changes. If changes were saved into the CMS, keep the required connection available until rollback is verified, then deactivate the installation if desired.
  5. Clear any cache in WordPress, your host, and your CDN, then hard-refresh a few key pages.
  6. View the page source and confirm OTTO titles, descriptions, canonicals, and schema are gone. Yoast should be the only SEO output left.

If OTTO-related tags remain after rollback, verify the specific fixes and categories rolled back, clear applicable page and CDN caches, and inspect both page source and rendered HTML. Check whether the remaining output comes from Yoast, another plugin, or changes previously written into the CMS. A connected OTTO installation alone does not mean rolled-back fixes should remain active.

πŸ” Reinstate deployments later

  1. Decide which tool owns each SEO field. Use either OTTO or Yoast for titles, descriptions, canonicals, and schema. Do not let both write the same field.
  2. In Yoast, turn off the outputs you want OTTO to manage, or leave OTTO paused if Yoast will remain the only source.
  3. Reconnect the OTTO installation if you deactivated the plugin or script.
  4. Before re-engaging OTTO, review the saved fixes and roll back any approvals you do not want restored. Restore the installation if necessary, turn Engaged back on, and deploy only the additional recommendations you want.
  5. Clear cache and check the live source again so only one set of tags is present.

Saved recommendations remain available without rebuilding the project. Fixes explicitly rolled back must be deployed again to restore their approval. Fixes only hidden by disengaging OTTO retain their approvals and can return when you re-engage, without another individual approval. **Code references:** - Engagement labels and restoration behavior: customer-frontend/src/modules/otto/shared/connection-status/ConnectionStatusCard.tsx:200–223. - Disengagement and CMS persistence warning: customer-frontend/src/shared/otto-widgets/disengage-confirm-modal.tsx:47–49. - Category-scoped rollback: customer-frontend/src/modules/otto/v3/overview/body/topBar/components/DeployControls.tsx:64–78. - Deployed/not-deployed filtering: customer-frontend/src/modules/otto/shared/features/issue-renderers/page-title/utils/customHooks/index.tsx:335–337. - Canonical fix support: content-assistant/app/ca/models/otto\_url.py:232–234,1139–1141.

βœ… Prevent the same conflict

  • Keep one owner for each SEO element: OTTO or Yoast, not both.
  • Pause OTTO before changing Yoast settings or switching SEO plugins.
  • After every deploy or rollback, check the live HTML, not only the WordPress editor.
  • Clear site and CDN cache before you judge whether a change is live.
  • Roll back all deployments if you need a guaranteed clean state, then restore only reviewed items.

πŸ’¬ If rollback status is unclear

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?