About Detecting a Website Platform
How can you tell what a site is built with?
Every platform leaves fingerprints. A generator meta tag, a predictable folder name in an asset URL, a cookie only one system sets, a header a particular host always adds - none of it is announced deliberately, and all of it is there to be read.
A CMS detector reads those signals and matches them against a library of known platforms. It is pattern matching rather than anything clever, which is why it is quick and also why it is occasionally wrong.
The most useful thing about it is that it works on sites you have nothing to do with. Wondering what a competitor is running, or what a prospective client will expect you to work in, takes a few seconds rather than a conversation.
CMS, ecommerce platform or site builder?
These get lumped together, and for practical purposes they behave differently:
- A CMS manages content - WordPress, Drupal, Ghost, Craft.
- An ecommerce platform manages products and checkout - Shopify, Magento, BigCommerce.
- A site builder produces the pages visually - Wix, Squarespace, Webflow.
- A static site generator builds pages ahead of time and serves plain files.
This tool reports which of those each detected platform is, rather than filing everything under "CMS". A shop running Shopify has no CMS in the strict sense, and saying so is more useful than pretending otherwise.
Why the platform matters for SEO
It sets the constraints you are working inside. What you can change about URLs, how titles and meta descriptions are managed, whether structured data comes for free or needs building, how much control you have over page speed - all of that is decided by the platform long before anyone writes a word.
It also predicts the problems. Certain platforms reliably produce certain issues, so knowing what you are looking at tells you where to look first, and which fixes are realistically available.
For agency work it is a scoping question as much as a technical one. A quote for a site you can edit freely is a different quote from one where every change needs a developer.
When detection comes up empty
A blank result is not a failure of the site. Plenty of well-built sites are bespoke, run something uncommon, or are static files with nothing to fingerprint at all.
Some platforms are also deliberately quiet. Removing the generator tag and renaming asset paths is standard hardening advice, and a proxy or CDN in front of the site can strip the headers a detector would otherwise read.
And detection can be misled in the other direction. A site migrated between platforms often keeps traces of the old one in its markup for years, so an unexpected result is worth a second look rather than immediate belief.
What this tool checks
Enter a URL and the tool loads the page and matches what it finds against a library of known platforms, reporting each one it recognises along with the category it belongs to and, where the platform reveals it, the version.
It looks at the platform specifically. A page usually carries far more technology than that - analytics, fonts, frameworks, hosting - and the full picture is a separate check.
Where to go next
The platform is the starting point rather than the answer. See everything else the page loads with the
technology check, look at how the page presents itself with the
Googlebot simulator, and check whether the platform is costing you anything with the
Indicateurs Web Essentiels test.