# **🔍 Overview**

In some cases, OTTO may inject an **Organization JSON-LD schema node** containing outdated information — such as an old phone number or a previous business name — into your homepage or other pages. This can be confusing because the outdated schema does not appear in **Domain-Level Schema** or **Page-Level Schemas** inside the Search Atlas dashboard, making it difficult to locate and remove.

This article explains why this happens and walks you through how to resolve it.

# **⚙️ Why This Happens**

When OTTO first analyzes your site, it may detect an existing Organization schema and store certain display fields internally. Under specific conditions, OTTO can re-inject this cached schema data into your page's **Custom HTML** (also referred to as `header_html_insertion`) even after the original schema has been updated or removed elsewhere.

Because the stored data bypasses the standard Domain-Level and Page-Level Schema panels, it remains invisible in the dashboard — making it appear as though OTTO is injecting schema from nowhere.

A platform-level fix has been deployed that strips the outdated cached fields to stop this from happening going forward. However, if your site was affected before the fix, you may still need to manually clear the stale schema using the steps below.

# **🚀 How to Remove the Stale Organization Schema**

1. In the left sidebar, navigate to **OTTO SEO → All Sites (SEO Automation)** (URL: `/seo-automation-v3`).
2. Select your website and open the **OTTO dashboard** for the affected domain.
3. Go to the **Active** tab within OTTO SEO → All Sites (SEO Automation) and review any active schema deployments listed there.
4. Look for any **Organization** schema entries that are active. If you find one containing outdated details, click it to open the editor and either **update the information** or **deactivate/remove the deployment**.
5. Next, check the **Custom HTML** or header injection settings. If your platform exposes an area for custom header code, search for any `<script type="application/ld+json">` blocks containing Organization data and delete them.
6. If you manage a **WordPress site**, log in to your WordPress admin panel and navigate to **Plugins**. Confirm the Search Atlas / OTTO plugin is up to date, as older plugin versions may continue serving cached schema even after dashboard changes.
7. After making changes, use a tool such as **Google's Rich Results Test** or **Schema Markup Validator** to verify the outdated Organization JSON-LD no longer appears on your page.

# **✅ How to Verify the Fix**

- Paste your homepage URL into **Google's Rich Results Test** (search.google.com/test/rich-results) and confirm the Organization schema now shows the correct business name, phone number, and other details.
- Use your browser's **View Page Source** feature and search for `application/ld+json` to check that no outdated Organization block remains in the raw HTML.
- If the stale schema still appears after following all steps, the data may be cached at the server or CDN level — try clearing your site cache and re-testing.

# **🛡️ How to Prevent This in the Future**

- **Keep business information current in OTTO.** Update your Organization details in the OTTO dashboard whenever your phone number, business name, or address changes.
- **Avoid adding Organization JSON-LD in multiple places.** Do not add Organization schema both through OTTO and through a separate plugin or theme option, as duplicate entries can cause conflicts.
- **Keep the Search Atlas plugin updated.** Platform fixes — including the schema caching fix — are delivered through plugin and dashboard updates.
- **Review Domain-Level Schema after major site changes.** Any time you rebrand or update contact information, audit your active schema deployments in OTTO to ensure everything is current.

# **💬 Need More Help?**

If you have followed the steps above and the stale Organization JSON-LD is still appearing on your site, our team can investigate directly. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type **human teammate** to be connected with a member of our team.