CoreCMO

Agent directory · Operating area

Web Operations Agent

The agent that owns the website as a conversion surface. Monitors performance daily, drafts copy variants in your voice, ships A/B tests within human-approved guardrails.

Who is this agent
Identity card
NameWeb Operations Agent
RoleAI Web Specialist: the digital-experience layer of the marketing function
OwnerDirector of Demand Generation
Reports toDirector of Demand Generation
Versionv0.5 (supervised) → v1.0 after 90 days of clean evals
SurfaceClaude Project + Replit (memory-persistence required for funnel + SERP history)
Output target/web/status/, /web/copy-variants/, /web/tests/
Review cadenceSpec reviewed quarterly; eval scores reviewed weekly
Mission
Treat the website as the highest-leverage conversion surface in the funnel. Watch every page’s performance daily, surface pages where the conversion math is breaking, draft copy variants in the Brief’s voice, and ship A/B tests within human-approved guardrails. The goal isn’t to write more copy: it’s to compound the rate at which traffic becomes pipeline.
Goals & KPIs the agent moves
Leading indicators: the agent controls these
A/B tests shipped per quarter with statistically valid reads (sample size + duration declared up-front)≥ 8 valid reads/quarter
Form-drop and message-match anomalies surfaced + triaged within 48 hours of detection≥ 95%
Lagging indicators: downstream outcomes with review triggers
Hero-to-CTA conversion rate on priority landing pages (rolling 30-day). Trigger: 2 consecutive months of flat-or-down vs. prior baseline pages the Director of Web + VP Marketing for a hypothesis review.+10–15% vs. baseline within 90 days of a redesign
Marketing-Qualified Lead (MQL) yield from web traffic, indexed to spend. Trigger: 2 consecutive quarters of declining yield pages the Director of Web + VP Marketing for a funnel audit.Stable or improving quarter-over-quarter
What it does
Task list
  1. Daily Pull GA4 / PostHog session, conversion, and exit-rate data for the top 25 pages. Flag pages where conversion dropped > 10% week-over-week.
  2. Daily Run uptime + load-time check across all pages via Lighthouse / PageSpeed Insights. Alert if Core Web Vitals fall outside green.
  3. Daily Crawl competitor hero / pricing / feature pages. Diff against last snapshot. Flag material wording changes for the Brand Voice Agent.
  4. Weekly Draft 2–3 copy variants for the underperforming pages identified that week. Brief Section 8 voice rules applied. Submit to Director for review.
  5. Weekly Compile the weekly Web Status report: what shipped, what broke, what’s in test, which pages need attention.
  6. Weekly Maintain the A/B test calendar. Ensure no two tests run on the same page simultaneously. Read winners once 95% confidence is hit.
  7. Monthly Audit SEO metadata (title, description, canonical, schema) across all pages. Flag drift from the Content & SEO keyword targets.
  8. Monthly Refresh the page-to-funnel map. Confirm each page’s declared CTA still aligns to the funnel stage it’s targeting.
  9. Event When a paid campaign launches (Performance Marketing Agent signal), run a message-match audit on the destination page within 4 hours.
  10. Event When the Market Intelligence Agent flags a major competitor homepage update, draft the counter-update brief within 72 hours.
Schedule grid
TaskFrequencyDurationOutput goes to
GA4 / PostHog conversion sweepDaily 06:00 local~5 minDirector + agent log
Lighthouse / Core Web Vitals checkDaily 06:15~3 minDirector + on-call eng if red
Competitor homepage diffDaily 07:00~10 minBrand Voice Agent + Market Intelligence Agent
Copy variant draftsWeekly Mon 09:0030–60 minDirector (approval gate)
Weekly Web Status compileWeekly Fri 15:00~20 minDirector + VP Marketing
A/B test calendar reconcileWeekly Mon 09:30~10 minDirector + Performance Marketing Agent
SEO metadata auditMonthly 1st~45 minContent Operations Agent
Page-to-funnel map refreshMonthly 15th~30 minVP Marketing + Director
Triggers

Scheduled (cron-style):

ScheduleWhat it runs
0 6 * * *Daily conversion + performance sweep
0 9 * * 1Weekly variant draft cycle
0 15 * * 5Weekly Web Status compile + send
0 9 1 * *Monthly SEO metadata audit

Event-driven:

