Connecting your website

SupaTraffic writes articles. Connecting a website lets it publish them for you too — either when you press Publish, or automatically as each one is finished.

Both are off until you turn them on. Connecting a site does not start publishing, and automatic publishing is a separate switch on the Connections screen.

What happens when you publish

  • We create the post: title, body, URL slug, excerpt, tags and cover image.
  • We set the SEO title and meta description where the platform lets us. Several do not — each one is spelled out below.
  • We never touch anything else on your site. No themes, no settings, no other posts, no products.
  • If a publish fails halfway, we ask the platform whether the post arrived before trying again — so a retry cannot leave you with two copies of the same article.

What each platform needs, and what it cannot do

  • WordPress (self-hosted). Enter your site address and approve the connection on your own site — we never ask for your WordPress password. Your site issues an application password instead. Limitation: WordPress does not let any external tool set the SEO title or meta description — Yoast and Rank Math keep those private to plugins running on your site. We write our description into the post excerpt, which Yoast uses as its fallback. Your theme may also show that excerpt on archive and category pages.
  • Ghost. Paste the Admin API key from Settings → Integrations, plus the API URL shown on the same screen. SEO title and description are fully supported. Limitation: Ghost’s Starter plan does not include the Admin API, so a Starter site cannot be connected at all. Ghost also converts our HTML into its own format, which can flatten tables and code blocks — we tell you when an article contains either.
  • Webflow. Connect with Webflow, then choose which CMS collection your articles go into. We write items into that collection and publish them. Limitations: Webflow has no per-item SEO fields — we can fill text fields, but you bind them to the page title and description once in the Designer. Webflow also drops code blocks from rich text, so we warn you rather than let them vanish. And if your site has never been published, press Publish once in Webflow first: until then there is no live site for an article to appear on.
  • Framer. Paste a project API key and your project URL. Articles go into a CMS collection you choose, and we publish the project. Limitations: same SEO binding as Webflow — you connect the fields once in Page Settings. Publishing a Framer project publishes the whole site, so anything else you left unpublished in the editor goes live with the article.
  • Shopify. Install from the Shopify App Store; articles go to a blog you choose. SEO title and description are supported.
  • HubSpot. Paste a private app token with the content scope. SEO title and meta description are supported. Limitation: the content scope requires Content Hub or Marketing Hub Professional or above. Free and Starter accounts have a blog in the interface but cannot grant API access to it.
  • Notion. Authorize us and pick a database. Note: you must share the database with SupaTraffic in Notion’s permission picker during authorization — if it is not selected there, we cannot see it. Notion has no built-in SEO or publishing concept, so those fields are ordinary properties, and whether they reach Google depends on whatever renders your Notion pages.
  • Next.js and other Git-based sites. Install our GitHub app on the one repository you choose. Each article arrives as a draft pull request containing a Markdown file with front matter — you review and merge it, and your normal deploy publishes it. We read one of your existing posts to learn your front-matter keys and content directory, then show you what we found so you can correct it.

Your credentials

Credentials are encrypted before they are stored and are used only to publish the articles you asked for. What a credential is able to reach is decided by the platform rather than by us — we request the narrowest access each one offers, which on some platforms is not narrow. WordPress application passwords in particular cannot be restricted: the one your site issues grants access to that site’s API as the user who approved it.

You can disconnect at any time from the Connections screen. Where the platform supports it, we also tell the platform to revoke the credential rather than merely deleting our copy. You can revoke it on the platform yourself at any time, and that stops us immediately regardless of what our records say. Articles already published stay where they are — they are yours.

Something not working?

The Connections screen shows the last error for each connection in plain language, and there is a Check connection button that re-tests the credential. If a connection says it needs reconnecting, the credential was revoked or expired on the platform’s side.

Still stuck? Write to [email protected] and tell us which site and which article — we can see what the platform sent back.