Use this guide to get OTTO schema markup live on your site when it's missing, stuck in a **PENDING** loop, or sitting in **SUGGESTED** status. Each section matches a specific symptom, so you can jump straight to the fix you need.

## 🧩 Step 1: Confirm Schema Generation in OTTO

Start by confirming the schema was generated and checking its deployment status.

- Open **OTTO** (or your other schema generator) and verify the schema was created correctly.
- Check the deployment status. If schemas show **Not Deployed** or sit in a **PENDING** connection loop, go to Step 1.5 first.
- If schemas show **SUGGESTED**, go to Step 1.6 — these need manual inputs from you.
- Copy the generated schema and compare it with your live site's code to confirm it's fully implemented.

Once you know the exact status, follow the matching section below.

## 🔄 Step 1.5: Resolve Stuck PENDING or Not Deployed Schemas in OTTO

Bulk-generated schemas (such as Product schemas with `aggregateRating`) can become stuck in a PENDING connection loop and never transition to **Deployed**. If your schemas show **SUGGESTED** instead, skip to Step 1.6 — those need manual inputs from you, not a backend fix.

### Symptoms

- Schemas display a **Not Deployed** or **PENDING** status indefinitely in the OTTO dashboard.
- Retrying deployment produces the same PENDING loop.
- The schema never appears in the live page source, even with no caching or plugin issue present.

### What to do

1. Confirm the **OTTO pixel/script** is correctly installed and connected to your site.
2. Wait 5–10 minutes, then retry deployment once from the OTTO dashboard.
3. If schemas remain stuck, contact **Search Atlas Support** and request a **manual deployment**. Include your domain and the affected schema list (for example, "60 Product schemas with aggregateRating on example.com").

Support can verify deployment on the backend and reset your OTTO AI generation quota, restoring any quota consumed by the failed attempts. In a recent case, 60 Product schemas were stuck in PENDING; Support confirmed they were generated and deployed on the backend, then reset the AI generation quota. Once schemas show as **Deployed**, continue with Step 2.

## ✍️ Step 1.6: Deploy Product Schemas Stuck in SUGGESTED Status

Product schemas stay in **SUGGESTED** status when they require manual inputs that OTTO cannot fill automatically. They will not deploy until you add the missing details yourself.

### How to deploy a SUGGESTED schema

1. In OTTO, open the schema marked **SUGGESTED**.
2. Fill in the required fields that OTTO could not auto-complete.
3. Save and deploy the schema from the OTTO dashboard.

For a visual walkthrough of where to find these schemas and which fields to complete, watch this short tutorial: [SUGGESTED schema navigation video](https://jam.dev/c/d510fe87-c4a9-407b-bcf1-eccdf879188e).

After you add the manual inputs and deploy, the schema moves out of SUGGESTED status. Continue with Step 2 to confirm it appears on your live site.

## 🔍 Step 2: Check the Live Site Source Code

Confirm the deployed schema is actually present on your page.

1. Visit your website.
2. Right-click the page and select **View Page Source**.
3. Search for key schema properties such as `"type": "Organization"`, `"address": "PostalAddress"`, and `"context": "https://schema.org"`.

If the schema is present in the page source, your deployment succeeded. If it's missing, continue with the steps below.

## 🧠 Step 3: Validate Schema with External Tools

Use an independent validator to confirm search engines can read your schema.

- Open the [Schema Markup Validator](https://validator.schema.org/) and enter your site URL to check whether schema is detected.
- As an alternative, use [Google's Rich Results Test](https://search.google.com/test/rich-results) to confirm your schema meets Google's structured data requirements.

A clean validation result confirms search engines can read your schema.

## ⚙️ Step 4: Clear Your Website Cache

Website caching can serve an outdated version of your site that excludes recent updates like schema markup.

- If you use a caching plugin or a CDN, clear or purge the cache so the latest page version is served.
- Reload your site and repeat Step 2 to confirm the schema now appears in the page source.

Once the cache is cleared and the schema shows in your live source, your markup is deployed and visible to search engines.

**🎯 You now know how to tell PENDING from SUGGESTED schemas in OTTO, supply the manual inputs SUGGESTED Product schemas need, and verify deployment on your live site. If schemas stay stuck in a PENDING loop after retrying, contact Search Atlas Support for a manual deployment and quota reset.**