Troubleshooting: Schema Errors

🛠️ Fix OTTO Schema Deploy All Button Issues

🛠️ Fix OTTO Schema Sync, FAQ Indexing & Timezone Metadata

🔍 OTTO Schema Not Showing in Rich Results Test

🛠️ Fixing Schema Creator Generation Failures

Schema Creator uses AI to build structured data (schema markup) for your pages. If the Generate Schema button seems to do nothing, the Deploy button stays grayed out, or the page keeps reverting to "You haven't generated a schema yet," this guide will help you get back on track quickly. 🔍 Common Symptoms You are likely experiencing one or more of the following: - The Deploy button is disabled (grayed out) after you generate a schema. - The page reverts to "You haven't generated a schema yet" even after clicking Generate Schema several times. - Error and success messages appear at the same time, but no schema is actually created. - FAQ or Breadcrumb schemas generate with empty content, such as missing questions (mainEntity) or missing breadcrumb steps (itemListElement). - A single-page generation returns an error while a bulk generation keeps spinning without finishing. - An intermittent message: "The AI was unable to generate valid schemas for the requested pages." 💡 Why This Happens Most of these issues were caused by bugs on our side, including temporary server errors, conflicting status messages, and empty FAQ or Breadcrumb output. These have been fixed in recent platform updates. However, your browser can still load an older, cached version of the page, which makes the problem reappear even after the fix. In addition, incomplete required fields and clicking Generate Schema repeatedly can interrupt an in-progress request and cause the page to reset. 🛠️ How to Fix It Work through these steps in order. Most customers are back up and running after the first two steps. 1. Hard refresh the page. This clears stuck status messages. Press Ctrl + Shift + R on Windows or Cmd + Shift + R on Mac. 2. Clear your browser cache or open an incognito/private window. This forces your browser to load the latest version of Schema Creator, including the recent bug fixes. 3. Complete all required fields. For FAQ schema, every question needs an answer. For Breadcrumb schema, every step needs a name and a URL. Missing details can cause empty or failed output. 4. Generate one schema at a time. If a bulk generation keeps spinning, try generating a schema for a single page first. Once that succeeds, add more pages in small batches. 5. Wait a few minutes and retry. If you see "The AI was unable to generate valid schemas for the requested pages," the AI service may be briefly busy. Wait 5 to 10 minutes, then click Generate Schema once. 6. Log out and log back in. This resets your session and clears any stale page state that survived the refresh. 📊 Confirming the Fix Worked After completing the steps above, verify everything is working: 1. Open Schema Creator from the Content section in the left sidebar. 2. Click Generate Schema****once and wait for the confirmation message. Generation can take up to a minute, so avoid clicking multiple times. 3. Review the preview. FAQ schemas should list your questions and answers (mainEntity), and Breadcrumb schemas should list every step (itemListElement). 4. Confirm the Deploy button is now active, then click it to publish the schema to your page. ✅ Tips to Avoid Future Failures - Click Generate Schema once and wait. Repeated clicks can interrupt the request and reset the page. - Keep bulk runs small. We recommend generating schemas for 10 pages or fewer at a time. - Fill in every field before generating, especially for FAQ and Breadcrumb schema types. - Hard refresh Schema Creator after a platform update so you are always using the latest version. 💬 Still Failing? Talk to Us If the problem continues after following all of the steps above, have this information ready to speed things up: the page URL you were targeting, the schema type you selected, the exact error message, and the approximate time you clicked Generate Schema. 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.

🛠️ Troubleshooting Delayed Page Schema

This article explains why credits may be deducted even when page-level schema does not appear, and how to resolve and verify the issue. 🛠️ Step-by-Step 1. Open the page-level schema generation area for the affected page and review the generation result or status. 2. Check whether the page contains clear, complete content that matches a supported schema type. AI may consistently misclassify ambiguous or thin pages. 3. Improve the page content and make its primary purpose clear before trying again. Recrawling the same unchanged page may produce the same classification. 4. Run schema generation again after the page changes are saved or published. Avoid repeated retries on an unchanged page. 5. Review the generated output and apply or save it if the product presents that option. ✅ How to Confirm It Worked Confirm that a schema result is visible for the affected page and that it matches the page's actual content type. A credit deduction confirms processing started, not that schema was successfully generated. If no schema appears after correcting the page and retrying once, contact support instead of repeatedly recrawling. 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.

🧩 OTTO and Yoast Schema Output Conflicts

🔍 Overview OTTO and Yoast can both generate Schema.org JSON-LD on the same WordPress page. When both systems publish overlapping schema, search engines may receive competing or invalid schema blocks. This can cause the Yoast schema graph to appear false, prevent the author Person entity from being included, or create duplicate BlogPosting data. MetaSync OTTO or an external Search Atlas sync does not intentionally remove a valid Yoast author entity. However, an OTTO deployment can interact with the SEO plugin output when both systems attempt to control schema on an OTTO-covered page. ⚙️ Why the conflict happens - Yoast generates a connected schema graph, commonly including WebPage, Article or BlogPosting, Organization, and Person entities. - OTTO may deploy page-level schema or schema-related recommendations through its WordPress integration. - When both outputs target the same page, WordPress can render competing JSON-LD blocks instead of one deduplicated graph. - Conflict handling may override, suppress, or incorrectly modify part of the Yoast graph, including the author Person entity. - Older conflict-handler behavior could produce an invalid value such as "@graph":false. ✅ Recommended workaround 1. Identify whether the affected URL is covered by an active OTTO deployment in Search Atlas. 2. Temporarily use one system as the schema owner for that URL. If Yoast is responsible for your author and article entities, do not deploy overlapping BlogPosting schema through OTTO. 3. Keep Yoast schema enabled and confirm that the post has a valid author assigned in WordPress. 4. Clear WordPress, plugin, server, and CDN caches, then request a fresh crawl of the page. 5. View the rendered page source and search for application/ld+json. Check whether multiple BlogPosting blocks or an invalid @graph value are present. 6. Validate the final output using Google’s Rich Results Test or Schema Markup Validator. Test the live URL after caches have cleared. 🧪 Troubleshooting checklist - Confirm the author profile is published and linked to the post in WordPress. - Check whether the author profile has a name and URL that Yoast can use for the Person entity. - Compare a page covered by OTTO with a similar page that is not covered. - Review the page source rather than only the WordPress editor or rendered visual page. - Look for duplicate Article, BlogPosting, WebPage, Organization, or Person entities. - Check Search Atlas plugin logs for unrecognized OTTO deployments or Yoast overrides. - After changing schema ownership, clear caches and retest the live page. 📌 Global BlogPosting schema support Global BlogPosting deployment should not be used as a workaround when Yoast already generates BlogPosting and author schema. Publishing both globally can increase duplication and may cause conflicting properties or missing connections in the Yoast graph. For reliable output, use Yoast as the source of truth for Yoast-managed article and author schema, or use OTTO for pages where OTTO is explicitly configured to own the complete schema output. Avoid deploying two independent global BlogPosting templates on the same URLs. 🛠️ When to request an investigation Contact support through the platform if the conflict continues after assigning one schema owner, clearing caches, and retesting the live source. Include the affected URL, whether OTTO is active for the page, the rendered JSON-LD output, and the relevant plugin log entries. This helps the team determine whether the issue involves duplicate schema, an invalid graph value, a deployment recognition problem, or an author configuration issue. 💬 Need help? 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.

🧩 OTTO and Yoast Schema Conflicts

🔍 What is happening OTTO and Yoast can both attempt to generate structured data on the same WordPress pages. When OTTO takes over schema output, Yoast may return an empty @graph:[] instead of its normal BlogPosting and author entities. This can affect many posts at once, including sites with 700 or more articles. The issue is usually a schema-output conflict, not missing author data in WordPress or Yoast. ✅ Confirm the conflict 1. Open an affected blog post in an incognito browser window. 2. View the page source and search for application/ld+json. 3. Check whether Yoast outputs an empty @graph while OTTO-related schema markup is present or controls the page output. 4. Test several posts, including posts with different authors and publication dates, to confirm the issue is site-wide. 5. Use Google’s Rich Results Test or Schema Markup Validator to compare an affected page with a page from before OTTO was enabled. 🛠️ Restore Yoast schema output 1. In WordPress, open the OTTO plugin settings or installation configuration. 2. Find the setting that enables OTTO schema, structured data, schema takeover, or replacement of existing schema. 3. Disable OTTO’s schema output or configure OTTO to preserve the existing Yoast schema. Do not disable OTTO’s other SEO changes unless required. 4. Save the configuration and clear WordPress, hosting, CDN, and browser caches. 5. Regenerate or recrawl the affected URLs if your setup provides a schema refresh or site scan option. Setting names can differ by OTTO plugin version and WordPress configuration. If no schema control is visible, temporarily deactivate the OTTO plugin on a staging site and retest. If Yoast schema returns, the conflict is confirmed. 👤 Verify BlogPosting and author data 1. Open a recently updated post and inspect its JSON-LD. 2. Confirm the @graph contains a BlogPosting entity. 3. Confirm BlogPosting includes an author property that references or contains a Person entity. 4. Check that the Person entity includes a valid name and, where applicable, a profile URL. 5. Test posts by multiple authors to ensure the fix applies across the site. Do not manually add duplicate BlogPosting or Person schema to every post. Duplicate entities can create new validation issues and may conflict with Yoast after future updates. 🧪 Validate at scale For a site with 700 or more posts, first validate a representative sample: old and new posts, posts by different authors, and posts using different templates. Then crawl the full blog section to identify pages that still return an empty graph or lack BlogPosting and author data. Search engines may need time to recrawl the corrected pages. A valid test result confirms the markup is present, but it does not guarantee immediate changes in search results. 🚨 If the issue continues Check for additional schema plugins, theme-generated JSON-LD, caching layers, and custom code that filters Yoast schema. Re-enable only one schema provider at a time on staging to identify competing output. When requesting help, include an affected URL, a page-source excerpt showing the empty graph, the OTTO plugin version, the Yoast version, and the result after disabling OTTO schema output. 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.

🔍 Fix Incorrect Breadcrumb Schema

🔎 Understand the schema error Incorrect schema can cause Google Search Console errors when a page contains invalid, incomplete, or mismatched structured data. For example, a subscription or event page may publish a BreadcrumbList that does not match the page hierarchy, URL, or visible navigation. Search Atlas may label this markup as MetaSync Breadcrumbs Schema. The error can affect a specific URL, such as https://experienceepic.com/theeventreport/, without affecting the rest of the site. 🛠️ Check the affected page 1. Open the affected URL in a browser and confirm that the page loads correctly. 2. Review the page's visible breadcrumb navigation, if available. The breadcrumb names and links should match the structured data. 3. Check whether the page is a subscription, product, event, or other page type. Breadcrumb schema should describe the page path, not the subscription details. 4. Run the URL through Google's Rich Results Test or Search Console's URL inspection tools to confirm the exact error and affected schema item. ⚙️ Correct the breadcrumb schema Use the system that currently adds schema to the page. If the markup is generated by your website, CMS, theme, or another SEO plugin, update or remove the conflicting BreadcrumbList there first. A page should not publish multiple conflicting breadcrumb definitions. If you manage the markup in Search Atlas, open More Features → Schema Creator → Breadcrumb. Review the breadcrumb entries and confirm that: - The schema uses the correct page URL. - Each breadcrumb has the correct name and position. - URLs use HTTPS and point to valid, canonical pages. - The final breadcrumb represents the current page. - There are no duplicate or empty entries. Save the corrected schema and publish or deploy it to the affected page. If the page should not have breadcrumb markup, clear the entries or remove the generated BreadcrumbList from that page. ✅ Validate and request reprocessing 1. Clear your website or CDN cache, if applicable. 2. View the page source and confirm that the old schema is no longer present. 3. Run the URL through the Rich Results Test again. 4. In Google Search Console, open URL inspection, enter the affected URL, and select Request indexing after the correction is live. 5. Allow Google time to recrawl the page. Search Console errors may remain visible until Google processes the updated markup. 🚫 Avoid common schema problems - Do not add breadcrumb schema solely to resolve a Search Console warning if the page has no corresponding navigation. - Do not use HTTP URLs when the site uses HTTPS. - Do not include subscription plans, prices, or payment details in BreadcrumbList markup. - Do not publish several schema versions for the same page from different tools. - Do not assume a successful test immediately removes an existing Search Console report. 💬 Get help with a persistent error If the incorrect schema continues after you update the page, provide the affected URL, the Search Console error text, and a copy of the current page source. 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.

🔍 Troubleshoot Missing Yoast Author Schema

