Detect Web Stories

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

• DOM selectors

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

• amp-story

Establishes

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

Does not establish

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

A confirmed Web Stories match also implies these technologies are present.

AMP

Can PluginView detect Web Stories without logging in?

Yes. PluginView only reads publicly accessible responses when checking for Web Stories — typically dom selectors. It does not bypass authentication or paywalls.

What category is Web Stories?

Web Stories is classified under Widgets in the PluginView directory.

How many fingerprint rules cover Web Stories?

This reference currently tracks 1 fingerprint rule across dom selectors. Individual rule bodies are proprietary and are not published.

What public signals suggest a site uses Web Stories?

Illustrative public indicators for Web Stories include amp-story. A live scan may match additional proprietary rules beyond these examples.