# Multica Workflow Recipe: SEO Audit to Site Growth Work

This file is an **optional workflow recipe**, not a required skill for routing work to the SEO Consultant.

If your Chief of Staff agent has a good role definition and the workspace includes an SEO Consultant, it should already know that an SEO audit belongs with the SEO Consultant. You do **not** need a separate skill just to say “send SEO work to the SEO agent.” That would be unnecessary agent bureaucracy.

## When to use this

Use this when you want a repeatable example workflow for broad SEO or ranking-improvement requests.

It is useful as:

- a reference pattern for the Chief of Staff
- a starter workflow recipe for the Multica MVP demo
- a checklist for what a good SEO/content workflow should include
- an example of how one broad request can become specialist tickets

It is not core plumbing.

## Trigger

A human asks for an SEO audit, ranking improvement, website improvement, or content opportunities.

Example:

```text
Do an SEO audit on https://example.com and have the team take actions to help us rank better.

Give me back a clear report on what you found, what the team did, and what needs approval before anything goes live.
```

## Expected Chief of Staff behaviour

1. Create/own the parent coordination issue.
2. Assign SEO Consultant to audit the site.
3. Assign Researcher only if evidence, competitor context, source material, or buyer language is needed.
4. Assign Blog Writer only if the audit supports blog/content opportunities.
5. Require readable HTML reports/previews styled similarly to the analysed site where useful.
6. Review specialist handbacks before final handback.
7. Return one decision package, not a pile of ticket debris.

## Parent issue shape

```md
## Outcome
Improve search visibility and identify practical site/content actions.

## Scope
Target site/pages, constraints, and what is explicitly out of scope.

## Child work
- SEO Consultant: audit and priority actions
- Researcher: supporting evidence if needed
- Blog Writer: content draft only if justified

## Acceptance criteria
Readable report, labelled evidence, prioritized recommendations, approval gates.
```

## SEO audit child ticket should ask for

- Pages/site inspected.
- Technical/on-page/content findings.
- Quick wins vs deeper fixes.
- Highest-priority actions with impact/confidence/effort.
- Blog/content opportunities only if justified.
- Evidence labels and gaps.
- HTML audit report.

## Research child ticket should ask for

- Source material.
- Competitor examples where useful.
- Buyer/customer language.
- Claims that need support.
- Evidence labels and gaps.

Only create this ticket when the SEO Consultant needs stronger context.

## Blog/content child ticket should ask for

- Recommended topic and why it fits.
- Search intent/audience.
- Inputs from SEO Consultant and Researcher.
- Draft or outline if warranted.
- Self-contained HTML approval preview styled similarly to the analysed site.
- Claims/gaps needing approval.

Only create this ticket if the audit supports content work. Do not manufacture a blog because the recipe has a Blog Writer in it.

## Final handback

Chief of Staff returns:

- Audit summary.
- Tickets completed and owners.
- Highest-priority actions.
- HTML report/preview links.
- Blog ideas/drafts only if supported by findings.
- Evidence labels and known gaps.
- Human approval needed before publishing, editing the site, spending money, or changing production.

## Success signal

The human can answer: “What should we do next, why, and what needs approval?” without reading every child ticket.