Troubleshooting: Audit Stuck, Empty or Zero Results

⚡ Fix Page Explorer Stuck in Processing Status

Overview The Page Explorer tool inside OTTO SEO's Site Audit occasionally shows a "Page is being processed" banner for an extended period, and the Recrawl Page button becomes disabled. This article explains what to do if you encounter this stuck state. Why Does This Happen? When a recrawl is triggered, Page Explorer runs background processing tasks for the page. In some cases, a known issue can cause the processing banner to persist even after the core work is complete, leaving the page flagged as still processing in the UI. What You Should Try First 1. Wait a little while. Short processing delays are normal. Give the system some time to finish background tasks before taking further action. 2. Hard-refresh your browser. Force a full page reload to clear any stale UI state that may be displaying an outdated processing status. 3. Check if your data is already updated. Scroll through the Page Explorer report for the affected URL. If metrics, issues, and recommendations are visible and up to date, the crawl likely completed successfully and only the UI state is stuck. 4. Navigate away and return. Go to a different section of the platform and then navigate back to Page Explorer. This can sometimes clear a stale processing state displayed in the UI. If the Banner Remains Stuck If the processing banner has been showing for an extended period and the Recrawl Page button remains disabled after trying the steps above, the processing job likely needs to be manually cleared on the backend. To escalate, please have the following ready: - The exact URL of the page showing the stuck processing status - Approximately how long the processing status has been stuck - The name of the OTTO SEO project or site affected 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 Stuck Page Explorer Data

🔍 Understanding outdated Page Explorer data Page Explorer data can occasionally remain unchanged while Search Atlas processes a crawl or updates site metrics. This may affect all pages or only specific segments, statuses, and filters. A recent crawl may also show different page totals across screens while processing is still completing. ✅ Check the latest available data 1. Open Site Metrics from the left sidebar. 2. Review the Page Explorer results and note the latest crawl or update date shown. 3. Clear active filters, segments, or status selections to confirm whether the issue affects all pages. 4. Check additional pages using pagination. If a filter was recently applied, return to page 1 before reviewing the results. 🔄 Refresh the Page Explorer view 1. Refresh the browser page. 2. Reopen Site Metrics from the left sidebar. 3. Remove and reapply any filters or segments. 4. Compare the results with the previous update date rather than relying only on the visible page count. 🧭 Check whether processing is still running Data may not update immediately after a crawl, analysis, or profile refresh. Allow the process time to finish, then check Page Explorer again. If other Site Metrics modules, such as backlinks, competitors, topical data, or position changes, are also showing old information, the delay may affect the broader site profile rather than Page Explorer alone. 🛠️ When to request help Contact the team if the data remains unchanged after refreshing and checking again later, especially when: - All pages have been stuck since a previous date. - The update date does not change after a completed analysis. - Filters show inconsistent results or page totals. - You see an error such as “Failed to Fetch Updated Profile.” - Different screens show conflicting crawl or page counts after processing has finished. Before contacting us, record the site, the date the data became outdated, the filters used, and any visible error message. A screenshot can also help us investigate faster. 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.

🔍 Site Audit Healthy Pages Showing Zero Score

