Drupal Detector
Paste any URL and instantly see whether the site is built with Drupal — with the matched evidence.
We do not store the URL you audit. Want the full audit (performance / images / SEO / accessibility + real-browser speed test)? → run the full audit
Why check this
Confirm the platform first: CMS decides what can be changed and whether it is worth it.
What this is
Drupal is a modular enterprise PHP CMS. Governments, universities and large content sites use it for complex permissions and multilingual trees. Confirmation tells you whether to attack aggregated CSS/JS, the cache layer, or a single contrib module that stalls first paint.
How to tell from a public page
- [Drupal] Paths expose the `sites/default/files` public files directory.
- [Drupal] HTML includes `drupal-settings-json` or settings data islands.
- [Drupal] Scripts reference `/core/misc/drupal` core assets.
- [Drupal] Generator or meta markings leave version traces.
How to read the result
Confirm only when structural paths or settings JSON reproduce; soft mentions remain only suspected. Absence can mean aggregation plus a CDN rewrote core paths. Migration write-ups that name several CMS products add confusion. After a hit, disable unused modules and revisit aggregation before redesigning the theme.
What to do next
Turn off idle modules, enable aggregation and page cache, and audit image style derivatives. Peer CMS checks often include WordPress — open WordPress detector. Holistic scoring sits on run the full performance / images / SEO / accessibility audit on the home page. Keep Drupal path evidence for whoever owns modules and theme.
Drupal template detector angle
People searching for a Drupal template detector usually want the active theme name, not just the CMS brand. On a confirmed hit, inspect aggregated CSS/JS path segments, theme registry hints in settings JSON, and `/themes/custom/<name>/` asset folders. Those paths distinguish a stock theme family from a fully custom theme package more reliably than marketing copy.
Related detectors
FAQ
How is Drupal detected?
From structural signatures in the public HTML and response headers (domains, paths, attributes, scripts). Every verdict lists how many times each pattern matched — nothing is guessed.
Can the result be wrong?
If only a bare brand keyword matches without structural evidence, we label it \u201clikely\u201d instead of \u201cconfirmed\u201d — we would rather under-report than cry wolf.
Do you save the URLs I check?
No. The audit runs inside the request and the URL you paste is not written to storage. There are no third-party tracking scripts on the page either, so no log of who checked what exists. Copy the result yourself if you want a record.
Can a website hide what it is built with?
Partly, but rarely completely. The HTML sent to your browser, the response headers, script paths and asset structure have to be exposed to work, so there is always something readable. Server-side code, build config and private APIs stay invisible. That is why this tool reports the evidence it found rather than claiming a full picture. No match does not mean the technology is absent.
Optimization help is available
Tell me your URL and what you want fixed — you get a clear scope, price and timeline.
To：[email protected] | Cc：[email protected]
