SEO by platform
SEO for BigCommerce
Articles publish into the store's built-in blog through the BigCommerce API, with a store-level API account token and your store hash. Posts start as drafts in your control panel until you publish them or switch the connection live.
How publishing works on BigCommerce
The connection publishes to the built-in blog with a store-level API account's access token, addressed by your store hash. It starts in draft mode like every connection, posts land with title, body and a meta description mapped into the native blog, and once a post is live the verifier fetches the storefront URL and records what came back.
Native blog, no plugin
Posts land with their title and body mapped into BigCommerce's built-in blog. There is no category hierarchy to map, and your theme controls the rendering.
Help centre: BigcommerceDrafts until you say otherwise
The connection starts in draft mode, so posts wait in your control panel until you publish them or switch the connection to publish live.
Published means the public URL answered
After every publish we fetch the public URL and record what came back. Published shows only when the page was found, a fresh 404 waits out a grace window, and a server error never concludes the page is missing.
Articles come off a planned calendar
Plan items on the content calendar and write them two ways: click Write on a card, or let Auto-write pick each one up at midnight on its calendar date. Both run the same researched pipeline, which drafts the article and then revises it against the content score across sweeps.
Every article is scored before you ship it
The content score runs 36 fixed checks in 6 categories, with no randomness anywhere: the same page always produces the same score. Each check comes back as a pass, a warn or a fail, and each failure names its specific fix.
What this connection will not do
Stated up front, because finding out after the first publish costs more. Each line is a fact about what we send BigCommerce, not a guess about the platform.
We do not set the post thumbnail: BigCommerce takes it as a path inside its own image manager, not a URL. Add the thumbnail on the post in the BigCommerce blog editor.
We send the post title and a meta description, and nothing for a separate SEO title. Set it on the post in the BigCommerce blog editor.
The API account must keep its content scope. Editing the account's scopes in BigCommerce can silently drop it. Documented: Bigcommerce
Connect it in three steps
The same fields the connect wizard asks for, in the order it asks.
Create a store-level API account
In the control panel, go to Settings, then Store-level API accounts, and create an account with content modify scope. Copy the access token.
Note your store hash
It is the short code in your control panel URL, store-XXXX.mybigcommerce.com. On a control panel with two stores, check the hash against the store you mean.
Connect and test
In the project's Publishing tab, choose BigCommerce, paste the token and store hash, and send a test publish. Check the post under Storefront, then Blog.
Questions people ask
The ones that decide whether this fits, answered with the verdict first.
- Why am I getting a 401 on publish?
- Token or scopes. Store-level API accounts are the supported kind here, and the account needs content modify scope. Create a fresh account with the right scopes and paste its token.
- The post exists but the blog page 404s. Why?
- The store's blog is disabled in storefront settings. Enable it, the posts were saved and appear once the blog itself is visible.
- My store's blog actually runs on WordPress. Which connection?
- WordPress. The connection follows where the posts must land, so a WordPress blog next to a BigCommerce store wants the WordPress connector.
Other platforms
Same pipeline, different door. Every platform page states what its connector sends and what it will not.
Shopify
Articles publish into your store's own blog through Shopify's Admin API, where content builds authority next to the collections and products it links to. New connections publish as drafts until you switch them live.
WordPress
Two connectors, one pipeline. Publish with an application password, or install the plugin and paste one Integration Key. Either way the article arrives with its images uploaded into your own media library, and the publish is confirmed by fetching the public URL.
GitHub
Articles commit as markdown files into the repository and path you choose, and your deploy turns each commit into a page. Built for Next.js, Astro, Hugo, Jekyll and any headless setup where a committed file becomes a page on the next build.
SEO by platform
See it on your own site
A free audit grades your site A+ to F, then the calendar, the writer and the BigCommerce connection do the week's work. No card required.