SiteLift LogoSiteLiftDocs

HubSpotHubSpot

Publish SiteLift articles to a HubSpot blog with a service key, with the featured image, meta data and structured data in place.

How it works

SiteLift publishes through the HubSpot Blog Posts API using a service key you create in your account. Service keys are the credential HubSpot now issues for integrations; the older private apps are retired. You choose the blog and the author once; every article is then created as a published post, and republishing an edited article updates the same post. HubSpot requires an author and a meta description on every published post, so both are always set.

Setup Guide

  1. 1

    Create a service key

    In HubSpot click the gear icon, then open Integrations → Service Keys in the settings sidebar and click Create service key. Name it SiteLift.

    Click Add new scope, type content in the search box and tick the scope named content (it covers the blog). Click Update, then create the key. Click Show and copy it.

    Service keys need Developer Tools access in HubSpot and can only carry scopes your own user has. If content does not appear, ask an admin to create the key.

  2. 2

    Have a blog and an author ready

    Posts go to a HubSpot blog, not a website page. Open Content → Blog: most accounts ship with a default blog. On the Blog authors tab make sure at least one author exists, because HubSpot refuses posts without one.

    Blogs are part of Content Hub and of Marketing Hub Professional and above. A free CRM account has no blog, so SiteLift finds nothing to publish into.

  3. 3

    Connect and pick a blog and author

    In SiteLift open Settings → Integrations, choose HubSpot and paste the key. SiteLift lists your blogs and blog authors; pick one of each. Added a blog or author after this step? Click Refresh in the picker.

  4. 4

    Publish

    Articles publish on your content calendar schedule. The published URL is the one HubSpot returns, so custom domains and blog root paths are respected.

Tip

Once connected you never log into HubSpot to publish. Articles go live on your SiteLift schedule, and edits made in SiteLift are pushed again when you republish.

What gets published

  • Title and featured image. Your blog template renders both, so the H1 and hero image leave the body and are sent as the post name and featured image (with alt text).
  • Slug. HubSpot slugs include the blog root, so an article becomes blog/your-article-slug when the blog lives at /blog.
  • SEO fields. The HTML title and meta description come from the article’s SEO data, with the first paragraph as a fallback for the description.
  • Structured data. The JSON-LD goes into the post’s head HTML.
  • Tags. Not sent; HubSpot tags must exist first, and most blogs manage them by hand.

Competitor comparison pages

Published as blog posts. HubSpot site pages must be built on a template from your theme, which SiteLift cannot choose for you, so each comparison page goes out as a post tagged Comparisons with the same title, body, meta title, meta description and structured data. The posts use your blog template and appear in the blog feed; the tag listing HubSpot generates for Comparisons acts as the hub. The dashboard shows a warning to that effect.

Troubleshooting

  • 401 or 403 from HubSpot. The key is wrong, was rotated, or is missing the content scope. Open the key under Settings → Integrations → Service Keys, add the scope or copy the current key, and reconnect.
  • No blogs found. The account has no blog. Blogs come with Content Hub and with Marketing Hub Professional or Enterprise; a free CRM account cannot publish posts. Create the blog under Content → Blog, then click Refresh in the picker.
  • Publish failed with a validation error. HubSpot refuses posts without an author or when the chosen blog was deleted. Use Test Connection to see which, then reconnect.
  • Post is live but on the wrong domain. The blog you picked is attached to that domain in HubSpot. Reconnect and pick the blog that lives on the domain you want.

Still stuck? Use Test Connection on the Integrations page; the message comes straight from HubSpot. Or write to support.

Previous

Ghost

Next

BigCommerce