The modern SEO team is already an agent team. There is a keyword researcher running cluster analysis at 2am. A brief drafter pulling SERP intent into outlines. A page auditor crawling templates on a schedule. A link analyzer scoring referring domains. According to Aira's 2025 State of SEO survey, 86% of SEO professionals now integrate AI into their workflow, up from 65% the year before. The work is happening.
What is not happening is persistence. The keyword agent posts a cluster recommendation in Slack on Monday. The brief drafter on Wednesday cannot see it, so it re-asks. The page audit lives in a Sheet that nobody opens. The link outreach decision sits in someone's DMs. Three weeks later a strategist asks "why did we go after that cluster?" and the chain is gone.
Source of truth, and journal
Here is the line I want to draw. Google Search Console remains the source of truth for performance data, impressions, clicks, query coverage. Ahrefs and Semrush remain source of truth for keyword volumes, difficulty scores, backlink graphs. Clearscope and SurferSEO remain source of truth for on-page optimization signals. Screaming Frog remains source of truth for crawl state. None of that moves.
Dock is the system of record for the agent's output. The keyword cluster brief. The content outline with intent rationale. The audit findings with recommended fixes. The link-acquisition decision and who approved it. Persistent, resumable, reviewable. Rows in Dock carry gsc_query_id or ahrefs_keyword_id pointers back to where the underlying data lives, so the journal stays linked to the truth without copying it. This is the AI workspace, not AI assistant shape.
Three workflows that fit
Keyword cluster to brief to assignment. The cluster agent reads from Ahrefs (decent agent surface) and Google Search Console (read-only via the Search Console API, well documented in Google Search Central). It writes the cluster, intent classification, and target page hypothesis into a Dock workspace as attributed rows. The brief drafter agent picks up rows tagged ready-for-brief, generates an outline, and assigns it to a human writer. Every step is signed by the agent that did it. See drafted by agent for why that signature matters.
Content audit and redirect map. Screaming Frog exports a crawl (CSV today, MCP-shaped tomorrow). The audit agent ingests, classifies pages by decay pattern, and proposes a redirect or refresh plan into Dock. A senior strategist reviews the proposal as a Dock row, not as a Slack screenshot. Approvals are logged. The audit trail is the agent audit and compliance story applied to content ops.
Link acquisition with attributed outreach. A prospecting agent pulls referring-domain candidates from Ahrefs, scores them, and drafts personalized outreach into a Dock pipeline. Send approvals stay human. Replies thread back into the same row. When the strategist asks six weeks later why a particular outreach landed, the chain (research, draft, edit, send, reply) is intact and attributed. This is the agent collaboration primer on the SEO surface.
Why SEO specifically, now
Answer Engine Optimization is half the game in 2026. AI-drafted content is showing up in AI Overviews, ChatGPT cites, Perplexity answers. The provenance question stops being a niceity and becomes table stakes for E-E-A-T. If your audit cannot show which agent drafted which claim, with what sources, reviewed by which human, you are guessing at quality. Dock makes that trivially auditable because the agent's work was attributed at write time, not reconstructed after.
Content ops is also team coordination. Strategist, writer, editor, technical SEO, and four agents are all touching the same brief. An async substrate where they all read and write, instead of pinging each other in Slack, is the only sane shape. The async-first playbook is the operating manual.
Start
Open /use-cases/seo for the worked example, or fork the editorial-calendar template and wire your first cluster agent into it this afternoon. The AI-workflow counterpart, how to build an SEO content engine with AI, goes step by step.
FAQ
Does Dock replace Ahrefs or Search Console? No. Ahrefs holds the keyword and backlink graph; Search Console holds your performance data. Dock holds what your agents concluded from that data (the briefs, the audits, the outreach decisions) with pointers back to the rows in the source systems.
How does Dock help with AEO? Answer engines reward content with clear provenance and reviewable claims. When an agent drafts a section, the source list and the human reviewer are captured in the row, so your E-E-A-T story is verifiable rather than asserted.
Where does agent-drafted content's provenance live? On the row itself. Every agent write is attributed; every human edit is signed. The byline is recoverable months later without forensic Slack search.
Multi-author coordination? That is the default mode. Strategist, writer, editor, and agents all read and write the same workspace. Comments thread on rows. Status moves with the row, not in a side channel.
Sources: