What is a CMS and why is it important to determine a website's engine?
The service searches for available technical characteristics of the engine: HTML code features, file paths, system directories, and other signatures. If the website's CMS cannot be identified online, this does not necessarily mean the site is running without a CMS. The engine may be custom-written, heavily modified, or intentionally obscure standard features.
A CMS, or Content Management System, is a website content and page management system. Editors use it to add products, articles, images, and other materials, while developers manage templates, modules, and some technical settings. Colloquially, a CMS is often referred to as a website engine or platform.
Information about the engine is useful for SEO audits, redesigns, project migrations, and evaluating future improvements. A CMS can help you understand the administration features in advance, find a specialist with the necessary experience, and check the compatibility of individual integrations.
What can you find out with CMS Detector?
CMS Detector's main task is to identify the CMS running on the resource being inspected. For popular platforms, a website typically exhibits characteristic technical characteristics, which the service uses to match the page to a known system.
Depending on the detector's capabilities, the scan result may also contain information about web technologies, frameworks, analytics systems, CDNs, or e-commerce components. This data is useful as additional information, but the primary scan result is the installed CMS or a message indicating that the system is not recognized.
When is it useful to know a website's CMS?
Verification is necessary when working on a project without access to the administrative panel or technical documentation. For example, an SEO specialist might find out a competitor's website's CMS before analyzing its technical capabilities, while a developer might evaluate a future migration or integration.
Another typical scenario is an old website about which the owner has almost no technical information. Determining the website's engine is useful before searching for a contractor, redesigning, updating the online store, or preparing a technical audit.
How to determine a website's CMS manually?
Manual verification is useful if the CMS checker fails or if you need to confirm the identified platform. A browser and a few open technical files are usually sufficient for a basic analysis.
It's best to start with the source code, then check robots.txt and the paths of connected resources. If the indicators match, the likelihood of a correct detection is significantly higher than relying on a single URL or the site's appearance.
How to find out the CMS from the page source code?
Open the page and select View Source or use the keyboard shortcut Ctrl+U if your browser supports it. Then, find the generator, platform names, and specific system paths.
It's useful to check references to CSS, JavaScript, images, and plugins. Even when the CMS name isn't explicitly stated, the structure of the linked resources often reveals the site's origin.
How to check CMS via robots.txt?
Open /robots.txt in the domain root and see which directories are closed or referenced in rules. The default configurations of individual CMSs may contain specific system directories.
This method can't be used in isolation. Robots.txt is edited manually and may retain old rules after migrating the site to a different engine.
How to identify an engine by file URLs?
Open the source code or developer tools and examine the URLs of CSS, JavaScript, images, and other resources. System directory names sometimes directly point to WordPress, Drupal, or another platform.
When using a CDN, source paths may be rewritten and files may be collected into shared bundles. In this case, this method provides less information, and it's better to switch to other signatures.
Is it possible to determine the CMS by the admin panel address?
Popular CMSs have standard administrative section URLs. For example, WordPress often uses /wp-admin/, while Joomla often uses /administrator/.
The presence of a login page may confirm the assumption, but the absence of a standard address proves nothing. The developer can change the admin panel's route or restrict network access.
Is it possible to identify a CMS by HTTP headers?
Sometimes HTTP headers contain the name of a technology, platform, or server component. These can be checked using browser developer tools or specialized technical analysis services.
Many websites intentionally remove unnecessary headers, so the CMS often remains unknown after such a check. This method is best used in conjunction with HTML, resource, and robots.txt analysis.
Is it possible to identify a website's CMS by its footer?
The footer of older websites sometimes retains the developer's signature, platform name, or link to the official CMS website. Builders may retain the branding of the chosen service.
This method is the simplest, but its reliability is low. The signature can easily be removed or retained after the project is transferred, so the final conclusion should be confirmed with technical evidence.
When I need to quickly understand the underlying technology of a competitor's website or a new client project, I start with automatic CMS Detector. If the system isn't detected, I check the source code, CSS and JavaScript paths, robots.txt, and HTTP headers. In-house, headless, and highly customized projects, standard indicators are often hidden.
What CMS can be identified?
The exact list depends on the specific CMS Detector database. It best detects common platforms with consistent technical characteristics. These include WordPress, Joomla, Drupal, OpenCart, Magento, PrestaShop, and other popular solutions.
Detectors can also detect website builders and SaaS platforms, such as Shopify, Wix, or Tilda. An online store may use a separate e-commerce CMS or a module installed on top of a universal content management system.
WordPress
WordPress is often identified by the /wp-content/ and /wp-includes/ directories, standard files, and other platform signatures. Even after changing the theme, some of these signatures usually remain available in the page code.
WordPress-based online stores may also use WooCommerce. Therefore, when conducting a technical analysis, it's helpful to distinguish between the main CMS and the e-commerce module, which handles the catalog, shopping cart, and checkout.
Joomla
Joomla has its own system paths, administrative structure, and distinctive template elements. On projects with a standard configuration, these characteristics make it possible to quickly identify the engine.
If the website was developed individually a long time ago, some of the catalogs and external features may have changed. In this case, the automatic CMS checker should be supplemented with manual analysis.
Drupal
Drupal is used for content and corporate projects of varying complexity. It can be identified by the combination of resource structure, characteristic files, HTML attributes, and other data that remains accessible to the visitor.
New versions of Drupal and heavily modified projects may have different external characteristics. Therefore, identifying the system version is usually much more difficult than identifying the CMS family itself.
OpenCart
OpenCart is often found in online stores and has a distinctive structure of files, modules, and templates. If the standard features are not hidden, CMS Detector can automatically identify the platform.
When analyzing a store, it's worth considering possible customization. Developers change themes, URLs, and individual catalogs, so the lack of an OpenCart signature doesn't preclude the use of this system.
Magento
Magento is focused on e-commerce projects and typically has a set of characteristic technical features. This definition helps you understand the underlying platform of your store even before accessing the admin panel.
Large projects often use CDNs, proxies, custom themes, and complex server infrastructure. These components can complicate automatic CMS detection based on a single page.
Shopify, Wix, and Tilda
Shopify, Wix, and Tilda are cloud-based platforms and builders, where a significant portion of the technical infrastructure is managed by the service itself. They can also be identified by their characteristic resources and code structure.
For an SEO audit, this information helps immediately consider the limitations and capabilities of a specific platform. However, the mere fact of using a website builder says nothing about the quality of an individual website's optimization.
What we actually did
Dental clinic · Kyiv and Chernihiv
+44% clicks from search
A domain with no history on a website builder. We built the semantic core for both cities, reworked the landing pages and built the link profile from zero. Four months: 34.8k clicks, impressions 1.32 → 1.76M, DR 0 → 41.
E-commerce · international
+96% clicks in two months
A catalog of digital 3D models. We clustered the semantics, rebuilt the hub pages and closed duplicates and indexing errors. Google users 247 → 532, CTR 2.4% → 4%.
Medical center · Ukraine
+68.75% visibility in the first month
Narrow visibility and a small semantic core at the start. Semantics, landing page structure, metadata and internal linking, then gradual link building.
Answers to your questions
How to determine a website's CMS online?
Enter the domain or full URL into CMS Detector and run the analysis. The service will check the page's public technical characteristics and compare them with known CMS signatures.
If the CMS is recognized, its name will appear in the results. If there are no matches, you can further check the source code, robots.txt, system paths, and HTTP headers.
Is it possible to find out a website's CMS for free?
A free check is suitable for quickly identifying an engine without installing a program or extension. Typically, the user simply needs to enter the desired website address and run the analysis.
The terms of each specific service may vary in terms of the number of checks and additional features. Before mass-analyzing several hundred domains, it's best to check the available limits separately.
Why doesn't CMS Detector detect the website's engine?
The cause could be a custom CMS, hidden system paths, missing signatures, or website protection from automated requests. Sometimes, the platform being used simply isn't in the detector's database.
The site can also operate without a traditional CMS or use a headless architecture. Therefore, the "CMS not defined" message does not confirm the absence of a content management system.
Is it possible to identify the CMS of an online store?
Yes, if the platform leaves visible technical indicators. CMS detector can recognize common e-commerce solutions or the underlying management system on which the store module is installed.
For example, a project could use WooCommerce alongside WordPress, or run directly on OpenCart, Magento, Shopify, or PrestaShop.
Is it possible to determine the CMS version?
Sometimes the version is present in the meta generator, resource parameters, or open system files. In this case, it can be detected automatically or through manual analysis.
Many websites hide their version numbers from public data. Therefore, it's much less easy to determine the exact version than the CMS family itself.
How to find out your CMS without an online service?
Start with the page's HTML source code and search for "generator", then inspect the CSS and JavaScript paths. After that, check robots.txt, typical administrative URLs, and HTTP headers.
No single feature provides a complete guarantee. It's best to compare several independent matches before drawing conclusions about the engine.
Is it possible to determine a website's CMS by its domain?
Yes, a domain is usually sufficient for automatic verification. The service automatically opens an accessible page and analyzes the technical characteristics returned by the site.
If a domain redirects to another address, the result will depend on the final page after the redirect. For a more precise check, you can specify its full URL.
How is CMS Detector different from Wappalyzer?
CMS Detector primarily answers the question of which CMS is used on a website. Its purpose is to identify the engine based on available technical characteristics.
Wappalyzer belongs to a broader class of web technology analyzers. In addition to CMS, it can display frameworks, analytics, CDNs, server-side components, and other stack elements.
Related services
Indexability check
Check if your page is indexable by Google: robots.txt, noindex, canonical, HTTP status, and other technical indicators. Online URL indexability checker.
Google index check
Check if a URL or website page is indexed in Google. Methods include Search Console, site:, the bulk checker, and reasons why pages are not indexed.
HTTP Status Checker
HTTP Status Checker by Seo-Gen: check URL response codes, redirects, and 4xx/5xx errors online. Suitable for single-page and bulk URL checking.
Redirect Checker
Online Redirect Checker: Check 301 and 302 redirects, redirect chains, HTTP codes, and final URLs. Quickly check redirects without installation.
Broken Link Checker
Broken Link Checker by Seo-Gen: Find broken and inactive links, 404 errors, and problematic URLs on your website. Online verification of internal and external links.
Robots.txt Checker
Robots.txt Checker for online robots.txt file analysis and verification. Find Allow, Disallow, and User-agent errors, and check URL accessibility for Googlebot and other search robots.
Sitemap Checker
Sitemap Checker from Seo-Gen checks your XML sitemap online: structure errors, URLs, sitemap index, lastmod, limits, and accessibility. Find issues before submitting your sitemap to Google.
Robots Meta Checker
Meta robots Checker checks Meta Robots and X-Robots-Tag, detects noindex, nofollow, and directive conflicts. Paste the URL and check the page settings.
Canonical Checker
Canonical Checker Online: Check rel=canonical, target URL, HTTP status, and common page canonicalization errors. Quick canonical check for SEO.
Hreflang Checker
Hreflang Checker by Seo-Gen: Check hreflang, x-default, canonical, language and region codes, backlinks and URL errors online.
CMS Detector helps you quickly identify a website's CMS by domain or URL and obtain basic information about the platform without accessing the admin panel. For standard WordPress, Joomla, Drupal, OpenCart, Magento, and other common solutions, automatic verification is often sufficient.
If the engine isn't found, check the source code, system paths, robots.txt, and HTTP headers. Enter the website address in the check box and run "Detect CMS" to see what technical signs are detected.
We reply within one business day. No newsletters, no “just a reminder” calls.
He will look at the site himself instead of passing it to a manager.
More on: CMS Detector – determine the website's CMS
How to determine a website's CMS online?
The fastest way is to use an online detector. A domain or URL of any accessible page is usually sufficient for checking. The service automatically retrieves public technical data and compares the detected indicators with its database.
Online CMS testing is convenient for a one-time analysis, when installing a Chrome or Firefox extension isn't justified. The results should be viewed as a technical determination based on available signatures, as some projects hide or modify standard platform features.
How to use CMS Detector?
Using the service consists of a few simple steps. First, enter the address of the resource you want to check, then run the analysis and wait for the results. For most open websites, this is enough to identify the CMS or get information about whether the engine is not recognized.
If an automatic CMS check doesn't yield a response, you can proceed to manual analysis. Source code, robots.txt, service directories, and HTTP headers can often help confirm or refute assumptions about a specific platform.
Enter the domain or website URL
In the verification field, you can enter a domain like example.com or the full address https://example.com/ if the service accepts both formats. Before launching, make sure the site is accessible from the browser and doesn't return a persistent error.
To identify a CMS, the address of the admin panel or internal page is usually not required. The public URL is sufficient, as the primary signatures are usually found in the HTML code, connected resources, and technical responses of the site.
Run a CMS check
Once launched, the service accesses the page and searches for known signs of control systems. These may include characteristic directories, the generator name, system files, URL patterns, and other data accessible to the average visitor.
This CMS check doesn't access the restricted administrative section of the site and doesn't require a login or password. The analysis is based on public technical information transmitted by the browser and server when a page is opened.
View the check result
If the detected signatures match a known system, the CMS name will be displayed in the results. If additional data is available, the service can also display detected web technologies or platform components.
Sometimes it's impossible to determine a website's CMS. In this case, the result simply means there aren't enough indicators to confidently identify it. A custom system, modified file paths, or protection against automated requests can hide the engine even if the site is functioning correctly.
How does CMS Detector work?
CMS Detector compares available page data with a set of characteristic features of known systems. This approach is called signature detection. WordPress, Joomla, Drupal, OpenCart, and other platforms often have their own names for directories, files, tags, and service URLs.
A single indicator rarely provides absolute certainty, so a good detector considers multiple data sources. The more characteristic matches found, the more reliable the result. A heavily modified website may not contain the usual CMS traces.
What CMS features does the service analyze?
Automatic analysis checks for features accessible without authorization. These primarily include the page's HTML code and links to included CSS or JavaScript files. Additional clues are provided by robots.txt, URL structure, and technical server responses.
Some platforms can be identified by several independent features. If the developer has removed the default meta generator, the engine may still be visible in resource paths or utility directories.
Meta generator and HTML code
Some CMSs add a tag to the <head> section, which can include the platform name. This is one of the most obvious ways to identify a CMS, but it shouldn't be relied upon alone.
The tag is often removed from the template or disabled by settings. However, other signatures may remain in the source code: comments, class names, included files, and system resource addresses.
Paths to CSS, JavaScript, and system files
Resource paths often reveal the platform being used. WordPress, for example, often has /wp-content/ and /wp-includes/ directories. Other CMSs have their own standard directories and file placement schemes.
With extensive customization, the developer may change some of the standard paths or serve resources via a CDN. Therefore, any identified fragment should be checked alongside other indicators.
URL structure
Some systems preserve characteristic parameters or page URL structures. On older and default-configured projects, this can quickly reveal which engine is being used.
Modern CMSs support human-readable URLs, and developers often define their own route structure. Because of this, a page's URL is now considered an additional feature rather than a reliable way to identify a site's CMS.
HTTP headers and technical server responses
HTTP headers sometimes contain information about technologies, server software, or platform components. This data can be obtained through developer tools, console utilities, or specialized analyzers.
Server headers are often cleared for security reasons. If they don't contain the engine name, this doesn't mean there's no CMS present and doesn't preclude verification using other methods.
robots.txt and service files
The robots.txt file is located at example.com/robots.txt and controls search engine bot access to specific sections. The standard rules for some CMSs include specific system directories.
Robots.txt content is easy to modify manually, so a match is used as an additional signal. For a reliable result, it's best to compare it with the source code and included file paths.
Why couldn't the site's CMS be detected?
Negative results occur even on functioning websites with a fully functional administrative system. The main reason is that CMS Detector only sees public technical indicators and does not access the project's internal settings.
If the service fails to identify the CMS, it's worth manually checking the site and comparing multiple data sources. Failure to find a result should not be interpreted as confirmation that the site was developed entirely without a CMS.
The site uses a custom CMS
A company's internal CMS may have no known signatures or public documentation. The detector simply has nothing to compare the detected structure to, so such a site often remains undetected.
A custom-built platform can utilize standard frameworks, databases, and JavaScript libraries. Analyzing the technologies will provide additional information, but automatically identifying the name of the internal CMS is usually impossible.
The site works without a CMS
Some projects consist of static HTML pages or are generated using tools that aren't traditional content management systems. In these cases, a traditional CMS may indeed be unnecessary.
There are also static site generators and headless architectures, where the interface and content management system are separated. For a typical CMS detector, such projects are more complex than classic WordPress or Joomla sites.
CMS signs are hidden
Developers can remove the meta generator, change system paths, rename directories, and configure resource delivery via a CDN. These changes reduce the number of obvious signatures.
Hiding individual features doesn't automatically make a CMS invisible. Other structural elements often remain accessible, so manually checking multiple sources sometimes yields the answer.
CMS is missing from the detector database
New, rare, regional, and internal systems may be missing from the service's signature database. In this case, even clearly visible technical features will not be associated with the name of a specific engine.
The CMS detector database should be updated as new platforms and versions become available. For an unknown system, it's more useful to consult the tech stack and documentation of the project itself.
The site is blocking automatic verification.
WAFs, bot protection, server restrictions, or CDNs can block automated analyzer requests. Sometimes, a site returns a different page to the detector, requires JavaScript, or requests additional verification.
The problem also occurs due to DNS errors, redirect loops, or temporary server unavailability. Before re-analyzing, it's worth opening the URL in a regular browser and verifying that the page actually loads.
Is it possible to determine the CMS version of a website?
The CMS version can sometimes be found in the meta generator, system files, parameters of connected resources, or other public data. On standardly configured older websites, this information is quite common.
Modern projects typically don't disclose the exact version unless necessary. Therefore, the check CMS version function doesn't produce results for every resource, even if the underlying platform is reliably identified.
From a security perspective, the lack of a version number in open source code is perfectly normal. For maintaining your own project, it's safer to check the version in the admin panel, package manager, or technical documentation.
How to determine the CMS of an online store?
You can test an online store's CMS using the same methods as a regular website. The difference is that stores often use an additional e-commerce module on top of a standard CMS.
For example, one store might run on WordPress with WooCommerce, while another project might run on OpenCart, Magento, Shopify, or PrestaShop. Therefore, the technical analysis result sometimes includes both the core platform and the e-commerce component.
What are the most common e-commerce platforms?
Well-known solutions include WooCommerce, OpenCart, Magento, Shopify, and PrestaShop. Each platform has its own structure of resources, templates, and utility components, which CMS Detector can recognize.
The platform name alone can't determine the quality of a particular online store. SEO, speed, and usability depend significantly more on the settings, theme, modules, server, and developer work than on the CMS name alone.
CMS Detector or Browser Extension – Which Should You Choose?
Online verification is convenient for one-off tasks, such as quickly identifying a website's CMS based on its domain. Users open the service, enter the URL, and receive results without installing any additional software.
A browser extension is more useful for specialists who regularly analyze websites during their work. It can display technologies directly while viewing a page, but requires installation and browser access.
When is an online CMS checker more convenient?
The online CMS checker is suitable for quickly checking one or more websites, especially on someone else's computer or device without configured extensions. The URL itself is usually sufficient to launch.
This format is convenient for website owners, marketers, and agency clients who don't require constant technical analysis. The results can be obtained directly on the service page.
When is a Chrome or Firefox extension useful?
Chrome CMS detector or a similar extension is useful for regular competitive analysis. A specialist opens a website and immediately sees detected platforms and related technologies, without having to copy each URL into a separate service.
Wappalyzer, which analyzes a broad tech stack, falls into this category. The choice between an extension and an online service depends primarily on the frequency of checks.
How accurately can you determine a website's CMS?
Accuracy depends on the number of open signatures, the relevance of the detection database, and the degree of project customization. Popular CMSs with a standard structure are usually easier to detect than custom or headless solutions.
The results are also affected by CDNs, WAFs, proxies, path changes, and resource pooling. Therefore, it's technically more accurate to talk about the detected characteristics of a specific platform rather than an absolute guarantee.
What to do after determining the CMS?
The CMS name helps you choose the next steps when working on your website. Before a technical audit, you can check the platform's specific limitations, available SEO settings, and how to implement any necessary changes.
When migrating or redesigning, engine information helps assess the compatibility of data, modules, and integrations. When working on someone else's project, it's also easier to find a developer who is already familiar with the specific system.
After selecting a CMS, it's worth checking the website's technical condition separately. The platform's name alone doesn't provide any information about canonical, hreflang, indexing, speed, microdata, redirects, or the quality of internal linking.