Detect Super Builder

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

• DOM selectors

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

• link, link, img

Establishes

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

Does not establish

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

A confirmed Super Builder match also implies these technologies are present.

NotionNext.js

Can PluginView detect Super Builder without logging in?

Yes. PluginView only reads publicly accessible responses when checking for Super Builder — typically dom selectors. It does not bypass authentication or paywalls.

What category is Super Builder?

Super Builder is classified under Page builders in the PluginView directory.

How many fingerprint rules cover Super Builder?

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

What public signals suggest a site uses Super Builder?

Illustrative public indicators for Super Builder include link, link, img. A live scan may match additional proprietary rules beyond these examples.