Detect Localised
Localised is local-first ecommerce platform.
Detection looks at dom selectors across 2 fingerprint rules among the site's public responses.
01
Websites using Localised
Loading website list…
02
Signal classes
PluginView evaluates public page signals in these classes when identifying Localised. Individual fingerprint rule bodies are proprietary and are not published.
- DOM selectors
03
Example public indicators for Localised
Illustrative indicators derived from public catalog metadata for Localised. A live scan may match additional proprietary rules beyond these examples.
- img
- span
04
What a detection means
- Establishes
- One or more public signals on the scanned page matched a known Localised signature (2 rules) at the time of the scan.
- Does not establish
- A sitewide install of Localised, an active vendor contract, exclusive use, or that Localised is still in place today.
05
How to check a site for Localised
- 1. Enter the website URL in the scan form — homepage, pricing, checkout, or login pages usually expose the strongest Localised signals.
- 2. PluginView reads only public responses (dom selectors) and scores them against the Localised signature set (2 rules).
- 3. Review the confidence score and text explanation for Localised on the results page.
06
FAQ: detecting Localised
- Can PluginView detect Localised without logging in?
- Yes. PluginView only reads publicly accessible responses when checking for Localised — typically dom selectors. It does not bypass authentication or paywalls.
- What category is Localised?
- Localised is classified under Cross border ecommerce in the PluginView directory.
- How many fingerprint rules cover Localised?
- This reference currently tracks 2 fingerprint rules across dom selectors. Individual rule bodies are proprietary and are not published.
- What public signals suggest a site uses Localised?
- Illustrative public indicators for Localised include img; span. A live scan may match additional proprietary rules beyond these examples.
