🔍 Overview
This article covers four common issues Search Atlas customers run into: a Site Audit showing 0 crawled pages, JS Rendering appearing enabled on a Starter plan, article generation failing despite available credits, and OTTO SEO showing a Disengaged status. Each section explains why the issue happens and the steps to resolve it.
📊 Site Audit Shows 0 Crawled Pages
If your Site Audit completes but shows 0 crawled pages, or appears stuck for many hours, one of the following is likely the cause.
JS Rendering is slowing the crawl significantly. When JS Rendering is enabled, crawls run approximately 19 times slower than a standard crawl. A site with a modest crawl budget can take 13–31 hours to finish. This is expected behaviour, not a failure — the crawl is still running in the background.
What to do:
- Go to OTTO SEO and open your Site Audit settings.
- Check whether JS Rendering is toggled on.
- If you do not specifically need JavaScript rendering for your site, turn it off and re-run the crawl. The audit will complete much faster.
- If JS Rendering is required, allow up to 31 hours for the crawl to finish before assuming it is stuck.
- If the crawl remains at 0 pages after 31 hours with JS Rendering off, 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.
⚙️ JS Rendering Appears Enabled on a Starter Plan
JS Rendering is a feature available on higher-tier plans. If you are on a Starter plan and see JS Rendering toggled on inside your Site Audit settings, this is a display issue — the toggle may appear active but the feature does not run at the crawl level on your plan.
What to do:
- Navigate to your Site Audit settings within OTTO SEO.
- Manually toggle JS Rendering off, then save your settings.
- Re-run the Site Audit to confirm pages are crawled correctly.
- If the toggle cannot be changed or the problem persists, 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.
If you need JS Rendering as a core part of your workflow, consider upgrading your plan. You can review plan options from your account settings.
💡 Cannot Generate Articles Despite Having Credits
Seeing an error when generating articles — even though your credit balance shows available credits — is usually caused by one of three things: a temporary sync delay, a session issue, or credits being allocated to a different workspace.
What to do:
- Refresh your browser and navigate back to Left sidebar → Content → Content Genius (What are we writing today?).
- Check that you are in the correct workspace — credits are workspace-specific. Switch workspaces from the top of the left sidebar if you manage more than one.
- Try generating a single article rather than multiple at once to rule out a bulk-request error.
- Log out and log back in to force a session refresh, then attempt article generation again.
- If the error message references a specific credit type (for example, AI words vs. article credits), confirm which credit pool applies to the article type you are generating. Different content tools within Content may draw from different credit pools.
- If none of the above resolves the issue, 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 — share a screenshot of the error message to speed up the resolution.
🚀 OTTO SEO Shows "Disengaged" Status
An OTTO Disengaged status means OTTO is not actively applying or monitoring optimisations for the connected site. This can happen after a plan change, a site reconnection, or if OTTO was manually disengaged previously.
What to do:
- Open OTTO SEO → All Sites (SEO Automation) from the left sidebar.
- Select the site that shows Disengaged.
- Look for the Engage OTTO button on the site dashboard and click it.
- Confirm the engagement prompt if one appears.
- Wait a few minutes, then refresh the page to verify the status has changed to Active.
- Re-run your Site Audit after re-engaging OTTO so that suggestions and deployed changes are reported accurately.
Note: If OTTO was disengaged during a period when JS Rendering was active, some page titles or deployed changes may have been misreported. Re-running the audit after re-engaging resolves this display inconsistency.
🔄 Quick Troubleshooting Reference
- Crawl stuck or slow: Disable JS Rendering and re-run, or wait up to 31 hours if JS Rendering is needed.
- JS Rendering toggle on Starter plan: Turn it off manually and re-run the audit.
- Article credit error: Check workspace, refresh session, confirm correct credit pool.
- OTTO Disengaged: Click Engage OTTO, then re-run the Site Audit.
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.