Publish AI articles to any CMS with a webhook
No native integration for your stack? QuickSEO can POST every published article to your own endpoint as JSON — full HTML and Markdown body, title, slug, tags, and cover image — secured with a Bearer token. Receive it in any language, drop it into any headless CMS, and the loop is automated.
How the Webhook integration works
Add your endpoint URL
Open your site’s Settings → Webhook Publishing, enter the URL that will receive the POST, and save. QuickSEO generates a per-site Bearer token — shown in full once — to authenticate every delivery.
Verify the request
Your receiver checks the Authorization: Bearer header against the token, then reads the article.published payload — title, slug, tags, cover image, and the body as both HTML and Markdown.
Create the post and return 2xx
Create (or update) the post in your CMS and respond with a 2xx. QuickSEO marks the article Published. Failures are retried with backoff, and deliveries are idempotent by article id.
Why teams use it
Works with any stack
A plain JSON POST means you can receive articles in Next.js, Laravel, Rails, a serverless function, or a no-code tool like Make or Zapier — and route them into any CMS you run.
HTML and Markdown in every payload
Each event includes the full article body as both rendered HTML and clean Markdown, so you can store whichever format your CMS expects without re-parsing.
Signed and idempotent
Every request carries a Bearer token you can regenerate, and deliveries are idempotent by article id — so a retry updates the same post instead of creating a duplicate.
Automatic retries
If your endpoint is briefly down, QuickSEO retries with backoff before giving up, so a transient blip doesn’t silently drop an article.
Frequently asked questions
What does the payload look like?
A JSON body for the article.published event containing the article id, title, slug, description, tags, cover image URL, and the body as both HTML and Markdown. The full shape and a copy-paste verification example are in the webhook docs.
How is the request authenticated?
Each POST includes an Authorization: Bearer header with a per-site token QuickSEO generates. The full token is shown only when you create or regenerate it; afterwards only the last 4 characters are displayed.
What happens if my endpoint is down?
QuickSEO retries with backoff (immediately, then after roughly 30 seconds and 2 minutes) before stopping. Each request has a 10-second timeout, and deliveries are idempotent by article id.
When should I use a webhook instead of a native integration?
Use the native WordPress or Ghost integrations when you’re on those platforms. Reach for the webhook when you run a headless or custom CMS, a static-site generator, or want to pipe articles through an automation tool.
More integrations
Auto-publish to Webhook today
Generate SEO-optimized articles and ship them straight to Webhook. Track how they perform across Google Search and AI chatbots — all in one dashboard.