How the growth loop works
WebmasterID Agent follows a seven-step loop from site verification through to human-approved shipping. Every step is auditable and reversible.
- 01
Connect sites via WebmasterID Core
WebmasterID Core verifies your ownership using DNS TXT records or file-based verification — the same standard used by Google Search Console. Only verified sites enter the Agent pipeline. No crawling of domains you do not own.
- 02
Attach data providers
OAuth or API key flows connect Google Search Console, Bing Webmaster Tools, DataForSEO, GA4, GitHub, and Vercel. Credentials are encrypted at rest. Each provider is scoped to a workspace — no cross-workspace access.
- 03
Providers sync on a schedule
The Agent fetches fresh signals from each active provider on a configurable schedule. GSC and Bing sync search performance. DataForSEO enriches keyword volume and SERP features. Every sync run is logged with a full audit trail.
- 04
Rule-based engine fuses signals
The Agent Brain runs a deterministic rule set over the fused provider data. It detects ranking drops, AI referral spikes, Core Web Vital regressions, and missing structured data — with no LLM guesswork in the audit path.
- 05
Work packages are queued
Findings are packaged into prioritised work items — each with the affected URLs, the signal that triggered it, severity, and a suggested remediation approach. You review the queue and pick what to act on.
- 06
Claude Code executes locally via MCP
The Claude Code MCP bridge lets Claude read work package context, write content, fix meta tags, update structured data, and apply code changes — entirely on your local machine. Nothing touches production until you approve.
- 07
You approve — then it ships
Every external action — commit, deploy, outreach message — requires explicit operator sign-off. The Agent surfaces the proposed change, you review it, and only then does it leave your environment.
Frequently asked questions
Do I need a WebmasterID Core account?
Yes. WebmasterID Core handles site ownership verification and identity. The Agent uses Core to confirm you own the sites it analyses — this is the compliance foundation that prevents the Agent from operating on domains you do not control.
How long does the first sync take?
Initial provider syncs typically complete in 2–5 minutes depending on the size of your GSC or Bing dataset. DataForSEO keyword enrichment runs asynchronously and may take a few extra minutes on first run.
Can the Agent make changes without my approval?
No. The Agent can draft, analyse, and queue — but every external action (commit, deploy, email, post) requires explicit human approval in the dashboard before it is executed.
Does Claude Code run in the cloud?
No. The Claude Code MCP bridge connects to your local Claude Code CLI installation. All code execution happens on your machine. The Agent never runs arbitrary code in its own infrastructure.