🧭 Overview Yoast author schema can intermittently appear to be missing when MetaSync OTTO or another external sync updates the page’s JSON-LD. In affected cases, the Yoast graph may be replaced with "@graph": false, or imported schema blocks may be dropped. This can prevent the expected Person entity for the author from appearing. ⚠️ Known causes - Yoast conflict handling: A known MetaSync conflict could produce invalid JSON-LD with "@graph": false on OTTO-covered pages. - External schema imports: Schema blocks that were not eligible for import could be silently skipped. - Sync timing: A page may briefly show older or incomplete markup while an external sync is processing. - Caching: WordPress, plugin, CDN, or browser caches can continue serving an earlier version after the schema is corrected. - Author data: Missing or incomplete author details in WordPress can prevent Yoast from creating a Person node. ✅ What Search Atlas has addressed Search Atlas has completed fixes for the MetaSync Yoast conflict handler and OTTO persistence across Yoast, Rank Math, and AIOSEO. These changes address invalid graph output and improve schema synchronization. Schema import eligibility and result reporting are also being improved, so unsupported or skipped blocks can be identified more accurately. 🔎 How to verify the issue 1. Open the affected page in an incognito browser window. 2. View the page source and search for application/ld+json, "@graph", and "@type":"Person". 3. Check whether the page contains "@graph": false, an empty graph, or a Person node without the expected author information. 4. Compare the page source with the rendered DOM. If they differ, a plugin, theme, or client-side script may be changing the markup. 5. Clear WordPress, SEO plugin, server, CDN, and browser caches, then check the page again. 🛠️ Recommended checks - Confirm the author has a valid WordPress user profile and display name. - Check that Yoast is enabled for the post type and that the page is not excluded from search or schema output. - Review whether OTTO or MetaSync is covering the page and whether an external schema sync recently ran. - Do not add a second manual Person graph until the existing Yoast and OTTO output has been reviewed. Duplicate entities can create new validation issues. - After changes, allow the sync to finish and purge all relevant caches before testing again. 📊 Expected result The page source should contain valid JSON-LD with an @graph array. That graph should include the article or webpage entities and, where author data is available, a linked Person entity. A temporary absence immediately after a sync can be cache-related, but repeated output of "@graph": false indicates a conflict or failed schema update. 💬 Get help When contacting the team, include the affected URL, WordPress and SEO plugin versions, whether OTTO or MetaSync covers the page, the time of the latest sync, and a page-source excerpt showing the JSON-LD. 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.

🛠️ Troubleshooting Page Schema Generation

This article explains what to do when page-level schema credits are used but no generated schemas appear in Search Atlas. Follow the self-serve steps below to resolve the issue on your own before reaching out to our team. 🔍 Step 1 — Verify Your Schema Output Location Generated schemas may not appear where you expect them. Check the following: - Navigate to the affected page inside your Search Atlas project and look for a Schema or Structured Data section within the page editor or page details panel. - Confirm you are viewing the correct project — schemas are stored per-project, so switching projects will show different results. - If you ran generation in bulk, allow a few minutes for all pages to finish processing before concluding that output is missing. 🔄 Step 2 — Check Page Classification Schema generation results depend on the page type classification assigned to each URL. An incorrect classification can cause the generator to produce no usable output or consume credits without visible results. - Open the affected page in your project and review the Page Type or classification setting (e.g., Article, Product, Local Business). - If the classification looks incorrect, update it to match the actual content of the page. - Save the updated classification before retrying generation. 🔁 Step 3 — Retry Schema Generation for One Page Before retrying your entire batch, test with a single page to confirm the fix works and to avoid consuming additional credits unnecessarily. - Select one of the affected URLs in your project. - Trigger schema generation for that page only. - Wait for the process to complete, then check whether the schema output now appears correctly. - If the single-page retry succeeds, you can proceed to re-run generation for the remaining affected pages. 📊 Step 4 — Review Credit Usage To confirm how many credits were consumed versus how many schemas were successfully produced: - Navigate to your account's Credits or Usage section in Search Atlas. - Compare the number of credits deducted against the number of schemas that appear in your project. - Note any discrepancy (e.g., 10 credits used, 0 schemas visible) so you have this information ready if you need to escalate. ✅ If the Issue Persists — How to Escalate Effectively If the steps above do not resolve the problem, our team can investigate at the backend level. Please have the following ready when you reach out: - The affected project name - The specific URLs that failed - The schema type selected for each affected page - The number of credits used without a result - Any error messages or unexpected behavior you observed - The approximate date and time the generation was run 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.

🛠️ Fix OTTO Schema Stuck & Focus Terms Quota

🔍 Overview Two common issues can appear together in OTTO: schemas that remain in a Not Deployed state even after a successful sync, and a Focus Terms quota that appears maxed out even when you have far fewer active articles than your plan limit. This article explains why both happen and what you can do right now. ⚙️ Why Schemas Get Stuck in "Not Deployed" After OTTO completes a sync (SYNC_COMPLETE), you may still see a number of schemas listed as Not Deployed. This is caused by one of the following: - Stale validation flag: Internally, a schema record can carry an is_valid = false flag from a previous failed generation attempt. Even though the sync finished, OTTO will not push a schema to your site while that flag is present. - Silent generation failure: In some cases, schema generation fails without surfacing an error message, leaving the record in a broken state. The Not Deployed count in the dashboard may also not match the number of records actually listed — this is a known display inconsistency that has been resolved in a recent update. - Schema needs review: Some schemas are flagged as Needs Review before deployment. These must be reviewed or approved before OTTO will deploy them. 🚀 How to Resolve Stuck Schemas 1. Navigate to OTTO SEO → All Sites (SEO Automation) in the left sidebar (URL: /seo-automation-v3) and open the Schema section for the affected site. 2. Filter the schema list by Not Deployed to isolate the stuck records. 3. Check whether any schemas are also flagged as Needs Review. Open each one and approve or make the requested edits, then save. 4. Once schemas are in a valid state, trigger a new Sync using the Sync button in the OTTO dashboard. This clears stale validation flags and re-attempts deployment. 5. After the sync completes, refresh the page and confirm the Not Deployed count has decreased. If schemas remain stuck after a fresh sync, it is likely the underlying record still carries a stale flag that requires a backend fix. Please contact support using the instructions at the bottom of this article. 📊 Why Your Focus Terms Quota Shows 120/120 The Focus Terms quota counts all articles that have ever been assigned a Focus Term inside OTTO — not just articles that are currently published or active. This means: - Articles that have been moved to Trash inside Search Atlas still hold their Focus Term slot. Trashing an article does not automatically release the quota. - If you have a large number of trashed articles (for example, 231 trashed articles), those records continue to consume quota until they are permanently deleted. - This is why you may see a quota of 120/120 while only ~38 articles appear active in your workspace. 💡 How to Free Up Focus Terms Quota 1. Go to Content → Content Genius (What are we writing today?) and use Restore article to view your Deleted articles. 2. Review the deleted articles and confirm you no longer need them. 3. Permanently delete the deleted articles you want to remove. A permanent delete — not just a move to Trash — is required to release the quota. 4. Once the permanent deletion is processed, your Focus Terms quota will update to reflect the freed slots. Important: Permanently deleted articles cannot be recovered. Make sure you have exported or saved any content you may need before deleting. 🛠️ Quick Reference: Common Questions - Will a new Sync automatically fix all stuck schemas? In most cases, yes. A fresh sync clears stale flags and retriggers deployment. If schemas remain stuck, a backend correction may be needed. - Does deleting trashed articles affect my live site? No. Articles already in Trash are not published. Permanently deleting them only removes them from Search Atlas. - Can I edit schema raw JSON directly? Full raw-JSON editing (including adding and deleting schema blocks) is currently in development and will be available in a future release. - Why does the Not Deployed count not match my list? This was a known display bug. It has been resolved in a recent platform update. If you still see a mismatch, refresh the page or trigger a new sync. 💬 Need More Help? 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.

🏷️ OTTO Schema Markup: What Null Fields Mean and How to Fix Them

🤔 What does a null field in schema markup mean? When OTTO detects existing schema markup on your site (shown as FOUND), it reads the current values. If a field shows null, it means the field exists in your schema but has no value assigned to it. Null fields are normal and expected in FOUND schemas — they highlight areas where data is missing. A common source of null fields is markup imported from a CMS (such as WordPress), which can leave required fields empty or inject malformed values. OTTO now sanitizes FOUND content before storing it, so newly imported schemas are cleaned automatically. If you still see null fields left over from an earlier import, regenerating the schema (below) refreshes them. 🔧 How to fix null fields 1. In OTTO, find the page with the null field warning 2. Click Regenerate Schema for that page 3. OTTO will attempt to auto-populate the field based on your site content and Brand Vault data 4. Review the regenerated schema and deploy it 🚫 What if the field is not applicable to my business? If your business genuinely does not use a field, you have two options: - Regenerate — OTTO will omit fields it cannot populate from your content - Edit manually — click the field in the schema editor and remove it or set an appropriate value Schema markup that fails validation (for example, a missing required field) is not deployed unless validation was explicitly suppressed for it. You can also add custom fields in the schema editor — they are preserved through the edit, save, and deploy cycle and will not be stripped or trigger warnings. 📋 FOUND vs. GENERATED schemas - FOUND — schema OTTO detected already on your page. Null fields here reflect gaps in your existing markup. - GENERATED — schema OTTO created from scratch. These are fully populated before deployment. 👀 Seeing a FOUND schema or null fields you didn't expect? A few past issues could cause a schema to appear as FOUND when it shouldn't — all are now resolved: - Stale FOUND schemas — a page could still show "schema detected" after its markup was removed or never actually parsed. OTTO now clears these stale FOUND records on the next crawl sync, so they no longer report null fields for markup that isn't there. - OTTO-deployed FAQ schema shown as FOUND — FAQ schema that OTTO itself deployed was sometimes mislabeled as FOUND instead of SUGGESTED. This has been fixed, so OTTO-managed schema is now categorized correctly. - Internal fields in the preview — internal display fields once appeared in the JSON-LD preview panel for older FOUND schemas; these are now stripped from the preview. If a page still shows leftover null fields from before these fixes, click Regenerate Schema to refresh it.

🛠️ OTTO Schema Deployment Stuck in Manual Review

🔍 Overview Some OTTO users have encountered a situation where schema deployments appear to succeed — the API returns a 'Success' response — but no schemas actually deploy. Affected schemas remain frozen in manual review status and cannot be deployed or modified. This article explains what caused this issue, what was fixed, and what to do if you are still affected. ⚙️ What Caused the Issue Engineering identified two root causes that prevented schemas from moving out of manual review: - Invalid data types for image dimensions: ImageObject schemas had width and height values stored as strings instead of the required numeric format. This caused schema validation to incorrectly block deployment of otherwise valid schemas. - Missing review or rating data: Certain schemas were flagged for manual review when the pages they were associated with lacked review or rating data. Once in review, the schemas could not be deployed or corrected — even after regeneration, no fields were presented to fix. These issues were confirmed by engineering and tracked internally. The underlying bugs have been fixed and the fix is live in production. ✅ What Was Fixed Engineering resolved the schema validation logic that was incorrectly blocking valid schemas from deploying. Specifically: - The validation error caused by string-formatted width/height values in ImageObject schemas has been corrected. - Schemas stuck in review due to absent review or rating data can now progress through the deployment pipeline without being blocked. Following the fix, affected schemas were manually reprocessed by the engineering team to regenerate and redeploy the pending queue. 🚀 What You Should Do Now If you experienced this issue, follow these steps to confirm your schemas are now deploying correctly: 1. Log in to your Search Atlas account and navigate to the OTTO section of your dashboard. 2. Check the status of your pending schemas. Schemas that were previously frozen in manual review should now show an updated status. 3. If schemas were recently reprocessed, allow a short period for the deployment queue to clear and for statuses to refresh. 4. Attempt to deploy any remaining schemas that are still in a pending or review state. If the option is now available, proceed with deployment as normal. 5. Verify that your deployed schemas are returning correctly by checking the relevant pages or using a schema validation tool of your choice. ⚠️ If Schemas Are Still Stuck The fix is live, but if your schemas are still showing as frozen in manual review or still not deploying after following the steps above, your account may need a manual reprocess triggered by our team. This is not something you can initiate yourself — our support team handles it 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. 💡 Tips to Avoid Schema Issues - Ensure that pages associated with schemas have sufficient structured data, including review and rating information where applicable, before initiating deployment. - If a schema enters manual review and presents no fields to correct after regeneration, do not attempt repeated deployments — contact support so the issue can be escalated to engineering promptly. - Monitor your schema statuses after bulk deployments to catch any that stall early.

🔧 Troubleshooting OTTO Schema Update Errors

