# **📋 Understanding OTTO Schema Deployment**

OTTO deploys schema markup by injecting it into the page using client-side JavaScript after the initial HTML loads. This means the schema code does not exist in the static HTML source that most validation tools fetch and analyze.

# **🛠️ Why Static Validators Show 'No Items Detected'**

Tools such as Google Rich Results Test and Schema.org Validator operate by requesting the raw HTML of a URL and parsing it immediately. They do not execute JavaScript, so any schema added dynamically after page load remains invisible to them. This is expected behavior for client-side schema injection.

# **✅ Correct Ways to Verify OTTO Schema**

1. Open the live page in Chrome and use **Inspect Element** (right-click → Inspect) to view the rendered DOM. Search for **application/ld+json** or your schema type to confirm injection.
2. Use Google Search Console **URL Inspection** tool and click **Live Test**. This runs a headless Chrome instance that executes JavaScript, allowing it to see the deployed schema.
3. Check the OTTO dashboard under **OTTO SEO → All Sites (SEO Automation) → Active** to confirm the schema deployment status shows **Deployed** for the target URL.

# **🚫 Common Misdiagnoses to Avoid**

- **Caching issues** – Clearing cache or regenerating schema will not make static validators detect client-side code.
- **CMS or generator errors** – The schema is not rendered server-side, so CMS rendering problems are unrelated.
- **NLP-disabled errors** – These are unrelated to schema visibility in static validators.

# **📌 Key Takeaway**

If OTTO shows schema as **Deployed** but static validators report **No items detected**, the schema is working as designed. Verify using browser DevTools or Google Search Console Live Test instead.

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.