Integrations Overview

PrismSEO connects to one data source and one or more publishing destinations. Search Console tells it what to write; your CMS is where the finished article lands. You keep your existing stack — PrismSEO just plugs into it.

Data source

• Google Search Console — read-only access to your queries, pages, clicks, and impressions. This is what grounds every content recommendation in real demand instead of keyword guesswork.

Publishing destinations

Pick whichever matches where your site lives. You can connect more than one.

• WordPress — publishes via the WordPress REST API using an Application Password. Articles land as drafts or live posts. Best for teams already on WordPress.
• Framer CMS — writes into a CMS collection with automatic field mapping and slug-safe updates. Best for design-led teams building in Framer.
• Webhook / Custom CMS — sends a signed JSON payload to any endpoint you control (Next.js, headless CMS, internal pipeline). Best for full control over storage and rendering.

How a publish works

Every destination follows the same shape, so the mental model is identical whichever you choose:

• You generate and review an article in Content.
• You click Publish and select a connected destination.
• PrismSEO sends the article — title, slug, HTML body, excerpt, and SEO metadata.
• You choose Draft (needs review) or Publish (goes live).
• The result is recorded in Publish History with a status and, on failure, the exact error.

Publishing is idempotent by slug / article ID — re-publishing the same article updates the existing post rather than creating a duplicate.

Recommended setup order

• Connect Search Console first so recommendations are grounded.
• Connect one publishing destination.
• Do a draft publish and confirm the slug, body, and metadata mapped correctly.
• Switch to live publishing once the output looks right in your CMS.

Security notes

• Credentials are encrypted at rest. WordPress uses a revocable Application Password; Framer uses a scoped API token; webhooks use a Bearer token you set.
• Prefer a dedicated publishing user in your CMS with only the capabilities it needs.
• For webhooks, validate the Bearer token on every request and only accept HTTPS. PrismSEO refuses to send to private or localhost URLs.
• Rotate tokens periodically; reconnecting in Integrations is all it takes.

For the exact request contract behind custom integrations, see the Publishing API Reference.