📋 Overview When updating a schema for a page in OTTO SEO automation, you may encounter errors that prevent you from saving or modifying your schema configuration. This article helps you identify whether you have an update error (during creation or modification) or a deployment error (during publishing), so you can troubleshoot the right issue. 🎯 What is a Schema Update Error? A schema update error occurs before you publish. It prevents you from saving changes to your schema configuration. Common causes include invalid field values, missing required fields, permission restrictions, or API rejections during modification. The schema is stuck in draft or editing mode and cannot be saved. 🎯 What is a Schema Deployment Error? A schema deployment error occurs during or after publishing. Your schema saves correctly, but fails to go live on your page. Common causes include a disconnected OTTO pixel, network timeouts, or pending approval states. If your schema saves but won't publish, that is a deployment issue, not an update issue. 🔍 Identify Your Error Type Ask yourself: Can I save my schema changes to the draft? If no, follow the Update Error steps below. If yes but your schema won't publish, see our Schema Deployment Errors article instead. ✅ Fix Schema Update Errors 📌 Step 1: Check Required Fields - Open the schema editor for your page in OTTO SEO automation. - Look for fields marked with a red asterisk (*) or red outline. - Fill in all required fields with valid data. - Attempt to save again. 📌 Step 2: Validate Field Formats Ensure all fields match their expected format: - URLs: must start with http:// or https:// - Numbers: no letters or special characters unless specified - Dates: must follow YYYY-MM-DD format - Email: must contain @ and a valid domain - Phone: must follow your region's standard format Correct any mismatched values and save. 📌 Step 3: Check Your User Permissions If the error mentions "permission denied" or "unauthorized," your account may lack schema editing rights. Contact your workspace admin to confirm you have editor or admin access to this page's schema. 📌 Step 4: Clear Your Browser Cache Stale cache can cause validation errors. Clear your browser cache and cookies, then refresh the page. Log back in and try updating the schema again. 📌 Step 5: Try a Simpler Change Make a small, obvious change to one field (such as adding a single character to a text field), then save. This helps isolate whether the error is field-specific or system-wide. If the simple change saves, the issue is with your original data. 📌 Step 6: Export and Reimport If the schema remains stuck: 1. Export your current schema configuration (if your platform provides this option). 2. Create a new schema from scratch for the same page. 3. Manually re-enter your data using the exported values as reference. 4. Save and test. ❌ Schema Update vs. Deployment: Quick Reference Update Error: Error appears when you try to save or modify the schema. Schema is in draft or editing mode. You cannot proceed to publish. Deployment Error: Schema saves correctly. Error appears when you publish or during publishing. Schema is pending or failed to go live on the page. If you can save your schema but it will not publish, do not follow the steps above. Instead, consult our Schema Deployment Errors article or contact support. 🚀 Next Steps Once your schema saves successfully, you can publish it to your page. If publishing fails, visit our deployment troubleshooting guide. 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.

🔧 Fix a Grayed-Out Schema Deploy Button

Overview After running AI schema generation in Search Atlas, you may notice the Deploy button remains grayed out and unclickable. This is a known issue that our support team can investigate and resolve on your account. Why This Happens The Deploy button may remain grayed out when the schema generation process does not complete successfully, leaving no valid schema available to deploy. The exact cause can vary by account and page configuration. What to Do Because the specific cause needs to be identified on a per-account basis, please reach out to our support team directly. When you contact us, please have the following ready so we can resolve this as quickly as possible: - Your project or site name in Search Atlas - The exact page URL where the Deploy button is grayed out - Any error messages you see on screen (exact wording, if any) - A screenshot of the grayed-out button if possible - The steps you have already tried (e.g., refreshing the page, re-running generation) 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.

🛠️ Fix BreadcrumbList Schema Errors in Search Atlas

🔍 Overview If Google Search Console is flagging BreadcrumbList structured data errors or Review snippet issues on your site, the most common cause is an incorrect or missing URL field in your schema markup. This article explains how to approach fixing those errors in Search Atlas, connecting Google Ads, and resolving structured data warnings reported by Google Search Console. 📋 Before You Begin - Make sure your site is added and verified in Search Atlas. - Have Google Search Console open in a separate tab so you can cross-reference the specific errors being reported. - Confirm you have Editor or Admin access in your Search Atlas workspace. 🗂️ Step 1 — Locate Your Site in Search Atlas 1. Log in to Search Atlas. 2. Find your site in the site list and click its name to open the site dashboard. 🔗 Step 2 — Navigate to Schema Settings 1. From your site dashboard, locate the schema or structured data tools available for your site. 2. Find the BreadcrumbList schema associated with the page or pages flagged in Google Search Console. ✏️ Step 3 — Update the URL Field in BreadcrumbList Schema The BreadcrumbList schema requires every ListItem to contain a valid, absolute URL in its item property. A missing, relative, or malformed URL is the most frequent cause of Google Search Console errors. 1. Open the BreadcrumbList schema entry for editing. 2. Review each ListItem in the breadcrumb sequence. Each item should have a Name field and a URL field. 3. Ensure each URL value is an absolute URL — it must begin with https:// and match the exact canonical URL of that page. 4. Common issues to fix in the URL field: - Relative paths such as /toys/ — replace with the full absolute URL. - Trailing slash inconsistency — match the format used in your sitemap and canonical tags. - Typos or extra characters in the domain name. - HTTP URLs on an HTTPS site — always use https://. 5. After correcting each URL field, save your changes to apply them. 6. If your BreadcrumbList schema is deployed site-wide via a template, update the URL pattern in the template so all pages inherit the corrected format. 📊 Step 4 — Validate Your Changes 1. After saving, use Google Search Console's Rich Results Test or the URL Inspection tool to confirm the BreadcrumbList errors are resolved. 2. If Review snippet errors were also reported, check that your Review schema includes all required fields (such as ratingValue and reviewCount) and that the schema is properly associated with the correct page. 🔗 Step 5 — Connect Google Ads (if applicable) If your workflow also requires connecting Google Ads as part of schema deployment or site metrics setup, follow these steps: 1. Navigate to the integrations or connected accounts section of your Search Atlas workspace settings. 2. Select Google Ads and follow the on-screen prompts to authorize the connection using your Google account credentials. 3. Once connected, verify that data is flowing correctly by checking the relevant reporting or metrics area within Search Atlas. 4. If you encounter an error during the Google Ads connection process, note the exact error message displayed and the timestamp, as these will be needed if you require further support. ⚠️ If You Cannot Locate the Schema or Google Ads Settings Because Search Atlas is actively developed, the exact location of schema tools and integrations may vary depending on your plan or workspace configuration. If you cannot find the areas described above, please have the following ready before reaching out to support: - Your site name and the URL(s) flagged in Google Search Console. - The exact error message(s) shown in Google Search Console. - A screenshot of the error and the page(s) affected. - Whether you are trying to connect Google Ads, deploy schema, or troubleshoot structured data warnings — or a combination of these. 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.

🔧 Troubleshooting AI Schema Generation Delay False Negatives

This article addresses a situation where AI-generated page-level schemas appear to complete successfully — credits are deducted and the platform confirms generation — but no schema output is visible when you check your pages. If you are experiencing this, the steps below will help you gather the information needed to resolve it. 🔍 Common Causes - Processing lag: Large batch jobs can take several minutes to fully propagate. The platform may confirm the job before all outputs are written. - UI cache: The page you are viewing may be showing a cached state from before the generation completed. - Partial job failure: In rare cases, the generation job starts and deducts credits but encounters an error mid-batch, leaving some or all pages without output. 🛠️ Step-by-Step 1. Wait a few minutes before taking further action. A delay between the confirmation message and results appearing in the interface is possible. Do not retry immediately. 2. Hard-refresh the page. Press Ctrl + Shift + R (Windows/Linux) or Cmd + Shift + R (Mac) to bypass the browser cache and reload the current view with fresh data. 3. Navigate away and return. Open a different section of the platform, then navigate back to the schema results page. This prompts the interface to load the latest data. 4. Check whether schema outputs have appeared. Return to the page or section where you submitted the generation request and look for any schema entries associated with the pages you submitted. 5. If outputs are still missing, do not retry the batch yet — a duplicate run may deduct additional credits. Instead, note the exact time of generation and the number of pages submitted, and contact our support team with that information. ✅ What to Have Ready When You Contact Support - The exact date and time you submitted the generation job. - The number of pages included in the batch. - A description of what you see in the platform (e.g., confirmation message received, but no schema output visible). - Your current credit balance, so our team can verify whether a credit adjustment is needed. 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.

🔧 How to Fix an Incorrect Page-Level Schema Type

This article explains what to do when the automatically generated schema assigns the wrong page type to your content. Based on known platform behavior, the schema page type is determined by AI inference and cannot be manually changed through a user-facing setting. Triggering another crawl is unlikely to resolve the misclassification, as pages with mixed or ambiguous signals may be consistently assigned an incorrect type. 📍 What This Means for You If your page has been assigned an incorrect schema page type, this is a platform limitation — there is currently no confirmed self-serve workflow that allows you to override the AI-assigned schema type directly within the tool. Attempting to retrigger a crawl will not reliably fix the misclassification. 🛠️ How to Get This Resolved Because the schema page type cannot be manually changed, the resolution requires direct assistance from our support team. To help us investigate and act on your request as quickly as possible, please have the following ready before reaching out: - The exact URL(s) of the affected page(s) - The schema type currently being assigned (the incorrect one) - The schema type you expect or need for that page - The project name in Search Atlas where the issue is occurring - Any relevant screenshots or error details showing the misclassification Having this information ready will allow our team to investigate the AI classification behavior for your specific page and take the appropriate backend action. 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.

🗺️ Fix Incorrect Google Maps URL in OTTO Schema

🔍 Overview If your OTTO project contains a sameAs schema array with a Google Maps URL pointing to the wrong business location, this guide explains why it happens and what steps to take to get it corrected. Because the field is read-only inside the platform, resolving this issue requires action from the Search Atlas support team. ⚠️ What This Issue Looks Like You may notice this problem when reviewing your structured data or schema output for a site managed in OTTO. Common signs include: - The sameAs field in your Local Business schema contains a Google Maps URL referencing an incorrect city or region. - The Google Maps link points to a completely different location than your business address. - The field is locked, preventing you from editing it directly inside the OTTO project. 💡 Why This Happens OTTO builds and caches schema data automatically based on the business information available at the time the project is created or last synced. In some cases, an incorrect Google Maps URL can become hardcoded in the schema cache if: - The source business data contained an error at the time of the initial schema build. - A previous Google My Business listing or map entry was linked to the wrong location. - The schema cache was not refreshed after a business address or Maps URL was updated. Because schema fields in OTTO are validated and locked to protect structured data integrity, these values cannot be edited directly by users once they are set. 🛠️ How to Resolve the Issue Follow these steps to report and fix a locked incorrect Google Maps URL in your OTTO schema: 1. Confirm the correct Google Maps URL. Open Google Maps, search for your business by name and address, and copy the full, accurate URL from the browser address bar. Make sure it resolves to the correct physical location. 2. Locate your OTTO project. Find the affected site in your OTTO project list. 3. Note the domain and incorrect URL. Record the exact domain name of the affected site and the incorrect Google Maps URL currently shown in the sameAs schema field. 4. Contact support via the chat widget. Share the domain name, the incorrect URL, and the correct replacement URL with the support team. The support team will manually update the database record and rebuild the schema cache for that project. 📋 Information to Have Ready To help the support team resolve your request as quickly as possible, prepare the following before opening the chat: - The full domain name of the affected OTTO project. - The incorrect Google Maps URL currently appearing in the sameAs schema field. - The correct Google Maps URL you want to replace it with. - Any relevant context about when the mismatch was first noticed or what may have caused it. 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.

🛠️ Fix FAQ Schema Deployment Errors in OTTO

🔍 Overview When deploying a Knowledge Based Trust (KBT) FAQ schema through OTTO SEO, you may encounter a deployment error that reads something like "questions should have answers" — even when every Q&A pair appears to have an answer filled in. This article explains why this happens and how to resolve it. ⚠️ Why This Error Occurs This error is most commonly caused by one of the following issues, even when the FAQ fields look complete on screen: - Hidden empty entries: A blank Q&A row exists in your list that is not immediately visible. OTTO validates every row, including ones you may have accidentally added and left empty. - Whitespace-only answers: An answer field contains only spaces or line breaks, which OTTO does not count as valid content. - Unsaved edits: Changes made to an answer were not saved before deployment was triggered, leaving the stored value empty. - Special characters in answers: Certain characters (such as unmatched quotation marks or HTML tags) can cause a field to be rejected during schema validation. - Answer field character limit: Answers that exceed the allowed character limit may be silently truncated or rejected, resulting in an effectively empty value at the schema level. 🛠️ How to Resolve the Error 1. Open your FAQ schema in OTTO SEO and navigate to the Q&A section for the affected page. 2. Scroll through every Q&A entry — including any rows below the fold. Look for any row where the answer field is blank, contains only spaces, or shows placeholder text. 3. Delete any empty or incomplete rows by clicking the remove/delete icon next to that entry. You do not need a minimum of 8 Q&As remove any that are not fully complete. 4. Check each remaining answer to confirm it contains real, readable text with no leading or trailing whitespace. 5. Re-save each Q&A entry individually by clicking the save or confirm button on that row before proceeding. 6. Attempt deployment again once all entries are confirmed complete and saved. 💡 Tips to Prevent This Error - Always save each Q&A row immediately after entering the answer — do not rely on a single bulk save before deployment. - Avoid copying and pasting text from Word or Google Docs without first pasting it into a plain-text editor to strip hidden formatting characters. - Keep answers between 50 and 300 characters as a safe range to stay within schema validation limits. - Review your FAQ list one final time before clicking Deploy to catch any overlooked empty rows. ❓ Frequently Asked Questions I can see answers in all 8 rows — why is OTTO still rejecting the deployment? Scroll down to check whether a 9th or later row exists below the visible area. Even a single empty row will trigger the validation error for the entire schema block. Delete any incomplete rows and redeploy. Will deleting empty rows affect my live FAQ schema? No. Removing an empty row that was never successfully deployed will not affect any content currently live on your website. Only fully deployed Q&As are written to your schema. Does the order of Q&A pairs matter for deployment? The order does not affect whether deployment succeeds, but it does control the sequence in which questions appear in your FAQ schema markup. Reorder entries as needed before deploying. 📞 Still Need Help? If you have followed all the steps above and the deployment error persists, our team is ready to investigate further. 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.

