Detect Swipe Pages

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

• Script sources

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

• .swipepages.com/

Establishes

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

Does not establish

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

Can PluginView detect Swipe Pages without logging in?

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

What category is Swipe Pages?

Swipe Pages is classified under Page builders in the PluginView directory.

How many fingerprint rules cover Swipe Pages?

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 Swipe Pages?

Illustrative public indicators for Swipe Pages include .swipepages.com/. A live scan may match additional proprietary rules beyond these examples.