🔍 Overview

When OTTO SEO generates Product schemas, they may sometimes remain in Suggested status and cannot be deployed. This can happen due to validation issues, missing content, or a stale schema state that prevents OTTO from marking the schema as ready. This article explains the most common causes and walks you through the steps to resolve them.

⚙️ Why Product Schemas Get Stuck in Suggested

There are several reasons a Product schema may not advance past Suggested status:

• Validation failure (is_valid = False): OTTO runs an internal validation check before allowing deployment. If the schema fails validation — even silently — it is blocked from moving forward.
• Missing or empty schema content: In some cases, OTTO generates a schema entry but the underlying markup content is empty or unavailable. The schema appears in the list but has nothing to deploy.
• Stale schema state: After regeneration, a schema can get stuck in a review or suggested state with no visible fields to correct, leaving no clear path to deployment.
• Irrelevant schema suggestion: OTTO may occasionally suggest a schema type that does not match the page content, which can cause the suggestion to stall without clear next steps.

🚀 How to Resolve Stuck Product Schemas

1. Navigate to OTTO SEO. In the left sidebar, click OTTO SEO → SEO Automation (All Sites) or go directly to /seo-automation-v3.
2. Locate the affected URLs. Find the specific pages where Product schemas are showing as Suggested. You can use the schema filter or search by URL to narrow down the list.
3. Review the schema details. Click on the schema to open its details panel. Check whether the schema has populated content and review any fields flagged for correction.
4. Edit and complete any required fields. If fields are visible and incomplete, fill them in with accurate product information (name, price, availability, description, etc.) and save your changes.
5. Regenerate the schema if content is missing. If the schema panel appears empty or shows no editable fields, use the regenerate option to trigger a fresh schema generation for that URL. Wait for OTTO to complete the process before attempting deployment again.
6. Attempt deployment. Once the schema shows valid content and passes the internal check, the Deploy button should become active. Click it to push the schema live.
7. Verify deployment status. After deploying, confirm the schema status has changed from Suggested to Deployed in the schema list for those URLs.

💡 Tips to Prevent Schemas Getting Stuck

• Ensure the target page has sufficient product-related content before OTTO generates a schema — sparse pages are more likely to produce incomplete suggestions.
• After regenerating a schema, allow a few minutes for OTTO to fully process before reviewing or deploying.
• If a schema type suggested by OTTO does not match the page (for example, an Article schema on a product page), dismiss it and manually select Product as the schema type before regenerating.
• Regularly review your schema list for any items sitting in Suggested status for more than 24 hours, as these may require manual intervention.

🆘 When to Contact Support

If you have followed all the steps above and your Product schemas are still stuck in Suggested status — especially if the Deploy button remains inactive or the schema content appears empty after regeneration — our team can trigger a manual deployment on your behalf.

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.

When you reach out, please have the following ready to speed up the resolution:

• The full URLs of the affected pages
• The domain or project name in OTTO SEO
• A screenshot of the schema status panel for each affected URL
• Any error messages or empty field warnings you have observed