Dashboard panels at a glance

The right panel is the control room

Most of the working context lives in the dashboard's right panel. This is where CLEA can combine analytics, prompts, suggestions, files, and workspace actions.

Use the right panel as the place to inspect evidence before asking CLEA to act.

Studio carries the working context

Studio is where the user works with CLEA. It is the place for chat, files, suggestion cards, and the operational parts of the workspace.

When you ask CLEA a question, make sure the question points to the area you want it to use.

Studio context

Studio is where chat, files, cards, and workspace actions come together.

Analytics carries the proof

Analytics is where prompt runs, sources, competitors, readiness, SEO, and connected data become visible.

Use analytics when you need proof before deciding what to do.

Panel choice

Use Studio for work and Analytics for proof before asking CLEA to act.

AI Visibility Overview

The AI Visibility Overview is the main starting panel for visibility health. It brings the first important signals into one place.

It is rich, so do not try to read everything at once. Start with the top signals, then scroll into deeper checks like AI sentiment when you are ready.

AI Search shows how your brand appears in AI answer contexts. This is where prompt results, mentions, and visibility patterns begin to make sense.

SEO and backlinks give CLEA more context about authority and website quality.

These signals help explain why a source may be trusted, why a competitor may appear, or why your own site is not clear enough yet.

1

AI Search

Review answer visibility and mention patterns.

2

SEO context

Check authority and page quality signals.

3

Search Console

Use query and page data when connected.

4

Google Analytics

Compare visibility work with page behavior.

Search Console

Search Console adds query and page performance context when connected.

If it is not connected, CLEA should not make Search Console claims. Connect it before relying on this part of the overview.

Google Analytics

Google Analytics adds behavior context when connected. It can help compare visibility work with real page usage.

Use it to understand which pages already matter and which pages need support.

Dashboard map

The dashboard is easiest to read as panels: overview, prompts, analytics, suggestions, calendar, workflows, sitemap, and page work.

Competitors and sources

Competitors and sources are the most practical proof surfaces after prompt results.

Who gets named

Competitor views help you see which companies appear in answers. This can reveal obvious competitors and unexpected rivals.

Which URLs get read

Source views help you see which URLs influence answers. A source can become a target for outreach, a content benchmark, or a signal that your own page is missing needed context.

Proof surfaces

Competitors show who gets named; sources show which pages shape the answer.

Suggestions and calendar

Suggestions and calendar turn the workspace from analysis into routine.

CLEA recommendations

Suggestions collect recommended actions. Use them to decide what to do next instead of trying to manually translate every metric into a task.

Upcoming runs

Calendar shows scheduled prompt runs and agent prompts. It helps you understand what CLEA will do next and when.

1

Suggestions

Decide what to do next.

2

Calendar

See what CLEA will run next.

3

Sitemap

Plan content work from evidence.

4

Page writer

Draft only after the brief and review path are clear.

Sitemap and page writer

Sitemap and page writer are for turning evidence into website work. Use them after you know which gaps are worth addressing.

The sitemap flow depends on the connected repository and the /clea-sitemap-expansion folder when GitHub-backed expansion is used.

Next step

Main website