OTTO deploys front-end fixes — meta titles, descriptions, and heading tags — in preview or live mode. Your CMS, WordPress database, and SEO plugin settings are never modified.

## 🖥️ Front-End Modifications

Front-end changes affect the **HTML** of your page — including meta titles, meta descriptions, and heading tags. How OTTO delivers these changes depends on your integration:

- **⚡ JavaScript injection** — used for preview mode and non-WordPress sites. Changes are injected directly in your browser session.
- **🔌 SA WordPress plugin** — applies changes at the server/plugin level, which can also influence CSS and title rendering.

The WordPress admin setting **Disable OTTO for Logged in Users** prevents OTTO injections from appearing to authenticated visitors. A prior regression (WP-313, now resolved) caused deployed titles to persist for logged-in users regardless of this setting. If you still see deployed titles for logged-in users, update to the latest plugin version.

### 👁️ Preview Mode

In preview mode, OTTO injects changes **only into your browser session**. Other visitors are not affected, and no permanent modifications are made to your site. Use preview mode to review a fix before deploying it.

### 🚀 Deployed State

Once deployed, a fix goes live and is **visible to all visitors**. Deployed fixes — such as Heading Length corrections or updated meta titles — remain active until you explicitly remove them.

### ↩️ How to Undeploy a Front-End Change

1. Go to your OTTO project and open the **Deployments** tab.
2. Filter or search by issue type (for example, Heading Length or Meta Title) to locate the specific fix.
3. Click **Undeploy** next to the fix.

The change is removed from the live page immediately.

### ⚠️ Known Issue: WordPress Plugin CSS Override (WP-315, Active)

If the SA WordPress plugin is active and your site CSS appears affected **site-wide**, this is an active regression — the plugin may override CSS beyond its intended scope.

**Temporary workaround:** Disable the SA WordPress plugin until the permanent fix is released. Re-enable it only after Search Atlas support confirms the WP-315 fix appears in the plugin changelog (not yet released as of 2026-05-24).

### 🔧 Resolved Issues: Cloudflare DNS and Heading Length

**Cloudflare DNS deployments reverting (OTTO-1931, resolved):** Deployed changes previously reverted shortly after application. If you are on Cloudflare DNS and still see deployments reverting, update to the latest OTTO version or contact support.

**Heading Length with inline HTML (WP-314, resolved):** Headings containing inline elements such as `<span>` or `<strong>` from Elementor previously produced corrupted output when replaced. If you deployed heading fixes before the WP-314 fix release, review those headings and redeploy if corruption is visible.

## ⚙️ Back-End Modifications

The **Content Assistant** tool does **not** write to your CMS (Content Management System). Platforms such as WordPress, Shopify, and Wix — and the data stored within them — are never modified by Search Atlas.

SEO plugin fields managed by tools like **Yoast** or **Rank Math** remain completely untouched. All Search Atlas changes operate within their own layer and do not interact with your CMS database or third-party plugin settings.

**🎯 You now know how OTTO previews and deploys front-end changes, how to reverse a deployment, and that your CMS and SEO plugin settings are never modified by Search Atlas. To explore what OTTO can optimize across your site, see the OTTO Optimizations guide.**