Detect PageLayer

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

• Script sources
• DOM selectors

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

• pagelayer-frontend?/js?/combined?.min?.js?ver?=0.0?
• link, #pagelayer-frontend-css, #pagelayer-global-styles, .pagelayer-bod…

Establishes

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

Does not establish

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

Can PluginView detect PageLayer without logging in?

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

What category is PageLayer?

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

How many fingerprint rules cover PageLayer?

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 PageLayer?

Illustrative public indicators for PageLayer include pagelayer-frontend?/js?/combined?.min?.js?ver?=0.0?; link, #pagelayer-frontend-css, #pagelayer-global-styles, .pagelayer-bod…. A live scan may match additional proprietary rules beyond these examples.