🧐 What Does a Zero Healthy Pages Score Mean? If your Site Audit shows 0 healthy pages, it does not necessarily mean your site has no healthy content. In most cases, this reading appears because the audit has not yet completed its full crawl, the results have not been refreshed after a recent crawl, or all crawled pages currently have at least one flagged issue preventing them from being classified as healthy. A page is only counted as healthy when it passes every technical check in the audit. Even a single minor issue — such as a missing meta description or a slow load time — moves that page out of the healthy category. ⚙️ How to Diagnose the Zero Score 1. Check the crawl status. Navigate to your Site Audit dashboard and confirm the crawl shows a Completed status. If the crawl is still running or was interrupted, wait for it to finish and then refresh the page. 2. Review the total pages crawled. If the crawled page count also shows zero, the crawler may not have been able to access your site. Verify that your robots.txt file is not blocking the Search Atlas crawler and that your site is publicly accessible. 3. Look at issue distribution. Open the Issues tab within Site Audit. If every page carries at least one flagged issue, that explains the zero healthy count. Focus on resolving the most common issues first to move pages into the healthy column. 4. Re-run the crawl. If you recently made fixes to your site, the current results will not reflect those changes. Trigger a new crawl by going to OTTO SEO → Site Audit → Overview (Website Overview) and clicking Recrawl Site and allow it to complete before reviewing your scores again. 📋 Understanding the Pruning Report The Pruning Report is the Page Pruning page inside Site Audit (OTTO SEO → Site Audit → Page Pruning for the selected audit) and is designed to help you identify pages that may be diluting your overall site quality. It groups pages into categories based on their performance signals, such as low traffic, thin content, or poor engagement metrics. Here is how to use the pruning report effectively: - Review each category separately. Pages are grouped by the type of concern — for example, low organic traffic, duplicate content, or no inbound internal links. Work through one category at a time rather than trying to address everything at once. - Decide on an action for each page. For every page flagged, you have three main options: Improve the page by adding value, Consolidate it by merging it with a related page, or Remove it if it provides no value and cannot be improved. - Use the status column. Mark each page with your chosen action inside the report. This helps you track progress and keeps your audit organised over time. - Do not delete pages impulsively. Always check whether a flagged page has any inbound links, conversions, or direct traffic before deciding to remove it. The report highlights candidates for pruning — the final decision is yours. ✅ How to Improve Your Healthy Pages Count Raising the number of healthy pages is a gradual process. Follow these steps to make consistent progress: 1. Open the Issues tab in Site Audit and sort issues by pages affected to find the highest-impact problems. 2. Address widespread technical issues first — such as missing title tags, broken internal links, or pages returning error status codes — because fixing one issue type can unlock healthy status for many pages at once. 3. After making changes on your site, return to Site Audit and run a new crawl to update your results. 4. Repeat this cycle regularly. Aim to schedule crawls at least once a week so your healthy pages metric stays current. 💡 Tips for Keeping Your Score Accurate - Make sure the correct domain is connected and verified in your project settings before running a crawl. - If your site uses JavaScript-heavy rendering, some pages may not be fully crawled. Check your crawl settings and ensure the crawler is configured to handle your site's technology. - Keep your crawl frequency consistent. Infrequent crawls mean the data you see may not reflect recent improvements or regressions. 🛠️ Still Seeing Zero After a Full Crawl? If your healthy pages count remains at zero after completing a fresh crawl and you have confirmed there are no blocking issues on your site, our team can investigate the crawl data 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 Blank Data in OnPage Audit Fields

🧩 What This Issue Looks Like You open an OnPage Audit and the field labels — such as Content Score, Word Count, and others — are visible but contain no data. (Note: Domain Rating is found under Keywords → Keyword Research (Keyword Research), not in the OnPage Audit.) The audit appears to have run, but every metric is blank or missing values. This is a known bug that requires investigation and a fix on the backend. There are no self-serve UI controls that reliably resolve it. 🛠️ What Is Actually Happening This is a backend data-loading issue affecting certain OnPage Audit projects. When it occurs, the audit fields fail to populate even though the audit appears to have completed. The root cause requires intervention from our engineering team and cannot be resolved by refreshing the page or adjusting browser settings alone. 📋 How to Escalate This Issue Because this is a backend bug, the fastest path to resolution is to contact our support team directly. To help us investigate as quickly as possible, please have the following information ready before reaching out: - Project name — the exact name of the project where the blank fields appear. - Affected fields — list which specific fields are blank (e.g. Content Score, Word Count). - When it started — the approximate date and time you first noticed the issue. - Any error messages — the exact text of any error or warning message displayed on the page, if applicable. Having these details ready will allow our team to locate your project quickly and apply the appropriate backend fix without unnecessary back-and-forth. 💡 What to Expect Once our team investigates your project on the backend, the missing data should be restored. You do not need to delete or recreate your audit — your existing audit and any historical snapshots will remain intact after the fix is applied. 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 Stuck OTTO Site Audit Scans

Overview If your OTTO Site Audit scan has been processing for an extended period without completing — especially on SiteGround hosting — a server-level cache conflict may be preventing the crawler from finishing its work. This article explains the general cause and what steps you can take, and what to have ready if you need to escalate to our team. Why Scans May Get Stuck on SiteGround SiteGround includes a built-in caching system that can interfere with OTTO's crawler by serving cached page responses instead of live content. This can cause the scan to receive incomplete or inconsistent data, leading to the crawl stalling rather than finishing or failing cleanly. Other hosting environments that apply aggressive server-side caching may exhibit similar symptoms. Step 1 — Clear Your SiteGround Cache Before retrying your OTTO scan, clear any active caches through your SiteGround hosting controls or any SiteGround-related caching plugin installed on your WordPress site. The exact steps will depend on the tools your hosting setup uses. In general: - Log in to your WordPress admin dashboard. - Locate any caching plugin or hosting-level cache management tool provided by SiteGround. - Clear or purge all cached content. - If your setup allows it, temporarily disable server-side caching while the OTTO scan runs. - Save any changes before proceeding. If you are unsure how to manage caching for your specific SiteGround configuration, consult SiteGround's official support documentation or contact their support team for guidance. Step 2 — Retry Your OTTO Site Audit Scan After clearing your cache, return to Search Atlas and attempt to start a new OTTO Site Audit scan for your connected website. If a previous scan is still showing as active or stuck, wait for it to time out or contact our team to have it cleared on the backend before starting a fresh crawl. Step 3 — Re-Enable Caching After the Scan Completes Once your scan has completed successfully, re-enable any caching you disabled in Step 1 to restore normal site performance for your visitors. If the Scan Remains Stuck If your OTTO Site Audit scan continues to stall after clearing your cache and retrying, our support team can investigate on the backend. To help us resolve this as quickly as possible, please have the following ready when you reach out: - The domain or project name connected to the stuck scan. - The approximate time the scan was started and how long it has been stuck. - Your hosting provider and any caching plugins currently active on your site. - Any error messages or unusual statuses visible on your OTTO dashboard. 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.

