Connect the surface you deploy through. Changes land where your code and content live.

Connectors let HubSEO deploy verified fixes to the place your site actually lives. Available connectors: GitHub, WordPress, and Shopify.

What a connector does

Without a connector, the AI fix workflow stops at the diff: you review the prepared change and apply it yourself. With a connector, HubSEO can push the approved change itself and immediately verify it with a live re-scan: deploy and verify, the middle tier of intervention.

Git PR Handoff

GitHub App

Opens the change as a branch or pull request on your repo, so your normal CI and review gates stay in charge.

CMS Sync

WordPress REST

Applies content-level changes through the REST API with an application password scoped to the site.

Storefront

Shopify Admin

Applies theme and content changes through the Admin API with a scoped access token.

Credentials

Third-party credentials are never stored in plaintext. They are encrypted with AES-256-GCM before storage: a 32-byte master secret, a fresh 12-byte IV per write, stored as { key_version, iv, tag, ciphertext }. Disconnecting a connector revokes the stored credential.

Entitlements

Connectors require a paid plan or admin access: Starter and above. Founding Members hold lifetime full access. See Plans.

Safety rules

Only safe_auto-classified changes with confidence ≥ 0.85 and a verified rollback plan can ever deploy without a click.
Protected directives: canonicals, 301 redirects, robots.txt, URL migrations. These are never auto-deployed, with or without a connector. See Autonomous mode.
Every deploy is followed by the verification re-scan. A deployed change that does not fix the measurement is reported as exactly that.

Automated Rollback Protection

Every connector deployment automatically captures a rollback state snapshot before writing:

GitHub: Records branch ref and Pull Request URL; rollback closes the PR and deletes the generated branch.
WordPress: Preserves prior post metadata (_yoast_wpseo_title, rank_math_title) in rollback_plan; rollback restores original values via REST API.
Shopify: Saves previous metafield values; rollback re-applies the captured pre-state.
Instant Rollback: In the project workspace, any deployed intervention can be reverted with 1-click via the Rollback button or POST /api/growth/interventions/[id]/rollback.

Connectors: GitHub, WordPress, Shopify