⚠️ Why OTTO and Yoast can clash
OTTO and Yoast can both write the same on-page fields. When both tools manage titles, meta descriptions, canonical tags, Open Graph data, or schema, search engines may see duplicate or conflicting signals. You do not need to remove OTTO or undo every optimization. Turn off only the modules that overlap with Yoast and leave the rest active.
🧭 Decide what each tool should own
Before you change anything, choose one owner for each field. A simple split that avoids clashes is:
- Leave with Yoast: SEO titles, meta descriptions, canonical URLs, Open Graph and Twitter tags, and schema or structured data.
- Title Tags, Meta Descriptions, Headings Length, Heading Optimizations, Image Alt Texts, and Internal Linking Opportunities are all real OTTO issue categories under Onpage Optimizations and Link Optimization. Headings, alt text, and internal links do not write Yoast's title, meta description, schema, Open Graph, or canonical fields, so they can stay deployed. Title Tags and Meta Descriptions write the same title and description fields Yoast owns, so do not leave those deployed if Yoast should own them. There is no per-module on/off switch for any of these categories.
If Yoast already outputs a field, disable the matching OTTO module. Do not let both tools publish the same tag.
🛠️ Turn off conflicting OTTO modules
- Open your project in Search Atlas and go to OTTO SEO.
- Open the OTTO project, then use the issue categories in the sidebar. To stop a category from being deployed again, open Settings and use Deployment Rules, then Never deploy, and block that issue type. On a WordPress site using the MetaSync plugin, overlapping output is controlled separately in WP Admin under Search Atlas, Settings, General, Post/Page Editor Settings, not in the Search Atlas project settings.
- The categories that write the same output as Yoast are Title Tags and Meta Descriptions under Onpage Optimizations, Schema Markup (Organization Schema, Domain-Level Schema, and Page-Level Schemas), Open Graph and Twitter Card under Miscellaneous, and Canonical Link under Link Optimization. Social metadata is not one module, and canonical is its own category.
- You cannot turn a category off. Either click the green Deployed pill on each fix so it returns to Deploy, or use Roll back all for that category. Both ask you to confirm. To stop new deploys, block the issue type under Settings, Deployment Rules, Never deploy. On WordPress with MetaSync, check the matching boxes in Post/Page Editor Settings: Disable SEO Meta Box only hides the editor box and does not stop title or description output; Disable Schema Markup Meta Box, Disable Social Media & Open Graph Meta Box, Disable Canonical Meta Box, Disable Common Robots Meta Box, and Disable Language Alternates Meta Box stop MetaSync emitting those tags and stop it suppressing Yoast. Saved values are kept. Leave headings, image alt text, internal links, missing keywords, and NLP fixes deployed if you still want them.
- Save your settings, then review a few important pages in WordPress to confirm Yoast is the only source for those fields.
Clicking Deployed, or Roll back all, undeploys those fixes and removes them from what visitors see. It does not delete the suggestions. Adding an issue type to Never deploy also rolls back that type's live fixes and then blocks new deploys. The WordPress Post/Page Editor Settings checkboxes stop MetaSync emitting and suppressing those tags immediately, but they do not delete saved values, and they do not undeploy the OTTO suggestions. After either change, purge the plugin, host, and CDN cache and recheck the page while logged out.
↩️ Roll back deployments that are already live
Roll back only the deployments that conflict with Yoast. You do not have to undo the whole OTTO installation.
- There is no history page. In the OTTO project, open the issue category in the sidebar, search for the page URL, and use the Deployed filter to see the fixes that are live.
- Each sidebar category is already one issue type. Open that category and filter the table to Deployed. There is no cross-site history to filter.
- In the category table, click the green Deployed pill on a fix to undeploy it, or select several rows and choose Roll back in the bulk bar. For the whole category, use Roll back all. The confirm dialog says Confirm Undeploy all and asks you to proceed. The pill returns to Deploy. This removes the live change. It does not delete the suggestion.
- Clear any site, CDN, or page cache, then view the page source.
- Check that each rolled-back field now comes from Yoast only, with one title, one meta description, one canonical, and one schema block.
If you do not want OTTO to put a change back, undeploy it first, then block that issue type under Settings, Deployment Rules, Never deploy. On WordPress, also check the matching Post/Page Editor Settings box so MetaSync stops emitting that output. Then clear the plugin, host, and CDN cache and recheck the page while logged out. Blocking the type rolls back fixes that are still live, so a missing rollback action is not the normal case.
✅ Keep pages optimized after the change
- Confirm Yoast still has the target title, meta description, and focus keyphrase on priority pages.
- Keep non-conflicting OTTO modules enabled so recommendations and safe optimizations continue.
- Do not install a second metadata plugin alongside Yoast.
- Recheck a sample of templates, not only one page, because theme or archive templates can still print old tags.
🔁 Turn the modules back on later
You can reinstate modules when you are ready for OTTO to own those fields again. Plan a clean handoff so both tools are not active at the same time.
- In Yoast, stop outputting the fields you want OTTO to manage, or disable the matching Yoast features.
- Return to OTTO SEO and switch the paused modules back on.
- Review the suggested changes, then deploy only the modules you restored.
- Clear cache and confirm the live page shows a single, correct value for each field.
Your earlier rollback does not delete the module. Turning it on again makes it available for a new deployment.
💬 Need a hand with a live clash
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.