Detect Weglot

PluginView evaluates public page signals in these classes when identifying Weglot. Individual fingerprint rule bodies are proprietary and are not published.

• Response headers
• Script sources

Illustrative indicators derived from public catalog metadata for Weglot. A live scan may match additional proprietary rules beyond these examples.

• weglot-translated
• cdn.weglot.com
• wp-content/plugins/weglot

Establishes

One or more public signals on the scanned page matched a known Weglot signature (3 rules) at the time of the scan.

Does not establish

A sitewide install of Weglot, an active vendor contract, exclusive use, or that Weglot is still in place today.

1. 1. Enter the website URL in the scan form — homepage, pricing, checkout, or login pages usually expose the strongest Weglot signals.
2. 2. PluginView reads only public responses (response headers, script sources) and scores them against the Weglot signature set (3 rules).
3. 3. Review the confidence score and text explanation for Weglot on the results page.

Can PluginView detect Weglot without logging in?

Yes. PluginView only reads publicly accessible responses when checking for Weglot — typically response headers, script sources. It does not bypass authentication or paywalls.

What category is Weglot?

Weglot is classified under Translation in the PluginView directory.

How many fingerprint rules cover Weglot?

This reference currently tracks 3 fingerprint rules across response headers, script sources. Individual rule bodies are proprietary and are not published.

What public signals suggest a site uses Weglot?

Illustrative public indicators for Weglot include weglot-translated; cdn.weglot.com; wp-content/plugins/weglot. A live scan may match additional proprietary rules beyond these examples.