How to fix server version on BigCommerce

Remove or suppress HTTP response headers that advertise your server software name and version to the public internet.

Steps for BigCommerce

  1. BigCommerce's SaaS infrastructure controls the 'Server' header — it is not configurable from the merchant admin.
  2. For custom middleware or API-driven storefronts (Catalyst/Next.js), add header suppression in your 'next.config.js' (see code snippets below) and deploy via Vercel or your chosen host.
  3. If using Cloudflare in front of BigCommerce, create a Cloudflare Transform Rule (Rules → Transform Rules → Modify Response Header) to delete 'X-Powered-By' and set 'Server' to a generic value.
  4. Verify via DevTools that no technology version string is visible in response headers.
Official BigCommerce documentation ↗

What is server version?

Every time a browser (or a bot) requests a page from your store, your web server sends back a set of "response headers" — invisible metadata about the response. Two of these headers, `Server` and `X-Powered-By`, often broadcast exactly what software is running your site and which version it is (for example, `Server: Vercel` or `X-Powered-By: Next.js`). This is called "server version disclosure" or "technology fingerprinting." While the header itself doesn't break anything, it acts like a name-badge that tells the whole internet: "Here's exactly what I'm running."

Attackers routinely scan millions of websites looking for servers running known vulnerable versions of software. When your headers announce your exact stack, you become a much easier target — automated exploit tools can match your version against public vulnerability databases (CVEs) and launch targeted attacks in seconds, without any human involvement. Suppressing these headers is a recognised security hardening step that reduces your "attack surface" and is increasingly expected by security audits, PCI-DSS assessments, and enterprise buyers reviewing your store. It also prevents competitors or scrapers from trivially identifying and copying your technology stack. Fixing it is usually a quick-win configuration change that has zero impact on site speed or user experience.

See the complete Server version guide for every platform and the full background.

Not sure if your BigCommerce store has this?

Run a free SEOLZ scan — we’ll find server version and every other issue across your whole site.

Scan my site free

Fix server version on another platform