## **⚠️ When to roll back deployments**

Roll back Search Atlas deployments when both tools are changing the same pages. Duplicate titles, meta descriptions, canonicals, or schema can remain until each deployed change is rolled back. Use the rollback controls in the affected OTTO SEO categories, then set the project to Disengaged so Search Atlas stops applying its changes. You can deploy the same changes again later. If the WordPress plugin writes changes into the CMS, also turn off the relevant sync settings. Turning sync off does not revert changes already written.

## **📋 Before you remove anything**

Take a few minutes to record the current setup so reinstating is straightforward.

- Note which site or project is affected and which pages were deployed.
- Confirm Yoast is the plugin you want to keep live during the pause.
- List caches you use, including your host, CDN, and any caching plugin.
- Avoid editing Yoast and deploying new Search Atlas changes at the same time.

**Nothing new should be published** until the rollback is finished and you have checked the live pages.

## **🛠️ Roll back live deployments**

1. Open the affected project in Search Atlas and go to **OTTO SEO**.
2. Set the project from Engaged to Disengaged before rolling changes back. This stops OTTO from applying further changes, but changes already deployed remain until you roll them back.
3. Roll back the live changes in OTTO SEO. Use Roll back all for a category, or select Deployed on an individual live change to roll that change back. Repeat this for every category that still has live changes.
4. On WordPress, deactivate the Search Atlas plugin if the installation is still connected. Deactivating or removing that installation stops OTTO from writing tags on the page.
5. Leave Yoast active. Do not deactivate Yoast as part of this rollback.
6. Clear your site cache, CDN cache, and any SEO or page-cache plugin cache.

Pausing alone is not enough. Changes that were already deployed stay on the site until they are removed and caches are cleared.

## **✅ Confirm nothing stays live**

Check a few important URLs after the cache clear, including the homepage and one or two inner pages.

- View the page source and confirm titles, meta descriptions, and canonicals come from Yoast only.
- Confirm you do not see a second set of SEO tags or schema from Search Atlas.
- Recheck in a private browser window so an old cached copy does not mislead you.
- If duplicates remain, clear caches again and confirm the Search Atlas installation is still deactivated.

Keep deployments paused until Yoast is the only plugin controlling those fields and the live source looks clean.

## **🚀 Reinstate deployments afterward**

Reinstate only after the Yoast conflict is fixed. Decide which tool owns titles, descriptions, canonicals, and schema, and turn off the overlapping Yoast output before Search Atlas publishes again.

1. Resolve the Yoast settings so it no longer outputs the same fields you want Search Atlas to deploy.
2. In Search Atlas, reconnect the site or reactivate the WordPress plugin if you deactivated it.
3. Return to **OTTO SEO** and turn deployments back on for that project.
4. Review the queued changes, then redeploy them. Reinstating does not happen by itself if the earlier rollout was fully removed.
5. Clear caches again and recheck the same URLs. You should see one clean set of SEO output, not two.

**Do not leave both tools publishing the same fields.** If duplicates return, pause deployments immediately and repeat the rollback until the overlap is fixed.

## **💬 If you need further assistance**

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.