Detect GreatPages

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

• Script sources

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

• .greatpages.com.br/

Establishes

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

Does not establish

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

Can PluginView detect GreatPages without logging in?

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

What category is GreatPages?

GreatPages is classified under Page builders in the PluginView directory.

How many fingerprint rules cover GreatPages?

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

Illustrative public indicators for GreatPages include .greatpages.com.br/. A live scan may match additional proprietary rules beyond these examples.