Publishing integrations

Every integration follows the same steps in Rankealo:

1. Open Integrations and choose your platform.
2. Fill in the credential fields (see each platform guide for where to find them).
3. Click Test Connection — Rankealo verifies credentials against the live API. You must pass before Save is enabled.
4. Click Save Integration. Publishing is now available for that domain.

Every platform receives the same core fields; the rest depends on the platform:

• TitleThe article title.
• ContentFull article body as HTML (or markdown where the platform supports it).
• Meta descriptionSEO meta description / excerpt, where the platform has a field for it.

Slug, featured image, tags and SEO title depend on the platform and your field mapping. Each platform guide lists exactly what it sends. Platforms also map fields differently (Webflow/Framer field slugs, Shopify blog posts, Notion database properties).

If you use the Custom API (webhook), the payload carries both Markdown and HTML so you can render it however your site prefers.

Rankealo stores the CMS post ID for each published article. When you edit an article — or when Improvements re-optimizes it from search performance — Rankealo updates the same post in place instead of creating duplicates. Webhook integrations receive an update_articles event with cms_post_id so your endpoint knows which record to patch.

Existing articles stay linked to the platform they were published to. If you connect a different CMS, Rankealo will not send an old post id to the new platform: updating or deleting such an article is refused with a message naming both platforms. To move an article, reconnect the original platform, or republish it to the new one (this creates a new post and does not remove the old one). You can also remove the article from Rankealo only, leaving the old post untouched.

Connect Slack under Settings → Integrations → Slack alerts. Rankealo asks for four bot permissions only: post messages, post to public channels without an invite, and list channels so you can pick one. It never reads your messages. Choose a channel, send a test message, and agent notify results are posted there with formatted blocks. The incoming-webhook field stays available as a fallback (and still carries AI-visibility alerts); when the app is installed it takes precedence for agent results.

When Slack approvals are enabled for your deployment, an agent that pauses for review posts Approve and Reject buttons in the same channel. The decision goes through the same approval as the dashboard, records who clicked, and replaces the buttons with the result. Disconnecting removes the stored token and revokes it at Slack.