SeoboxSeobox

Integrations

S
By Seobox Eng Team
Published on: 2026-07-17•9 min read•Last reviewed: 2026-07-17
TL;DR

Connect Seobox to WordPress, Webflow, Shopify, a headless stack, or Google Search Console — how each integration works and what it unlocks.

Connecting your CMS

Every site in Seobox needs a publishing destination. Add a site from the dashboard, then choose the CMS type that matches your stack — the generation pipeline is identical regardless of destination; only the publish step changes.

Key takeaway: You can generate and review content without connecting a CMS at all — the integration only controls how (and whether) approved articles get pushed live automatically.

WordPress

Connect via the site URL plus an application password (Users → Profile → Application Passwords in WordPress admin) — no plugin install required. Once connected, approved articles publish as WordPress posts with the title, body, featured image, and SEO meta fields (compatible with Yoast/Rank Math field conventions) set automatically.

Webflow

Connect via a Webflow API token scoped to your site and select the CMS Collection that should receive new articles. Field mapping (title, slug, rich-text body, meta description) is configured once per collection during setup.

Shopify

Connect via a private app access token and publish generated articles directly to your store's blog. Useful for stores running content marketing alongside product pages without a separate CMS.

Headless / custom stack

If your frontend pulls content from a custom API or static site generator rather than a traditional CMS, use the headless integration: Seobox pushes finished articles to your endpoint as structured JSON (title, slug, body, meta fields) via the same signed-webhook mechanism described in Webhooks, or you can pull them directly with GET /v1/api/blogs from the REST API.

No CMS connected

Sites can also run in review-only mode with no CMS connected at all — generated drafts sit in your dashboard for manual copy-paste or export, useful during evaluation or for sites where publishing goes through a separate approval workflow.

Google Search Console

GSC is a separate integration from your CMS connection and is what powers the opportunity engine described in keyword research. Connecting it lets Seobox pull real ranking and click data for your site instead of relying on estimated third-party metrics.

  1. From a site's settings, click Connect Search Console — this starts a standard Google OAuth consent flow.
  2. Select which verified GSC property maps to this site.
  3. Seobox runs an initial sync (last 28 days of query-level performance data) and then keeps it updated automatically.
  4. Disconnect at any time from the same settings panel — this revokes the stored token and stops further syncs.

Search Console data directly feeds:

  • Ranking-gap detection — keywords you rank for on page 2–3 that are close to breaking into page 1.
  • Decay detection — pages that were previously getting clicks and impressions and are now declining.
  • Live performance snapshots — actual clicks, impressions, CTR, and position per query, refreshed on demand or on your regular sync schedule.

Choosing between manual sync and automatic publishing

Every CMS integration supports two modes:

Mode What happens
Review first Generated drafts wait in your dashboard for manual approval before publishing
Auto-publish Articles that clear the quality-scoring gate publish automatically with no manual step

Most teams start in review-first mode while validating output quality against their brand voice, then move specific sites (or specific content types) to auto-publish once they trust the pipeline.

Troubleshooting a failed publish

  • WordPress: confirm the application password hasn't been revoked and that the connected user still has publishing permissions.
  • Webflow: confirm the mapped Collection still exists and its field schema hasn't changed since setup — a renamed or deleted field breaks the mapping silently.
  • Shopify: confirm the private app token is still active and scoped to write_content.
  • Any integration: check for a blog.failed webhook event or the run status via GET /v1/api/blogs/:uid — the failure reason is included in both.

FAQ

Can one account connect multiple CMS types across different sites? Yes — each site has its own independent CMS connection, so an agency managing WordPress, Webflow, and headless clients from one account is a normal setup.

Does disconnecting Search Console delete existing opportunity data? No, historical data already synced stays available; disconnecting only stops future syncs.

What happens to already-published articles if I switch CMS type on a site? Nothing retroactive — the new connection only affects future publishes. Previously published articles remain wherever they were originally pushed.