Deliver more SEO work with the team you have.
Audits, content plans and monthly deliverables, run the same way for every retainer. Your team keeps the calls on priorities. Your agents do the crawling, sorting and first drafts.
An example of how an SEO team could set this up. Nothing here is a built-in template.
Your team
Defines the audit
Your agent
Crawls and ranks, outside ORCA
SEO lead
Trims and prioritises
Your client
Approves the fixes
Finding. Three issues account for most of the lost crawl budget.
Recommendation. Fix canonicals first, then the category templates.
Every retainer runs the same audit. Every client keeps its own context.
Define the monthly technical audit once: who crawls, who prepares, who prioritises, what the client approves. Each retainer runs it with its own crawl, history and decisions.
Nothing here is built in. Click an owner to change it, click a step to rename it, add one.
Delegate the crawl. Keep the call on priorities.
Hand the sorting and first-pass audit to an agent that already has your crawl tooling. Scope it to one campaign. Your SEO lead decides what the client sees and in what order.
- Agents run on your setup. ORCA holds the task and the context.
- A role, a permission list and a campaign boundary. The server checks every request against them.
- Review points live in the workflow. Approval is a workflow step owned by the reviewer. Approve campaign output is off for the agent.
- Broken canonicals on 41 product pages
- Core Web Vitals failing on category templates
- 18 orphaned blog posts
Illustrative. Your agent runs on your own setup. Sharing stays off until the reviewer approves.
Clients approve fixes. They never see the crawl.
The client gets the audit, the recommended order, and one decision to make. The raw crawl, who ran it, and your SEO lead's edits stay on your side. Try the switches in the workspace.
Never shown to the client: workflow controls, owner assignment, agent permissions and scope. Hidden until you switch them on: who prepared the work, internal review notes.
Common questions.
Short answers about how an SEO team would run work in ORCA.
Does ORCA crawl sites or run audits itself?
No. Your team or your agent runs the crawl with the tools you already use. ORCA holds the task, the exports, the audit and the review step, and shows the client what you choose to share.
Can the same workflow cover content plans and link audits?
Each service gets its own workflow. A monthly content plan might have a strategist preparing and an editor reviewing. You define the steps, owners and review points per service.
Who decides what the client sees?
Your agency. By default the client sees the audit, the recommended order and the decision you need. Internal edits, the raw crawl and agent details stay with your team.
Same product. Same review step. A different service each time.
Pick the one closest to yours and see the workflow, the assignment and the client view shaped for that kind of work.
Start with one retainer. Build from there.
Run the monthly audit for one client with your team, refine it, then hand the crawl to an agent when you are ready.