🔧 Fix OTTO Auto-Generated Incorrect Schema Markup

Why Is OTTO Adding the Wrong Schema? OTTO generates schema markup automatically based on its built-in AI defaults. When no custom prompt exists for a project, OTTO has no context about your business type, industry, or goals — so it falls back on generic or statistically common schema types. In some cases, this results in incorrect schema suggestions being applied to businesses that have nothing to do with the suggested schema type. This is not a bug. It is expected default behavior when OTTO lacks the business-specific context it needs to make accurate recommendations. The fix is to configure a custom OTTO prompt that tells OTTO exactly what your business does. Important: OTTO Prompts vs. Content Genius Custom OTTO prompt settings apply only to the OTTO dashboard and the automations OTTO runs within it. These settings do not affect Content Genius or any other tool in Search Atlas. If you use Content Genius, you will need to manage context and instructions separately within that tool. Step 1 — Configure a Custom OTTO Prompt Adding a custom prompt gives OTTO the business context it needs to generate accurate schema, meta tags, and other SEO recommendations. To configure your custom prompt for an affected project, navigate to the OTTO dashboard and look for the project settings or prompt configuration area. Once you locate the custom prompt field, enter a clear, specific description of the business. Include details such as: - Business type and industry (for example, "This is a licensed plumbing company serving residential customers") - Primary services or products - Target audience - Any schema types that are not relevant to the business Save your prompt, then repeat this process for every project that is showing incorrect schema suggestions. Tip: The more specific your custom prompt, the more accurate OTTO's recommendations will be. Two to four sentences covering business type, services, location, and exclusions will produce the best results. Step 2 — Delete Incorrect Auto-Generated Schema After saving your custom prompt, remove any incorrect schema that OTTO has already deployed. In the OTTO dashboard, look for the schema management area where auto-generated schema markup is listed. From there, select the incorrect schema entries and delete them so they are no longer applied to your pages. If you are unable to locate the custom prompt configuration or schema management area within the OTTO dashboard, please reach out to our support team for guided assistance. When doing so, have the following ready: your project name, the incorrect schema type(s) being generated, and any relevant page URLs where the incorrect schema appears. 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.

OTTO Schema Not Appearing in Google Rich Results

🔍 Overview When OTTO deploys schema markup, it should appear on your live site and pass Google's Rich Results Test. If you're seeing the wrong schema type or if the schema isn't showing up at all, this is a known issue that requires investigation by our support team. ⚙️ What May Be Happening OTTO schema deployment not appearing in Google Rich Results is a bug-category issue. The root cause can vary depending on your site configuration, and our team will need to investigate your specific setup to identify what is preventing the schema from appearing or validating correctly. 📋 What to Have Ready When You Escalate To help our team resolve this as quickly as possible, please have the following information ready before reaching out: - The exact URL of the page where schema is not appearing. - The schema type you expected OTTO to deploy (e.g., Product, Article, FAQ). - The schema type that is actually appearing, if any (e.g., WebPage, or nothing at all). - A screenshot or copy of the result from Google's Rich Results Test for that URL. - The name of your OTTO project and the date/time you first noticed the issue. - Any recent changes made to the page or site (content updates, plugin changes, theme changes) that may be relevant. 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.

🔧 OTTO Activity Tab Errors and Schema Rollback

🗺️ What This Article Covers This article explains two issues you may encounter in OTTO (OTTO SEO): an error on the Activity or Work Summary tab that asks you to contact support, and how to roll back AI-generated JSON-LD schema changes and export a change log for your project. Both issues are common and usually self-resolvable in a few steps. ​ ⚠️ Why the OTTO Activity Tab Shows a "Contact Support" Error The most common cause of the OTTO Activity tab or Work Summary export throwing a "Something went wrong. Please contact support" error — or loading indefinitely — is a missing or disconnected Google Search Console (GSC) connection on your project. OTTO relies on live GSC data to populate the Activity tab and generate the Work Summary export. If GSC is not linked, or the OAuth token has silently expired, OTTO cannot retrieve the data it needs and will display this error. Other causes include a briefly expired GSC OAuth token (where the connection appears active but has lost authorisation in the background) or a short-lived platform sync delay. Always check your GSC connection status before contacting support — it resolves the error in the vast majority of cases. ​ 🔌 Step 1 — Check and Reconnect Your GSC Integration 1. Navigate to Left sidebar → OTTO SEO → Installation Guide. 2. Select your project from the project selector at the top of the page. 3. Scroll to the Google Search Console section and confirm whether your GSC property shows a green Connected status. 4. If the status is Not Connected, Disconnected, or missing entirely, go to Site Metrics → (GSC page) and click Connect GSC Account to complete the OAuth authorisation prompts to re-link the property. 5. Once reconnected, allow 2–5 minutes for OTTO to sync your GSC data, then return to the Activity tab and refresh the page. ✅ Step 2 — Confirm the Activity Tab Now Loads After reconnecting GSC, navigate to Left sidebar → OTTO SEO → Overview and select your project from the project selector. Click the Activity (also labelled Work Summary) tab. The tab should now display your full OTTO task history without any error. If the error persists after reconnecting GSC and waiting 5 minutes, try clearing your browser cache or switching to a different browser before contacting support. ​ ↩️ Step 3 — Roll Back AI-Generated JSON-LD Schema Changes If OTTO has deployed JSON-LD structured data markup to your project and you need to revert those changes, follow these steps: 1. Navigate to Left sidebar → OTTO SEO → All Sites → Select your project → Tasks. 2. Select your project from the project selector at the top of the page. 3. In the task list, filter or search for tasks of type Schema or JSON-LD to locate the recently deployed changes. 4. Click the specific task you want to revert to open its detail panel. 5. Select the Rollback or Undo option within the task detail panel and confirm the action when prompted. 6. Repeat for each schema task you need to revert. Important: Rolling back a task removes the AI-deployed schema markup from the affected pages. This action is not automatically reversible — confirm you want to revert before proceeding. If you need to re-deploy the same schema later, you can do so again from Left sidebar → OTTO SEO → All Sites → Select your project → Tasks. ​ 📤 Step 4 — Export the Work Summary (Change Log) To download a full timestamped log of all OTTO activity — including schema deployments, rollbacks, and other AI-driven changes — for your project: 1. Navigate to Left sidebar → OTTO SEO → Overview and select your project from the project selector. 2. Click the Activity (or Work Summary) tab. 3. Click the Export Work Summary button in the top-right area of the tab. 4. The downloaded file will contain a complete timestamped log of every task OTTO has applied to your project, which you can use as a change log for review or handoff. Note: If the Export Work Summary button returns a "Something went wrong" error, this is almost always caused by the missing GSC connection described in Step 1. Reconnect GSC first, then retry the export. ​ 🔍 Quick Troubleshooting Checklist - Activity tab loading indefinitely or throwing an error? Check your GSC connection at Left sidebar → OTTO SEO → Installation Guide. - "Something went wrong. Please contact support" on the Work Summary export? Reconnect GSC at Left sidebar → OTTO SEO → Installation Guide, wait 2–5 minutes, and retry. - Need to see a complete log of every change OTTO made? Go to Left sidebar → OTTO SEO → Overview → Activity tab and click Export Work Summary. - Need to roll back specific JSON-LD schema changes? Go to Left sidebar → OTTO SEO → Tasks, filter by Schema type, and use the Rollback option on each relevant task. - Export still failing after reconnecting GSC? Clear your browser cache or switch browsers, then retry before contacting support. 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.

🔧 Fix Bulk Schema Deployment and OG Descriptions in OTTO SEO

Overview Two common questions from OTTO SEO users involve bulk schema deployment and the OG description field. This article explains what each one means and what to do if you are experiencing issues with either. What Is OG Description? OG description stands for Open Graph description. It is a short text snippet that controls how your page appears when shared on social media platforms such as Facebook and LinkedIn. It is part of your page's on-page metadata and is separate from your standard meta description, though both describe your page content. If you are unsure how OG description applies to your specific setup in OTTO SEO, or if the field is behaving unexpectedly, our support team can review your account and clarify how it is being used. Bulk Schema Deployment in OTTO SEO OTTO SEO allows you to generate schema markup for multiple pages at once. If you are experiencing issues with bulk-generated schemas — such as schemas that appear to disappear or do not behave as expected — this is something our support team can investigate directly on your account. Because the specifics of bulk schema behavior can vary depending on your site configuration and account state, there is no single universal self-serve fix. The most reliable next step is to contact our team so they can review what happened and guide you through completing your deployment correctly. When reaching out, please have the following ready: - The name of the project or domain where you are working - A description of what you attempted (e.g., generating schemas for multiple pages at once) - What you observed — for example, schemas that were generated but later could not be found - Any error messages or unusual behavior you noticed, with approximate timestamps if possible 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.

Troubleshoot Schema Markup Errors in Search Atlas

Overview Schema markup added through Search Atlas should appear in your page source as valid JSON-LD. If you followed the setup steps but the schema is missing or returning an error, this article explains the most common causes and what to check in your Brand Vault settings. Common Reasons Schema Markup Fails - Incorrect configuration in Brand Vault: The JSON-LD block or entity details may have been entered in the wrong area or left incomplete. - Malformed JSON syntax: A missing comma, bracket, or quotation mark breaks the entire schema block. - Knowledge Graph fields left incomplete: Required entity fields were skipped, preventing the schema from generating correctly. - Page not yet re-crawled: The schema was saved correctly but the page source reflects a cached version. - Conflicting schema on the page: An existing schema block on your site is overriding or duplicating the one set in Search Atlas. What to Check in Brand Vault 1. Open Brand Vault from the header apps-grid icon → More Features → Brand Vault. 2. Verify your schema entry. Confirm that the JSON-LD block has been entered in the correct area of Brand Vault for the service page you are testing, and that the URL associated with it matches the page you are checking. 3. Validate the JSON-LD syntax. Copy your schema text and paste it into a JSON validator such as jsonlint.com or the Google Rich Results Test. Common issues include: missing closing braces }, unmatched quotation marks, trailing commas after the last property, and incorrect nesting of @type values. 4. Correct and re-save the schema. If errors are found, fix the JSON and re-enter the corrected version in Brand Vault, then save your changes. 5. Review Knowledge Graph settings. Within Brand Vault, ensure all required entity fields are filled in for your business type. Incomplete Knowledge Graph data can prevent schema from rendering even if the JSON-LD block itself is valid. Complete as many fields as possible. 6. Test the page source. After saving, open the service page URL in a browser, right-click, and select View Page Source. Use Ctrl+F (or Cmd+F on Mac) and search for application/ld+json to confirm the schema block is present. 7. Check for caching delays. If the schema does not appear immediately, allow time for the page to be re-crawled or clear your site cache and test again. 8. Check for conflicting schema. If a schema block already exists on your site outside of Search Atlas, it may conflict with or override the one you configured. Review any existing structured data on the page. If the Issue Persists If you have verified your Brand Vault configuration, corrected any JSON syntax errors, completed all Knowledge Graph fields, and confirmed the page is not cached — but the schema still does not appear in the page source — please reach out to our support team. To help us investigate quickly, have the following ready: the exact service page URL, the JSON-LD block you entered, and a screenshot or copy of the page source showing the missing schema. 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.

🛠️ Fix Schema Failures, Billing & Refund Issues