🛠️ Site Auditor: Fixing "Invalid URL" Errors and Missing Sites on the All Audits Page

Most "Invalid URL" reports in Site Auditor are actually a visibility issue: the site was added successfully but sits below the first page of the All Audits table. Click Load More and refresh the tab first, then use the steps below only if the site is genuinely missing. 📋 What the All Audits Page Does The All Audits page is where you manage every site submitted to Site Auditor. From here you can launch new audits, search and sort existing ones, trigger recrawls, and open detailed audit reports. Navigation: Left Sidebar → OTTO SEO → Site Audit → All Audits Note (June 2026): The All Audits page interface — including pagination, row layout, the top bar, and filters — may change shortly as an updated design rolls out. The steps below describe the current layout and will be revised when the new design ships. 🔍 Find a Site That Is Not Showing in All Audits The All Audits table loads a limited batch of entries at a time, so a site you just added may exist but not appear on the first view. Work through these checks before assuming an audit failed: 1. Scroll to the bottom of the table and click Load More (if available) to retrieve the next batch. Repeat until your target site appears. 2. If a recently added site still does not appear, refresh the browser tab — newly submitted audits sometimes render only after the page reloads. 3. Use the search bar at the top of the table to filter by domain name instead of paging through every entry. Note: A separate known pagination bug affects the Custom URL Based Indexing feature (page size and navigation), which is distinct from the All Audits page covered here. All Audits pagination works normally — if Load More does not retrieve additional entries, contact Support using the steps at the end of this article. Outcome: Your site appears as a row in the All Audits table with its status, and you can open its report. ⚠️ Why You See an "Invalid URL" Error When the Site Is Actually Added In many cases the URL is valid and the audit starts normally — the site is simply hidden by pagination. Support has confirmed identical URLs working on their end while the customer's added sites were already present in the All Audits list, just below the first page. Before troubleshooting the URL itself: - Click Load More at the bottom of the All Audits table to load every entry. - Refresh the browser tab so any just-added sites render. - Search by domain name to confirm whether the site is already listed. If the site is still absent after loading all entries and refreshing, continue with the format and submission checks below. ✅ Verify the URL Format If the site is genuinely missing, confirm the URL is formatted correctly: - Include the protocol: https://yourdomain.com/ or http://yourdomain.com/. - Remove trailing query strings (?), fragments (#), and leading or trailing spaces. - If your domain uses a non-standard TLD (for example .download), it may have been affected by a known validation issue — see the URL Validation Error for Non-Standard TLDs in Site Explorer and OTTO article for current status, then re-add the domain to confirm it works. Outcome: A correctly formatted URL is accepted and the audit begins crawling. 💬 Use the Agent Chat Workaround For persistent errors when adding a domain to OTTO or Site Auditor, Agent Chat may provide an alternative submission path. Verify the exact Agent Chat label and location within your OTTO project first, as the interface can vary. 1. Open the relevant OTTO project and locate the Agent Chat option. 2. Type: Add [your full domain URL] as a new site audit. 3. The agent uses an alternative submission path to add the domain. Outcome: The domain is submitted through Agent Chat and appears in your All Audits list. 🔁 Check for Duplicate or Pending Submissions Submitting the same domain more than once can cause display inconsistencies. Search by domain name on the All Audits page and review any entries showing a Pending or Processing status before re-adding the site. 🧹 Clear Cache and Try a Different Browser - Clear your browser cache and cookies. - Retry in a different browser — Chrome, Edge, or Safari are recommended. - Disable browser extensions that may interfere with the Search Atlas dashboard. 🆘 Contact Search Atlas Support If the URL passes format checks and the site is still missing after loading all entries, contact Search Atlas Support through the in-app Help Widget. Include the exact URL(s), your browser, and the full error message text so the team can reproduce the issue. ⚙️ Other Actions on the All Audits Page - New audit: Click + New Audit and enter your domain URL. - Recrawl: Go to OTTO SEO → Site Audit → Overview (Website Overview) and click the Recrawl Site button. - Open a report: Click the domain name or report icon to view the full audit. - Sort and filter: Click any column header to sort entries; available columns may include date, health score, and status. 🔗 Related Articles - How to Run a Site Audit in Search Atlas - How to Recrawl an Existing Site in Search Atlas - URL Validation Error for Non-Standard TLDs in Site Explorer and OTTO - OTTO Setup and Feature Walkthrough 🎯 You now know to click Load More and refresh the tab before assuming an audit failed, and how to verify URL format or use the Agent Chat workaround for genuine errors. If a site is still missing after these steps, reach out through the in-app Help Widget with your exact URL and error text.

