scanned May 25, 2026

Plausible

plausible.io

Plausible provides simple, privacy-friendly web analytics as an alternative to Google Analytics.

62/100

Tier 4 · Agent-Ready

Content answers67/100
Protocol plumbing50/1008 of 16 checks pass

Scored by asking 15 questions a buyer of a analytics product asks, then grading this site’s own pages: answered, hedged (partial or vague), or silent (no page answers it). How scoring works

This report is public. Own plausible.io? Claiming is free: crawl every page, re-audit as you fix, and track your score over time.

Sign in to claim

The fix queue

38 points sit between plausible.io and 100: 9 open questions and 8 missing protocol checks, ordered by estimated payoff.

Point estimates are per fix under scoring v2. They are not additive to a promised total.

01enterprise · importance mediumGoes silent+7 content pts est.

For the enterprise plan, do you offer a formal SLA with uptime guarantees and compensation credits? I can't find specific percentages on the pricing page.

What the pages say

No page on the site addresses this.

The fix

Add a dedicated SLA or status page, or include explicit uptime guarantees and compensation credit terms on the Enterprise pricing page.

Where we looked: /contact, plausible.io, /docs/trial-to-paid, /contact

confidence high · grounding synthesized · weight 0.00 · Absent

02operations · importance mediumGoes silent+7 content pts est.

For the self-hosted version, what's the minimum RAM and CPU you recommend for handling 100k monthly pageviews? Your docs mention Docker but don't specify hardware.

What the pages say

No page on the site addresses this.

The fix

Add a self-hosting requirements page to the docs that lists minimum/recommended RAM, CPU, and storage for common traffic tiers (e.g., 100k pageviews).

Where we looked: /jobs/infrastructure-engineer, /blog/may-2020-recap, /blog/june-2020-recap, /blog/community-edition, /blog/april-2020-recap, /blog/scaling-customer-support

confidence high · grounding synthesized · weight 0.00 · Absent

03support · importance lowGoes silent+7 content pts est.

If I pay for enterprise support, what's the actual guaranteed response time for critical issues—4 hours, 24 hours? The pricing page says 'priority' but doesn't define it.

What the pages say

None of the retrieved chunks specify a guaranteed response time for critical issues under enterprise support, nor do they define what “priority” support means. The Enterprise plan is described as including custom limits, SSO, managed proxy, and Sites API, but support SLAs or response times are not mentioned anywhere on the retrieved pages.

The fix

Add a dedicated Support/SLA or Enterprise plan details page that explicitly defines guaranteed response times for critical issues and explains what “priority” support includes.

Where we looked: /contact, /blog/scaling-customer-support

confidence high · grounding synthesized · weight 0.00 · Absent

Hedged · 6 of 15 questions

A buyer gets something, then has to guess the rest. Expand any row for the evidence and the fix.

04I run a WordPress multisite network with 40 subsites. Does your plugin handle network-wide activation, or do I need to configure each site individually?integrationHedges+2 pts est.

I run a WordPress multisite network with 40 subsites. Does your plugin handle network-wide activation, or do I need to configure each site individually?

What the pages say

The retrieved chunks confirm that Plausible offers a WordPress plugin for standard installations, but none of them mention whether it supports WordPress multisite network activation or subsite-level configuration. The only multisite mentions in the chunks refer to third-party search plugins (Relevanssi and SearchWP), not Plausible's own analytics plugin.

The fix

Add explicit documentation on the WordPress plugin page or in a FAQ stating whether Plausible supports WordPress multisite network activation and how to configure it across subsites.

Where we looked: /docs/proxy/introduction, /docs/change-domain-name, /wordpress-analytics-plugin, /blog/wordpress-plugin-for-site-search, /blog/wordpress-plugin-for-site-search

confidence high · grounding synthesized · weight 0.70 · Vague

05For white-label analytics, can I use my own subdomain like analytics.myagency.com, or am I limited to a subdirectory on your domain?operationsHedges+2 pts est.

For white-label analytics, can I use my own subdomain like analytics.myagency.com, or am I limited to a subdirectory on your domain?

What the pages say

