Action Plans

Action Plans turns Maya's findings into a managed task board. Instead of a report that says "you have gaps," you get concrete tasks — prioritized by impact, assignable, and tracked to completion on a kanban.

Enterprise feature. Action Plans is included in the Enterprise plan. On other plans the page shows an overview and a Request Enterprise Access button.

The board

Three columns — To Do, In Progress, Done — with drag-and-drop. Each card carries:

• Priority (low / medium / high)
• Subtasks you can check off individually
• Assignee
• A source tag showing where the task came from: maya (Maya's own analysis), brand (your team's manual entries), or bing (Bing Webmaster signals)

You can create tasks manually, and Maya Chat can create plans for you (confirmed before writing).

Where tasks come from

Generated tasks are derived from real signals — visibility gaps, citation opportunities, technical findings, search-console movement — and ranked by expected impact, so the top of your To Do column is a defensible answer to "what should we do this week."

Done means verified

Dragging a card to Done is treated as a claim, not proof. An independent verifier then:

1. Writes a spec of what "done" should look like for this task — the evidence type (content change, technical change, published page, YouTube, off-web) and the target URL.
2. Fetches the live page (and Search Console for "published" claims) to collect evidence.
3. Has a calibrated judge compare evidence to spec and returns a verdict: done, looks incomplete, or unclear — with a short recommendation when something's missing.

This keeps the board honest: "done" in Maya means the change is actually observable on the live site, not just checked off in a meeting. Search/AI-awareness signals (impressions, citations appearing) are reported as context but don't gate the verdict — rankings take time; the work itself is what's verified.

Working rhythm that works

• Review the generated To Do column weekly; archive what you won't do rather than letting it rot.
• Keep subtasks small enough that "done" is observable on a URL — that's what the verifier can confirm.
• Watch the source tags: if all your progress is brand-sourced while maya-sourced tasks sit untouched, you're doing your roadmap, not the visibility roadmap.