<p>This article covers OTTO crawl behavior, schema deployment, technical SEO automation, indexing requests, Knowledge Graph generation, and Local SEO reporting.</p>
<h2>⚠️ Error 1: OTTO crawl shows "in progress" for hours without completing</h2>
<p><strong>What's happening:</strong> Large sites or sites with redirect chains can cause crawl timeouts.</p>
<p><strong>Steps to try:</strong></p>
<ul>
<li>Go to Left Sidebar → OTTO SEO → Site Audit → Overview (Website Overview) → Recrawl Site button</li>
<li>If the recrawl button is greyed out, wait 30 minutes, refresh the page and try again</li>
<li>For very large sites (10,000+ pages), crawls may take up to 4 hours</li>
</ul>
<h2>⚠️ Error 2: OTTO schema deployments are not appearing on the live site</h2>
<p><strong>What's happening:</strong> Schema is deployed via our content delivery layer. DNS propagation or caching on your site can delay visibility.</p>
<p><strong>Steps to try:</strong></p>
<ul>
<li>Use Google's Rich Results Test to check if schema is present</li>
<li>If not visible after 24 hours, go to Left Sidebar → OTTO SEO → All Sites (SEO Automation) → Select Your Site → OTTO Grader (Onpage Optimizations) → Schema Markup → Regenerate → Enable</li>
<li>Confirm your CMS connection is active</li>
<li>WordPress users: confirm the Search Atlas WordPress plugin is installed and connected</li>
</ul>
<h2>⚠️ Error 3: Technical SEO fixes show as "applied" but are not live</h2>
<p><strong>What's happening:</strong> Fixes applied through OTTO require your CMS connection to be active. If the connection token expired, fixes queue but do not push.</p>
<p><strong>Steps to try:</strong></p>
<ul>
<li>Go to Top-right Corner Avatar → Settings → CMS Connectors</li>
<li>Reconnect your CMS integration</li>
<li>Clean cache</li>
<li>Re-apply the pending fixes</li>
</ul>
<h2>⚠️ Error 4: Site Audit not detecting new pages added after the last crawl</h2>
<p><strong>What's happening:</strong> OTTO crawls are scheduled — new pages are picked up on the next scheduled crawl, not immediately.</p>
<p><strong>Steps to try:</strong></p>
<ul>
<li>Trigger a manual recrawl from Left Sidebar → OTTO SEO → Site Audit → Overview (Website Overview) → Recrawl Site button</li>
<li>Note: a Site Audit recrawl updates Site Audit and Page Explorer only. It does not update the OTTO project. See the next section for how to get new pages into OTTO.</li>
</ul>
<h2>⚠️ Error 5: OTTO on-page optimization pages not appearing after recrawl (only partial pages/fixes showing)</h2>
<p><strong>What's happening:</strong> After a recrawl, OTTO may detect all new pages in Site Audit, but the On-Page Optimizations section may only show fixes for a subset of pages (for example, 1 fix visible despite 17 pages detected). This is typically caused by a project processing issue on the backend that requires a manual reprocess.</p>
<p><strong>Steps to try:</strong></p>
<ol>
<li>First, trigger a recrawl: Left Sidebar → OTTO SEO → Site Audit → Overview (Website Overview) → Recrawl Site button</li>
<li>Wait for the crawl to complete, then check Left Sidebar → OTTO SEO → Overview (OTTO Grader, Onpage Optimizations) to see whether the full page count is now reflected</li>
<li>If the page/fix count still does not match the number of detected pages, click the <strong>Reprocess</strong> button on the OTTO project dashboard when it is available. If you do not see the button, or the count still does not match after the reprocess, contact Support through live chat and ask for a <strong>manual project reprocess</strong></li>
<li>Once the manual reprocess completes, refresh the OTTO dashboard and verify all pages now appear under On-Page Optimizations</li>
</ol>
<h2>⚠️ Error 6: Indexing requests not being submitted to Google</h2>
<p><strong>What's happening:</strong> Google Search Console must be connected and authorized for indexing requests to go through.</p>
<p><strong>Steps to try:</strong></p>
<ul>
<li>Go to Left Sidebar → Site Metrics → Site Explorer (GSC accounts screen)</li>
<li>If your account is not connected → Click Connect GSC Account</li>
</ul>
<h2>⚠️ Error 7: Knowledge graph is not populating</h2>
<p><strong>What's happening:</strong> The knowledge graph requires your Brand Vault to have basic company information filled in.</p>
<p><strong>Steps to try:</strong></p>
<ul>
<li>Go to More Features (top-right) → Brand Vault</li>
<li>Ensure your business name, description, and website URL are correct and saved</li>
</ul>
<h2>⚠️ Error 8: OTTO shows "No data" for a project that was previously working</h2>
<p><strong>What's happening:</strong> Projects with expired domain connections stop receiving data.</p>
<p><strong>Steps to try:</strong></p>
<ul>
<li>Go to Left Sidebar → OTTO SEO → All Sites and verify the domain is still listed</li>
<li>If the project is missing, re-add it via Left Sidebar → OTTO SEO → All Sites → + Create</li>
</ul>
<h2>⚠️ Error 9: Local SEO presentation reports</h2>
<p><em>(Section content to be completed.)</em></p>
<h2>Why do new pages show in Page Explorer but not in OTTO Automation after a recrawl?</h2>
<p>The Site Audit crawl and OTTO reprocessing are two different processes. Running a Site Audit scan (recrawl) does not update your OTTO project. New pages can appear in Page Explorer while they do not yet appear in OTTO Automation.</p>
<p>For OTTO to pick up the new pages, the project needs to be reprocessed. There are two ways:</p>
<ul>
<li>Click the <strong>Reprocess</strong> button on the OTTO project dashboard. If the button is not visible on your dashboard, contact Support through live chat and ask for a manual project reprocess.</li>
<li>Wait for the next scheduled automated reprocess.</li>
</ul>
<h3>What if the Reprocess button is not available?</h3>
<p>After a reprocess, the button becomes available again only after a cooldown. The dashboard shows when it will be available again (for example, in 2 hours). Come back once it is available and run it again.</p>
<h3>Does changing the crawl frequency start a reprocess right away?</h3>
<p>No. Changing the crawl frequency does not force an immediate run. Use the Reprocess button when it is available, or wait for the scheduled run.</p>