Intended events
Versioned site, run, finding, proposal, quota and provider-health envelopes with event ID, timestamp, environment and tenant scope.
Explore SEOForge
Planned developer integration · not yet live
Customer-configured outbound webhooks are not available yet.
SEOForge currently receives internal provider webhooks where implemented, but that is not a customer event product. There is no endpoint registration, signing-secret issuance or delivery log for customers today.
Nothing publishes without approvalPaid product accessNo ranking guarantees
customer endpoint: unavailable
signing secret: not issued
delivery log: not live
Intended protection
Customer-controlled HTTPS endpoint, separately issued signing secret, timestamped HMAC verification and secret rotation.
Will not
Carry provider credentials, expose private chain-of-thought, approve production from a callback, or trust unsigned/replayed requests.
Planned setup
Register, verify, sign, retry.
- No customer registration UI exists today
- Launch requires signatures and replay protection
- At-least-once delivery requires idempotent consumers
- Retry/backoff and terminal failure must be visible
- Payload versioning and retention limits must be documented
Example future workflow
Send proposal.ready without exporting the proposal.
The event would contain stable IDs, site, state and an authenticated review URL. The customer fetches authorized detail from SEOForge and performs the production decision in the protected UI. This delivery flow is not live.
Paid deployment · human authority
Do not build against an outbound contract that does not exist yet.
Use the current dashboard and discuss roadmap requirements with sales.