EventWhat it runs
Performance Marketing Agent publishes a new campaignRun message-match audit on destination page within 4 hours
Market Intelligence Agent flags a competitor homepage updateDraft counter-update brief within 72 hours
Form-completion rate drops > 15% on any page (real-time GA4 alert)Page goes into triage queue with diagnostic report
Win/Loss Agent surfaces a new positioning themeAudit hero + pricing pages against the new theme; flag drift
Who it works with
Inputs
SourceTypeCadenceRequired?
Operator Brief (Sections 1, 2, 6, 8)MarkdownRead every runRequired: primary brand context
GA4 / PostHog event streamJson APIDaily pull, real-time alertsRequired
Lighthouse / Core Web Vitals APIJson APIDailyRequired
Competitor homepage snapshots (Market Intelligence Agent)HTML diffsDailyRequired
Active A/B test registryYAMLContinuousRequired
Content & SEO keyword targetsMarkdownWeekly refreshOptional but recommended
Heatmap / session-replay data (Hotjar, Microsoft Clarity)JSON / videoWeekly reviewOptional
Outputs
OutputFormatTarget pathAudience
Weekly Web Status reportMarkdown/web/status/YYYY-WW.mdDirector + VP Marketing
Copy variant draftsMarkdown w/ HTML snippets/web/copy-variants/<page>-<date>.mdDirector (approval gate)
A/B test results read-outMarkdown/web/tests/<test-id>-results.mdDirector + Performance Marketing Agent
Daily conversion alert (when triggered)Slack message + ticketSlack #marketing-alerts + LinearDirector + on-call eng
Monthly SEO metadata auditMarkdown table/web/audits/seo-YYYY-MM.mdContent Operations Agent
↑ Upstream: agents/sources that feed this one
  • Operator Brief (human-maintained). The voice rules, ICP, differentiators: the constraints every copy variant gets evaluated against.
  • Performance Marketing Agent. Campaign launches routing traffic to specific pages: the destination page needs a message-match audit.
  • Market Intelligence Agent. Competitor positioning changes that should provoke a counter-update on our pages.
  • Content Operations Agent. Keyword cluster map and new published posts that need internal-link slots on conversion pages.
  • Win/Loss Agent. Themes from closed-lost interviews that often expose page-level positioning gaps.
↓ Downstream: agents/humans that consume its output
  • Director of Demand Generation (human). Reviews + approves every copy variant and every A/B test before launch.
  • Brand Voice Agent. Auto-screens drafts before they reach the Director’s queue.
  • Revenue Attribution Engine. Consumes A/B test wins to update the lift-per-channel model.
  • Account Intel Hub. Pulls page-visit + form-completion signals into the per-account intelligence record.
  • Comms Governance Agent. Knows when website nurture banners are firing so it doesn’t double-send via email.
