Try or ByeTry or Bye

Plausible Verification Failed (Couldn't Verify Installation)

Workaround available Web Updated October 21, 2026

Quick answer

The verification tool can fail even when tracking works: it only visits the exact URL you added and can't see scripts loaded after consent or through an outdated proxy. If real visits appear in the dashboard, you can ignore the error.

Most likely fix: Verify manually.

Symptoms

The installation check reports it couldn't find or verify the snippet, while you believe it is installed.

Why it happens

  • Site lives at a different URL than the one added (www vs non-www, subpath)
  • Script loads only after cookie consent (Cookiebot or similar)
  • Outdated copy of the script served by a custom proxy
  • Cached page without the snippet

How to fix it

Try these in order — the most common fix is first.

  1. 1. Verify manually

    1. View page source and search for plausible.init
    2. Open DevTools > Network, reload and confirm a request to plausible.io (pa-...) with status 200
    3. Visit the site from another device and check the realtime dashboard

  2. 2. Update the proxied script

    1. If you proxy the script, update your proxied copy to the latest snippet version
    2. Purge cache and re-run verification

  3. 3. Load the script outside the consent gate

    1. Plausible is cookieless; after checking with your legal team, load it without waiting for consent
    2. Otherwise rely on manual verification instead of the tool

This guide also covers

  • plausible verification failed
  • plausible couldn't verify installation
  • plausible verify integration

Still not working?

If Plausible Analytics keeps failing, you're not alone. See every Plausible Analytics problem users report or the alternatives people switch to.

Other Plausible Analytics errors