CMS, framework, server, analytics
The detector loads the page as a browser would and looks for the signatures left by the technologies it uses: the server’s HTTP headers, the “generator” tag, typical file paths, analytics scripts. It recognises WordPress, WooCommerce, Shopify, PrestaShop, Joomla, Drupal, Wix, Laravel, Next.js, React, Vue.js, Bootstrap, Google Analytics, Google Tag Manager, the Meta pixel, Cloudflare, Nginx, Apache and LiteSpeed, among others.
What it is useful for
- Planning a redesign: knowing which CMS your current site runs on helps estimate the migration.
- Looking at competitors: which e-commerce platform, analytics and advertising tools do the sites in your sector use?
- Checking a supplier: does the delivered site use the technology stated in the quote?
- Checking your tags: are Google Analytics, Google Ads or the Meta pixel actually installed?
Limits of detection
The detector reads the HTML sent by the server without running JavaScript: tools loaded later (for example through Google Tag Manager) may not show up. Many sites also hide their signatures for security reasons, and a custom-built site often has no known signature at all. The crawler respects the robots.txt file of the sites it checks. For a fuller review of a page, try the SEO analyzer and the website speed test.
Are you an agency? We work white-label →
Frequently asked questions
Is the detection 100% reliable?
No. It relies on signatures visible in the code and headers. A site can hide them, and tools loaded later by JavaScript may not show up.
Why does my site show no technology?
It may be custom-built, or its signatures are hidden. That is common and not a problem.
Does the tool respect the sites it checks?
Yes. It loads a single page like a visitor, identifies itself as ITLabsProBot and respects robots.txt.