🔍 Overview
OTTO automates a wide range of on-page and technical SEO tasks across your site. While you can track progress inside the platform and share reports with clients, it is important to understand exactly what data is available today, what is not yet surfaced, and why — so you can set accurate expectations with your clients.
📋 What OTTO Reporting Currently Shows
Search Atlas includes reporting features that can surface OTTO activity for client-facing use. At a high level, OTTO reporting is able to show aggregate counts of optimizations that have been deployed across a connected site — for example, a total number of actions applied. However, the specific named reporting panels, categories, and snapshot views available may vary depending on your plan and how your project is configured.
To access OTTO-related data for a client report, open the relevant project inside Search Atlas and look for reporting or export options associated with that project. If you are unsure which sections apply to your client's campaign, reach out to support for guidance on what is currently available for your account.
⚠️ Current Granularity Limits: Counts vs. Detailed Fix Lists
At this time, OTTO reporting surfaces aggregate counts rather than a line-by-line log of every individual fix applied. This means:
- You can see that a certain number of optimizations were applied, but the report will not list each URL alongside its specific before-and-after change.
- Fix-level detail — the specific content change made on a specific URL — may be visible inside the OTTO section of the platform itself, but this granular view is not yet available as a formatted, exportable client report.
This is a known platform limitation, not missing data. The underlying activity is recorded, but granular fix-level reporting is not yet available as a shareable export format.
🤖 Why Some Fixes May Not Appear in Audit Counts
OTTO can deploy certain optimizations — such as schema injection or dynamic tag updates — using JavaScript rendering. Because many SEO audit crawlers evaluate pages before JavaScript executes, these fixes may not be reflected in audited issue counts even though they are live on the page.
This does not mean the fix was not applied. It means the audit crawler saw the pre-render version of the page. To confirm that fixes are active, you can:
- Use Google Search Console or the URL Inspection tool to check the rendered version of specific URLs.
- View the raw page source versus the rendered source in your browser's developer tools to confirm injected elements are present after JavaScript execution.
📤 Sharing Progress With Clients
Because granular, fix-level export is not yet available, here are practical ways to communicate OTTO progress to clients today:
- Use aggregate counts available within the platform to show the volume of optimizations deployed over a given period.
- Supplement with Google Search Console data — show improvements in crawl coverage, indexing, or search performance alongside OTTO activity to provide context.
- Document changes manually for high-priority pages where specific before-and-after detail is needed, using the URL-level view inside the OTTO section of the platform.
- Set expectations upfront that current reporting reflects totals and summaries, and that more granular exportable reports are a known roadmap item.
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.