Detect Bricks

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

• Script sources

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

• wp-content/themes/bricks/assets/

Establishes

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

Does not establish

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

Can PluginView detect Bricks without logging in?

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

What category is Bricks?

Bricks is classified under Page builders, WordPress themes in the PluginView directory.

How many fingerprint rules cover Bricks?

This reference currently tracks 1 fingerprint rule across script sources. Individual rule bodies are proprietary and are not published.

What public signals suggest a site uses Bricks?

Illustrative public indicators for Bricks include wp-content/themes/bricks/assets/. A live scan may match additional proprietary rules beyond these examples.