Connect Webhook to SEOryon
For teams with their own stack. SEOryon POSTs an HMAC-signed JSON payload to your endpoint on publish, update, delete, and unpublish, and your code decides what happens next.
- How it connects
- HMAC-signed JSON (oryon-v1) POSTed to your endpoint
- Edit after publishing
- Yes, updates republish the same post
- Delete and unpublish
- Yes, from SEOryon
- Tables
- No. SEOryon sends a structured bullet list instead.
Before you connect
Get these in place first. They are the difference between a connection that goes green and one that fails on the first publish.
- A live HTTPS endpoint that verifies the signature and acts on the events.
- Somewhere safe to store the signing secret.
- A developer to wire it up. Receiver snippets in Node, PHP, and Python are provided.
How to connect, step by step
The same steps SEOryon walks you through in the app, with the screens you will actually see.
- 1
In SEOryon, open Settings, Integrations, Webhook and generate the signing secret.
Screenshot comingThe webhook integration screen in SEOryon with the endpoint URL and signing secretSEOryon: endpoint URL and signing secret. - 2
Build your receiver from the guide, in Node, PHP, or Python. It verifies the HMAC-SHA256 signature over the raw body, rejects anything stale or unsigned, then acts on the event.
- 3
Paste your endpoint URL into SEOryon and save.
- 4
SEOryon sends a test event and verifies the response before marking the connection healthy.
What happens when you click Connect
Connecting runs a real test publish. SEOryon creates a draft, verifies it, deletes it, and only then marks the connection healthy, so a connected badge means publishing genuinely works.
What you can do once Webhook is connected
- The full payload: content_html and content_md, meta title and description, excerpt, featured image, tags, canonical URL, and language.
- JSON-LD included: Article, plus FAQPage when the article has a visible FAQ, and the connected json_ld_graph.
- An optional author byline.
- Publish, update, delete, and unpublish all sync as separate events.
What to know about Webhook
The honest part. Every platform has edges, and you should hear about them from us before you hit them.
Tables are off for a generic webhook. SEOryon cannot control how an unknown receiver renders HTML, so it sends a structured bullet-list comparison instead.
Your receiver has to verify the HMAC and act on the events. A receiver that returns 200 and quietly does nothing looks healthy to SEOryon, because there is no way to tell from the outside.
Comparison tables do not publish as tables on Webhook, so SEOryon sends a structured bullet list instead. See the full table support matrix.
What publishing looks like
Every approved article arrives at your endpoint as a signed JSON payload with the content, the metadata, and the structured data, ready for your stack to render.
SEO on Webhook
Best practices that move the needle
The payload carries everything a search engine needs. Make sure your receiver uses it.
- Verify the signature before you trust a payload, then act on the event.
- Write the meta title, meta description, and canonical URL from the payload into your template head.
- Handle update, delete, and unpublish too, not just publish, so removed posts really disappear.
- Keep URLs stable and match on the slug SEOryon sends, since that is how updates find the right post.
- Render the JSON-LD blocks as they arrive, including FAQPage when the article carries a visible FAQ.
Other integrations
See it on your own site, free.
Start a 3-day free trial and generate 3 real articles on your own site before you decide. Cancel before day 3 and you pay nothing.
- Done-for-you articles, monthly
- Built on your real search data
- Publishes straight to your CMS
- Built for Google and AI search
- 3-day free trial, cancel anytime