Most of the numbers in a SaaS blog post did not originate there.
We extracted 5,034 claims from 961 posts across 46 SaaS domains and classified each one by how it attributes its data. Only 34.5% are first-party, drawn from the company's own product, survey, or customer data. The other 65.5% are borrowed: a figure from someone else's research, survey, or report, restated in the prose.
Borrowing is ordinary, even necessary. Synthesizing the wider industry is what a blog does. The problem is what happens to a borrowed number after it lands in the post, because the publisher cannot vouch for a figure it did not generate, and 70% of those borrowed claims carry no external link a reader can follow back at all.
Fresh content is not accurate content.
A post can score perfectly on recency and still rest on a number that traces nowhere. The deficit is baked in at the point of creation, and it is content debt that no freshness audit catches.
How 5,034 Blog Claims Break Down by Attribution
The claims fall into four categories.
34.5% are first-party. The company's own product data, its own survey, its own customer metrics. SaaS blogs generate real first-party data, and these are the claims a publisher can stand behind, because the source is the publisher.
20% cite a third-party source with a verified external link. A reader can click through, check the methodology, and evaluate the finding. This is the floor for attribution that holds up: fewer than one in three borrowed numbers carries a link a reader can actually follow.
15% name a source with no external link. Some say "according to a named analyst firm" with no URL at all. Many more link only to the publisher's own pages, a same-domain citation that points back to the blog rather than out to the source. Either way the reader gets a label and no path to the data.
31% are unsourced. No name, no link, no trail. A number appears in the prose as if it were common knowledge. "72% of B2B buyers prefer self-service." Says who? Published when? Based on what sample?
The risk concentrates in the gap between naming and linking: seven in ten borrowed claims offer no external link a reader can follow, and even the linked share is only as durable as the pages those links point to.
Why 70% of Borrowed Claims Cannot Be Checked
Of the 3,299 third-party claims in the dataset, only 1,006 carry an external link in the claim's own paragraph. That is 30.5%.
The other 69.5% split in two. 752 claims name a source but provide no verified external link. 1,541 cite nothing at all. Together, these 2,293 claims are numbers a reader cannot check without a separate search.
Naming a source is a label. Citing it is a path a reader can follow.
A sentence reading "HubSpot reports that 60% of marketers prioritize blog content" gives a reader a brand and a number. The report, the year the data was collected, and the methodology behind it stay out of reach. The claim is orphaned data from the moment it ships, and it will not acquire a trail unless someone goes back and adds the link by hand.
The gap between sourced and verifiable is where blog claim attribution breaks down. A team that names its authorities believes it is citing its data. Naming without linking leaves the reader to trust the writer, and the writer to trust their memory of the original, and no one able to confirm the number did not drift through three layers of repetition before it reached the prose.
The scan shows what ends up published. It does not show what happens during the writing. That part depends on the team.
Most content teams track publishing cadence, not claim attribution. The two require different infrastructure. As readers weigh in above, the gap between what teams intend and what they actually do at the claim level will sharpen.
The unsourced claims do not trace back to careless writers. Every domain in the scan publishes regularly and updates often. The gap exists because the workflow never included a sourcing step. I have shipped that gap myself: a statistic I remembered reading, pasted with no link, or pulled from an earlier post that never linked the original either. The number propagates. The provenance does not.
What First-Party Blogs Do Differently
The 46 domains spread across a wide range. First-party share runs from 0% on blogs that write entirely about the broader industry to 65% on blogs that write mostly about themselves, with a median near 29%. The spread reveals editorial culture more than content quality.
The blogs at the top of the first-party range share a trait: they write about data they own. Stripe, MailerLite, and Clari lead the dataset, each attributing more than 60% of their claims to internal product data, transparency reports, and customer metrics. These blogs make claims a reader can check against the company itself, because the company is the source.
A high first-party rate does not make a blog more rigorous, and a high borrowed rate does not make one careless. A blog covering an industry it does not generate data about has to borrow, and every borrowed number then has to be linked, checked, and kept current to stay verifiable. The blogs that lean on their own data sidestep that maintenance burden entirely. The ones that synthesize the field inherit all of it.
The difference is infrastructure. Whether the publishing system records a source at the point of creation determines whether a claim enters the world with a trail attached or as one more number a reader has to accept on faith.
Why Freshness Audits Miss the Source
Freshness and attribution measure different axes. One captures when a post was last touched. The other captures whether the numbers inside it can be checked.
A post published last week can rest on a borrowed figure that links to a page returning a 404. A post from two years ago can link every claim to a named, dated study. Recency says nothing about whether a reader can reach the source, which is the axis a freshness audit never checks.
That gap is freshness theater: teams update dates and check that links return a status, while the claims inside the post were never part of the audit. When I audit our own posts, freshness is the easy pass and the one that proves the least. Across 46 companies with very different editorial operations, the pattern held.
AI-assisted drafting makes it worse. When a writer uses a model to draft a post, the statistics arrive with no provenance at all. The number sounds plausible. The source is nowhere. Without a system that traces the citation supply chain from published claim back to primary source, there is no way to separate what is real, what is approximate, and what was generated from training data. Any system that detects when published data goes stale can only work if the data was traceable in the first place.
Living content starts with knowing where each claim originated.
How We Built This Dataset
The scan used LiquiChart's claim extraction and source verification infrastructure. Posts were fed through the same claim extraction engine that powers the Content Health Scanner. Each post was parsed for statistical assertions, and each assertion was classified by attribution type: first-party, sourced with a link, sourced without a link, or unsourced. The tool did not judge quality. It recorded provenance.
We selected 46 SaaS domains with active blogs and collected recent posts from each. A programmatic filter excluded statistics roundups, annual benchmark compilations, product announcements, and quote-heavy listicles, and the remaining titles were reviewed by hand for posts carrying fewer than two data claims. The result is 961 posts that represent ordinary, argumentative SaaS blog content: posts that make a case, support it with data, and move the reader toward a conclusion.
Each claim was classified by a single question: can a reader verify this number? First-party claims count as verifiable because the company is the source. Linked third-party claims count as verifiable because the reader can click through. Named-no-link and unsourced claims are unverifiable because the path ends at the prose. A link only counts when it appears in the claim's own paragraph and survives tracking-link filters; an earlier pass credited any external link near the claim, which inflated the linked share by treating navigation and neighboring-paragraph links as citations. Source URLs were then checked for availability and, where a date was present, for freshness. The full methodology is published for reproducibility.
The gap this scan reveals is structural. The posts are fresh. The statistics are recent. For 65.5% of the claims, the source sits on someone else's server, and for seven in ten of those, the publisher left no way to reach it.
We ran this scan on 961 posts from 46 SaaS blogs, our own included, and I could not vouch for our numbers until we did. The Content Health Scanner runs the same extraction on any URL. Run it on one of yours.