🧠AI SEO/OTTO SEO Project Overview & Recommendations

Category: Project Access Utility

Category: Documentation Access

Path:

Top Project Header → Domain Report button → ⋮ Vertical three-dot menu

When clicking the three vertical dots (⋮) located immediately next to the Domain Report button in the top-right project header, a contextual menu appears with three options:

Only Deep Freeze affects the state of the project.
The other two items provide access and documentation, but do not modify project behavior.

Deep Freeze is a project-level state control designed to preserve work, lock automation, and pause active SEO operations without losing progress.

It is used when a project should remain intact but inactive.

“Preserve all progress when discontinuing work with a client, securely maintain the current state while awaiting the client’s return, or save the optimized state and reduce costs by freezing the site.

Dynamic SEO and AI content generation will be disabled.
Deployment and rollback are restricted while frozen.

By deep freezing this project, its quota will remain blocked for 14 days after freezing.”

Inside the Deep Freeze confirmation modal, OTTO explicitly defines the intended use cases:

Once Deep Freeze is enabled:

This ensures the project remains exactly as-is, with no drift, no automation, and no accidental changes.

Inside the modal:

Once confirmed, the project enters a frozen state immediately.

The OTTO Grader is a project-level aggregate score displayed prominently in the Project Overview.

It is calculated by evaluating:

Each page contributes to the overall score based on its individual optimization status.

“Only the issues fixed with OTTO (excluding issues fixed by other means).”

This is a critical distinction.

The four Holistic SEO Pillars, Content, Authority, Technicals, and UX Signals, are scored using the same attribution logic.

Each pillar reflects:

🔍 Tooltip explanation:

“This chart shows your project's performance across the four pillars of a holistic SEO strategy: Content, Authority, Technicals, and UX Signals. Hover each of the pillars for more detailed information on them.”

When a project is Deep Frozen:

This preserves the exact scoring state at the moment of freezing, ensuring historical accuracy.

OTTO scoring answers:

It does not attempt to replace full SEO audits or external performance metrics. Instead, it provides a clear, honest view of OTTO’s contribution to your site’s optimization.

Each row in the list represents a task category, not an individual page.

Common task types shown here include:

Each task row contains:

This structure allows users to decide how much control they want before entering deeper workflows.

Clicking Deploy on a task row will:

This means:

Deploying a task here is equivalent to bulk-deploying that category from Recommendations — but without leaving the Overview context.

Clicking View task expands or navigates into the full Recommendations interface for that task category.

This is where users can:

The dropdown exists to ensure manual review is always available before or after deployment.

The Expanded Tasks View serves three critical purposes:

This design ensures OTTO supports both:

without forcing users into one mode.

The transition from Overview to Recommendations is spatial, not navigational.

This design reinforces a single continuous experience:

As the user scrolls into Recommendations, the interface gradually shifts emphasis:

Importantly, this shift is intentional but non-disruptive.
Users never “leave” the Overview — they progress through it.

This layout ensures that:

In short:

Overview and Recommendations are not separate destinations — they are consecutive layers of the same workflow.

(Navigation & Scope Layer)

Location:
Far left of the screen, fixed, full-height vertical column.

The left sidebar defines what type of SEO work you are performing at any given moment. Each item represents a category of issues OTTO has detected across your site.

Expandable issue groups such as:

Each issue displays a counter (for example, 0 / 485), indicating:

Clicking an issue:

This sidebar acts as the map of the Recommendations system.

(Execution Layer)

Location:

Center of the screen, occupying the largest visual area.

The main workspace is where all SEO work actually happens.

Depending on the selected issue, this area may display:

This is where you:

The layout adapts to the problem being solved, but the interaction logic remains consistent across sections.

(Management & Scale Layer)

Location:

At the top of the main workspace, directly beneath the page header.

The top control bar allows you to manage entire issue categories at once, rather than acting on individual rows.

These controls are intentionally separated from individual fixes to reduce accidental mass changes.

For every issue category, the OTTO Grader appears directly beneath the category title.

This score reflects how optimized the site is within that specific category, not the entire project.

As fixes are enabled or rolled back, the grader updates to reflect progress.

The grader is informational only — it does not trigger actions by itself, but helps you gauge completion and impact.

This column establishes a clear baseline before any change is made.

This column is where decisions are made.

Across almost all Recommendations sections, the same icons appear in predictable locations:

These icons are always placed next to the element they affect, reinforcing safe, granular control.

Recommendations is designed to scale SEO execution without sacrificing precision.

By separating:

OTTO allows you to:

This structure is what enables automation with oversight, rather than blind auto-deployment.

DKN analyzes your business and creates a structured topical map that strengthens your website’s authority. Each node becomes a recommended page with a title, category, and target keywords. You can refine these details and generate SEO-optimized content directly from Content Genius. Interconnected pages improve your topical relevance and help search engines trust your site.

The Domain Knowledge Network includes:

- Business Description — A detailed explanation of what the business does, the services it provides, and how it positions itself.

- Central Entity— The primary entity that defines the business at an entity-SEO level.

- Source Context — The overall contextual framing of the website and its content.

