MyDealList · Due diligence
How to Audit Traffic Quality Before Buying a Content-Driven SaaS
Spot fake traffic, bots, and unsustainable referral spikes in Google Analytics or Plausible before you buy a content-driven SaaS. A practical buyer diligence checklist.
Content-driven SaaS businesses—tools that grow through SEO, affiliates, YouTube, or newsletters—often look healthier in a pitch deck than they do in raw analytics. Traffic quality decides whether MRR is durable or a temporary mirage. Before you wire funds, you need a repeatable audit for Google Analytics (GA4), Plausible, and related sources.
Pair this with Technical Due Diligence for Website Buyers and Red Flags When Buying SaaS on Twitter.
Screen content-led assets in the deal feed or upgrade via pricing.
Why Traffic Lies (and Sellers Sometimes Do Not Notice)
Not every bad chart is fraud. Common failure modes:
- Bot and spam traffic inflates sessions without conversion.
- Referral spikes from temporary campaigns, private communities, or paid blasts that will not recur.
- Vanity SEO pages that rank for irrelevant queries.
- Self-referrals and misconfigured tracking double-counting users.
- Channel concentration—80% from one keyword cluster or one affiliate about to churn.
Your job is to separate monetizable human attention from noise.
Access You Should Require
Refuse to proceed without time-boxed read access to:
- GA4 (or Plausible / Fathom / Cloudflare Web Analytics) for 12–24 months where available.
- Search Console (or Bing Webmaster) property access.
- Ad accounts if paid is material (Google, Meta).
- Email platform stats if newsletter is a growth engine.
- Stripe (or equivalent) alongside traffic—so you can join sessions to revenue.
The Traffic Quality Audit (Step by Step)
1. Trend shape over 12–24 months
Plot users/sessions and converting events monthly. Flag:
- Step-changes right before listing
- Smooth growth that suddenly flatlines after a Google update
- Seasonality the seller calls “temporary” without proof
2. Channel mix and concentration
In GA4: Traffic acquisition → session default channel group. In Plausible: Sources.
| Check | Healthy pattern | Warning |
|---|---|---|
| Top channel share | Diversified; organic + product-led | >70% one brittle source |
| Direct traffic | Stable brand/direct | Unexplained direct spikes |
| Referral | Named partners, docs, communities | Spam domains, “Free share” sites |
| Paid | Clear CAC and LTV story | Paid props up “organic” story |
3. Engagement quality
Humans behave differently from bots:
- Engagement rate / bounce by landing page (context matters for tools vs. blogs).
- Pages/session and engaged sessions.
- Scroll / event completion if instrumented.
- Geography: sudden traffic from regions that never convert.
4. Landing page → signup → paid funnel
Join analytics to product metrics:
- Signup rate by channel
- Trial-to-paid by channel
- Refund and chargeback rates after campaigns
If “viral” traffic never reaches checkout, it is not an asset—it is a cost center.
5. Bot and spam detection heuristics
- Spiky sessions with ~0 engagement from odd hostnames
- Perfect-length sessions repeated (bot scripting)
- Language/geo mismatches vs. customer base
- Hostnames that never appear in Search Console queries
In Plausible, shared-link public dashboards still warrant CSV export and source inspection. In GA4, use explorations to exclude known spam and compare filtered vs. raw.
6. SEO sustainability (content-driven thesis)
- Top queries: commercial vs. accidental informational
- Dependence on one feature SERP or brand query
- Content velocity vs. decay (are rankings aging out?)
- Manual actions or security issues in Search Console
Red-Flag Patterns Before You Sign
- Hockey-stick sessions, flat revenue in the same window.
- Seller refuses Search Console but pushes “Looker screenshots.”
- Primary growth from a Facebook group admin who is the seller's friend.
- Affiliate cookie stuffing or incentivized installs showing as “organic.”
- Analytics property created weeks before listing (history wiped).
Cross-check social selling claims with red flags for Twitter deals.
A One-Page Diligence Scorecard
Score each 1–5:
- History depth & access completeness
- Channel diversification
- Engagement authenticity
- Funnel conversion integrity
- SEO / referral durability
- Alignment of traffic with Stripe cohorts
Proceed only if weighted average is strong and no single critical fail (e.g., inaccessible books, bot-majority traffic).
How Buyers Should Use Findings in Negotiation
Traffic quality issues are not always deal-breakers—they are price and structure inputs:
- Haircut multiple for concentrated or decaying SEO.
- Earn-out tied to retained organic sessions or signup volume.
- Holdback until Search Console and analytics transfer cleanly.
Find candidates worth auditing in MyDealList; for ongoing deal intelligence, see pricing.
Related Reading
Comments from Pro members
Selected feedback from verified Pro subscribers. Timestamps update while you read.
- Jordan K.…
Switched to Pro mainly for the extra analyses and Reddit/X coverage. This workflow section matches how I screen listings now—saves me hours every week.
Pro
- Priya S.…
The cross-marketplace point is huge. I used to miss duplicates across sites. Premium paid for itself after one decent lead I would have skipped.
Pro
- Marcus T.…
As a Pro user I appreciate the emphasis on red flags before diligence. If you are still on Free, at least read the checklist twice before you wire funds.
Pro
- Elena R.…
I send founders here when they ask how I find sub-$10k deals. The internal link to pricing is honest—you really do need Premium or Pro if you are serious.
Pro
- Chris V.…
MyDealList + a simple spreadsheet is my stack for 2026. Dynamic feed + alerts beats refreshing five marketplaces manually. Worth upgrading from Premium to Pro if you scale volume.
Pro
Leave a Reply
Your email address will not be published.