🔍 Fix Shopify Location Pages Missing from Site Audit

🗺️ What This Article Covers If your Shopify store has location pages stored under the /pages/ path and they are not appearing in Search Atlas's Site Audit or Page Explorer — or if their meta descriptions look outdated despite being updated in Shopify — this article explains what to have ready when reaching out to our support team. 🤔 Why This Happens Shopify location pages under the /pages/ path can go missing from the Search Atlas Site Audit crawler. The root cause varies by store and requires investigation by our support team to identify correctly. ✅ Information to Gather Before Contacting Support Because this issue requires investigation by our support team, please collect the following details so we can resolve it as quickly as possible: 1. Your Search Atlas project name and the full domain URL associated with the Site Audit project where pages are missing. 2. Example URLs of the specific Shopify location pages (e.g. yourstore.com/pages/location-name) that are not appearing in Site Audit or Page Explorer. 3. Whether the pages appear in your Shopify sitemap. You can check this by visiting yourstore.com/sitemap.xml in a browser and looking for your location page URLs. Note whether they are present or absent. 4. Whether each missing page is publicly visible in your Shopify store settings. 5. When the pages were last updated in Shopify and approximately when the most recent Site Audit crawl was run. Sharing these details upfront allows our team to identify the root cause and apply the correct fix. 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 Historical Metrics in Site Metrics

Why Historical Metrics May Not Display The Site Metrics tab displays historical traffic and performance data for the domains you analyze. Sometimes this data may not appear, appear incomplete, or show stale information. This can happen for several reasons, including temporary data processing delays, browser caching issues, or a broader system issue. Troubleshooting Steps - Hard refresh your browser: Perform a hard refresh (Ctrl+Shift+R on Windows, Cmd+Shift+R on Mac) to clear any cached data that may be preventing updated metrics from displaying. - Check the date range: Make sure the date range selected covers the period where you expect to see data. A narrow or custom range can hide months that are actually available. - Allow time for processing: Data processing delays can cause temporary gaps in historical metrics. If the issue appeared recently, check back after some time has passed. When to Contact Support If historical metrics are still not displaying across one or more domains after trying the steps above, there may be a broader issue affecting data availability. To help us investigate quickly, please have the following information ready: - The affected domain(s) - Which specific metrics are missing or incomplete (e.g., organic traffic, paid traffic, keywords, backlinks) - The date range where data appears incomplete or missing - When you first noticed the issue 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 Loading Errors During Site Audit

