Plausible growth teardown: 98/100

Plausible scores 98 out of 100 on our Level 0 Growth Scan of its public footprint, run on 29 Oct 2026. Visibility is the weakest of the three pillars we scored, at 93. The one failed check is a missing /llms.txt, which takes 30 minutes to fix. AI engines already name Plausible in 70% of answers to its category’s buying questions.

Plausible is a web analytics service positioned as a simple, privacy-friendly alternative to Google Analytics. Its homepage title says exactly that. Everything in this teardown comes from plausible.io, its DNS records and the public AI engine answers we captured. We hold no account with Plausible and have no inside information.

Method

We scanned plausible.io on 29 Oct 2026. A Level 0 scan reads the public footprint only: the homepage and linked pages, DNS, rendered tags and the AI engine answers. The modules that ran were Agent Readiness, SEO Technical, Content and Entity, Social Footprint, Tag Health, Tech Stack and Email Authentication, then the free AI Visibility snapshot. Conversion and Retention were not scanned, show as “Not scanned”, and are left out of the Growth Score.

The AI snapshot works like this. A model reads the homepage and writes 5 questions a US buyer of web analytics would ask, none of which name Plausible. We ask each question once on Gemini and once on Google AI Mode, through the real consumer apps. That is 10 answers. We count the answers that name the brand as a whole word and the answers that list a plausible.io URL among their sources.

The number

98 out of 100. Visibility 93, Acquisition 100, Measurement 100. Of 46 checks, 1 failed, 4 warned and the rest passed or were informational.

Measurement is clean. SPF, DKIM and DMARC all pass. The rendered homepage loads an analytics tag and nothing we flag. Acquisition passes on the social footprint checks: profiles are linked from the site and resolve, and the homepage carries Open Graph title and image.

Finding 1: AI engines already recommend Plausible

Mention rate 70%, citation rate 40%, 2 of 2 engines checked. Gemini named Plausible in 4 of 5 answers and cited plausible.io in 2. Google AI Mode named it in 3 of 5 and cited it in 2. Both rates pass our thresholds of 40% for mentions and 20% for citations. Of the 4 domains we checked that day, Plausible was the only one above 0%.

The questions were about analytics tools for small businesses and ecommerce, simple traffic analysis, cookie-less visitor tracking and Google Analytics alternatives. The last two are where Plausible’s positioning does the work. The sources engines cited most often were not plausible.io but third-party pages: bootstrap.build, quantummetric.com and amplitude.com appeared twice each, usefathom.com once. That is the citation gap. Engines know the brand but reach for other people’s pages to describe the category.

Finding 2: no /llms.txt (Fail)

GET https://plausible.io/llms.txt returned 404 on 29 Oct 2026. We checked it again by hand on the same day. Robots.txt allows AI crawlers and the site is otherwise ready for agents, so this is the single failed check across the scan.

An llms.txt is a Markdown file at the site root: an H1, a one-line summary, and H2 sections linking the 10 to 30 pages an engine should read first. For Plausible that is pricing, the docs, the comparison pages and the privacy explainer. Effort: 30 min.

Finding 3: the homepage title is 75 characters (Warn)

The homepage title is “Plausible Analytics | Simple, privacy-friendly Google Analytics alternative”. That is 75 characters against a target of 30 to 60, so search results cut it. The positioning is right. The fix is to keep the first clause and lose the brand suffix, or move the brand to the end where truncation costs least. Effort: 1 day, because the title pattern is site-wide.

Two smaller warns sit in the same pillar. The About page exists at /about but is linked only from body text on the homepage, not the header or footer, so entity signals are weaker than they could be. Effort: 2 hours. The contact page has an FAQ section without FAQPage JSON-LD. Effort: 2 hours.

If we were fixing this

1. Publish /llms.txt. Effort: 30 min.
2. Shorten the homepage title to 60 characters or fewer and apply the pattern site-wide. Effort: 1 day.
3. Add About to the footer. Effort: 2 hours.
4. Add FAQPage JSON-LD to the contact page FAQ. Effort: 2 hours.
5. Close the citation gap. Engines name Plausible but cite other domains for the category. The pages to build or expand are the comparison and definition pages that answer the 5 buyer questions directly, so the cited URL becomes plausible.io. Effort: 1 month.

What is already good

Email authentication passes on all three records. The homepage and every page we checked carry a canonical. Robots.txt allows AI crawlers. The site renders its content in the raw HTML, so engines do not depend on JavaScript to read it. The positioning in the title is the same positioning engines repeat back in their answers, which is why the mention rate is 70% without an llms.txt at all.

Run the same scan on your own domain at /scan.