OTTO Onboarding & Product Evaluation

🗺

Installation Plan

4-phase approach to setting up OTTO from scratch

1

Account Setup

🔵 Go to searchatlas.com and create a fresh account using a personal email — not your work one. This simulates what a real new user experiences.

🔵 Complete every step of the onboarding wizard — do not skip. Every screen is a data point for your product evaluation.

🔵 Note the flow: how many steps, what information is asked, what feels confusing or unclear.

🔵 Track your "time to value" — how long before you see something useful.

2

Domain Preparation

🟣 Choose a domain you own — even a cheap test domain from Namecheap/GoDaddy works.

🟣 Ensure you have DNS access or can add a <script> tag to the <head> of the site.

🟣 Set up Google Search Console for that domain if not already done — OTTO requires GSC integration.

🟣 Confirm the domain is live and indexable (not under a maintenance page).

3

OTTO Installation

🟡 Inside the dashboard, navigate to the OTTO setup flow.

🟡 Connect your Google Search Console account when prompted.

🟡 Install the OTTO tracking script — either via a DNS TXT record or an HTML snippet in the <head>.

🟡 Wait for verification — the platform will confirm detection. Note how long this takes.

🟡 Check if there are CMS-specific guides (WordPress, Shopify, etc.) and evaluate their quality.

4

Platform Exploration

🟢 Let OTTO crawl and audit your site — note how long it takes and if progress is communicated.

🟢 Go through every recommendation category generated by OTTO.

🟢 Try applying at least 2–3 recommendations end-to-end and note friction points.

🟢 Check mobile experience — navigate the full dashboard on a phone.

🟢 Use Chrome DevTools + Claude to inspect network calls and UI components.

✅

Product Evaluation Checklist

Tick off items as you explore — progress is tracked automatically

🔍

Missing Pieces to Look For

Common product gaps to identify during your exploration

⚠ UX Dead Ends

Recommendations Without a Path

Recommendations that tell you *what* to fix but not *how* — leaving users to Google it themselves. Flag every one of these.

⚡ Context Switching

Features That Push You Off-Platform

Any action that requires you to leave the platform to complete. This breaks the workflow and is a major retention risk.

🧩 Unexplained Data

Data Shown Without Context

Metrics, scores, or charts that display numbers without explaining what they mean or what a good/bad score looks like.

🔄 No Feedback Loop

No Visible Progress Over Time

Users need to see that OTTO's recommendations are moving the needle. If there's no before/after or score trend, users won't feel value.

📲 Mobile Gaps

Desktop-Only Experience

Check if any critical workflows are broken or hidden on mobile. Many users check dashboards on the go.

🖱 Click Fatigue

Too Many Clicks for Simple Actions

Count how many clicks it takes to perform common actions. Anything over 3–4 clicks for a recurring task is a friction point.

⚔️

Competitive Analysis

OTTO benchmarked against top SEO tools — scores are estimated baselines for reference

Capability Radar — OTTO vs Competitors

Estimated scores across 6 key dimensions (update as you learn more)

Automation Score Comparison

How much each tool automates vs just recommends

Tool	Technical SEO	On-Page	Automation	Data Freshness	UX	Reporting	OTTO Advantage?
OTTO (Search Atlas)	75	80	85	70	78	65	⭐ Automation-first
Surfer SEO	60	90	55	75	85	80	Strong on-page
Semrush	95	85	65	90	70	90	Better tech audit
Ahrefs	90	80	60	85	75	85	Better backlinks
SE Ranking	80	75	70	75	80	75	Balanced all-round

* Scores are estimated baselines for orientation. Update them as you learn more about the platform through hands-on use.

📦

Feature Coverage Breakdown

Categories to evaluate and how much focus each deserves

Evaluation Focus Distribution

How to distribute your exploration time across areas

Onboarding Friction Points (Estimated)

Where users are most likely to drop off — validate during your walkthrough

🔧

Chrome DevTools + Claude Integration

Give Claude full browser visibility to analyze OTTO in real-time

The Playwright MCP server connects Claude Code directly to a browser — giving it the ability to take screenshots, inspect the DOM, intercept network requests, and interact with UI. Once set up, you can ask Claude to audit any page of the OTTO platform in real-time.

1

Install Playwright with Chromium

Run this in your terminal to install Playwright and download the Chromium browser it will control.

            # Install Playwright globally

            npx playwright install chromium

2

Add Playwright MCP to Claude Code

Register the MCP server so Claude Code can use it in every session.

            # Add the Playwright MCP server

            claude mcp add playwright npx @playwright/mcp@latest

3

Verify the Integration

Restart Claude Code and confirm the MCP is active.

            # List active MCP servers

            claude mcp list

            # You should see: playwright → npx @playwright/mcp@latest

4

Use These Prompts with Claude

Once active, Claude can see and interact with the OTTO platform. Try these:

"Open the OTTO dashboard and show me what you see"

"Click through the onboarding and tell me what's missing"

"Inspect the network requests when OTTO loads recommendations"

"Run a Lighthouse audit on this page and summarize it"

"What API calls are made when I click Apply on a recommendation?"

"Check the DOM structure of the recommendations panel"

📝

My Notes & Findings

Log your observations here as you go through the onboarding

🚀

Signup Flow Observations

⚙️

OTTO Installation Notes

🔍

Product Gaps Identified

💡

Ideas for Improvement

⚔️

Compared to Competitors

🔧