- Target Audience — A detailed definition of who the business serves, including demographics and intent.

- Monetization — How the business generates revenue and which models apply.

- Central Search Intent — The core search intent the site is designed to satisfy.

Once these fields are completed, it consolidates this information into OTTO’s internal knowledge systems, influencing downstream automation and recommendations.

When you click Generate Domain Knowledge Network, the system analyzes your business information and automatically creates a structured topical map for your website.

Generate Domain Knowledge Network

Automatically builds a structured topical map based on your business information, creating SEO-optimized page recommendations organized into a hierarchical content network.

The interface presents structured fields and inputs where business information is defined. These inputs are not page-specific; they apply at the domain level. There are no deploy toggles here, changes act as source data rather than direct fixes.

This section explains how users navigate the Domain Knowledge Network (DKN), what each UI area does, and how users move from strategy → structure → content creation.

Left Sidebar → Content Strategy → Domain Knowledge Network

Controls what network you’re working on and how it can be modified.

This panel defines the input layer for the DKN.

🔄 Generate Domain Knowledge Network

➡️ Clicking this button:

This is the starting point of the entire DKN workflow.

UI Flow

After generation, users land on the Domain Knowledge Network Overview.

➡️ Monitor progress and content coverage at a glance

This visual area shows:

This is the strategic visualization layer of the DKN.

This is the execution layer.

➡️ Turn strategy into actionable content production

When clicking Edit or Create:

Users can modify:

CTA:

​Create Article

This connects the DKN directly to the content editor.

Once an article is created:

➡️ This is where DKN → Content → Optimization fully connects.

The UI supports an iterative workflow:

The Domain Knowledge Network UI guides users from business understanding to topical structure and finally to content creation, providing a clear path from strategy to execution through interconnected pages and hierarchical navigation.

Users define:

Edits are saved as reference intelligence. There is no “enable” action; once saved, the information becomes available to all downstream systems.

Topical Maps allow you to build a structured topical plan around a target keyword or existing page. OTTO identifies related concepts and subtopics, then organizes them into a pillar-and-supporting-page structure that you can review, edit, and act on.

We build a topical map around your target keyword, automatically discovering related concepts and subtopics. Once the topical map is generated, you can go and create articles with the help of AI. This tool not only saves you time but also ensures a thorough exploration of your topic, helping you improve thematic relevance.

At the top of the main workspace, you see:

Near the top-left of the table area there’s a small cluster of controls/icons:

➕ Create Topical Map (blue button, top-right)

A structured list with two primary columns:

Each row shows:

From your screenshot, examples include:

This column contains the action controls for each pillar page.

For each row, you have three controls (aligned horizontally):

At the bottom-right of the list area:

🗑️ Delete

Removes the topical map or supporting page suggestion entirely.

Primary path to reach these screens

Inside Recommendations

Shared controls you’ll repeatedly see

Located above the table:

Each row represents one target page (destination of the internal link).

Displayed as:

When expanded, the target page shows:

Below each target page:

Fields:

Actions:

This enables users to manually seed internal link relationships.

Tooltip copy (recommended):

OTTO uses crawled site data and topical relevance to identify pages that should be internally linked.
By adding these links, you improve site navigation, distribute authority, and help search engines crawl and index your content more effectively.

Internal Linking Opportunities identifies and manages contextually relevant internal links between pages, giving users full control to deploy, edit, or roll back links that strengthen site structure and SEO authority.

Navigation
Link Building → WILDFIRE

What WILDFIRE Is
An advanced backlink acquisition system.

How It Works

Navigation

Link Building → Canonical Link

What OTTO Does

Navigation

Link Building → Issues with Links

What OTTO Does

Instant Indexing allows OTTO to submit URLs directly to search engines using official indexing endpoints, accelerating discovery and crawl.

OTTO integrates with:

This module is designed for scale, speed, and priority-based indexing.

AI SEO → Recommendations → Indexing → Instant Indexing

Dynamic Indexing is NOT internal linking
Dynamic Indexing is indexation recovery logic

It targets pages that:

AI SEO → Recommendations → Indexing → Dynamic Indexing

⚠️ Results are not immediate
Indexation depends on Google’s crawl cycles.

It uses internal links only as a technical mechanism to trigger crawling.

Each block is collapsible / expandable.

Purpose
Ensure every page has a properly optimized Open Graph description for social sharing.

UI Layout

How it works tooltip

OTTO checks whether Open Graph tags exist and meet length requirements. When missing or suboptimal, it generates optimized versions for better social visibility.

Current state

Includes:

Purpose
Optimize how content appears when shared on X (formerly Twitter).

UI Behavior

Tooltip

Ensures Twitter Card descriptions are accurate, engaging, and optimized for maximum social visibility and CTR.

Functionality

Purpose
Defines the twitter:site value globally or per page.

Behavior

Detect pages missing the lang attribute on the <html> tag.

Current state

Tooltip

OTTO checks your page HTML for a missing lang attribute to improve accessibility, localization, and correct search engine indexing.

Table columns

Pagination

Modal Structure

Inline notice

Custom HTML will be deployed instantly to your page.

Typical Use Cases