When OTTO SEO deploys a Heading Length fix, it pushes changes to your page's HTML heading tags (H1–H6) — not your site's navigation header or banner area. Undeploying a fix removes the injected text for sites with a working CMS connector or Cloudflare Worker. For Website Studio sites using only the pixel script, undeployment will not work — see the compatibility note below.

**What the change looks like:** For example, if your original H1 was "Shoes" and OTTO's Heading Length fix determined it was too short, it may have rewritten it to "Buy Affordable Running Shoes Online" — replacing or expanding the original text within the heading tag.

**Before you begin:** The undeploy workflow requires a properly configured OTTO installation (CMS connector or Cloudflare Worker). Website Studio sites using only the manually installed pixel script cannot deploy or undeploy fixes at all — OTTO's deployment pipeline is non-functional (is\_deploy\_functional = False) without a CMS connector or Cloudflare Worker. Approved fixes are saved in the database but are never pushed to your live site. If you are in this configuration, connect a supported integration before attempting any deploy or undeploy actions — see the compatibility note further down.

**Two separate actions — don't confuse them:** (1) **Undeploying a fix** via the OTTO dashboard, which explicitly reverses that optimization and removes the injected text from your live site; and (2) **Removing the OTTO pixel or script** from your site, which only stops future changes and does NOT roll back already-deployed fixes. To remove injected heading text, you must use action (1).

# **🔍 Why OTTO SEO Is Modifying Your Heading Tags**

OTTO SEO's Heading Length fix rewrites HTML heading tags (H1–H6) to meet on-page SEO length recommendations. When deployed, the fix applies those changes live to your website's front end. This affects on-page heading elements only, not your site's top navigation or banner area.

Disengaging OTTO from your site (for example, removing the pixel/script or disconnecting the CMS connector) stops new changes from being applied, but it does not roll back fixes that were already deployed. Those deployed fixes stay active on your live site until you explicitly undeploy each one. This is expected behavior, not a bug.

**Important:** Removing the OTTO pixel or script from your site does NOT undeploy fixes. Previously deployed heading changes will remain on your live site until each fix is individually undeployed from within the OTTO SEO dashboard. Disengaging OTTO and undeploying a fix are two separate actions with different outcomes.

# **🛡️ Is OTTO's Heading Injection Safe? (Google Compliance)**

