Evidence and impact
Finding, sources, baseline, expected metric and uncertainty.
Explore SEOForge
Human approval
Autonomous work stops exactly where human authority begins.
Agents research, draft and validate. They cannot self-approve, merge, deploy or publish. Every consequential change arrives as an individually reviewable proposal with evidence and rollback context.
Nothing publishes without approvalPaid product accessNo ranking guarantees
Production boundary
- Agent tools: prepare only
- API, CLI and MCP: no approval endpoint
- GitHub: protected merge remains human
- WordPress: publication requires human action
Interactive demonstration
Inspect the proposal and stage a decision.
This sandbox changes only its local demonstration state. It cannot publish, call a provider or alter production.
Interactive demonstration
Proposal SF-1842 · Content opportunity
@@ app/blog/seo-operations/page.mdx
- Search automation publishes content automatically.
+ SEOForge prepares evidence-backed work for explicit human approval.
+ Production checks and rollback context remain attached.
Sources verifiedBuild passedRollback ready
Demo only—these controls cannot publish anything.
Approval packet
A yes or no backed by the complete decision surface.
Diff and preview
Exact content, code, media and rendered desktop/mobile result.
Risk and validation
Affected routes, build, schema, links, smoke checks and residual risk.
Rollback
Revert commit or CMS revision plus post-revert verification.
Decision workflow
Every revision returns to a controlled state.
- 01
Agent submits one immutable proposal with evidence
Evidence, owner and next state remain visible.
- 02
Reviewer inspects files, diff, preview, checks and expected impact
Evidence, owner and next state remain visible.
- 03
Reviewer approves, rejects or requests a specific revision
Evidence, owner and next state remain visible.
- 04
Material revision creates a new validated proposal version
Evidence, owner and next state remain visible.
- 05
Approved GitHub merge or WordPress publication uses protected identity
Evidence, owner and next state remain visible.
- 06
Production checks attach results and can prepare rollback
Evidence, owner and next state remain visible.
What approval does not mean
Approval does not guarantee rankings, validate unsupported claims or authorize future changes. It applies to one identified proposal version.
Paid access boundary
Approval operates inside subscribed workspaces after onboarding. The public sandbox is educational and offers no free product or production access.
Questions
Know the boundary before connecting production.
Can an agent approve its own work?+
No. Agent execution and authenticated human production approval are separate controls.
Can an API token merge or publish?+
No. Public developer surfaces cannot gain approval, merge, deploy or credential retrieval tools.
What happens after I request changes?+
The proposal returns to preparation and must pass relevant checks as a new version.
Can I reject without publishing?+
Yes. Rejection closes or returns the proposal and changes nothing in production.
Is the interactive demo connected to a site?+
No. It changes local demonstration state only and cannot publish anything.
Paid deployment · human authority
Keep autonomous preparation fast and production authority human.
Book a paid product walkthrough to inspect the approval boundary end to end.