🔍 Overview If OTTO fails to load after you have completed the setup steps, the most common cause is not a technical error with the installation itself. OTTO requires a completed site audit before it can activate and display your SEO recommendations. This audit can take up to 24 hours to finish, and OTTO will remain in a loading or pending state until it does. This article explains the site audit prerequisite, how to check its progress, and what to do if the process takes longer than expected. 📋 Why the Site Audit Is Required Before OTTO can analyse your website and generate optimisation tasks, it needs a full picture of your site's current SEO health. The site audit crawls your pages, collects technical data, and builds the foundation OTTO uses to prioritise recommendations. Without a completed audit, OTTO has no data to work from and cannot load your dashboard correctly. - The site audit runs automatically when you connect a project to OTTO. - Audit duration depends on the size of your website. Most audits complete within a few hours, but large sites can take the full 24 hours. - No action is required from you while the audit runs. ✅ How to Check Your Site Audit Progress You can monitor the status of your site audit at any time by following these steps: 1. Open the Search Atlas platform and sign in to your account. 2. Navigate to OTTO SEO → Site Audit (All Audits) at /site-audit in the left sidebar. 3. Locate the project connected to OTTO and review the audit status column. 4. If the status shows In Progress or a percentage complete, the audit is still running. This is expected behaviour. 5. If the status shows Completed, return to OTTO SEO → All Sites (SEO Automation) in the left sidebar and reload OTTO. Refreshing the OTTO page before the audit is marked as completed will not speed up the process and may display a loading error. Allow the audit to finish fully before expecting OTTO to activate. 🔄 What Happens When the Audit Completes Once the site audit reaches 100% completion, OTTO updates its status automatically. You do not need to restart the audit or re-connect your project. The expected sequence is: - Site audit status changes to Completed in the audit list. - OTTO activates and loads your personalised SEO task list. - Your dashboard populates with recommendations, fixes, and priority scores based on the audit data. If you are logged in when the audit finishes, simply refresh the OTTO SEO page to see OTTO fully loaded. If you return later, OTTO will load automatically on your next visit. ⚠️ When to Escalate the Issue In most cases, waiting for the site audit to complete resolves the OTTO loading error without any further action. However, you should escalate if any of the following situations apply: - The site audit status has shown In Progress for more than 24 hours without advancing. - The audit status is shown as Completed but OTTO still fails to load after refreshing. - The audit list page shows an error or your project does not appear in the list at all. - You connected your project more than 24 hours ago and have not received any audit progress update. If any of these conditions apply, our team can investigate the audit job directly and resolve any processing delays on the backend. 🛠️ Quick Troubleshooting Summary 1. Check the audit status at OTTO SEO → Site Audit (All Audits) (/site-audit) before assuming an installation problem. 2. Wait up to 24 hours if the audit is still in progress. This is normal and expected. 3. Refresh OTTO via OTTO SEO → All Sites (SEO Automation) only after the audit status shows Completed. 4. Escalate to the team if the audit stalls beyond 24 hours or if OTTO does not load after a completed 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.

🔧 Troubleshooting Stalled Content Score, Authority, and UX Signals

Overview If your Content Score, Authority, or UX Signals metrics appear stuck or are not improving over time, this article explains what each metric represents and what you should have ready when reaching out to our team for help. What These Metrics Measure Content Score reflects how well your pages are optimised for target keywords, topical depth, and on-page structure. A stalled Content Score typically means content has not been updated or expanded recently, target keywords are not well-aligned with page content, or topic gaps exist relative to competing domains. Authority is driven primarily by your backlink profile — the number, quality, and relevance of domains linking to your site. If Authority is not growing, the referring domain count may have plateaued or declined. UX Signals reflect real-world user experience data (such as Core Web Vitals and CrUX data). These metrics are sourced from external data providers and may update on a different cadence than other metrics in the platform. What to Try First - Confirm your domain is correctly configured in your Search Atlas project — check that the target country, language, and domain format (with or without www) match your intended settings. - Check whether content on your key pages has been updated recently. Metrics are unlikely to improve if no changes have been made to the underlying pages. - Review your backlink profile for any net loss of referring domains over the past 30–90 days, which would explain a stalled or declining Authority score. - For UX Signals, be aware that real-world experience data from external sources may take longer to reflect recent site improvements. When to Contact Support If you have reviewed the above and your metrics remain unexpectedly stalled, please contact our team. To help us investigate efficiently, have the following ready: - Your project name and the exact domain as it appears in Search Atlas - Which specific metric(s) appear stalled (Content Score, Authority, and/or UX Signals) - Approximately how long the metric has been flat or declining - Any recent changes you have made to your site or content that you expected to be reflected 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 Site Audit Postprocessing Failures and Schema Quota

