Seo Opportunity Brief
The mission requires SEO opportunity brief as a governed work product. ServAI can include this role when its capability coverage is needed.
Builds evidence-based organic search opportunities and measurement plans without inventing rankings or traffic. This is a capability composition ServAI can bring into a mission when the work requires it—not a role the customer must manually staff for every job.
ServAI starts from the outcome, resolves the Agency capabilities required, checks entitled Industry and cross-industry Role Pack depth, and proposes the smallest relevant team. This role enters only when its capability contribution is justified.
The mission requires SEO opportunity brief as a governed work product. ServAI can include this role when its capability coverage is needed.
The mission requires content/search hypotheses as a governed work product. ServAI can include this role when its capability coverage is needed.
The mission requires measurement plan as a governed work product. ServAI can include this role when its capability coverage is needed.
The exact capability IDs below come from the accepted Agency role contract. ServAI uses this coverage when deciding whether the role belongs in a mission team.
Audience insight with evidence source, recency and confidence.
Observed competitor channel presence or activity with dated evidence.
Dated market, culture, platform or creative trend signal with source and geography/audience context.
Campaign measurement framework linking business/communication objectives to metrics and sources.
Assessment of completeness, freshness and comparability of campaign measurement inputs.
Required data/action interface for an Agency workflow without naming a parallel connector runtime.
This role is native to ServAI Agency. If the same mission also requires sector knowledge or cross-industry professional depth, the Mission Router can combine entitled Industry Packs and Role Packs without converting this role into a separate pack or silently activating anything missing.
These are governed work products from the accepted role contract. They do not themselves publish, execute, spend or make client commitments.
Prepared inside the mission scope, tied to the required evidence and routed through the role’s review chain before any separate approval or external action.
Prepared inside the mission scope, tied to the required evidence and routed through the role’s review chain before any separate approval or external action.
Prepared inside the mission scope, tied to the required evidence and routed through the role’s review chain before any separate approval or external action.
Mission assembly connects the specialist to the relevant Agency rooms while preserving one client, brand and campaign context.
Self-review is not the approval model. The accepted role contract names peer and senior review paths before any separate human decision or external action.
Peer review checks domain reasoning, evidence boundaries, client/brand scope, and material omissions before senior review or human decision.
Required for: external-client deliverable; campaign strategy recommendation; creative territory recommendation; media allocation recommendation; material performance conclusion.
The role can prepare decision-ready work inside its authorized scope. Approval, execution and other sensitive external actions remain behind ServAI’s existing authority controls.
Inside the exact mission, client, brand and campaign scope with the required evidence and review chain.
A team proposal or prepared work product never grants these authorities.
These boundaries are part of the accepted role contract.
“I can prepare the Agency work and evidence inside the authorized client, brand and campaign scope, but I cannot approve or execute the external action.”
When a request crosses evidence, scope or authority boundaries, the role stops at a governed proposal and routes the decision to the appropriate human or existing ServAI gate.
Give ServAI the mission. If this specialist’s capabilities are required, ServAI can include the role in the proposed team and explain why. If not, the smallest relevant team stays smaller.