BigCommerce SEO and GEO, in the HTML your store sends.
Clione connects to your BigCommerce store without code, drafts the signals every product, category and page is missing, and publishes them through the Widget API. The graph is rendered on the server, not added later by a script.
What lands in your BigCommerce store.
Descriptions that feed site search too
Who each product is for, how people choose it and the objection to answer, plus search keywords that also fill BigCommerce's own site search field.
One graph per product page
Organization, WebSite, BreadcrumbList and Product, plus FAQPage when the product has questions.
FAQs for the whole catalog
Generated, or imported by CSV with BigCommerce's own ids, and shown on the page by the FAQ renderer.
What rendered, signal by signal
Clione fetches your live product pages after each push and tells you when a signal goes missing.
Rendered on the server, through the Widget API.
BigCommerce's Widget API puts Clione's signals into the page the server builds. They are in the HTML your store sends, not injected in the browser afterwards.
- The JSON-LD graph on every product page, server-side
- Questions shown as an accordion by the FAQ renderer, installed from Store Settings
- Your reviews' ratings in the product schema, read from BigCommerce's own reviews. No reviews, no rating
Products, categories and pages. No shopper data.
Clione syncs the products first, then the categories, then the content pages, with the time and count of each sync. It reads your catalog and your content, and it never calls a customer API.
- Enrichment, FAQs, publishing and checks on all three
- A stale catalog re-syncs on its own, and that sync only reads
- When a PIM or an app overwrites a field Clione pushed, the next sync names the field and the date
Pushed, then checked on the live page.
After each push Clione fetches your live BigCommerce page and reports what rendered against what it pushed. Every page is checked again on a schedule, and you hear the moment a signal goes missing.
Running Catalyst or another headless storefront?
It reads the same BigCommerce catalog Clione enriches, and prints Clione's signals from the product metafields or the API. We set it up with your developers.
Clione on headless storefronts →What BigCommerce merchants ask.
Do I need a developer or a theme edit?
No. You authorize Clione on the store and sync the catalog. The setup checklist walks you through installing the schema injector and the FAQ renderer, then checks that both are working.
Will it clash with my theme's structured data?
No. Clione's Product node carries its own stable @id and sits beside any node your theme already prints, instead of duplicating it.
Do categories and pages get the graph too?
Every product page gets the full graph today. Categories and content pages get their meta description and search keywords now, and their own graph is on the way.
I run several client stores. Does that work?
Yes. One organization holds many stores, each with its own quotas and roles, and one dashboard sets them side by side. That's how Clione for agencies works.
What does it cost?
Nothing, during the beta. Clione is taking selected stores into this stage, in limited places, free of charge, and prices are published when the beta ends in Q1 2027.
Bring your BigCommerce store. We'll open one product.
On a short call we put what your store serves today beside what Clione would publish through the Widget API.