Plausible describes two white-label integration paths—an embedded dashboard (iframe via the Sites API) and a fully custom UI built with the Stats API—but the retrieved chunks do not specify whether you can host the dashboard on your own subdomain (e.g., analytics.myagency.com) or if you are limited to a subdirectory on Plausible's domain.

The fix

Add a FAQ or documentation section on the white-label page that explicitly states whether customers can use a custom subdomain, a subdirectory, or only iframe/API integration for white-label dashboards.

Where we looked: /white-label-web-analytics, /white-label-web-analytics

confidence high · grounding synthesized · weight 0.70 · Vague

06Your CCPA compliance page says you don't 'sell' data, but under CCPA's broad definition, does sharing with your hosting provider or payment processor count as a sale requiring disclosure?privacyHedges+2 pts est.

Your CCPA compliance page says you don't 'sell' data, but under CCPA's broad definition, does sharing with your hosting provider or payment processor count as a sale requiring disclosure?

What the pages say

Plausible states that they "do not sell your data and only share it with trusted service providers where necessary to operate and provide the service," and they identify Hetzner as the German company that owns their servers. Their compliance documentation also states that "No data is shared with or sold to third parties." However, the chunks do not explicitly address whether sharing with a hosting provider or payment processor qualifies as a "sale" under CCPA's broad definition, nor do they identify a specific payment processor or provide a CCPA-specific analysis of service-provider sharing.

The fix

Add a dedicated CCPA compliance FAQ or section that explicitly defines "sale" under CCPA, lists subprocessors (hosting provider, payment processor), and states whether such sharing is considered a sale or falls under the service-provider exception.

Where we looked: /security, /docs/compliance

confidence medium · grounding synthesized · weight 0.65 · Vague

07Using your Looker Studio connector, how often does the data refresh—real-time, hourly, or daily? I need near real-time for our ops dashboard.integrationHedges+2 pts est.

Using your Looker Studio connector, how often does the data refresh—real-time, hourly, or daily? I need near real-time for our ops dashboard.

What the pages say

The retrieved chunks do not specify how often the Plausible Looker Studio connector refreshes data. While the site mentions that Looker Studio reports are “dynamic” and “automatically update whenever the original data source changes, ensuring your reports automatically reflect the most current information” ([3], [13]), it does not state whether the connector provides real-time, hourly, or daily data updates. The Plausible realtime dashboard itself updates every 30 seconds ([4]), but this is distinct from the Looker Studio connector refresh behavior.

The fix

Add a dedicated FAQ or documentation section for the Looker Studio connector that explicitly states the data refresh interval (e.g., real-time, hourly, or daily) and whether near real-time is supported for ops dashboards.

Where we looked: /blog/google-looker-studio-guide, /for-saas, /blog/google-looker-studio-guide, /docs/guided-tour

confidence high · grounding synthesized · weight 0.70 · Vague

08Your UTM builder is handy, but what's the maximum character length you'll store for UTM campaign names? I have some very long campaign identifiers from our ad platform.technicalHedges+2 pts est.

Your UTM builder is handy, but what's the maximum character length you'll store for UTM campaign names? I have some very long campaign identifiers from our ad platform.

What the pages say

Plausible describes `utm_campaign` as flexible and allows any campaign identifier, but the retrieved documentation does not specify a maximum character length for stored UTM campaign names.

The fix

Document the maximum character length (if any) for UTM campaign, source, medium, content, and term values stored in Plausible.

Where we looked: /blog/utm-tracking-tags, /blog/utm-tracking-tags

confidence medium · grounding synthesized · weight 0.65 · Vague

09I'm building a dashboard that pulls from your API every 5 minutes. Is there a daily request limit or rate limit I should know about?limitsHedges+1 pt est.

I'm building a dashboard that pulls from your API every 5 minutes. Is there a daily request limit or rate limit I should know about?

What the pages say

API keys have a rate limit of 600 requests per hour by default. The retrieved chunks do not mention a separate daily request limit.

The fix

Clarify in the API documentation whether there is a daily request limit in addition to the hourly rate limit.

Where we looked: /docs/stats-api

confidence high · grounding stated · weight 0.80 · Vague

What the pages already answer cleanly

