## **🔍 Understanding Blocked Meta Deployments**

OTTO SEO can automate title-tag and meta-description updates. If these fixes are marked as blocked, check the account-level and project-level Deployment Rules. A blocked issue type remains available for review but cannot be deployed. If an approved change is missing from the live site, investigate the installation, connection, and caching separately. [A]

## **⚙️ Common Causes of Deployment Blocks**

Before troubleshooting, distinguish between a fix blocked by Deployment Rules, a missing or disconnected installation, and an approved fix that is not appearing on the live page. These conditions require different checks.

- Third-Party SEO Plugins: Rank Math, Yoast SEO, and All in One SEO can generate titles and meta descriptions alongside OTTO. The Search Atlas WordPress plugin includes compatibility handling for overlapping SEO output, so another SEO plugin being active does not automatically mean deployment is blocked. Investigate an actual output conflict before changing plugin settings. [B]
- **Deployment Toggles Disabled:** The global deployment settings for meta tags inside OTTO may be turned off.
- Aggressive Caching: WordPress page caches, hosting caches, and CDN caches can serve an older version of a page after an OTTO change. This may make an approved fix appear missing. Check fresh page output after clearing the relevant caches; caching is separate from an issue type being blocked by Deployment Rules. [C]
- Installation or Connection Problems: If the OTTO code is missing, cannot run, or the site integration is disconnected, fixes may not reach the live site. Review the installation status and the installation guide or diagnostics available for your integration. Do not interpret a connection problem as a Deployment Rules block. [D]

## **🛠️ Step-by-Step Fixes for Blocked Deployments**

Follow these steps to restore your meta tag deployments and resolve the blocked state:

1. Check for Conflicting SEO Output: On WordPress, first confirm whether another plugin is actually interfering with OTTO’s titles or meta descriptions. Keep the Search Atlas plugin updated and inspect the resulting page output. Do not deactivate Yoast or Rank Math solely because it is installed. If a conflict is confirmed, adjust the relevant output using that plugin’s supported controls or ask support for integration-specific guidance. [B]
2. Verify Deployment Rules in OTTO: Open your site’s Settings, choose Automation, and find Deployment Rules. Open Never deploy and ensure the title-tag and meta-description issue types are not selected for blocking. Review inherited account rules and any project-specific overrides, then save your changes. Clearing a block allows deployment; it does not itself deploy pending fixes. [A]
3. **Clear Site and Server Caches:** Clear all layers of caching on your website. This includes your WordPress caching plugins (such as WP Rocket or LiteSpeed), hosting-level caches (such as Kinsta or WP Engine), and your CDN cache (such as Cloudflare).
4. Verify the OTTO Installation: Open the site’s Settings and choose Connections to review its installation status and installation guide. Use the diagnostics available for your installation method. For WordPress, also confirm that the Search Atlas plugin is active, updated, and connected to the intended site and OTTO project. Follow the installation-specific instructions rather than assuming every integration uses the same connection test. [D]
5. Deploy Eligible Fixes: After removing the relevant deployment blocks and resolving installation problems, return to the title-tag or meta-description fixes, select the eligible changes, and use Deploy. Review the deployment result and refreshed counts, then verify the live page. Removing a block does not automatically deploy fixes or guarantee that pending counts increase. [E] \*\*Code references\*\* - \*\*[A]\*\* `content-assistant/app/ca/models/otto\_deploy\_block.py:1–6`; `customer-frontend/src/modules/otto/shared/components/settings-modal/sections.ts:11–15`; `customer-frontend/src/modules/otto/shared/components/settings-modal/automation-section.tsx:98–112`; `customer-frontend/src/modules/otto/shared/deploy-rules/ProjectNeverDeploySection.tsx:56–105`; `AccountDeploymentRulesSettings.tsx:105–109`. - \*\*[B]\*\* `metasync/includes/class-metasync-seo-conflict-handler.php:1218–1222,1272–1274,1405–1406`; `metasync/otto/metasync-otto-seo-functions.php:987–1002`. - \*\*[C]\*\* `metasync/otto/Otto\_pixel\_class.php:243–258,300–333`. - \*\*[D]\*\* `customer-frontend/src/modules/otto/shared/components/settings-modal/connections-section.tsx:45–59`; `customer-frontend/src/modules/otto/shared/installation-guide/components/ottoStatusCard.tsx:49–67`. - \*\*[E]\*\* `customer-frontend/src/modules/otto/shared/features/issue-renderers/page-title/utils/customHooks/index.tsx:112–158`.

## **💬 Contact Support for Assistance**

If you have verified your settings, deactivated conflicting plugins, cleared your cache, and your meta updates still fail to deploy, our team can review your account directly. 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.