🔍 Overview Some customers notice that their site audit crawls complete the crawling phase but then show both crawl_state: failed and postprocessing_status: failed. In the same session, schema generation may consume quota credits for pages — sometimes 17 or more — while producing no visible output. This article explains what causes these issues, what they mean for your data, and what steps you can take right now. ⚙️ What Is Postprocessing and Why Does It Fail? After Search Atlas finishes crawling your site, it runs a postprocessing stage that compiles raw crawl data into the audit issues, scores, and recommendations you see in your dashboard. If this stage fails, the audit cannot display results — even if pages were successfully crawled. The most common reason postprocessing fails is a data conflict caused by concurrent activity. If a second crawl starts — or existing crawl data shifts — while the first crawl is still being processed, the system encounters rows it cannot reconcile and throws an internal error. This is a known platform issue and engineering has already deployed a fix for the most common crash scenarios (KeyError and IndexError during issue compilation). Other factors that can contribute to postprocessing failures include: - JavaScript-heavy pages: Sites with JS rendering can take significantly longer to crawl (median crawl time is over 13 hours in some cases). A crawl that appears stuck may still be running. Do not cancel and restart — this can trigger the concurrent conflict described above. - Homepage detection errors: On certain site configurations, the system fails to identify the homepage correctly, resulting in zero pages crawled and a failed state. This is actively being resolved by engineering. - Stale recrawl frequency settings: Some audits are stuck on a "never reprocess" state due to missing recrawl frequency data. A backfill fix is in progress to resolve this automatically. 📊 Why Does Schema Generation Consume Quota With No Output? Schema generation quota is deducted at the point the generation job is triggered — before output is confirmed. If postprocessing fails or the crawl produces incomplete page data, the schema generation job may still fire for the pages that were queued, consume credits, and then fail silently because it has no valid page content to work with. This means you can lose quota credits for pages — such as the 17-page scenario — without receiving any schema markup in return. The credits are consumed because the generation attempt was made, not because output was produced. Your credits are not lost permanently. If schema generation fails due to a platform-side postprocessing error rather than invalid input on your end, the support team can review your account and arrange a credit adjustment where appropriate. 🚀 Steps to Take Right Now 1. Check your crawl status: Go to Left sidebar → OTTO SEO → Site Audit → All Audits and review the status of the affected audit. If the status shows failed, do not immediately trigger a re-crawl. 2. Wait before retrying: If your site uses JavaScript rendering, allow at least 14–16 hours before concluding a crawl is stuck. Cancelling early and restarting increases the risk of a concurrent conflict. 3. Avoid running overlapping crawls: Do not start a new crawl for the same site while a previous crawl or postprocessing job is still active. Check Left sidebar → OTTO SEO → Site Audit → Crawl Monitoring to confirm all jobs for that site have fully completed before launching a new one. 4. Retry the audit once: After confirming no other crawl is active for the site, go to Left sidebar → OTTO SEO → Site Audit → All Audits, locate the failed audit, and trigger a fresh crawl. The platform fix for postprocessing crashes is already deployed and should resolve the most common failure mode. 5. Note your quota consumption: If schema generation consumed credits without producing output during the failed session, make a note of the affected site name, the date of the failed crawl, and the approximate number of pages affected. You will need this when contacting support for a credit review. 💡 What to Expect Going Forward The engineering team has resolved the primary crash causing postprocessing failures. Additional fixes currently in development will address homepage detection errors and stale recrawl frequency settings. These will be applied automatically — no action is needed on your part. If you re-run the audit and it fails again, or if you believe your schema quota was consumed unfairly, the support team can investigate your specific account logs and take action. 🆘 Still 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.

🛠️ Fix Site Audit and OTTO Tasks Stuck at Approval

🔍 Overview Some customers notice that Site Audit and OTTO tasks appear to start normally but never complete — they consistently stop at the approval step, even after waiting several days or retrying multiple times. This is a known issue that our team investigates on a case-by-case basis. ⚙️ What Is the Approval Step? The approval step is a required checkpoint where OTTO waits for you to review and confirm recommended changes before applying them to your site. Tasks will remain paused at this step until action is taken. If your tasks are stuck here and you are unable to move them forward, this may indicate an underlying issue that requires backend investigation. 📋 What to Have Ready When Escalating Because this issue requires investigation by our support team, please have the following information ready before reaching out: - Project name — the exact name of the Search Atlas project where the tasks are stuck. - Affected site URL — the domain associated with the stuck tasks. - Task type — which specific Site Audit or OTTO task types are affected (e.g. meta titles, schema, internal links). - How long the tasks have been stuck — approximate date and time when you first noticed the issue. - Any error messages — copy the exact text of any error or status message displayed on the affected tasks. - Steps already attempted — note anything you have already tried, such as navigating away and back, or waiting for a data refresh. Having this information ready will allow our team to investigate and resolve the issue as quickly as 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.

🛠️ Fix Stuck Site Audit and OTTO Tasks

