🔍 Overview
Some customers have noticed a sharp drop in Flawless Pages, unexpected changes in OTTO ROI figures, or both — often following a period of site instability. This article explains the most common causes, what happened behind the scenes, and the steps you can take to stabilise and restore your results.
⚠️ Why Did My Flawless Page Count Drop So Dramatically?
A sudden drop in Flawless Pages (for example, from 600+ down to 96) is almost always caused by one or more of the following technical events:
- OTTO recrawl crash: A known bug caused OTTO's recrawl process to crash when it encountered pages with a NULL status code. This halted suggestion generation and left affected URLs in an unresolved state.
- Meta data rollback: In some cases OTTO rolled back previously applied meta data and keyword optimisations, causing pages that were previously counted as Flawless to lose their optimised status.
- 500 errors introduced by OTTO Gateway: A Metasync/OTTO Gateway issue rewrote valid 200 responses as 500 (API_ERROR) on certain URLs. Google Search Console began de-indexing those pages, removing them from the Flawless count.
- Lost canonical tags: A rendering issue caused OTTO to drop canonical URLs on specific render paths, which can cause Google to treat pages as duplicate or unverified, reducing the Flawless count.
- Site stuck in manual reprocess state: If OTTO got stuck reprocessing your site, new optimisations could not be applied and previously counted pages reverted to an unoptimised state.
Credits spent on pages that were later affected by these bugs are a legitimate concern. Please escalate through the chat widget (instructions at the bottom of this article) so our team can review your account and arrange any appropriate credit adjustment.
📊 Why Are My OTTO ROI Figures Changing (e.g. $165K → $105K)?
OTTO ROI is a dynamic, recalculated estimate — it is not locked in at the moment optimisations are applied. The figure changes whenever:
- The underlying page count changes (e.g. pages drop from Flawless back to Needs Work after a rollback or error).
- Keyword ranking data refreshes from Google Search Console or our crawler, updating traffic and value assumptions.
- Pages are de-indexed by Google following server errors (500s), reducing the estimated organic value OTTO can claim.
- OTTO re-scans your site and discovers pages that were previously miscounted or skipped due to the NULL status-code crash.
This means a drop from $165K to $105K does not necessarily mean $60K of real revenue was lost — it reflects a corrected calculation after page or ranking data changed. Once underlying issues are resolved and pages return to Flawless status, the ROI figure will recover accordingly.
🚀 Steps to Stabilise OTTO and Recover Your Pages
- Run a fresh scan: Go to Left sidebar → OTTO SEO → All Sites and click Scan next to your site. This forces OTTO to recrawl with the latest fixes applied and clears stale NULL status-code entries.
- Check for stuck reprocessing: In Left sidebar → OTTO SEO → Overview, confirm your site does not show a Processing or Pending status badge. If it does, contact support immediately via the chat widget.
- Review the All Audits log: Navigate to Left sidebar → OTTO SEO → All Audits to see a history of changes OTTO applied or rolled back. This helps you identify which pages lost their optimisations and when.
- Check Crawl Monitoring for 500 errors: Go to Left sidebar → OTTO SEO → Crawl Monitoring and filter by 5xx status codes. Any URLs showing 500 errors should be flagged to support so the Gateway rewrite issue can be investigated for your domain.
- Re-apply optimisations to reverted pages: Once the scan completes and no errors remain, OTTO will automatically re-suggest optimisations for pages that were rolled back. Apply them to restore your Flawless count.
- Monitor GSC re-indexing: After 500 errors are resolved, Google typically re-crawls and re-indexes affected pages within 1–4 weeks. Your ROI figure will rise again as those pages return to the index.
💡 How to Prevent This From Happening Again
- Keep a staging environment key active if your site uses custom render paths — this prevents OTTO from bailing out and dropping canonicals mid-render.
- Do not freeze and unfreeze OTTO rapidly during active reprocessing, as this can trigger the stuck-state bug.
- Check Crawl Monitoring weekly for any spike in 4xx or 5xx errors so you can catch gateway issues before Google de-indexes pages.
- Review the All Audits log after every OTTO scan to confirm optimisations were applied and not rolled back.
🙋 Still Seeing Discrepancies?
If your page count or ROI figures continue to fluctuate after following the steps above, or if you believe credits were unfairly consumed during a crash event, our support team can manually audit your account history and arrange corrections.
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.