Connect your store once — its built-in blog fills itself.
BigCommerce’s built-in Blog is a real, indexable storefront surface, and DraftSEO publishes to it over your store’s API. Article images are uploaded onto the store itself, so every picture serves from your own BigCommerce CDN — nothing hot-links back to us.
| Connection | Store API token + WebDAV — from Settings → Store-level API accounts + File Access |
|---|---|
| Setup time | ~5 minutes, once |
| Content target | The native Built-in Blog — real indexable storefront pages, no plugin |
| Image hosting | Your store’s CDN — uploaded to your store, never hot-linked |
| Publish modes | Auto · draft · scheduled |
Who does what
Nothing — after the one-time connect (an API account plus a WebDAV password), the blog runs itself. Prefer control? Publish as drafts and approve each post in your store admin.
You run the store. The blog brings the next buyers.
Setup
Settings → Store-level API accounts → Create, with Content set to Modify, Information & Settings set to Read-only and Products set to Read-only. Copy the store hash and access token. BigCommerce can’t add a scope later — so set all three now.
~2 minutes
Settings → File Access (WebDAV) — note your WebDAV username (your email) and generate a password. This is how article images get hosted on your store.
~1 minute
Connect a site → BigCommerce → paste the store hash, token and WebDAV credentials.
~2 minutes
Buyer keywords in, product-aware articles out — published to your store blog on your schedule.
Ongoing · zero clicks
What you win
Buying guides and comparisons catch shoppers mid-decision — organic traffic with intent.
Posts and images live on your BigCommerce store and its CDN — nothing external to break later.
Stores that publish weekly compound; autopilot makes weekly automatic.
FAQ
A Store-level API account with three scopes — Content set to Modify (to write the posts), Information & Settings set to Read-only (so we can read your storefront domain) and Products set to Read-only (so articles can link to your products and categories; DraftSEO never changes them) — from Settings → Store-level API accounts, plus a WebDAV password from Settings → File Access. Pick all three when you create the account: BigCommerce doesn’t let you add one afterwards. It takes a few minutes and no app install — the blog is your store’s native one.
On your own store. BigCommerce has no store-token API for standalone blog images, so DraftSEO uploads each one to your store via WebDAV — they then serve from your BigCommerce CDN, never hot-linked from our servers.
No. DraftSEO publishes to the store’s built-in blog through the store API you create — there’s no app to install and no marketplace approval.
No card required. Watch it land on your store blog.