Overview This article covers three common issues that sometimes occur together: schema markup failing to deploy, charges appearing after a subscription cancellation, and how to request a refund for disputed invoices. Read through the relevant section below to understand your situation and take the right next step. Schema Deployment Failures Schema deployment can fail for several reasons. Common causes include: - OTTO SEO not activated on the site: Schema deployment requires OTTO SEO to be active on the target domain. Verify that OTTO SEO is enabled for your site before attempting to deploy schema. - Google Search Console not connected: OTTO SEO requires a verified Google Search Console connection. Check that your GSC account is properly linked and shows no errors. - Conflicting schema on the page: If duplicate schema already exists in your site theme or another plugin, OTTO may detect a conflict and pause deployment. Remove or disable the conflicting schema source and retry. - Inactive or paused subscription: Schema deployment is a paid feature. If your subscription has lapsed, deployments may not publish until your plan is reactivated. - Unsupported schema type for the page: Certain schema types require specific page attributes. Make sure the page content matches the schema type you have selected. After addressing the relevant cause above, retry the schema deployment from within the OTTO SEO tool. If the issue persists, please reach out to our support team with your site URL, the schema type you are trying to deploy, and a description of the error you are seeing. Charged After Canceling Your Subscription If you see a charge after canceling, consider the following: - Cancellation timing: Search Atlas bills at the start of each billing cycle. If you canceled after your renewal date, the charge for that cycle may have already processed. Cancellation stops future renewals — it does not automatically reverse a charge that has already been made. - Cancellation may not have completed: A cancellation is only confirmed when you receive a confirmation email from Search Atlas. If you did not receive one, your subscription may still be active. Log in to your account and check your subscription status. - Multiple workspaces or add-ons: If your account includes additional workspaces or add-ons, these may generate separate charges. Review your invoices in your account billing section to identify which item generated the charge. If you believe you were charged in error, gather the relevant invoice details (invoice number, charge date, and amount) and contact our support team to open a refund dispute. Requesting a Refund for a Disputed Invoice If you would like to dispute a charge or request a refund, gather your invoice number, charge date, and the amount in question before reaching out. Our support team will review the details and advise on next steps in line with our refund policy. 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.

🔧 Fix OTTO Project Activation and Schema Deployment Errors

Overview If your OTTO project fails to activate or you receive an error when trying to deploy schemas, this article explains what to do next. Because the specific causes of OTTO activation and schema deployment errors can vary and require investigation on the backend, the steps below are designed to help you gather the right information before reaching out to our support team. What to Check Before Contacting Support Before escalating, run through the following to help our team investigate faster: - Note the exact error message you are seeing (for example, 'unable to process request' or any other specific wording). - Identify which OTTO project is affected — have the project name and the associated website URL ready. - Note the approximate date and time when the error first occurred. - Try refreshing your browser and attempting the action again. If the error persists after a refresh, it is unlikely to resolve on its own. - Check whether the issue affects one specific project or all projects in your account, and note that detail when you reach out. What to Have Ready When You Escalate Our support team will need the following details to investigate your OTTO activation or schema deployment error: - Your account email address and the name of the affected workspace. - The exact error message displayed when the failure occurs. - The name of the affected OTTO project and the website it is connected to. - A screenshot or screen recording of the error if possible. - The timestamp of when the error occurred. 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.

🍞 Fix Missing Item URL in Breadcrumb Schema

🔍 What Is This Issue? When MetaSync generates a BreadcrumbList schema on custom taxonomy archive pages (such as category, tag, or custom taxonomy archives), it may omit the item URL property from one or more breadcrumb list elements. Google Search Console flags this as a "Missing field item" error in the Rich Results report, which can prevent your breadcrumbs from appearing in search results. This typically affects pages like /blog/category/news/ or any archive URL tied to a custom taxonomy, where the taxonomy label is included in the breadcrumb trail but its corresponding URL is not passed through to the schema markup. ⚠️ Why Does This Happen? The BreadcrumbList schema requires every ListItem to include three properties: - @type — set to ListItem - position — the numeric order of the item in the trail - item — an object containing the @id (URL) and name of that breadcrumb step On taxonomy archive pages, MetaSync may resolve the taxonomy label correctly but fail to attach the corresponding archive URL to the item property. The result is a ListItem entry with a name but no URL, which Google treats as invalid markup. 🛠️ How to Fix the Missing Item URL Follow the steps below to manually correct the breadcrumb schema for your taxonomy archive pages using the Search Atlas Schema module. 1. Log in to Search Atlas and navigate to the Schema Creator by clicking the apps-grid icon in the header, then selecting More Features → Schema Creator. 2. Search for the taxonomy archive page that is generating the error (for example, a category or custom taxonomy archive URL). 3. Open the existing BreadcrumbList schema for that page. If no schema exists, create a new one by selecting BreadcrumbList from the schema type menu. 4. Locate the ListItem entry that corresponds to the taxonomy label (this is the step missing its URL). 5. In the item field for that ListItem, enter the full absolute URL of the taxonomy archive page — for example, https://yourdomain.com/blog/category/news/. 6. Confirm that every ListItem in the breadcrumb trail has a valid name, position, and item URL populated. 7. Save the schema and use the Google Rich Results Test (search.google.com/test/rich-results) to validate the updated markup before resubmitting in Search Console. ✅ How to Verify the Fix in Google Search Console 1. Go to Google Search Console and open the Enhancements section in the left menu. 2. Select Breadcrumbs to view the current error report. 3. Click on the "Missing field item" error to see affected URLs. 4. After applying the fix in Search Atlas, click Validate Fix next to the affected URLs. 5. Google typically re-crawls and updates the status within a few days to two weeks. 🧩 Additional Notes - If you are using Rank Math or another SEO plugin alongside MetaSync, check that both tools are not outputting competing BreadcrumbList schemas on the same page. Duplicate or conflicting schema blocks can cause further validation issues. Disable breadcrumb schema output from the third-party plugin if MetaSync is your primary schema tool. - Custom taxonomy archives sometimes require the breadcrumb trail to be configured manually, as MetaSync cannot always resolve dynamic archive URLs automatically. - If your breadcrumb schema was previously generating valid markup and stopped after a recent update, check the Schema module for any unsaved changes or reset configurations. 💬 Need More Help? 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.

🛠️ Fix JobPosting Schema Errors on Non-Job Pages

🔍 Overview If Google Search Console is flagging JobPosting schema errors on pages that are not job listings — such as city-level service pages or location landing pages — this is a known schema deployment issue. Incorrect schema associations can confuse Google's crawlers, suppress rich result eligibility, and contribute to traffic drops across multiple pages. This article explains why this happens and how to fix it using OTTO SEO. ⚠️ Why This Happens There are several reasons why JobPosting schema may appear incorrectly on non-job pages: - Stale schema type display: After pasting a new schema JSON and deploying, the schema list may still show the old schema type (for example, "Organization" or "JobPosting") instead of the updated one. The label is outdated even though a different schema was deployed. - Schema shown as deployed without generation: In some cases, OTTO may display a schema as deployed at the page level even if no schema was intentionally generated or pushed to that page. - Validation suppression conflicts: When deploying with validation suppressed, the system may return an is_approved: false status for schemas that were found on the page, causing confusion about what is actually live. Any of these conditions can result in the wrong schema type being associated with pages across your site — including high-volume city-level pages — which Google may then flag as errors. 🔎 How to Identify Affected Pages 1. Go to the left sidebar and select OTTO SEO → SEO Automation (URL: /seo-automation-v3). 2. Open the site that contains the affected pages. 3. Navigate to the Schema section within OTTO. 4. Review the schema type listed for each page. If city pages or non-job pages show JobPosting as their schema type, they are incorrectly flagged. 5. Cross-reference with Google Search Console under Enhancements → Job Postings to confirm which URLs are being flagged. 🛠️ How to Fix Incorrect JobPosting Schema Follow these steps to remove or correct the schema on affected pages: 1. In OTTO SEO, locate the affected page in the schema list. 2. Check the schema JSON that is currently associated with the page. If it contains @type: JobPosting and this page is not a job listing, the schema needs to be replaced or removed. 3. Paste the correct schema JSON for that page type (for example, LocalBusiness or Service schema for city-level pages). 4. Before deploying, confirm the schema type label in the list has updated to reflect the new JSON. If it still shows the old type, refresh the page and check again. 5. Use the per-row validation bypass option if the schema fails validation but you are confident the JSON is correct. A warning will appear — review it before proceeding. 6. Deploy the corrected schema to the page. Important: After deploying, wait 24–48 hours and then re-check Google Search Console to confirm the JobPosting errors have cleared for those URLs. 🚫 How to Remove Schema Entirely from a Page If a city-level page should not have any structured data deployed through OTTO, you can remove the schema row entirely: 1. In the OTTO SEO schema list, find the affected page row. 2. Select the row and choose the option to delete or unassign the schema. 3. Confirm the removal and redeploy so the page is no longer associated with any schema through OTTO. This ensures Google will no longer detect a JobPosting signal on that page, which should resolve the Search Console error over time. 📊 Monitoring Recovery Across City Pages Once corrections are deployed, monitor progress using these steps: - In Google Search Console, use the URL Inspection Tool to request re-indexing for your most important city pages. - Check the Enhancements report weekly to track the decline in JobPosting errors. - Within Search Atlas, use Left sidebar → AI Visibility → Visibility to monitor any traffic recovery trends at the domain or page level. ✅ Best Practices to Prevent This Issue - Always verify the schema type label in the OTTO schema list matches the JSON you intend to deploy before clicking deploy. - Only apply JobPosting schema to pages that genuinely list job openings with required fields (title, hiringOrganization, jobLocation, datePosted). - For location or city pages, use LocalBusiness, Service, or WebPage schema types instead. - After any bulk schema deployment, spot-check a sample of URLs in Google Search Console to catch mislabeled schema early. 💬 Need More Help? 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.

🛠️ OTTO Schema Deploy All Button and Pending Items

🔍 Overview The Deploy All button in OTTO SEO lets you push multiple schema tasks to your site at once. However, customers sometimes notice that after clicking Deploy All, certain schema tasks remain in a pending state or the task counter does not update as expected. This is a known issue that requires investigation by our support team. ⚙️ How the Deploy All Button Works The Deploy All button is designed to deploy all schema tasks that are currently eligible for deployment. The pending counter reflects the number of schema tasks that still need action and should update as tasks are processed. ⚠️ Known Issue: Tasks Remaining Pending After Deploy All Some customers have reported that after clicking Deploy All, one or more schema tasks remain in a pending state or the counter does not reflect the expected change. This behavior has been identified as a bug and is handled on a case-by-case basis by our engineering team. This is not something that can be resolved through standard troubleshooting steps on your end. Our team will need to investigate your specific project to determine the cause. 📋 What to Have Ready When You Escalate To help our team resolve this as quickly as possible, please have the following information ready before reaching out: - Project name or the site URL affected - Exact number of tasks showing as pending after clicking Deploy All - Screenshot of the pending task counter and schema task list - Timestamp of when you clicked Deploy All and first noticed the issue - Any recent changes made to the site (plugin updates, theme changes, etc.) around the time the issue began 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.

🛠️ Fix OTTO Stale Organization JSON-LD on Pages

🔍 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.

🔧 Fix OTTO Schemas Stuck in Not Deployed

🔍 What This Article Covers If your OTTO schemas show SYNC_COMPLETE but remain stuck in a Not Deployed status, this article explains why that happens and what you need to do to get them deployed successfully. ⚙️ Why Schemas Get Stuck in Not Deployed A SYNC_COMPLETE status means OTTO has successfully synced your schema data from your site. However, syncing is only the first step. Before OTTO can deploy a schema to your pages, it validates that all required fields for that schema type are populated with real data. For Product schemas, the most common reason deployment stalls is that one or more of these required fields are empty or incomplete: - review — at least one customer review must be present - aggregateRating — a valid aggregate rating value (e.g., 4.5 out of 5 based on 30 reviews) must exist - name — the product name must be populated - offers — pricing and availability details must be present If any required field is missing, OTTO cannot produce a valid schema that meets Google's structured data guidelines, so it holds the schema in Not Deployed rather than pushing broken markup to your site. 🛠️ How to Fix Schemas Stuck in Not Deployed 1. Go to the left sidebar and select OTTO SEO → SEO Automation (URL: /seo-automation-v3). 2. Locate the schemas listed as Not Deployed and click into each one to open the schema detail view. 3. Review the field checklist. Any field flagged as missing or invalid will be highlighted. 4. Return to the corresponding page or product on your site and add the missing data — for example, enable customer reviews, add an aggregate rating, or complete pricing information. 5. Once the required fields are populated on your site, trigger a fresh sync by clicking Sync within the OTTO schema panel. 6. After SYNC_COMPLETE runs again with the updated data, OTTO will re-validate the schema. If all required fields now pass, the status will move to Deployed automatically. 📋 Common Required Fields by Schema Type - Product — name, offers, review, aggregateRating - Article — headline, author, datePublished - LocalBusiness — name, address, telephone - FAQ — at least one Question and acceptedAnswer pair If OTTO detects that a required field cannot be sourced from your page at all, it will leave the schema in Not Deployed to protect your site from invalid structured data that could trigger Google Search Console errors. ✅ How to Confirm Deployment Succeeded After syncing with the corrected data, the schema card status will update to Deployed within a few minutes. You can also use Google's Rich Results Test tool to confirm the structured data is live and valid on your page. 💬 Need More Help? 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.