6 of 15. Answered with enough specificity for a buyer to act on. This is the bar the queue above is chasing.

migrationAnswered

We're switching from Google Analytics—can you import our historical data, or do we start from zero? If import is possible, how far back does it go?

What the pages say

Yes, you can import your historical Google Analytics data into Plausible; you do not start from zero. Plausible imports data from your first Google Analytics visitor until your first Plausible Analytics visitor to avoid double-counting. The practical lookback limit is constrained by Google's data retention policies: for Universal Analytics, Plausible can import as far back as your UA data retention settings allow; for GA4, Google defaults to 2 months of event-level data retention (14 months on paid GA4 plans), and once Google deletes that data it cannot be recovered.

Source: /docs/your-plausible-experience, /for-freelancers-agencies, /docs/google-analytics-import, /blog/ua-vs-ga4, /docs/google-analytics-import

confidence high · grounding synthesized · weight 0.95 · Answered

pricingAnswered

I'm on the 10k pageviews plan and hit my limit mid-month. Does Plausible stop tracking entirely, or do I get billed for overages automatically?

What the pages say

Plausible does not stop tracking, and you are not billed automatically for overages. On the 10K plan, a single month over your limit requires no action and won't trigger extra charges or an upgrade. You would only need to upgrade if your traffic consistently exceeds 10K for two consecutive months. Even if your dashboard were temporarily locked after two consecutive over-limit months, stats continue to be collected in the background.

Source: /contact, /docs/billing

confidence high · grounding synthesized · weight 0.95 · Answered

securityAnswered

You mention EU-hosted analytics, but where exactly are your servers located? Are they all in Germany, or spread across multiple EU countries?

What the pages say

Plausible's infrastructure is spread across multiple EU countries, not solely Germany. All visitor data is stored on servers owned by Hetzner in Falkenstein, Germany. They use UpCloud, a Finnish company, for database hosting and storage of data exports, and Bunny, a Slovenian company, as their CDN. These are the only three providers that touch visitor data, and all three are European-owned, ensuring no visitor data is transferred outside the EEA.

Source: /eu-hosted-web-analytics

confidence high · grounding stated · weight 1.00 · Answered

technicalAnswered

You claim 'more accurate' data than GA, but what percentage of visitors do you actually capture when adblockers are present? Do you have any proxy or server-side workaround?

What the pages say

Plausible says its default script is blocked by roughly 6–26% of visitors depending on the site and audience (up to 60% on very tech-savvy sites), so it captures roughly 74–94% of visitors by default (or about 40% in extreme tech-savvy cases). It is not blocked by Firefox, Chrome, or Safari out of the box, but is blocked by some ad-blocker extensions that block all JavaScript tracking indiscriminately. For a workaround, Plausible offers a proxy option that routes the script through your own domain as a first-party connection; when proxied, Plausible says it is “not blocked by any browser or adblocker” and is only blocked by visitors who disable JavaScript entirely.

Source: /wordpress-analytics-plugin, /most-accurate-web-analytics, /blog/google-analytics-adblockers-missing-data, /contact

confidence high · grounding synthesized · weight 0.95 · Answered

technicalAnswered

Your conversion tracking mentions funnels, but can I set up multi-step funnels with conditional branching, or only linear page sequences?

What the pages say

Plausible only supports linear page sequences, not multi-step funnels with conditional branching. Their documentation explicitly states: "Funnels in Plausible are always linear. Each funnel follows one defined path from start to finish. Branching or conditional paths are not supported. If you need to compare two different paths, create two separate funnels."

Source: /docs/funnel-analysis

confidence high · grounding stated · weight 1.00 · Answered

Protocol plumbing · 50/1008 of 16 checks pass · each fix +6 protocol pts est.

The other half of the score: 16 checks for the files and headers agents look for. The 8 below are installs, not judgment calls, and most are an afternoon. Expand any for the snippet and the standard it follows. They sit after the queue because none of them changes what your pages say.

llms.txtDiscoverability+6 pts est.

Sitedex generates this file from your crawl. Grab it in Files from this audit below.

Standardllmstxt.orgCommunity spec

Content signalAccess+6 pts est.
Install snippet
User-agent: *
Content-Signal: search=yes, ai-input=yes, ai-train=no
Allow: /

