Detect EmbedPress

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

• Script sources
• DOM selectors

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

• embedpress/assets?/js?/ads?/pdfobject?/front?/documents-viewer-script?/…
• #embedpress-css, #embedpress-elementor-css-css, #embedpress_blocks-cgb-…

Establishes

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

Does not establish

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

Can PluginView detect EmbedPress without logging in?

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

What category is EmbedPress?

EmbedPress is classified under Widgets, WordPress plugins in the PluginView directory.

How many fingerprint rules cover EmbedPress?

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

What public signals suggest a site uses EmbedPress?

Illustrative public indicators for EmbedPress include embedpress/assets?/js?/ads?/pdfobject?/front?/documents-viewer-script?/…; #embedpress-css, #embedpress-elementor-css-css, #embedpress_blocks-cgb-…. A live scan may match additional proprietary rules beyond these examples.