🛠️ Fix Null Field Errors in OTTO Schema Markup

🔍 What Does the 'offers': null Error Mean? When OTTO generates schema markup for your pages, it pulls structured data from the content it finds on that page. If OTTO detects a Product Schema on your page but cannot find pricing, availability, or offer-related content, it inserts 'offers': null as a placeholder in the generated schema. This is not a system crash or a bug — it means OTTO found a schema type that typically includes an Offers field, but the corresponding data was either absent from the page or not yet provided. Search engines like Google may flag a null Offers field as incomplete structured data, which is why it surfaces as an error in your schema report. 📋 Understanding OTTO Schema States: 'Review' vs. 'FOUND' OTTO assigns each schema one of two states to help you manage your markup: - Review — OTTO has drafted a schema based on page content, but it requires your approval before being applied. Fields may be incomplete. - FOUND — OTTO has detected an existing schema already present on the page (e.g., hardcoded in your theme or CMS). OTTO surfaces it so you can see and manage it, but it originates from your site's existing code. A common point of confusion: customers are sometimes told that FOUND schemas cannot be edited or removed. This is incorrect. Both Review and FOUND schemas can be managed within OTTO — you can edit individual fields, leave non-applicable fields empty where acceptable, or work with your developer to remove hardcoded schemas from the source if needed. ⚙️ How OTTO Auto-Populates the Offers Field When you click Regenerate on a schema, OTTO re-scans the page and attempts to pull fresh data. Here is what happens depending on your page content: - If pricing or offer data exists on the page — OTTO will auto-populate the Offers field with values it finds (price, currency, availability, etc.). - If no offer data exists on the page — OTTO will again return 'offers': null. Regenerating alone will not fix this if the underlying page content does not include offer information. Regeneration is a useful first step, but it is not a guaranteed fix. If your page genuinely does not contain product pricing or availability, you have additional options outlined below. ✅ When Is an Empty or Null Offers Field Acceptable? Not every business sells products or services with listed prices. If the Offers field does not apply to your page or business model, leaving it null or omitting it entirely is often acceptable. Consider the following: - Google's structured data guidelines do not require an Offers field for all Product schemas, but they do recommend it for better eligibility in rich results like price snippets. - A null Offers field will typically generate a warning rather than a critical error in Google Search Console, meaning your schema is still valid — just not fully enhanced. - If the Offers field genuinely does not apply to your business (e.g., you list products but handle pricing offline or via inquiry), it is safe to remove or omit this field. 🛠️ How to Resolve the 'offers': null Error in OTTO Follow the steps below based on your situation: 1. Go to the left sidebar and select OTTO SEO, then navigate to your schema markup section within OTTO. 2. Locate the schema showing the 'offers': null error and open it for editing. 3. Option A — Your page has pricing data: Click Regenerate to prompt OTTO to re-scan the page. If pricing, availability, or offer details are present in your page content, OTTO will auto-populate the Offers field. Review the result and approve the schema. 4. Option B — You want to add offers manually: Instead of regenerating, click into the schema editor and manually enter the Offers details — including price, price currency, and availability. This is the most reliable method when your page content is minimal or structured in a way OTTO cannot easily parse. 5. Option C — Offers do not apply to your business: In the schema editor, you can clear the Offers field entirely or remove that property from the schema. An empty or omitted Offers field will not break your schema — it will simply not qualify for offer-related rich result features. Save and approve the updated schema. 🔗 Note: Relative vs. Absolute URLs in Schema Some customers experiencing schema errors alongside the null Offers issue have also encountered a separate problem: OTTO or an existing schema may be generating relative URLs (e.g., /products/item) instead of absolute URLs (e.g., https://www.yoursite.com/products/item) in fields like url or image. Search engines require absolute URLs in structured data. If you notice URL-related warnings in Google Search Console alongside your schema errors, check that all URL fields in your schema use the full absolute format including the protocol and domain. 💡 Quick Reference: Which Option Should I Use? - Page has pricing content but offers show null → Regenerate the schema, then review and approve. - Page content is sparse or OTTO cannot detect pricing → Manually enter Offers details in the schema editor. - Offers do not apply to your business or page → Clear or omit the Offers field; this is safe and will not invalidate your schema. - Schema is marked FOUND and appears hardcoded → Edit the field in OTTO, or work with your developer to update the source code 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.

🛠️ Fix Product Schemas Stuck in Suggested Status

🔍 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

🛠️ Fix Recurring Schema Deletion Bug in OTTO

🔍 Problem Overview Some customers experience a bug where a deleted VacationRental schema keeps reappearing on their pages after removal. This causes SEO optimizations to disappear overnight and prevents proper site indexing. The issue stems from a database inconsistency where schema rows marked for deletion are not properly flagged as deleted in the system. 🛠️ Root Cause Engineering identified that schema records with a deleted_at timestamp but was_deleted = False were not being fully processed. This caused the system to treat them as active, leading to automatic re-deployment of the schema during nightly reprocessing cycles. ✅ Permanent Fix Applied Engineering executed a one-time database correction: Set was_deleted = True on all schema rows where deleted_at IS NOT NULL AND was_deleted = False. They also fixed the underlying deletion code path to ensure future deletions are properly recorded and respected. 🧪 Verification Steps 1. Go to Left sidebar → OTTO SEO → Site Audit → Page Explorer. 2. Locate a page where the VacationRental schema previously reappeared (e.g. taking-flight-with-disc.html). 3. Confirm the schema no longer appears on the page. 4. Wait 24 hours and recheck the page to ensure the schema does not return. 5. Verify SEO optimizations remain intact and indexing resumes normally. 🛡️ Prevention The deletion logic has been corrected so that any schema marked for deletion is immediately and permanently flagged with was_deleted = True. Related fixes in the OTTO pipeline now prevent silent re-deployment of stale schemas and ensure audit trails are maintained. 📌 Related Fixes (Completed) - OTTO: Domain Level Schema Retains Old Location After Removal From Brand Vault - OTTO & Audit: Manual reprocessing is un-deploying the schema - fix(otto): clean stale FOUND schemas for pages with no HTML schema data 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.

Fix 'offers': Null Error in OTTO Product Schema

When OTTO auto-generates a Product schema and cannot extract pricing or availability data from your page, it may leave the offers field empty or null. This causes the schema to be flagged as invalid and prevents your page from qualifying for Google Product rich results. This article explains why it happens and how to fix it manually. 📋 Why This Happens OTTO builds Product schema by crawling your page at the time of generation. If your product page does not display price and availability in a format OTTO can read during that crawl, the offers property is left null and the schema fails validation. Regenerating the schema without first updating your page content will reproduce the same null result — it is not a bug that resolves itself on retry. Important: Google requires the offers property for Product pages to qualify for rich results in search. A Product schema without valid offers data will not unlock enhanced listings, even if the rest of the schema is correct. 🔧 How to Fix It 1. In your Search Atlas dashboard, go to Left sidebar → OTTO SEO → All Sites → [your project] → Overview → Onpage Optimizations (OTTO Grader) and navigate to Schema Markup. 2. Find the page showing an invalid schema status. It will be marked with a red or error indicator. 3. Open the schema to enter the editor. 4. Choose the fix that matches your page: - Page has no pricing data: Remove the offers property from the schema entirely. This clears the validation error. Note that the page will not qualify for Product rich results without it. - Page does have pricing data: Populate the offers field manually. At minimum, include price, priceCurrency, and availability — the three properties required by schema.org for a valid Offer. 5. Save your changes and deploy the schema. ⚠️ Known Limitations - OTTO cannot auto-populate offers if pricing data is not visible and machine-readable on the live crawled page. Manual entry is the only resolution in that case. - If price or availability changes on your page after the schema is deployed, you will need to update the schema manually to keep it accurate. 💬 Need More Help? 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.

🛠️ Fix Schema Deployment Failures and AI Suggestion Deletions

🔍 Overview Some customers have reported that schemas approved inside OTTO fail to go live, projects cannot be activated, and AI-generated schema suggestions are automatically deleted shortly after being created. These issues were caused by bugs in the OTTO schema pipeline — both have now been fully resolved through a platform update. This article explains what caused the problems, confirms the current status, and walks you through steps to verify your projects are working correctly. ⚠️ What Was Causing These Issues Two separate but connected bugs affected the OTTO schema pipeline: - AI Schema Generator producing invalid schema suggestions: A bug in the AI schema generation pipeline caused schema suggestions to be automatically deleted shortly after being created, resulting in AI suggestions disappearing without explanation. - Schema deployment failures and project activation blocks: A separate bug prevented approved schemas from going live. In some cases, this also blocked entire projects from activating within OTTO. ✅ Current Status — Issues Resolved Both issues have been fixed at the platform level. The following changes were deployed: - The AI Schema Generator bug that caused suggestions to be automatically deleted has been resolved. New suggestions will no longer be removed unexpectedly. - The bug that prevented approved schemas from going live and blocked project activation has been resolved. No action is required on your end to receive these fixes — they have been applied automatically across all affected accounts. 🔄 Steps to Verify Your Projects Are Working If your projects were affected, follow these steps to confirm everything is functioning correctly: 1. Open OTTO and navigate to the project that was experiencing issues. 2. Check the project activation status. The project should now show as active. If it is still showing as blocked, try deactivating and reactivating OTTO for that project. 3. Navigate to the Schema section within your OTTO project. 4. Review your AI-generated schema suggestions. New suggestions generated after the fix will no longer be auto-deleted. 5. Approve any schemas you wish to deploy and confirm they move to an approved or deployed status within a few minutes. 6. If you had schemas that were deleted during the affected period, you can regenerate them by using the schema generation option within your OTTO project. 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.

🛠️ Fix OTTO Schema Reversions

🔍 Why schema markup can revert An approved LocalBusiness schema correction may appear to revert when a later OTTO deployment action replaces, undeploys, or reprocesses the page-level schema. A mass undeploy or domain-level deployment change can remove a previously applied correction. In some cases, stale schema records with an invalid status can also block a new deployment. The live page may continue serving older schema if the previous markup was not fully removed or if another deployment source is still active. Approval confirms the proposed correction; it does not prevent later deployment changes from updating the live markup. 📋 Audit the deployment history 1. Open the affected project and identify the exact URL where the schema changed. 2. Review the OTTO schema deployment history for that URL and the domain around the time of the reversion. 3. Look for page-level undeployments, mass undeploy actions, domain-level changes, failed deployments, or records marked stale or invalid. 4. Compare the last approved schema with the schema currently shown on the live page. 5. Record the event time, affected URL, schema type, deployment status, and any error or validity message. This audit identifies whether the change came from an intentional deployment action, a cleanup process, or a stale schema record that prevented the correction from being applied. ✅ Restore accurate structured data 1. Confirm the business facts first, including the business name, address, phone number, hours, URL, and location details. 2. Remove or resolve the stale or invalid schema record through the OTTO schema workflow. Do not change valid business facts just to work around a deployment error. 3. Submit the corrected LocalBusiness schema for approval when required. 4. Deploy the approved schema through OTTO using the affected page or domain deployment workflow. 5. After deployment, verify the live page source and a structured-data testing tool to confirm that the intended schema is present and outdated markup is gone. Using the OTTO workflow preserves the approved facts and creates a traceable deployment record. Avoid manually adding replacement schema to the site while an OTTO deployment is being repaired, because multiple sources can cause conflicting or duplicate markup. 🧪 Verify deployment integrity - Confirm the schema record is valid and no longer marked stale. - Check that the deployment status shows completed rather than stuck or failed. - Verify the live page contains one consistent LocalBusiness definition where appropriate. - Recheck the page after caching has cleared, since the live result may not update immediately. - Keep the deployment event details if the schema changes again. 💡 Prevent future reversions Before approving or deploying a correction, confirm the target URL and deployment scope. Review recent domain-level and page-level actions before running bulk changes. When a deployment is stuck, resolve the stale schema status first instead of repeatedly submitting the same correction. This protects valid business information and makes the deployment history easier to trace. 💬 Need help? 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.

🛠️ Troubleshooting AI Schema Generation Not Displaying

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.

🛠️ Fix OTTO SEO Schema Update Errors

🔍 Overview If you encounter a persistent schema update error in OTTO SEO — even after confirming the OTTO pixel is installed — the issue is usually related to pixel placement, crawl status, schema conflicts, or CMS compatibility. Follow the steps below in order to identify and resolve the problem. 📍 Step 1: Verify Pixel Placement The OTTO pixel must be placed in the section of your site. Placing it in the footer will prevent it from executing correctly and can cause schema update errors. - Go to the left sidebar and navigate to OTTO SEO → Installation Guide. - Confirm the pixel snippet is inserted inside the tag of your site template. - If it is placed in the footer or body, move it to the correct location and save your changes. 🗂️ Step 2: Check Page Crawl Status Schema updates depend on an up-to-date crawl of the affected page. If the page has not been crawled recently, the update may fail. - Go to the left sidebar and navigate to OTTO SEO → Site Audit → Page Explorer. - Locate the affected page and check when it was last crawled. - If the crawl data is outdated, proceed to Step 3. 🔄 Step 3: Trigger a Manual Recrawl If the affected page has not been crawled recently, triggering a manual recrawl will refresh its data and allow the schema update to proceed. 1. Go to the left sidebar and navigate to OTTO SEO → Site Audit → Crawl Monitoring. 2. Locate the affected page and trigger a recrawl. 3. Wait for the crawl to complete before retrying the schema update. ⚠️ Step 4: Review Existing Schema Conflicts If your page already contains schema markup hardcoded directly in the HTML, duplicate schemas can create conflicts that block OTTO SEO from applying updates. - Inspect your page's source code for any existing JSON-LD, Microdata, or RDFa schema markup. - Remove or consolidate any duplicate schema definitions. - Ensure only one schema source is active for the page before retrying. 🖥️ Step 5: Check CMS Compatibility Some CMS platforms restrict or limit script injection, which can prevent the OTTO pixel from executing fully even if it appears to be installed. - Confirm that your CMS allows third-party scripts to run in the section. - Check for any security plugins, Content Security Policy (CSP) rules, or caching layers that may be blocking the pixel. - If your CMS has a script manager or tag manager, verify the pixel is published and not in a draft or paused state. 🔁 Step 6: Retry the Schema Update Once you have completed the steps above, attempt the schema update again from within the OTTO SEO interface. 1. Go to the left sidebar and navigate to OTTO SEO → All Sites. 2. Click on your project card. 3. Navigate to the Schemas section. 4. Re-attempt the schema update for the affected page. ✅ What to Expect After completing all steps, the schema update should apply successfully. If the error still persists, it may indicate a deeper site configuration issue that requires manual review by our support team. 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.

🔄 Troubleshooting OTTO SEO Schema Generation Delays

This article addresses a known display issue where page-level schema generation in the OTTO SEO tab reports as successful, but the generated schemas do not appear immediately. This is typically a delay between the backend completing the generation and the UI reflecting the result — not a failed generation. 🔍 What Is Happening When schema generation appears to complete but no output is visible in the OTTO SEO tab, there may be a delay in the UI displaying the results. The generation may have completed successfully on the backend even though nothing is shown on your screen yet. 🛠️ What to Do 1. Do not re-run the generation immediately, as the schema may already exist on the backend. 2. Wait a moment, then refresh the page and navigate back to the OTTO SEO tab for the affected domain. 3. Check whether the schema output is now visible in the OTTO SEO tab for the page(s) you targeted. 4. If the schema is still not visible after refreshing, contact our support team before retrying the generation — a member of our team can verify whether the output was saved on the backend. ✅ How to Confirm It Worked - The schema output is visible in the OTTO SEO tab for the specific page(s) you targeted. - The schema content is populated and not blank or in a loading state. - You are able to copy, edit, or implement the schema without triggering a new generation. 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.

🛠️ Fix WordPress Schema Errors and Plugin Conflicts

🔍 Understanding the Problem After activating OTTO SEO, some customers notice new ImageObject metadata validation errors appearing in Google Search Console (GSC). At the same time, others wonder whether installing a third-party schema plugin alongside OTTO will cause conflicts. This article explains both issues and how to resolve them quickly. ⚙️ Why ImageObject Errors Appear After Switching to OTTO When you activate OTTO SEO, it takes over schema markup generation for your entire site. If a previous plugin or theme was outputting incomplete or differently structured ImageObject schema, GSC may flag the transition as new errors — even if OTTO's output is technically correct. Common reasons these errors appear include: - Images on your pages are missing alt text, which is required for valid ImageObject schema. - Featured images are not set on posts or pages, leaving the contentUrl or url property empty. - Your theme outputs its own image schema that conflicts with OTTO's output, producing duplicate or malformed markup. - GSC is still processing a cached version of your previous schema and will resolve automatically within a few days. 🖼️ How to Fix ImageObject Validation Errors 1. Add alt text to all images. In the WordPress Media Library, open each flagged image and fill in the Alt Text field. For bulk updates, use the Media Library grid view to edit images quickly. 2. Set featured images on all posts and pages. Go to each post or page in the WordPress editor, open the Featured Image panel, and assign a relevant image. 3. Check for theme-generated schema. Some themes (such as Astra or GeneratePress) include built-in schema output. Open your theme settings and disable any structured data or schema markup options to prevent duplication. 4. Re-validate in GSC. After making changes, open Google Search Console → Enhancements → Schema errors, select the affected URLs, and click Validate Fix. GSC typically re-crawls within a few days. 5. Use the Rich Results Test. Paste any affected URL into Google's Rich Results Test tool to confirm your schema is clean before requesting validation. 🔌 Will Installing a Schema Plugin Conflict with OTTO? Yes — in most cases, running a dedicated schema plugin alongside OTTO SEO will cause conflicts. OTTO SEO generates its own comprehensive structured data for your site, including Organization, WebPage, Article, BreadcrumbList, and ImageObject schema. Adding a second plugin that outputs the same schema types produces duplicate markup, which can confuse search engines and trigger additional GSC errors. Plugins known to conflict with OTTO's schema output include: - Yoast SEO (when schema is enabled) - Rank Math (when schema module is active) - Schema Pro - Schema & Structured Data for WP & AMP - All in One SEO (AIOSEO) with schema features enabled ✅ Recommended Setup for Schema in WordPress Follow these best practices to keep your schema clean and conflict-free: - Use OTTO SEO as your single schema source. Do not install additional schema plugins. OTTO deploys schema per page/URL after you approve or publish the recommendation (or automatically if OTTO auto-deploy is enabled). - Disable schema output in your theme. If your theme has structured data settings, turn them off. - Disable schema in any remaining SEO plugins. If you use another SEO plugin for features OTTO does not yet cover (such as a sitemap from a legacy setup), navigate to that plugin's settings and disable only its schema or structured data module — you do not need to uninstall the entire plugin. - Audit your schema regularly. After any plugin update or theme change, re-run a spot-check in the Rich Results Test to catch new conflicts early. ⏱️ How Long Until GSC Errors Clear? Once you have fixed the underlying issues, GSC errors do not disappear instantly. Expect the following timeline: - 1–3 days for Googlebot to re-crawl your most frequently visited pages. - Up to 2 weeks for validation to complete across all flagged URLs. - Clicking Validate Fix in GSC speeds up the process by prompting Google to prioritise re-crawling those URLs. If errors persist beyond two weeks after your fixes, re-check the affected pages using the Rich Results Test to confirm there is no remaining conflicting output. 💬 Need More Help? 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.

🛠️ Fix ImageObject Schema Errors and Manage OTTO Schema Settings

🔍 Overview After connecting your WordPress site to OTTO, you may notice ImageObject metadata validation errors appearing in Google Search Console (GSC). These errors are typically caused by conflicting schema output — OTTO generates its own structured data, and if a separate schema plugin is also active on your site, both sources attempt to output schema markup at the same time. The result is duplicate or malformed structured data that GSC flags as invalid. The good news: OTTO has a built-in schema management feature inside your project settings. You do not need a third-party plugin to manage schema, and you do not need to leave OTTO to fix this. This article walks you through exactly how to resolve the issue. ⚙️ How OTTO Handles Schema OTTO can generate and inject structured data (schema markup) for your connected site on a per-page basis after you approve or publish the recommendation (unless OTTO auto-deploy is enabled). This includes common schema types such as Article, BreadcrumbList, WebPage, and ImageObject. Because OTTO manages schema natively, running an additional WordPress schema plugin alongside it will almost always produce conflicts. Common symptoms of a schema conflict include: - ImageObject validation errors in GSC under Enhancements or Rich Results - Duplicate structured data warnings in third-party schema testing tools - Unexpected schema types appearing that you did not configure 🗂️ Step 1 — Deactivate Your WordPress Schema Plugin Before adjusting anything in OTTO, remove the source of conflict by deactivating any schema or structured data plugin currently active on your WordPress site. Common plugins that conflict with OTTO include Rank Math, Yoast SEO (when schema output is enabled), Schema Pro, and WP Schema. 1. Log in to your WordPress Admin Dashboard. 2. Go to Plugins → Installed Plugins. 3. Locate the schema or SEO plugin generating structured data. 4. Click Deactivate. Do not delete it yet — confirm the errors clear first. If you rely on that plugin for other features (such as redirects or sitemaps), check whether those features can be handled by OTTO or a separate dedicated plugin before fully removing it. 🔧 Step 2 — Access OTTO Schema Settings in Project Settings OTTO gives you direct control over whether it outputs schema markup for your site. To access these controls: 1. Log in to your Search Atlas account. 2. From the left navigation, open OTTO SEO → All Sites (SEO Automation). 3. Select the project connected to the affected site. 4. Click the Settings icon or navigate to the Project Settings tab for that project. 5. Scroll to the Schema section. 6. Here you will see a toggle or option to enable or disable OTTO's schema output for the site. If you want OTTO to handle all schema going forward (the recommended approach), ensure the Schema option is enabled in OTTO and the WordPress plugin is deactivated. If for any reason you prefer to manage schema entirely through a plugin, you can deactivate schema in OTTO's settings so only one source outputs structured data. ✅ Step 3 — Validate the Fix in Google Search Console After resolving the conflict, confirm the errors are clearing in GSC: 1. Open Google Search Console for your property. 2. Go to Enhancements or Rich Results in the left sidebar. 3. Locate the ImageObject report showing errors. 4. Click into the report and select Validate Fix. 5. Google will re-crawl the affected URLs. Full validation can take several days depending on crawl frequency. You can also use Google's Rich Results Test tool to spot-check individual URLs immediately after making your changes, before GSC re-crawls. ❓ Frequently Asked Questions Will deactivating my schema plugin break my site's SEO? No. As long as OTTO's schema output is enabled for your project, OTTO will continue generating structured data for your site. You are switching the source, not removing schema entirely. Can I customize the schema OTTO outputs? OTTO manages schema output automatically based on your content. For specific customizations beyond the built-in controls, consult the OTTO project settings or reach out via the chat widget below. The errors are still showing after I made these changes — why? GSC does not update instantly. After clicking Validate Fix, allow 3–7 days for Google to re-crawl your pages. If errors persist after that window, there may be another plugin or theme function injecting schema. Use the Rich Results Test to inspect a live URL and check the page source for duplicate application/ld+json script blocks. Do I need to repeat these steps for multiple sites? Yes. Schema settings are configured per project in OTTO. If you manage multiple connected sites, check each project's settings individually. 💬 Need More Help? 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.

🛠️ OTTO Dynamic SEO Injecting Wrong Schema Types

🔍 What Is Happening OTTO's Dynamic SEO feature uses AI to detect and inject structured data (schema markup) onto your pages via the data-otto-pixel='dynamic-seo' attribute. In some cases, the AI may generate and approve schema types that do not match your page's content — for example, injecting VacationRental, Course, SoftwareApplication, WebApplication, or MobileApplication schema onto a page about an unrelated topic such as basement waterproofing. This issue is caused by the Dynamic SEO AI misclassifying page content during schema generation. The incorrect schemas are then approved and deployed automatically. Your sitewide schema and other Search Atlas components are not affected — only the schemas generated and injected by the Dynamic SEO feature. ⚙️ How to Confirm the Issue 1. Open your browser's developer tools on the affected page (right-click the page and select Inspect, then go to the Elements tab). 2. Search for data-otto-pixel='dynamic-seo' in the page source. If this attribute is present alongside incorrect schema types, OTTO's Dynamic SEO feature is the source. 3. Note which schema types are listed. If they do not match your page's actual topic or business type, you are experiencing this issue. 4. Optionally, confirm your sitewide schema is unaffected by reviewing your schema settings in the Search Atlas dashboard — sitewide schema is managed separately from Dynamic SEO-injected schema. 🚀 Steps to Resolve Because removing specific incorrect schemas requires a backend correction to mark them as deleted and sweep the affected project, this issue cannot be fully resolved through the platform UI alone. To get it fixed as quickly as possible, complete the diagnostic steps below and then contact support — providing the details up front will allow engineering to act immediately without back-and-forth. 1. Identify all pages on your site where incorrect schema types are being injected by OTTO's Dynamic SEO feature, using the inspection method described above. 2. Note the exact incorrect schema types appearing on each affected page (for example: VacationRental, Course, SoftwareApplication). 3. Open the live chat widget (bottom-right of any Search Atlas page) and submit a message that includes: - The URL(s) of the affected page(s) - The incorrect schema type(s) appearing on each page - Confirmation that data-otto-pixel='dynamic-seo' is present in the page source 4. The support team will escalate to engineering, who will remove the incorrect schemas at the database level and run a project sweep to ensure they are fully undeployed from your live site. 5. Once engineering confirms the fix, re-inspect the affected pages using the steps above to verify that the incorrect schema types no longer appear in the page source. If any incorrect types remain, reply to your open support conversation with the remaining schema details so engineering can re-sweep. 💡 Why This Cannot Always Be Self-Resolved Incorrect schemas injected by Dynamic SEO are stored and tracked at the database level with unique IDs. Fully removing them requires an engineering action to mark those records as deleted and confirm the deployment is cleared from your live site. Simply disabling a se

Fix OTTO Schema Deployment Errors and Failures

Overview When OTTO generates schemas automatically, the AI can occasionally produce invalid data — such as numeric fields stored as text, corrupted characters (like malformed ampersands), or null-valued fields. These errors cause schemas to fail validation and become stuck in an undeployed state, and you may see a message like No deployable recommendation found. This article explains the known issue and provides concrete steps you can take to resolve it. In cases where the malformed data cannot be corrected through the steps below, the Search Atlas support team can investigate and resolve the affected recommendations directly. Common Symptoms - Attempting to deploy a schema has no effect. - A message appears saying No deployable recommendation found. - Schemas remain stuck in an undeployed state even after repeated attempts. - Schemas were generated for product pages that have no review or rating data, resulting in empty or invalid fields. What To Do 1. Identify the affected schemas. Navigate to the OTTO section of the platform and locate the schemas that are failing to deploy. Note which recommendations are sitting in an undeployed or pending state. 2. Check for obvious data issues. Look at the field values in the affected schema recommendations. Common problems include: numeric fields (such as width, height, price, or rating values) appearing as text strings rather than numbers; special characters that look corrupted or broken (such as malformed ampersands in titles or descriptions); and fields that are empty or contain null values where real content is expected. 3. Edit the affected schema fields manually. If you can identify the malformed field, edit it directly within the schema recommendation to correct the value — for example, change a text-formatted number to a proper numeric value, remove corrupted characters, or delete empty fields that are causing validation failures. Save the changes and attempt to deploy the schema again. 4. Remove invalid review or rating fields for pages with no review data. If a schema was generated for a page that has no reviews or ratings, open the schema recommendation and remove the review and rating fields entirely. Schemas without those fields can deploy successfully when the source page does not contain that data. Save and attempt deployment again. 5. Attempt deployment after corrections. After editing the affected fields, try deploying the schema again. In most cases, correcting the malformed or empty fields resolves the validation error and allows the schema to deploy successfully. 6. Contact Search Atlas support if schemas remain stuck. If you have corrected the visible field issues and the schema still cannot be deployed, reach out to the support team with the details of the affected schemas and account. The team can investigate the underlying data at the account level and resolve any remaining malformed recommendations directly. Why This Happens The OTTO AI schema generator can produce field values in the wrong format or leave required fields empty when source page data is missing or ambiguous. This results in schemas that fail internal validation and cannot be deployed until the underlying data problems are corrected. If you need further assistance, please contact the Search Atlas support team through the chat widget or your account's support channel and we'll be happy to help.

🛠️ Fix GSC Schema Errors from OTTO Deployments

🔍 What Is This Issue? After OTTO deploys schemas to your site, Google Search Console (GSC) may flag schema errors or warnings on certain pages — including your homepage. This can happen when OTTO deploys structured data to a page that has not yet been crawled, or when a schema type (such as Article schema) is removed and the change is not yet reflected in Google's index. This article walks you through the steps that our support team has confirmed resolve this issue. ⚙️ Step 1: Review and Roll Back Problem Schemas in OTTO The first step is to identify which schemas are causing the GSC errors and temporarily remove them so your site is in a clean state before reindexing. 1. Go to your Search Atlas dashboard and navigate to OTTO. 2. Locate the site experiencing GSC errors and open its OTTO settings. 3. Review the schemas currently deployed on the affected page (for example, your homepage). 4. Temporarily roll back or undeploy the schemas that GSC is flagging as errors. If you are unsure which schemas to remove, start with any recently changed or newly added schema types on that page. 5. Save your changes inside OTTO. 🌐 Step 2: Republish Your Site After rolling back the schemas in OTTO, you need to push those changes live on your website. - Wix users: Log in to your Wix dashboard and republish your site so the updated (schema-free) version is publicly accessible. - Other platforms: Clear any caching layers and ensure the live version of your page no longer contains the flagged schema markup. You can verify this by viewing the page source or using Google's Rich Results Test tool. 📊 Step 3: Request Reindexing in Google Search Console Once your site is republished without the problematic schemas, ask Google to recrawl and reindex the affected page. 1. Open Google Search Console and select your property. 2. Paste the URL of the affected page (e.g., your homepage) into the URL Inspection tool at the top of the screen. 3. Click Request Indexing. Google will queue the page for recrawling, which typically takes a few hours to a few days. 4. Once Google has recrawled the page, the schema errors should no longer appear in the Enhancements or Rich Results reports in GSC. 🚀 Step 4: Redeploy Schemas After Errors Clear After Google has confirmed the errors are resolved (or after the flagged errors disappear from GSC reports), you can safely redeploy your schemas through OTTO. 1. Return to OTTO in your Search Atlas dashboard and open it for your site. 2. Redeploy the schemas you rolled back in Step 1, making sure the affected pages have been fully crawled by OTTO before deploying structured data to them. 3. Repub

OTTO Schemas Stuck in Review — Fix Deployment Issues

🔍 What Is This Issue? Some users find that schemas generated by OTTO become stuck in a Review status and cannot be deployed. When you attempt to deploy them, the process runs indefinitely and fails — sometimes causing you to lose credits by regenerating the same schemas repeatedly. This issue has been investigated and fixed by the Search Atlas engineering team. Multiple underlying causes were identified, including a validation error that incorrectly blocked valid schemas from deploying, and a pipeline bug affecting schemas on pages that had no review or rating data. Both have been resolved in platform updates. ⚙️ Why This Happens - A schema validation bug was incorrectly flagging valid schemas and preventing deployment. - Product pages with no review or rating data caused certain schema types to get stuck in Review with no fields to correct. - A broader schema pipeline issue affected AI generation, schema importing, validation, and deployment across multiple domains. All of these issues have been patched. If you are still experiencing stuck schemas, the steps below will help you resolve them. 🚀 How to Resolve Stuck Schemas 1. Refresh the page and check schema status. After the recent platform fixes, some schemas that were previously stuck may now show as deployable. Reload your OTTO session and review the current status of your schemas before taking further action. 2. Attempt deployment again. Try deploying the schemas that were previously stuck. In many cases, the engineering fixes applied to the platform will allow previously stuck schemas to deploy successfully without any additional steps on your end. 3. Avoid repeated regeneration. If schemas are still showing as stuck, do not keep regenerating them. Each regeneration consumes credits and will not resolve an underlying platform-side issue. Contact support instead so the team can manually deploy the pending schemas and escalate any credit loss on your behalf. 💡 Tips to Avoid Wasting Credits - Do not regenerate schemas that are stuck — regeneration should be a last resort only after confirming the platform-side issue is resolved. - If a schema is stuck with no fields to correct and no clear error message, this is a platform-side issue and regenerating will not fix it. Reach out to support instead. - Keep an eye on your schema quota after any deployment attempts that failed, and report unexplained credit loss to the support team so it can be reviewed and escalated. 📬 Still Experiencing This Issue? If your schemas remain stuck after following the steps above, please contact the Search Atlas support team via the chat widget in your dashboard. The team can manually deploy pending schemas and investigate any credit loss caused by the issue.

🛠️ Resolving Page-Level Schema Null Value Warnings and Internal Link Redirect Issues in OTTO

This article explains why OTTO flags null values in your Page-Level Schema Markup, why fixing Review and Aggregate Rating warnings can feel like a loop, and how to clear internal link warnings tied to redirected URLs. ⚠️ Why OTTO Flags Null Review and Aggregate Rating Schema Fields OTTO scans each page for content patterns that match known schema types. When it detects a star-rating element on the page, it interprets that element as review-related content and suggests Review and Aggregate Rating schema properties. The warning appears when OTTO has no underlying data to populate those properties. If the page has no actual product reviews, rating values, or review counts, OTTO cannot fill the Review and Aggregate Rating fields, so they remain null and trigger the schema warning. Why the fix loops and how to break it The fix appears to loop because the warning is not caused by a broken setting you can toggle off. OTTO keeps detecting the star-rating element and keeps suggesting the same Review and Aggregate Rating properties, but there is no review data on the page to satisfy them. Re-running the fix re-detects the same element and re-creates the same null fields. Here's what to do: instead of re-running the fix, choose the path below that matches your page. How to resolve the null schema warnings Choose the option that matches your page: - If the page has no reviews: the null Review and Aggregate Rating values are expected. You can safely dismiss this warning or manually populate the Review and Aggregate Rating fields. The star-rating element triggers the suggestion, but with no review data available, these fields cannot be populated automatically. - If the page should display reviews: add genuine review content to the page, such as customer reviews, a numeric rating value, and a review count. Make sure that review data is visible on the page so OTTO can detect it. Once that data exists on the page, OTTO can populate the Review and Aggregate Rating fields instead of leaving them null. After you confirm which case applies and update the page accordingly, OTTO can resolve the Review and Aggregate Rating fields on the next crawl rather than re-flagging empty values. Note: Other schema fields can trigger a similar Review Required state. For example, numeric fields such as an ImageObject's width and height that are flagged as strings can keep a page stuck in Review. This is a known issue tracked separately (OTTO-2193); if you encounter it, reach out to support so it can be confirmed against that fix. 🔗 Why OTTO Warns About Internal Links Pointing to Redirected URLs OTTO flags internal links when they point to a URL that redirects to another URL. In this case, internal links still point to /collections/halloween-collection, which redirects to /collections/halloween. Relying on that redirect is what triggers the internal link warning. How to fix the redirected internal link warnings 1. Find every internal link that points to the redirecting URL, /collections/halloween-collection. 2. Update each of those links to point directly to the final destination, /collections/halloween, so they no longer rely on the redirect. 3. Save your changes and allow OTTO to recrawl the site. Once the internal links point directly to /collections/halloween and OTTO recrawls the site, these internal link warnings should clear. 🎯 You now know that null Review and Aggregate Rating warnings come from a star-rating element with no review data behind it, and that internal link warnings clear once you point links directly to the final URL instead of a redirect. Update the relevant pages and links, then let OTTO recrawl to confirm the issues resolve.

🛠️ Fixing the "Field 'url' Contains a Relative URL" Schema Validation Error in OTTO

When OTTO flags the warning "Field 'url' contains a relative URL — absolute URLs are required", a URL field in your schema holds a path instead of a full web address. Find the field, prepend your site's protocol and domain, and the warning clears immediately. ⚠️ What This Error Means Schema markup standards require every URL value to be absolute — it must include the protocol and domain so search engines can resolve it unambiguously. A relative URL is missing that prefix. - Relative URL (invalid): /blog/my-article - Absolute URL (required): https://www.example.com/blog/my-article Any value that begins with / or ../ is relative and will trigger this warning. 🔍 How to Find the Affected Field OTTO does not currently highlight the specific field causing the error, so you need to locate it manually inside the schema editor. 1. Open OTTO and navigate to the schema that shows the warning. 2. Click Review Schema to open the schema editor. 3. Scan every field whose key is url, image, sameAs, contentUrl, or any other key that holds a URL value. 4. Identify any value that starts with / or ../ — these are the relative URLs you need to fix. This issue appears most often in Article, Product, BreadcrumbList, ImageObject, and Organization schema types, but can occur in any schema that references a URL. ✏️ How to Convert a Relative URL to an Absolute URL Once you find a field with a relative value, update it by prepending your site's full protocol and domain. 1. Note your site's root domain — for example, https://www.example.com. 2. Click the affected field in the schema editor to edit its value. 3. Replace the relative path with the complete absolute URL. 4. Click Save to apply the change. Example: - Before: /products/blue-widget - After: https://www.example.com/products/blue-widget Repeat for every field in the schema that still contains a relative path. A single schema can have multiple url fields — each one must be absolute. ✅ How to Confirm the Fix Is Complete 1. After saving, click Review Schema again. 2. Check the validation results for the "Field 'url' contains a relative URL" warning. 3. If the warning is gone, your schema is valid and ready to deploy through OTTO. If the warning persists, at least one more field still holds a relative URL. Return to the schema editor, locate the remaining instance, and apply the same fix. 🎯 You can now identify any relative URL field inside an OTTO schema and convert it to an absolute URL to pass validation. For a full overview of how OTTO validates and deploys schema markup across your site, see the OTTO Schema Management guide.

🛠️ Troubleshoot Missing, Pending, or Suggested Schema Markup in OTTO

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. 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 and enter your site URL to check whether schema is detected. - As an alternative, use Google's Rich Results Test 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.