This article addresses a specific issue where page-level schemas appear to generate successfully — credits are deducted and a confirmation message is shown — but no schema output is visible in the OTTO SEO tab afterwards. This is typically caused by a display delay or a rendering hiccup following processing, and does not always mean the generation failed.

# **🔍 Common Causes**

- **Display lag after processing:** The AI engine finishes generating the schema, but the UI does not automatically refresh to show the result.
- **Browser or session cache:** A stale cached state can prevent newly generated content from rendering correctly.
- **Partial processing interruption:** A brief network or server interruption during generation can cause output to be stored but not surfaced in the UI.

# **🛠️ Step-by-Step**

1. After seeing the generation confirmation, **perform a hard refresh** of the page (Ctrl + Shift + R on Windows/Linux, or Cmd + Shift + R on Mac) to clear any cached state and force the UI to reload the latest data.
2. If the schema still does not appear, **navigate away** from the OTTO SEO tab to another section of the platform, then return to the OTTO SEO tab. This triggers a fresh data fetch from the server.
3. If you are still not seeing output, **log out of your account and log back in**, then return to the project and check the OTTO SEO tab again.
4. If the schema remains absent after completing the steps above, **do not re-run the generation immediately** — note the domain (e.g., shepcorestore.com), the approximate time of generation, and the number of credits deducted, and contact support so the team can investigate without you losing additional credits.

# **✅ How to Confirm It Worked**

After refreshing or re-navigating, you should see the generated schema code populated in the OTTO SEO tab for the relevant pages. Each page that was processed will display its schema markup in the corresponding field. If schemas are present and credits were deducted, the generation completed successfully. If the fields remain empty but credits were still used, this confirms a display or delivery issue that requires support review — your generation data is likely stored on the backend and can be recovered without re-running and spending additional credits.

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.