🛠️ Fixing Custom HTML Content Module Glitches After OTTO Activation

Camilo Aponte

Camilo Aponte

Last updated on Sep 30, 2026

If your site shows broken headings or banner issues after activating OTTO, the cause is malformed HTML inside your Custom HTML Content module deployments — not OTTO itself. Delete the affected deployments and clear your site cache to restore your layout.

🔍 What Causes Custom HTML Content Module Glitches

Malformed HTML structure inside the Custom HTML Content module's deployments causes overwritten headings, broken banners, and layout shifts. OTTO does not generate or modify this content — the problem originates from how the HTML was structured before or during deployment. OTTO's global rollback and undo features do not reach inside the Custom HTML Content module, so each deployment must be individually cleared using the steps below.

🛠️ How to Fix Custom HTML Content Module Glitches

In Search Atlas, go to OTTO → Miscellaneous → Custom HTML Content, then follow these steps in order:

  1. Click the first deployment in the module menu.
  2. Delete all text inside that deployment.
  3. Click Edit & Deploy to save the now-empty deployment.
  4. Repeat steps 1–3 for every remaining deployment in the list.
  5. Clear your site cache through your hosting provider or caching plugin.

Reload your site after the cache clears. Your headings, banners, and layout should return to normal.

Note: If you are on a White Label plan and custom HTML added via Report Builder disappears automatically, this is a separate known issue currently being resolved — contact support.

💡 How to Prevent Custom HTML Content Glitches on Future Projects

Apply these two guidelines when onboarding new clients to avoid repeating this issue:

  • Validate HTML before deploying. Every entry in the Custom HTML Content module must use well-formed, properly nested HTML. Run your code through an HTML validator before clicking Edit & Deploy.
  • Leave the module empty if you don't need it. If a client's project does not require custom HTML injections, do not add deployments to the Custom HTML Content module. Unused deployments with malformed markup are the most common trigger for these glitches.

🎯 You now know how to clear malformed HTML deployments from the Custom HTML Content module and prevent site glitches from affecting future client projects. For a broader overview of what OTTO deploys and manages on your site, see the OTTO Activation overview article.