Website Technology Checker

What does a website technology checker actually look at?

A website technology checker reads the traces a site leaves in its source code and server headers. By technology I mean three layers. First comes the CMS or store platform. Next come the server and CDN that deliver the page, and then the tracking tags. Each layer leaves its own fingerprints.

• Generator tag: WordPress, Joomla, TYPO3 and Wix write their name, and often their version, into this tag.
• HTTP headers: cf-ray points to Cloudflare, powered-by: Shopify to a Shopify store.
• File paths: addresses such as /wp-content/, cdn.shopify.com or /_next/static/ hint at the platform.
• Cookie names: laravel_session points to Laravel, PHPSESSID to PHP.

Not every trace carries the same weight. For example, a header or generator tag is hard evidence, while a bare file path is only a likely hint. According to W3Techs data from September 2026, 40.2% of all websites run WordPress. Also, 31.5% use none of the content management systems they track. In other words, it is normal for one site in three to show no known CMS.

Why check what a website is built with?

Before I write a proposal or take over a site, the platform is the first thing I look at. The same task can mean a very different timeline and budget on a different system. These are the situations where I use the tool most.

• Competitor research: a rival's store platform, ad tags and cookie tool are a natural first step in SEO competitor analysis.
• Handover and redesign: when you switch agencies, you cannot plan a migration without knowing the old system.
• Pre launch ad check: before a campaign starts, confirm that GA4 and the Google Ads tag really sit in the page.
• Comparing proposals: check whether the recommended system also powers successful sites in your industry. I cover this in how to evaluate a web design proposal.

That said, the platform alone says little about quality. A fast, carefully built WordPress site easily beats a sloppy setup on a hosted platform. So treat the result as a starting point for web design decisions. Then weigh speed, maintenance cost and your team's habits as well.

Which CMS and e-commerce platforms can it recognize?

Specifically, the signature list covers 80 technologies across seven groups. While building it, I checked live sites for each platform and kept only the traces that held up.

• Hosted platforms: Shopify sends a powered-by header and _shopify cookies, and Wix sends x-wix-request-id. Squarespace names itself in the Server header, while Webflow marks pages with a data-wf-page attribute.
• Open source systems: WordPress, Joomla, Drupal and TYPO3 mostly reveal themselves through the generator tag or typical folders.
• Store software: WooCommerce, Magento or Adobe Commerce, Shopware, PrestaShop and OpenCart leave plugin folders, init scripts or session cookies.
• Frameworks: Next.js, Nuxt, Gatsby, Astro, SvelteKit and Angular leave data blocks or build folders behind.

For hosted platforms the tool shows a single name; for WooCommerce running on WordPress it shows both together. Moreover, your platform choice shapes everything from integrations to payments. If you want a second opinion on that decision, have a look at my e-commerce consulting page.

What do the tracking health lines tell you?

Tracking health shows the parts that matter for ad measurement at a glance. The colors carry a priority: red means urgent, amber means worth fixing, green means fine and blue is for information.

• GA4: green when a measurement ID sits in the page. If there is no ID but GTM exists, the tool notes that GA4 may load inside the container.
• Google Ads tag: without an ID that starts with AW-, conversions may go unmeasured.
• Universal Analytics: red if UA code is still in the page. According to Google's announcement, standard UA properties stopped processing data on July 1, 2023.
• Consent Mode and cookie banner: amber when the consent signal or the cookie tool is missing.
• Meta Pixel: only an info note if absent, since not every business runs Meta ads.

In campaign work, the most common problem I see is a tag that exists while the conversion action never fires. So a green line does not mean measurement is complete. If you want the setup checked end to end, that is the first week of my Google Ads management work. For choosing analytics tools, my guide to website traffic analysis tools is a good place to start.

Why check Consent Mode and the cookie banner together?

A consent management platform (CMP) collects the visitor's choice, and Consent Mode passes that choice on to Google tags. One without the other stays half done. In its Consent Mode guide, Google states that the default command must run before any config or event command. Out of order, the defaults do not work.

For traffic from the European Economic Area, Google also asks advertisers to collect consent and share consent signals with it. Otherwise measurement, ad personalization and remarketing features stop working for those users.

That is why the tool looks at two things at once. Does a CMP sit in the page, and does a gtag('consent', 'default') command exist? Without the default command, the tool checks for a CMP or GTM and notes that the setting may come from there. For the legal side, my article on building a GDPR compliant website goes deeper. Always check current rules and your legal adviser's view for anything critical.

How accurate is a website technology checker?

A website technology checker that reads raw HTML is fast and safe, but it has blind spots. My tool reads the first HTML response and does not run JavaScript. As a result, a few things slip past it.

• Tags inside GTM: when GA4, Google Ads or a pixel loads later from the container, only the GTM ID shows up.
• Server side tagging: setups that send data from your own subdomain may leave no trace in the page.
• Bot protection: some firewalls answer our tool with a status such as 403. In that case, the tool warns about gaps.
• Hidden headers: servers that switch off Server or X-Powered-By do not reveal themselves.

For a final answer, open the page in your browser and watch the tags live with Google Tag Assistant. To see where a domain is hosted, combine the DNS lookup and IP lookup tools. That way you get one step closer to the real host behind a CDN.

How do you use the results for SEO and ad decisions?

The detection result is a starting point; the real value shows in the decisions you make with it. In my own projects I use platform data in three places.

1. Site migration: if the platform changes, I plan in advance how old URLs map to new ones. After the move, I test the rules with the redirect checker.
2. Speed work: a heavy page builder, old jQuery copies or fonts from Google servers can slow a page down. I explain the ranking side in how site speed affects SEO.
3. Campaign measurement: with the tags in place, I mark campaign links with the UTM builder. Then I split reports by source.

In short, platform data brings technical SEO and ad measurement to the same table. For a second pair of eyes on your technical base, reach me through my SEO consulting page.