Connect your tools
Bring search evidence in and send approved content to your website.
Two connection types serve different purposes: Search Console contributes evidence, while publishing integrations deliver content. External assistants use a third, separate connection through MCP.
Choose your destination
| Connection | What it does | What you need |
|---|---|---|
| Google Search Console | Imports organic search data and informs research | Google access to a matching property |
| WordPress | Creates posts as drafts or live content | Site URL, username and application password |
| Shopify | Creates articles in a selected blog | Store domain, Admin API access token and blog |
| WordPress.com | Creates posts and uploads their covers to your hosted site | WordPress.com account consent for one site |
| Webflow | Creates CMS items directly, or through your existing webhook | Site API token, collection and field mapping |
| Ghost | Creates posts with preserved HTML and a featured image | Ghost API URL and Admin API key |
| Wix | Creates native blog posts with covers and an existing author | Wix Blog and site authorization |
| Framer | Sends articles to a mapped CMS collection | Project API key and article-template component |
| Custom webhook | Sends article HTML to your own publishing workflow | Public HTTPS receiver and field mapping |
| MCP | Lets an authorized assistant work with your account | An MCP-compatible assistant and account consent |
Connect, then select
Connecting credentials and selecting a publishing destination are separate steps. After saving a connection, open Plan → Schedule and publishing and choose where future articles should go.
Set the destination to Draft for the first delivery. Confirm that the article appears correctly before switching to live publication.
Optional at setup
You can skip Search Console or publishing during onboarding. Research can use market and website evidence without Search Console. Articles can be prepared without a CMS connection.
Skipped integrations do not secretly publish through another destination.
Keep connections healthy
Credentials can expire, permissions can change and websites can move. Re-test after changes. If a delivery is ambiguous, check the actual destination before submitting it again.
Never share credentials in a support conversation or assistant prompt. Use the integration's dedicated form.
