Modernes Web / Webhooks
Veröffentlichen Sie Artikel über eine Webhook-URL in jedem CMS oder jeder Plattform.
Overview
The Webhooks integration is designed for any CMS or web platform that is not WordPress, Shopify, or Wix. By configuring a webhook URL, you can receive article data from Rankfender via HTTP POST requests and process it in your own system. This makes it possible to connect Rankfender to any modern web platform, including Next.js, Gatsby, Hugo, custom CMS solutions, or any backend that can receive HTTP requests.
How It Works
When an article is published from Rankfender with the Webhooks integration active, Rankfender sends an HTTP POST request to your configured webhook endpoint. Your server receives the request, processes the article data, and creates the content in your CMS or platform. This decoupled approach gives you complete control over how articles are handled on your end.
Article Payload
Each webhook POST request includes a JSON payload with the following article data:
| Field | Type | Description |
|---|---|---|
| title | string | The article title. |
| content | string (HTML) | The full article content as HTML markup. |
| meta_description | string | The SEO meta description for the article. |
| featured_image_url | string (URL) | The URL of the article's featured image. |
| keywords | array of strings | The target keywords associated with the article. |
| publish_date | string (ISO 8601) | The intended publish date for the article. |
Setup
To configure the Webhooks integration:
- Enter your webhook endpoint URL - Navigate to Project Settings > Integrations > Webhooks and enter the full URL of your webhook endpoint. This must be a publicly accessible HTTPS endpoint that can receive POST requests.
- Add custom headers (optional) - If your endpoint requires authentication, you can add custom headers that will be included with every webhook request. Common use cases include API keys, bearer tokens, or custom authentication headers.
- Test the connection - Click Test Connection to send a test payload to your endpoint. Rankfender will report whether the request was successful based on the HTTP response status code. A 2xx response indicates success.
Supported Platforms
The Webhooks integration works with any platform that can receive HTTP POST requests. Common use cases include:
- Next.js - Create an API route that receives the webhook and creates content in your data layer.
- Gatsby - Use a serverless function or a content management backend that triggers Gatsby rebuilds.
- Hugo - Set up a server-side handler that writes markdown files and triggers site rebuilds.
- Custom CMS - Build a webhook receiver that maps the article payload to your CMS's content model.
- Headless CMS platforms - Route webhook data through a middleware layer to platforms like Contentful, Sanity, or Strapi.
Managing the Integration
You can manage the Webhooks integration from Project Settings > Integrations:
- Active/Inactive Toggle - Toggle the integration on or off. When inactive, no webhook requests will be sent, even if articles are published. The endpoint configuration is preserved.
- Update Endpoint - Change the webhook URL or custom headers at any time. Changes take effect immediately for subsequent article publications.
- Test Connection - Re-test the connection after making changes to verify that your endpoint is still receiving requests correctly.