Version number on a website: how to find it, show it and manage it
The version number on a website can mean two different things. Visitors and testers often want to find the version of the software a site runs on, such as its content management system or framework. Site owners want to know which release of their own site is live, show it to the right people and keep a record of what changed. This guide covers both: where version numbers appear, whether to hide them, which versioning scheme to use, how to keep a changelog, and how versioned file names keep a site fast.
The short version
- Software versions show up in generator meta tags, response headers, file addresses and footers, but can be removed or faked.
- Removing a public version string is a reasonable small step; updating the software is what actually protects the site.
- Give your own site a release identifier the team can see, and a changelog that people can read.
- Semantic versioning suits things others depend on; calendar versioning suits regularly released websites.
- Version the file names of stylesheets and scripts, then let browsers cache them for a long time.
The kinds of version on a website
| Version of | Example | Who needs it |
|---|---|---|
| The site's software | CMS, framework or plugin version | Maintainers, testers |
| The site release | 2026.11.11 or a build number | The site team, support |
| Styles, scripts, images | app.3f9a1c.css, or ?ver= on the address | Browsers and caches |
| An interface (API) | /v2/orders | Connected systems |
| A page's content | "Last updated 11 November 2026" | Readers and search engines |
How to find the version number of a website
There is no single place, but most sites give away some signals. Check them in this order:
- Page source. Open the source of the page and look for a meta tag named generator in the head. Many content management systems add one. In WordPress it comes from the wp_generator() function, which outputs the generator tag on the wp_head hook (WordPress code reference, read 11 November 2026).
- Response headers. In the browser's network tools, look at the headers of the page. Fields such as X-Powered-By or X-Generator often name the framework or language version.
- File addresses. Stylesheet and script addresses often carry a version, for example a ?ver= parameter, which can reveal the version of the system or of a plugin.
- Visible text. Footers, about pages, admin login pages and release notes sometimes state the version directly.
- Detection tools. Browser extensions and online services that identify technologies combine the same signals automatically.
Treat the result as a hint, not a fact. The OWASP Web Security Testing Guide shows how easily these signals are disabled or changed: one of its examples is a server that answers with the header "X-Powered-By: Blood, sweat and tears" (OWASP WSTG, Fingerprint Web Application Framework, read 11 November 2026).
Should you hide your site's version?
Automated scanners look for version strings and match them against lists of known vulnerabilities, so a site that announces an old version is an easy target. Removing the generator tag, version headers and version parameters on public pages takes little effort, and we do it on the sites we run. It should not be mistaken for security. The same OWASP guide calls such efforts security through obscurity that only slows the most rudimentary adversaries, and recommends keeping frameworks, libraries and components up to date, replacing those that no longer receive security fixes, and keeping an inventory of components and their versions, for example a software bill of materials, so affected parts are found quickly when a new vulnerability is published.
In practice: hide the version from the public, record it carefully for yourselves, and update. A site whose version is hidden but years out of date is still vulnerable; a site that is current is safe whether or not the version shows.
Showing a version number on your own site
The people who need your site's version are your team, your support staff and whoever fixes the next problem. Useful places for it:
- A status endpoint, such as /version or /health, that returns the release identifier, build time and commit, readable by monitoring tools.
- An admin view or a small line visible only to signed-in staff.
- The build output and deployment log, so every release is tied to the code that produced it.
- A visible footer line only where users benefit, for example in a web app whose users report problems to support and need to say which version they see.
The identifier should be generated at build time from the version control system, not typed by hand, so it always matches the code that is live.
Choosing a versioning scheme
Semantic Versioning 2.0.0 uses MAJOR.MINOR.PATCH: increase MAJOR for incompatible changes to an interface, MINOR for backward compatible new functionality, and PATCH for backward compatible bug fixes. It is the right choice when other software depends on yours, such as an API, a library or a WordPress plugin. Calendar Versioning uses the release date instead, for example 26.04 for YY.0M as Ubuntu does, 2026.2 for YYYY.MINOR as JetBrains does, or 2026.08.19 for YYYY.0M.0D as yt-dlp does (both read 11 November 2026). For a company website or a web app released continuously, a date-based version plus the commit is usually clearer than a semantic number nobody depends on.
| Scheme | Example | Fits |
|---|---|---|
| Semantic versioning | 2.4.1 | APIs, libraries, plugins, apps with compatibility promises |
| Calendar versioning | 2026.11.11 | Websites and services released on a regular rhythm |
| Build or commit identifier | build 1482, commit 3f9a1c2 | Internal tracing, alongside either scheme |
Keeping a changelog
A version number says that something changed; a changelog says what. The Keep a Changelog convention (version 1.1.0, read 11 November 2026) describes a changelog as a curated, chronologically ordered list of notable changes for each version, written for humans, with the latest version first and the release date shown. It groups changes into Added, Changed, Deprecated, Removed, Fixed and Security, keeps an Unreleased section at the top for upcoming changes, and warns against using raw commit logs, which are full of noise. For a website, the changelog can be internal; for an API or a web app with customers, a public one builds trust.
Versioned files and caching
Version numbers matter most to browsers. Stylesheets, scripts, fonts and images are downloaded once and kept in the browser cache. If a file keeps its name when it changes, visitors may see the old version; if the cache time is short, every visit downloads it again. The solution is to put a version or a content hash in the file name, such as app.3f9a1c.css, so a changed file gets a new address, and to serve those files with a long cache time. The Cache-Control header's immutable directive tells the browser that the response will not be updated while it is fresh, as in Cache-Control: public, max-age=604800, immutable (MDN, Cache-Control, read 11 November 2026). Hashes in file names are more reliable than a ?ver= query string, because some caches treat query strings differently, and they leak no software version.
Versions of content pages
For articles and guides, the version that matters to readers is the date. Show when a page was published and when it was last updated, and keep the same dates in the page's structured data. Change the updated date only when the content changed in substance; readers and search engines both notice dates that move without new content.
How we help
On the sites we build and run, version strings are removed from public pages, every release has a build identifier and an entry in the changelog, assets are versioned and cached, and software is kept current. See website development, WordPress maintenance for updates and monitoring, website redesign, and our security audit for a check of what your site reveals and what it runs.
Questions people ask
How do I find the version number of a website?
Look in the page source for a generator meta tag, which many content management systems add, check the response headers for fields such as X-Powered-By, look at the version strings on stylesheet and script addresses, and check the footer or an about page. Browser extensions that detect technologies read the same signals. None of these is guaranteed, because site owners can remove or change them.
Is it a security risk to show the version number?
A public version string makes it easier for automated scanners to match a site to known vulnerabilities, so removing it is a sensible small step. It is not protection in itself: OWASP's testing guide describes hiding versions as security through obscurity that only slows the most basic attackers. Keeping the software updated is what protects the site.
Should a company website have a version number?
Visitors rarely need one, but the team running the site does. A version or build identifier that is visible to the team, in an admin view, a status endpoint or a small line for logged-in users, makes it quick to see which release is live when something goes wrong.
What is the difference between semantic versioning and calendar versioning?
Semantic versioning uses MAJOR.MINOR.PATCH and changes the first number when something incompatible changes, which suits software that others depend on, such as an API or a plugin. Calendar versioning uses the release date, such as 26.04 or 2026.11.11, which suits websites and apps released on a regular rhythm where compatibility promises matter less.
Why do file names on websites contain numbers or random strings?
They are versioned assets. Adding a version or a content hash to the file name of a stylesheet or script lets browsers keep the file in their cache for a long time, because a changed file gets a new name and is downloaded fresh. It makes sites faster without visitors seeing outdated files.
Sources
- WordPress code reference: wp_generator() (read 11 November 2026)
- OWASP Web Security Testing Guide: Fingerprint Web Application Framework (read 11 November 2026)
- Semantic Versioning 2.0.0 (read 11 November 2026)
- Calendar Versioning (read 11 November 2026)
- Keep a Changelog 1.1.0 (read 11 November 2026)
- MDN Web Docs: Cache-Control (read 11 November 2026)