🔍 Overview Some customers notice that Site Audit crawls or OTTO AI agent tasks start but never seem to finish. In most cases the job is still running — it is processing in the background and will complete. This article explains the common causes, what to check, and how to keep things moving. ⚙️ Why Tasks Appear Stuck There are several known reasons a Site Audit or OTTO task may look frozen: - JavaScript rendering slows crawls significantly. When JS rendering is enabled, audits can take up to 13–17 hours to complete. This is expected behaviour, not a bug. The crawl progress bar may appear idle for long periods. - Worker interruption during retry. If a background worker pod is restarted while a task is retrying, the job can enter an in_progress state that does not resolve on its own. This requires a manual refresh or re-trigger. - Recrawl frequency set to "never reprocess". If a site's recrawl frequency was not set correctly, the audit will not queue a new crawl. It will appear stuck because no reprocess is scheduled. - Orphaned reprocess tasks. In rare cases, an internal reprocess task becomes detached from the main audit job. The status reads "still processing" indefinitely until the orphaned task is cleared. 🚀 Steps to Resolve a Stuck Task 1. Go to Left sidebar → OTTO SEO → All Sites (SEO Automation) (URL: /seo-automation-v3). 2. Locate the affected site or project. Check the current status label — if it shows in_progress or still processing for more than 18 hours, the task may need a manual reset. 3. Click Refresh data on the project dashboard. This triggers a status sync and can resolve misread processing states. 4. If the audit does not update after refreshing, open the project and use the Create Project option to re-initiate a fresh audit run for the affected domain. 5. If you recently enabled JS rendering and the audit has been running for fewer than 17 hours, wait for the crawl to complete before taking further action. JS-rendered audits are significantly slower by design. 📊 Check Your Recrawl Frequency Setting A missing or incorrect recrawl frequency is a common hidden cause of audits that never restart. To verify your setting: 1. Go to Left sidebar → OTTO SEO → All Sites (SEO Automation). 2. Select the affected site. 3. Review the crawl schedule or recrawl frequency setting. If it is set to never reprocess, update it to your preferred frequency (daily, weekly, or monthly). 4. Save the change and trigger a manual crawl to confirm the audit queues correctly. 💡 A Note on Regulated Industry Instructions (FDA and Similar) If you have added compliance instructions — such as FDA advertising guidelines — to your OTTO or AI agent workflow, it is important to understand how the agent reads and applies those instructions: - OTTO and the AI agent process your custom instructions on a per-task basis. If a task was already queued or cached before you added the instructions, it may complete using the previous configuration. - To ensure compliance rules are applied, add your instructions before starting a new task. Do not rely on mid-run instruction changes affecting tasks already in progress. - After saving compliance instructions, trigger a fresh audit or task run so the agent picks up the updated configuration from the start. - Always review AI-generated suggestions before publishing. The AI agent surfaces recommendations based on SEO best practices. You are responsible for verifying that any content or metadata changes meet your regulatory requirements before they go live. Search Atlas does not validate suggestions against specific regulatory frameworks such as FDA, HIPAA, or FTC guidelines. Compliance review remains the responsibility of your team. 🛠️ When to Contact Support Reach out if: - A task has been stuck for more than 18 hours and a manual refresh or re-trigger has not resolved it. - Your compliance instructions are consistently being ignored across multiple fresh task runs. - You see an audit looping between queued and in_progress repeatedly without completing. 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 Zero Scores in Holistic SEO Pillars

🔍 Overview The Holistic SEO dashboard displays four pillar scores — Content, Authority, Technical, and UX — to give you a complete picture of your site's SEO health. Some customers have noticed that Content and Authority scores appear as 0 even when their site has clear signals, such as published content and backlinks. This article explains why this happens and what to do if you are affected. ⚙️ Why Pillar Scores Show Zero Content and Authority pillar scores may display as zero due to a backend data issue. The scoring system may fail to correctly retrieve or calculate values for these pillars even when your site has relevant signals, resulting in scores displaying as zero rather than their true values. This is a known bug. If you are seeing zero scores for Content or Authority despite having active content and backlink signals on your site, this is likely caused by the same underlying issue. 🛠️ What to Do If You Are Affected Because this is a backend bug, there are no self-serve steps that will reliably resolve it. Instead, please escalate to our support team so an agent can investigate your account directly. To help us resolve this as quickly as possible, have the following ready when you reach out: - Your project or site name as it appears in the platform - The specific pillars showing zero (e.g. Content, Authority, or both) - Confirmation that your site has active content and backlink signals — for example, published pages and known referring domains - Any relevant timestamps — when you first noticed the zero scores and whether they appeared after a specific 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 Stuck Site Audit Processing Errors

🔍 Understand the Issue A site audit may show as completed but actually have a background processing error that makes results appear incomplete or stuck. This is not an approval gate or account restriction — your subscription is active and you can run new audits. 🛠️ Re-run the Audit The fastest fix is to start a fresh audit for the same domain. This bypasses the stuck processing and generates complete results. 1. Go to Left sidebar → OTTO SEO → All Sites 2. Locate the domain (e.g. easygold.com.au) in your site list 3. Start a new audit for that domain 4. Wait for the new crawl to finish and review the updated report 📊 Verify Results After the new audit completes, check the report for full data. If the issue persists, it may indicate a deeper processing problem that our engineering team has addressed in recent updates for large sites and JavaScript rendering. 💡 When to Contact Support If re-running the audit does not resolve 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.

🔧 OTTO Suggested Fixes Blank After Site Audit

