🧠 OTTO SEO Project Overview & Recommendations

Camilo Aponte

Camilo Aponte

Last updated on Sep 30, 2026

Open the OTTO SEO module and navigate to All Sites (SEO Automation) in the left sidebar to land on the Project Overview: a decision-making dashboard showing your weighted site health score, prioritized issue categories, and a deployment readiness checklist. This article explains the full two-layer workflow, from reading your project health to deploying and rolling back SEO recommendations.

The workflow is divided into two layers:

  • Project Overview — establishes context, system health, priorities, and readiness
  • Recommendations — where you review, customize, deploy, measure, and roll back SEO fixes, including Custom HTML Content

The site health score is weighted, not a simple average. High-impact signals like page titles contribute more to your grade than low-impact signals like social meta tags — so fixing a small number of high-signal issues can produce a large improvement in your overall score.

🧭 How to Reach the Project Overview

The Project Overview is the default landing screen for every OTTO SEO project — a decision layer, not an execution workspace. Navigate to it using this path: Left sidebar → OTTO SEO → All Sites (SEO Automation)

The Overview loads automatically as soon as you select a project. Everything here answers one question: Is this project ready for action, and what should I focus on next?

No fixes are deployed from this screen. The grade shown here is a weighted score: higher-impact signals such as page titles count more than lower-impact ones such as Twitter tags — which is why a small number of high-signal fixes can produce a sharp improvement in your overall grade.

🏷️ The Project Header: Identity, Context, and State

The top of the screen anchors you to which project you are working on and confirms whether OTTO is technically ready to act — preventing a common mistake: working on the wrong site or acting before systems are properly connected.

Project Identity (Top Left)

The top-left corner displays:

  • The project name
  • The primary domain
  • A platform indicator (for example, a WordPress logo if detected)

This confirms that all scans, all recommendations, and all deployments apply only to this specific site and environment. Always verify the project identity here before making changes in Recommendations.

System Status Panels (Top Row)

Below the project identity is a horizontal row of compact panels. These are system-level indicators, not performance metrics. They answer:

  • Is OTTO connected?
  • Is it informed?
  • Is it allowed to act?
  • Is it configured correctly?

UUID Panel

Location: Top row, left-center

This panel shows whether OTTO's tracking identifier (UUID) is correctly connected to your site.

How it looks:

  • A toggle switch showing whether OTTO is engaged or disengaged
  • A Scan ⚡ button alongside the toggle

How to use it:

  • The toggle reflects the current engagement state
  • Click Scan ⚡ to force a validation check and confirm or re-establish the connection

How to interpret it: If this panel shows an error or red state, OTTO may still analyze your site — but automation, deployment, and indexing may be limited or blocked. Resolve this panel before moving into Recommendations.

Brand Vault Panel

Location: Top row, center | Icon: ✏️ Pencil (Edit)

This panel reflects the completeness and accuracy of your project's Brand Vault configuration — a quick visual indicator of how fully Brand Vault has been populated and whether your business intelligence layer is properly configured. The completion state shown here is directly tied to the structured data stored inside Brand Vault.

📋 Working with Recommendations

The Recommendations layer is where SEO work is reviewed, customized, deployed, measured, and rolled back. Within Recommendations, you can also manage Custom HTML Content — create, edit, validate, preview, and deploy it directly through the OTTO Agent. Custom HTML Content is distinct from standard SEO fix types and requires HTML validation before deployment.

To roll back a deployed fix:

  1. Locate the specific fix type (for example, Heading Length ) in your OTTO SEO list
  2. Open its deployment detail
  3. Click Undeploy to remove it from the front end immediately

Use Undeploy any time a deployed fix causes unintended front-end changes, such as unexpected heading text appearing on your site.

⚠️ Known Issues & Upcoming Changes

Upcoming: Several issue types are moving to the main OTTO SEO Automation dashboard only

In an upcoming release, the following issue types will only be accessible from the main OTTO SEO → All Sites (SEO Automation) dashboard — not the per-page detail view:

  • Topical Maps and Supplemental Content
  • Meta Description
  • Meta Keywords
  • Missing Keywords
  • Internal Link Suggestions

If you currently manage any of these from the per-page detail view, switch to the main OTTO SEO → All Sites (SEO Automation) dashboard now.

Cloudflare proxy: character encoding bug (OTTO-1357)

If your site is proxied through Cloudflare, OTTO's script injection may corrupt special characters in headings that contain nested HTML. If you observe character encoding errors after engaging OTTO, contact Support and reference bug OTTO-1357.

🎯 You now understand how the OTTO SEO / OTTO SEO Project Overview and Recommendations layers work together — from reading your weighted health score and confirming system readiness to deploying fixes and rolling them back when needed. Confirm your UUID panel connection and populate Brand Vault before moving into Recommendations to deploy your first fixes.