StandardCloudflare proposalVendor proposal

Clean crawlAccess+6 pts est.

StandardSitedex metricSitedex metric

Markdown negotiationRendering+6 pts est.

StandardRFC 9110 + 7763IETF RFC

MCP cardInteraction+6 pts est.

Sitedex generates this file from your crawl. Grab it in Files from this audit below.

StandardModel Context ProtocolCommunity spec

OpenAPI specInteraction+6 pts est.

StandardOpenAPI SpecIndustry standard

WebMCP widgetInteraction+6 pts est.

Sitedex generates this file from your crawl. Grab it in Files from this audit below.

StandardW3C WebMCP draftW3C / WHATWG

Organization schemaIdentity+6 pts est.

Sitedex generates this file from your crawl. Grab it in Files from this audit below.

StandardSchema.org + JSON-LDIndustry standard

Already passing 8 of 16: robots.txt, sitemap.xml, AI crawler access, Server-rendered content, Canonical URLs, Meta descriptions, HTML lang attribute, Sitemap lastmod.

Ask this site’s index

Sitedex already serves plausible.io as an MCP endpoint. Ask plausible.io anything an AI agent might ask, and see what its index returns. (To score your own site, use the form below.)

Snippets & configs

For developers and the engineer-on-call: copy these into your tools or your site.

Files from this audit

Built from this crawl. Download or copy each, then install it at the path noted.

llms.txt

Built from this crawl. Install at /llms.txt so agents start here.

organization.json

Organization JSON-LD, pre-filled from this crawl. Wrap in a ld+json script.

server-card.json

MCP server card built from this crawl. Host at /.well-known/mcp/server-card.json.

webmcp.json

WebMCP discovery manifest built from this crawl. Host at /.well-known/webmcp.json.

MCP endpoint

https://mcp.sitedex.dev/s/plausible-io/mcp

The URL anyone's agent points at. Read-only; safe to share.

Claude Code

claude mcp add plausible --transport http https://mcp.sitedex.dev/s/plausible-io/mcp

One command, then the agent has it.

Cursor / Continue

{
  "mcpServers": {
    "plausible": {
      "url": "https://mcp.sitedex.dev/s/plausible-io/mcp"
    }
  }
}

Drop into mcp.json.

WebMCP: two parts

WebMCP-capable browsers run the widget at runtime. Crawlers without JS rendering need the discovery manifest to find your tool surface. Install both.

1 · Widget script

<script async src="https://sitedex.dev/widget.js"></script>

Drop in <head>. In browsers with WebMCP, this script registers your site's tools with navigator.modelContext.registerTool().

2 · Discovery manifest

{
  "schema_version": "2026-04",
  "name": "Plausible",
  "description": "Plausible provides simple, privacy-friendly web analytics as an alternative to Google Analytics. WebMCP tools served by Sitedex.",
  "homepage": "https://plausible.io",
  "documentation": "https://app.sitedex.dev/sites/plausible.io",
  "source": "navigator.modelContext",
  "tools": [
    {
      "name": "search_site_content",
      "description": "Ask about this site in plain language and get the most relevant passages from its pages, each with the source URL and a relevance score. Searches the site's published text, not live inventory or accounts."
    },
    {
      "name": "get_site_info",
      "description": "This site's profile: name, description, category, who it is for, page count, and AI Visibility Score. Use it to learn what the site is before you search it."
    },
    {
      "name": "list_site_pages",
      "description": "The pages indexed on this site, with title, URL, and path. Use it to see what the site covers, or to find the path to pass to get_site_page."
    },
    {
      "name": "get_site_page",
      "description": "The full markdown of one page on this site, by path. Use it after search_site_content points you at a page and you want all of it."
    }
  ]
}

Host alongside the script at /.well-known/webmcp.json. Crawlers that don't render JS rely on this.

Your turn

See which of these questions your site goes silent on.

Free, about 5 minutes. We crawl your site, test it against the buyer questions your category asks, and name what’s vague, contradictory, or missing, plus the files AI agents look for.

ComingEmbeddable grade badgeScore history and deltasOpt-in public board