SiteLift LogoSiteLiftDocs

BigCommerceBigCommerce

Publish SiteLift articles to your BigCommerce blog and comparison pages as storefront pages with a store-level API token.

How it works

SiteLift uses a store-level API account to write to the BigCommerce blog. Each article becomes a published blog post under /blog/, matched by URL so a republish updates the same post. Comparison pages publish as content pages under your compare path.

Setup Guide

  1. 1

    Create a store-level API account

    In the control panel open Settings → Store-level API accounts and click Create API account. Choose V2/V3 API token and name it SiteLift.

    Under OAuth scopes set Content to modify and Information & Settings to read-only (SiteLift reads the store name and URL from it), then save. BigCommerce shows the access token once in a dialog (and downloads a text file with it); copy it now.

    The store hash is the id in the API path field on that screen, https://api.bigcommerce.com/stores/{hash}/v3/, and in your control panel address, store-{hash}.mybigcommerce.com. You can paste either URL into SiteLift as it is.

  2. 2

    Connect in SiteLift

    Open Settings → Integrations, choose BigCommerce, paste the API path (or the hash) and the token. SiteLift confirms the store name before saving.

  3. 3

    Publish

    Articles publish on your content calendar schedule and appear at https://your-store.com/blog/your-article/.

Tip

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

What gets published

  • Title. The storefront theme renders the post title, so the H1 is removed from the body.
  • Featured image. BigCommerce blog thumbnails must be files uploaded to the store’s image manager, which the API cannot do for external images. The hero image therefore stays inside the body, at the top of the post, where readers still see it.
  • SEO fields. The meta description and meta keywords (from the target keywords) are set on the post.
  • Structured data. The JSON-LD is appended to the body as a script tag, which Stencil themes output as-is.
  • Tags. Target and secondary keywords become blog tags.

Competitor comparison pages

Supported. Comparison pages publish as storefront content pages at /compare/your-brand-vs-competitor (your compare path), with a hub page at /compare. Unpublishing hides the page.

Troubleshooting

  • 401 or 403 from BigCommerce. The token or store hash is wrong, or the API account lacks a scope. It needs Content set to modify and Information & Settings set to read-only. Edit the account or create a new one, then connect again.
  • Published URL opens a 404. Blog visibility may be off for the storefront, or the store uses a channel where the blog is disabled. Check Storefront → Blog in the control panel.
  • Hero image missing. Some themes hide images at the top of a post. The image is in the body; adjust the theme’s blog post template to show it.

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

Previous

HubSpot

Next

GoHighLevel