🛠️ Understanding OTTO Grader Undeployed Fixes Count

Camilo Aponte

Camilo Aponte

Last updated on Sep 30, 2026

🔍 Overview

You may notice that your OTTO Grader displays a total count of undeployed fixes — for example, 344 fixes not deployed — while every individual category shows 0 issues remaining. This can be confusing, but it is a known display behaviour that has a straightforward explanation.

💡 Why This Happens

The total undeployed fix count shown on the OTTO Grader summary reflects a cumulative historical snapshot of all fixes that were identified across your site at the time OTTO last ran a full audit. This number does not always update in real time when you resolve issues category by category.

There are two common reasons for the mismatch:

  • Fixes were resolved outside OTTO: Some issues may have been corrected manually in your CMS or by another tool. OTTO tracks that a fix was recommended but cannot automatically confirm it was applied externally, so the count persists until a new full scan is completed.
  • Pending scan refresh: OTTO updates category-level counts more frequently than the top-level summary. If you recently deployed fixes, the summary total may lag behind the individual category totals until the next full grader sync.

📊 How to View the 344 Undeployed Fixes

To investigate which specific fixes make up the undeployed count, follow these steps:

  1. In the left sidebar, click OTTO SEO, then open SEO Automation to go to the OTTO dashboard (/seo-automation-v3).
  2. Open the OTTO Grader for the relevant site.
  3. Review each fix category listed in the grader. Even if a category shows 0 deployable fixes, expand it to check for items marked as Ignored, Skipped, or Not Applicable — these still count toward the undeployed total.
  4. Look for a Filters or Status dropdown within each category and set it to show All statuses, not just active ones. This reveals fixes that were dismissed or excluded rather than deployed.
  5. Check the Ignored Fixes section if available. Any fix you or a team member previously ignored is excluded from the deployable queue but still included in the undeployed summary count.

⚙️ How to Reconcile the Count

Once you have identified where the undeployed fixes are sitting, you have two options to bring the summary count to zero:

  • Deploy the fixes: If any ignored or skipped fixes are still valid improvements, update their status to active and deploy them through OTTO.
  • Mark fixes as Ignored or Not Applicable: If certain fixes do not apply to your site (for example, recommendations for page types you do not use), explicitly mark them so OTTO can exclude them cleanly from the count.

After taking either action, trigger a manual rescan by navigating to OTTO SEO → Overview (OTTO Grader) to recalculate the summary total against the current state of all categories.

🚀 Best Practices to Keep Your Count Accurate

  • Run a full OTTO Grader rescan after making bulk changes to your site, whether through OTTO or manually in your CMS.
  • Regularly review the Ignored fixes list to ensure nothing important has been accidentally dismissed.
  • Address fixes category by category and rescan between sessions so the summary total stays in sync.
  • Avoid making large structural site changes (URL changes, template updates) without triggering a rescan immediately after, as stale fix recommendations can inflate the undeployed count.

🙋 Still Need Help?

If you have followed the steps above and your undeployed fix count still does not reflect the correct number, or you cannot locate where the 344 fixes are categorised, our team is happy 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.