🗺️ Understanding the Two-Step Model OTTO's workflow is divided into two distinct stages that must each be completed separately. Step 1 — Issue Discovery: When you run a Site Audit or recrawl your domain, OTTO scans your site and surfaces SEO issues and opportunities in the Onpage Optimizations section. This step identifies what needs to be fixed. It does not automatically create suggested fixes. Step 2 — Fix Generation: Suggested fixes must be actively generated for each issue after discovery. They will never populate on their own as a result of crawling or recrawling. This is the step most customers miss. ❓ Why Are My Suggested Fixes Blank? Seeing hundreds of blank suggested fixes after a site audit or recrawl is expected behaviour — it is not a bug or a processing delay. A blank fix field simply means no fix has been generated for that issue yet. Common reasons this happens: - You recrawled the site but did not trigger fix generation afterwards. - Only a small initial batch of fixes were generated in a previous session (for example, 4–6 out of hundreds of issues), leaving the rest blank. - Fix generation requires a deliberate action — either manual or via Atlas Agent — and does not run in the background. Important: There is no automatic background process that will populate blank fixes after a recrawl. Waiting will not cause fixes to appear. ✅ How to Generate Suggested Fixes You have two options to generate suggested fixes for your open OTTO issues. Option 1 — Generate Fixes Manually 1. Go to Left sidebar → OTTO SEO → Overview. 2. Select your site from the site list. 3. Open the Onpage Optimizations section. 4. Click into an issue category that shows blank fixes. 5. For each issue row, click the Generate Fix action button to create the suggested fix for that specific issue. Option 2 — Use Atlas Agent (Recommended for Large Sites) 1. Go to Left sidebar → OTTO SEO → Overview. 2. Select your site. 3. In the Onpage Optimizations section, activate Atlas Agent to batch-generate fixes across all open issues. 4. Atlas Agent works through the full issue list and populates suggested fixes at scale, saving you from processing hundreds of rows individually. ⚠️ What Recrawling Actually Does Recrawling refreshes the issue discovery layer only. It will: - Detect new SEO issues introduced since the last crawl. - Mark previously resolved issues as fixed. - Update issue counts and page-level data. Recrawling will not: - Generate or populate suggested fixes for any issues. - Trigger any background reprocessing of fix content. - Replace the manual or Atlas Agent fix-generation step. 🚀 Step-by-Step: Fix Blank Suggestions Now If you are seeing hundreds of blank suggested fixes, follow these steps to resolve it: 1. Confirm your recrawl has completed by checking Left sidebar → OTTO SEO → Crawl Monitoring. 2. Navigate to Left sidebar → OTTO SEO → Overview and open Onpage Optimizations for your site. 3. Use Atlas Agent to batch-generate fixes across all open issues, or generate fixes individually for your highest-priority pages first. 4. Refresh the page after generation completes to see all suggested fixes populated. 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.

✅ Site Audit Issues Page Blank Screen in Firefox (Resolved)

If the Site Audit Issues page shows a blank screen in Firefox, switch to Chrome, Edge, or Safari to access it immediately. This was a Firefox-specific rendering bug (engineering ticket SPE-770) that has been fixed and deployed to production. ⚠️ What the Issue Looks Like When using Firefox, the Site Audit Issues page renders as a completely blank screen with no error message or error code displayed. No audit data loads and no feedback appears on screen. All other supported browsers load the page correctly. 💡 Immediate Workaround Open the Site Audit Issues page in any of the following browsers instead of Firefox: - Google Chrome - Microsoft Edge - Safari (macOS only) The page loads fully in all three browsers with no loss of functionality or data. 📋 Fix Status Search Atlas engineering replicated and confirmed this as a Firefox-specific rendering defect, logged it as ticket SPE-770, and deployed a fix to production. If you were previously affected, the issue should now be resolved when using Firefox. As part of the same engineering effort, the Issues page was also upgraded with a new data layer (React Query migration, ticket OTTO-2115), which improved overall reliability and loading behaviour. Affected-pages search and filter behaviour on the Issues page was also corrected as part of this work — if you notice any differences in how the page loads or how search and filters behave, this is expected and reflects these improvements. 🛠️ If the Blank Screen Still Appears in Firefox If the Site Audit Issues page still shows a blank screen in Firefox after the fix, follow these steps: 1. Open the Firefox menu and go to Settings → Privacy & Security → Cookies and Site Data → Clear Data. 2. Reload the Site Audit Issues page. 3. If the blank screen persists, contact Search Atlas support and include your Firefox version number and a screenshot of the blank page. 🌀 You can now access the Site Audit Issues page without interruption in Firefox after the deployed fix. If the issue reappears, contact Search Atlas support with your Firefox version and a screenshot so the team can investigate.