OTTO's Heading Length fix only modifies the visible text inside your page's H1–H6 tags. It does not use hidden content (such as `display:none` styling), keyword stuffing, or cloaking — the rewritten heading is the same for users and for search engine crawlers, and is contextually relevant to the page's topic. This is consistent with [Google's Search Essentials (formerly Webmaster Guidelines)](https://developers.google.com/search/docs/essentials), which define deceptive practices as showing different content to users than to crawlers or stuffing unrelated keywords to manipulate rankings — neither of which apply to OTTO's heading rewrites.

This safety guidance applies specifically to the Heading Length fix covered in this article and is distinct from other OTTO fix types (for example, injected FAQ sections or keyword lists), which are addressed in their own documentation.

# **🛠️ How to Undeploy the Heading Length Fix**

To remove the injected heading text, locate and undeploy the Heading Length fix inside OTTO SEO:

1. Log in to Search Atlas and open **OTTO SEO** for your site.
2. Locate your list of deployed fixes.
3. Find the fix labelled **Heading Length**.
4. Click **Undeploy** next to the Heading Length fix.
5. Confirm the action in the dialog that appears.
6. Wait for the status to update to **Undeployed**.
7. Verify on your live site that the heading text has returned to its original state.

Once undeployed, OTTO SEO removes the heading text change from your live site. For most CMS connector and Cloudflare Worker installations, this happens immediately. For pixel or manual script installations, visible changes on the live site and reflected audit state may lag or behave inconsistently — hard-refresh your browser and re-crawl your Site Audit if the change does not appear promptly.

**Compatibility note:** Use this checklist to identify your installation type and the level of undeploy support available:

- **WordPress CMS Connector** — fully supported for deploy and undeploy. If you are using the WordPress plugin for OTTO, do not also add WordPress as a separate CMS connector integration — having both active simultaneously can cause deployment conflicts. The WordPress plugin alone is sufficient.
- **Cloudflare Worker** — fully supported for deploy and undeploy. If your Cloudflare Worker shows as connected but OTTO's connection scanner cannot detect the pixel/UUID on your live site, undeploy actions may not execute correctly. In this case, contact support to verify Worker status before relying on the undeploy workflow.
- **Website Studio pixel-only** — NOT supported for deploy or undeploy. OTTO projects in this state will show is\_deploy\_functional = False and is\_active = False; both flags must be resolved by connecting a supported integration. Approved fixes are saved in the database but never pushed to your live site until you add a supported connector.
- **Pixel or manual script on a third-party CMS** — limited support; the Site Audit dashboard may not accurately reflect the live state. **Important:** If your project uses the manually installed pixel script, the Site Audit dashboard may display the original (pre-OTTO) heading text even when your live site is correctly showing the deployed version. This is a known reporting discrepancy — do not use the Site Audit view as the sole confirmation that a fix has or has not been deployed.

**⚠️ Known issue — Website Studio pixel-only setups:** This is a confirmed product issue. OTTO projects on Website Studio with only the manually installed pixel are flagged as is\_deploy\_functional = False and is\_active = False on the backend, meaning no fix will ever reach your live site regardless of the dashboard status shown. The supported resolution is to connect a CMS connector or deploy a Cloudflare Worker. If you cannot do either, contact Search Atlas support for guidance.

**⚠️ Known issue — Cloudflare Worker not detected:** If you have connected a Cloudflare Worker but OTTO's connection scan still shows the pixel as undetected, this is a known issue. The Worker deployment may be functional even if the scan reports otherwise — contact support to verify backend status before troubleshooting further.

If you are unsure which category you fall into, go to **OTTO SEO > Installation Guide** and confirm that a CMS connector or Cloudflare Worker is shown as connected. If neither is connected, contact Search Atlas support to verify your OTTO installation configuration before attempting any deploy or undeploy actions.

# **✅ Confirming the Heading Text Is Removed**

After undeploying, reload your website and check the affected heading. The OTTO-injected text should no longer appear on the live page.

**Note:** The Site Audit dashboard may continue to display the previous heading text after undeploying due to a known reporting delay. For pixel-based installations, the Site Audit crawler may not accurately reflect the live deployment state even when JS rendering is active. Verify changes directly in your browser (or via browser dev tools by inspecting the heading element on the live page) rather than relying solely on the Search Atlas dashboard.

**Known reporting discrepancy — manual pixel (manual\_script) installs:** If you are using the manual pixel (manual\_script) installation, be aware that the Site Audit dashboard may not accurately reflect currently deployed heading changes — it may display original source titles instead of OTTO-deployed ones, even with JS rendering enabled. This is a known reporting discrepancy; the live site state (verified in your browser) is the authoritative source.

# **⏱️ If the Heading Text Persists After Undeploying**

For most installations, undeployed changes propagate to the live site within a few minutes. If the original heading text does not return:

- Hard-refresh your browser (Ctrl+F5 or Cmd+Shift+R) to bypass local browser cache.
- Clear any CDN or page cache (for example, Cloudflare, WP Rocket, or your hosting provider's cache layer).
- Re-crawl your Site Audit so the dashboard reflects the current live state.
- If the injected text still persists after 24 hours, contact Search Atlas support with your OTTO project UUID so the team can investigate.

**Troubleshooting note for pixel script installs:** If you use the pixel script and the Site Audit report still shows the original heading text after deploying a fix, this may be a known dashboard display issue — not a failed deployment. Verify the live page directly in your browser or use a third-party HTML inspection tool to confirm the actual deployed state before re-attempting deploy or undeploy.

# **🧩 About Other Content OTTO May Inject**

OTTO may also inject supporting SEO content beyond heading changes — such as keyword lists or FAQ sections — that may not be prominently visible in your site's main design. This content is contextually relevant, legitimate SEO content placed to support the page's topic, and is distinct from the Heading Length fix covered in this article.

**Is this black-hat SEO?** No. Google's Webmaster Guidelines define hidden content as deceptive when it shows different content to users than to search engines, or when it stuffs unrelated keywords solely to manipulate rankings. The supporting content OTTO injects is topically relevant to the page, identical for users and crawlers, and intended to improve the page's semantic completeness — not to deceive. If you have concerns about specific content types being injected on your site, or want a particular injection removed, contact Search Atlas support.

**🎯 Once you undeploy the Heading Length fix, your original heading text is restored to the live site (subject to your installation type). If unexpected text persists after undeploying, contact Search Atlas support for further assistance.**