Detect PublishPress Blocks

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

• DOM selectors
• HTML markup

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

• link?\;version:\1']
• <divclass=wp-block-advgb-*

Establishes

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

Does not establish

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

Can PluginView detect PublishPress Blocks without logging in?

Yes. PluginView only reads publicly accessible responses when checking for PublishPress Blocks — typically dom selectors, html markup. It does not bypass authentication or paywalls.

What category is PublishPress Blocks?

PublishPress Blocks is classified under WordPress plugins in the PluginView directory.

How many fingerprint rules cover PublishPress Blocks?

This reference currently tracks 2 fingerprint rules across dom selectors, html markup. Individual rule bodies are proprietary and are not published.

What public signals suggest a site uses PublishPress Blocks?

Illustrative public indicators for PublishPress Blocks include link?\;version:\1']; <divclass=wp-block-advgb-*. A live scan may match additional proprietary rules beyond these examples.