Home / Knowledge Base / Tools and integrations / How to Find Out What CMS a Site is Built On

How to Find Out What CMS a Site is Built On

Tools and integrations 2 min read Updated 12.09.2026
How to identify the engine, why the result is probabilistic, why this is important for competitor analysis and evaluating someone else's project — and why CMS does not affect rankings.

Identifying the CMS answers the question "what is the site built on". This rarely concerns your own site, but is constantly relevant when analyzing competitors, evaluating someone else's project before purchase, or preparing for an audit. You can check it using the CMS detector.

How It Is Determined

The tool looks for characteristic traces: paths to themes and plugins, meta-generator, cookies, server headers, typical admin panel addresses, and files of specific engines. Therefore, the result is a probability, not a passport: a well-configured site hides traces, while constructors are immediately visible.

Why This Matters in Practice

  • Assess labor costs. Edits on a constructor and a custom engine cost differently.
  • Understand limitations. Some constructors do not allow changing meta-tags and robots.txt — this is important to know before starting work.
  • Check security. A well-known CMS with an outdated version is a common cause of hacks, see Shield.
  • Understand someone else's project before purchase or handover for work.
Knowing the CMS Says Nothing About Rankings
The search engine does not rank by engine. Speed, markup, structure, and content matter — things that can be done well or poorly on any platform.

What the Engine Often Reveals

FeatureWhat It Indicates
Paths like /wp-content/, /bitrix/, /local/Classic CMS with predictable structure
Meta-generator in the page codeEngine and sometimes its version — it's better to hide the version
Server cookies and headersPlatform and caching settings
Static domains of the constructorThe site is built on a constructor, edits are limited by its capabilities

Should the Engine Be Hidden?

Knowing the CMS itself does not harm anyone, but the engine version in plain sight is a hint for automatic vulnerability scanners. Removing the meta-generator and version from response headers takes a minute and reduces one reason for hacking.

What to Check Next

  1. robots.txt — is the site closed by the standard template of the engine?
  2. Meta-tags — template headers on all pages indicate an unconfigured CMS.
  3. Speed — heavy themes and unnecessary plugins are immediately visible.
  4. Response headers — the engine version in headers helps not you, but those looking for vulnerabilities.

FAQ

Does CMS affect rankings?
No. The search engine does not rank by engine: speed, structure, markup, and content matter, which can be done well on any platform.
Why does the detector sometimes make mistakes?
It relies on traces — paths, headers, cookies. A well-configured site hides them, so the result is probabilistic.
Why know the competitor's engine at all?
To assess its limitations and labor costs: some constructors do not allow changing meta-tags and robots.txt.
Was this article helpful?
Try it on your project Everything described in the article is available in the dashboard — the registration bonus is already in your balance.
Open dashboard