Detect WebsiteBuilder

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

• Meta tags
• JavaScript globals

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

• generator: \bWebsite Builder
• _site.urls.dataproxy: .mywebsitebuilder.com

Establishes

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

Does not establish

A sitewide install of WebsiteBuilder, an active vendor contract, exclusive use, or that WebsiteBuilder 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 WebsiteBuilder signals.
2. 2. PluginView reads only public responses (meta tags, javascript globals) and scores them against the WebsiteBuilder signature set (2 rules).
3. 3. Review the confidence score and text explanation for WebsiteBuilder on the results page.

Can PluginView detect WebsiteBuilder without logging in?

Yes. PluginView only reads publicly accessible responses when checking for WebsiteBuilder — typically meta tags, javascript globals. It does not bypass authentication or paywalls.

What category is WebsiteBuilder?

WebsiteBuilder is classified under Page builders in the PluginView directory.

How many fingerprint rules cover WebsiteBuilder?

This reference currently tracks 2 fingerprint rules across meta tags, javascript globals. Individual rule bodies are proprietary and are not published.

What public signals suggest a site uses WebsiteBuilder?

Illustrative public indicators for WebsiteBuilder include generator: \bWebsite Builder; _site.urls.dataproxy: .mywebsitebuilder.com. A live scan may match additional proprietary rules beyond these examples.