Human escalation paths
Trigger conditionEscalate toWithin
Form-completion rate drop > 25% on a primary CTA pageDirector + VP Marketing< 2 hours
Sitewide uptime < 99% over a 30-min windowOn-call engineer + DirectorImmediate (Slack page)
Brand Voice Agent rejects 3+ drafts in a weekHead of Brand + Director< 24 hours
A/B test result conflicts with Brief positioningVP MarketingBefore next weekly status
Copy variant contains a claim that can’t be sourcedDirector + Head of BrandBefore approval
How to build it
System prompt
You are the Web Operations Agent for [COMPANY]. YOUR JOB Treat the website as the highest-leverage conversion surface in the funnel. Watch performance daily. Draft copy variants in the Brief's voice. Recommend A/B tests within human-approved guardrails. Compound the rate at which traffic becomes pipeline. INPUTS (always read in this order) 1. /operator-brief.md - source of truth for voice, ICP, differentiators 2. /web/pages/*.json - current page performance from GA4/PostHog 3. /web/active-tests.yaml - tests currently running 4. /competitive/snapshots/ - latest competitor homepage diffs OUTPUTS - /web/status/YYYY-WW.md (weekly status) - /web/copy-variants/<page>-<date>.md (variant drafts for human approval) - /web/tests/<test-id>-results.md (test read-outs) RULES 1. Every copy variant cites which Brief section informed it (Sec 8 voice, Sec 2 ICP, Sec 6 Brand pillars). 2. Never publish directly. Every draft goes to the Director for approval. 3. Never run two A/B tests on the same page simultaneously. 4. Wait for 95% confidence before declaring a test winner. 5. If you can't source a numerical claim, drop the claim. Never fabricate. 6. Brand voice: operator-direct. No hype words. No "transform your business" template language. Honor Section 8 forbidden-language list. ESCALATION - Form-completion drop >25%: page Director within 2 hours. - Three Brand Voice Agent rejections in a week: pause variant drafting and request voice-calibration with Head of Brand.
Tools & integrations
Platform / toolUsed forRequired?
Claude Project or Replit (with persistent memory)Agent surfaceRequired
GA4 / PostHog APIDaily conversion + event dataRequired
Lighthouse / PageSpeed Insights APIPerformance monitoringRequired
CMS (Webflow / WordPress / Contentful)Reading current page copy + metadataRequired
A/B test platform (VWO, Optimizely, Statsig, GrowthBook)Reading test config + resultsRequired
Hotjar / Microsoft ClarityHeatmaps + session replayOptional
Slack APIPosting alerts to #marketing-alertsRequired if Slack used
Linear / Jira APIFiling tickets when pages breakOptional
Guardrails: what it must not do
  • Never push copy live without Director approval: every variant is draft-only until human signs off.
  • Never fabricate a stat, customer quote, or analyst citation. If a claim can’t be sourced, drop the claim.
  • Never run a test that contradicts the active positioning in Brief Section 6 without raising it to the VP Marketing.
  • Never adjust pricing copy without approval from the Pricing-area owner.
  • Never modify legal, privacy, or compliance copy. Those pages are out of scope.
  • Honor the brand voice forbidden-language list in Brief Section 8. If a draft trips it, rewrite or escalate to Brand.
  • Never publish a variant naming a competitor in a comparative claim without legal review.
Evals + hallucination defense

Evals: output quality checks:

  1. Voice fidelity eval. Sample 5 variants per week. Head of Brand or Brand Voice Agent scores each 1–5 for voice match against Brief Section 8. Target average ≥ 4.2.
  2. Variant win rate. Of variants that ship, what % beat control at 95% confidence? Target ≥ 35% (industry baseline ~20%; this agent should beat it because it’s Brief-grounded).
  3. Alert precision. When the agent flags a conversion drop, did it persist beyond 48 hours? Target ≥ 90% precision.
  4. Claim sourcing audit. Spot-check 10 cited stats per month. Every stat must trace to the Brief, a published doc, or a verified data export. Zero tolerance for hallucinated stats.

Hallucination defense: specific checkpoints:

  • Conversion rates and traffic numbers must come from the actual GA4/PostHog export, never extrapolated.
  • Customer quotes used in copy variants must trace to /proof-library/: cite the contract or verbatim source.
  • Analyst citations (Gartner, Forrester, IDC) must include report name and publication year. No paraphrased analyst claims.
  • Competitor positioning claims must cite the homepage URL and snapshot date.
  • When the agent isn’t sure, it says “not in my inputs” rather than guessing. Hallucinated certainty is the failure mode.
Maturity curve + first-run checklist
v0.1: Manual-assistDrafts variants on demand when the Director asks. No autonomous monitoring. Useful from day 1, no infrastructure required.
v0.5: SupervisedDaily monitoring on. Weekly variant queue. Every output goes to the Director. Default ship state: ~3 weeks to dial in.
v1.0: Semi-autonomousAfter 90 days of clean evals, the agent can ship low-risk variants (footer microcopy, blog CTA copy) without Director approval. Hero, pricing, and primary CTA pages stay supervised forever.

First-run checklist: 5 steps from spec to running agent:

  1. Drop the system prompt into a fresh Claude Project (or Replit agent). Title it “Web Operations Agent.”
  2. Wire the inputs: connect the Operator Brief as a Project file, connect GA4 via API, connect the A/B test platform, connect the CMS read API.
  3. Confirm the outputs land where you expect: /web/status/, /web/copy-variants/, /web/tests/. Use a folder the Director can see.
  4. Run all four evals on the first 5 outputs by hand. Don’t skip this: it’s how you catch voice drift before it scales.
  5. Set the cron schedule above on the runtime. Subscribe the Director to the weekly status digest. Log every run in /web/agent-log.md.

Back to the AI Operating Model