BigCommerce & platform news, tracked daily.
BigCommerce releases and broader ecommerce-platform changes that affect how stores are built and ranked.
What changed, as it happens.
Tracked daily from primary sources. The items below are what we're watching for clients right now.
Category URLs join what BigCommerce will translate
BigCommerce's Translations Admin GraphQL API now supports category URL path translations for multilingual Stencil storefronts. A new CATEGORY_URL_PATHS resource type addresses each category as bc/store/categoryUrlPath/{category_id}, with queries and mutations for listing, updating and deleting url_path translations. The documentation adds a dedicated Category URLs page, and the translations overview now links to both Category URLs and Product URLs.Source: BigCommerce Changelog →
Our take: Product URLs were already translatable; categories are what this adds. Changing a live category path changes the URL, so a storefront already serving translated copy on English slugs needs a redirect for every path it fixes, plus a pass over internal links and the hreflang cluster pointing at them. Do it before the localized pages accumulate rankings.
Read our full take →Google is testing a countdown badge on Shopping ads
Google is running an experimental "Deal Ends" annotation on Product Listing Ads that adds a real-time urgency badge, such as "3 days left", to the ad. Search Engine Roundtable reports the test is running globally with the exception of the EEA, Switzerland and the UK.Source: Search Engine Roundtable →
Our take: Nobody has said what feeds the countdown. Merchant Center already carries promotion start and end dates, and if those are the input then the badge is being generated from a field plenty of stores set once and never revisit. The excluded markets narrow it further. The EEA, Switzerland and the UK regulate countdown claims and reference pricing more tightly than anywhere else this is running, and skipping all three suggests the open question here is compliance rather than rendering.
Read our full take →Featured promotions get an API field, a callout message, and four page types
BigCommerce added featured-promotion support to the Promotions API and the Stencil context. A new is_featured_promotion boolean marks a promotion as featured, a featured_promotion_callout_message field carries up to 80 characters of callout text, and a read-only promotion_category field reports whether a promotion is a cart or a shipping promotion. An is_featured query parameter filters promotions by the flag. On the storefront side, a new featured_promotions array on the Product object exposes each featured promotion's ID, callout text, priority and category, and it is available on product detail pages, category listings, brand pages and search results. A store can have a maximum of five featured promotions.Source: BigCommerce Developer Changelog →
Our take: Cornerstone picked up featured-promotion callouts in July, which left the display side ready with no documented way to choose what filled it. The API is that half. Five is a low cap, and it makes this a merchandising slot rather than somewhere to dump every live discount; the priority value in the Stencil context says you are expected to order them. Category, brand and search pages carrying the same context matters more than the product page does, because a free-shipping threshold does more work on a listing page than it does at the cart.
Read our full take →WP Engine will let WordPress brands swap the commerce layer for BigCommerce and keep the front end
WP Engine announced a strategic partnership with Commerce (NASDAQ: CMRC), BigCommerce's parent company, to launch WP Engine Commerce Connect for BigCommerce. The pitch is that high-growth mid-market brands can modernize commerce capabilities without abandoning what they have built in WordPress: content, themes, custom designs, URL structures, SEO foundation, and front-end experiences stay in place while BigCommerce runs commerce underneath. WP Engine CEO Heather Brunner said growing brands "shouldn't have to choose between WordPress and commerce capabilities they need to scale," and Commerce CEO Travis Hess described it as "an open, flexible foundation bringing content and commerce together to create richer customer experiences." The announcement publishes no pricing, no availability date, and no technical architecture.Source: WP Engine →
Our take: "No changes to SEO" is a claim to verify, not a feature. A replatform that preserves URLs still tends to move templates and internal linking, and those move rankings on their own. The architecture has not been published, so there is no way yet to judge what changes at the URL level. Ask for that before anyone signs.
Read our full take →Google’s UCP checkout puts a Buy button on product listings inside AI Mode and Gemini
Google documented the merchant side of the Universal Commerce Protocol — an open standard for agentic commerce that lets a shopper complete a purchase straight from a product listing in AI Mode and Gemini, paying through Google Pay with card and shipping details from Google Wallet. Only listings carrying the native_commerce(checkout_eligibility) product attribute get the Buy button, so it’s a per-product opt-in rather than an account-wide switch. Onboarding runs through an interest form, a Google Pay & Wallet Console account, and a technical implementation against the developer docs; eligibility currently covers products in the US, Canada, and Australia, and participation is limited to selected merchants while the early-access program rolls out in phases.Source: Google Merchant Center Help →
Our take: Per-product opt-in is the planning detail: you can pilot agentic checkout on a controlled slice of the catalog instead of flipping the whole store. US, Canada, or Australia? Early-access queues reward early paperwork, so file the interest form now.
Read our full take →
Custom ecommerce software, AI apps, and SEO — the work other agencies quote around, built in-house.
20+ years of BigCommerce engineering, now AI-augmented. Tell us your store, your stack, and your deadline — we quote fixed scope on the first call.