Skip to content

Pipe SEO content anywhere

Point a signed webhook at your automation stack. Every publish ships structured content you can route to custom CMS, Slack, or internal tools.

The Webhook connector is built and waiting for release. Get an email the day it opens.

See the product roadmap
g.ac

How you connect

Coming soon
  • HTTPS webhook URL + signing secret

What goals.ac will do on Webhook

Planned behaviour for this destination, step by step.

  1. 01

    HMAC-SHA256 signatures

    X-GoalsAC-Signature-V2 signs the timestamp, delivery id, and body, so replays can be rejected. Redirects are not followed.

  2. 02

    Rich event payload

    Title, markdown, HTML, metaDescription, keywords, FAQ, citations, jsonLd, status.

  3. 03

    Output modes

    both | markdown | html | full canonical, choose what your worker needs.

  4. 04

    article.publish / article.test

    Test events let you wire Zapier/Make without publishing live.

Formats that will publish here

  • Any long-form piece
  • Automation fan-out

Webhook questions

How do I verify the signature?
Compute HMAC-SHA256 of "timestamp.deliveryId.rawBody" with your secret, using X-GoalsAC-Timestamp and X-GoalsAC-Delivery, and compare it to the v2 value in X-GoalsAC-Signature-V2. Reject timestamps older than 5 minutes and delivery ids you have already seen. The older X-GoalsAC-Signature (body only) is still sent.
Why did redirects fail?
We POST only to the configured HTTPS URL, 3xx redirects are not followed.
What is “full” mode?
Includes the canonical content model (FAQ, citations, JSON-LD) alongside body fields.

Start on WordPress today

WordPress publishing is live now. Your drafts, voice and keyword plan carry over when Webhook opens.