The question ‘is this blog worth it at all?’ almost always gets the same answer: a handful of impressive statistics about companies that have blogs. They circulate through presentations, proposals, and articles, cited without a source or linked to another piece that cites nobody in turn. After years of being passed around, it is no longer possible to tell who calculated them, when, or from what data. Your decision about whether to keep publishing cannot rest on something like that—and it does not have to, because you already have the data you need to answer the question.
Why widely circulated blog statistics tell you nothing
Before treating such a figure as a benchmark, try one exercise: follow its references all the way back to the beginning. In most cases, the trail ends at another marketing article rather than a study that describes its sample, timeframe, and calculation method. Even if you do find the source, four problems remain that make the figure irrelevant to your website.
- No traceable sourceThe references end at another article, not a study with a documented sample and methodology.
- A different market and industryA result gathered from international technology companies does not translate to a local service business.
- A different definition of a leadSometimes it means a newsletter signup, sometimes a download, and sometimes a sales inquiry. These are not comparable.
- An unknown measurement pointYou do not know whether the effect was measured after one quarter of publishing or after several years of building a mature content library.
This article deliberately includes no figures from third-party reports on blog effectiveness. The reason is simple: we could not point to their original source, sample description, or the definitions used in the calculation. A figure presented without that context sounds credible but cannot be verified. Instead, we describe a method you can apply to your own data—one whose result will reflect your website, your industry, and your definition of an inquiry.
Changing the benchmark is the whole shift in approach. You are not interested in how many leads ‘companies with blogs’ generate, but whether your articles appear in the histories of people who actually contacted you. The data you already collect can answer that question, with no need to compare yourself with an anonymous average.
Content rarely converts immediately
The second reason blogs look weak in reports is more mundane: they are assessed with tools designed to evaluate sales pages. An article almost never produces an inquiry in the same minute. Someone reads a guide, closes the tab, returns a few days later—now without a recorded source—checks the pricing page, and only then writes. In a session report, this looks like three unrelated visits and one inquiry from nowhere.
- Day 1
Arrival from a search engine on a guide, several minutes of active reading, then an exit without any action
- Day 5
A direct return, another article from the same section, and the pricing page
- Day 12
A direct visit to the pricing page, opening the chat, and a question about implementation scope
- Day 12
A callback request submitted after the chat conversation
The practical conclusion is simple: evaluating content requires a longer window than a single visit and a unit other than the session. We cover both the technique for linking successive visits into one history and the pitfalls of assigning credit in our separate guide to the customer journey on a website. Here, we use it solely to answer the question of content's contribution.
Three ways to measure content's contribution
You do not need to begin with a comprehensive analysis. These three methods run from the simplest to the most labor-intensive, with each answering a slightly broader question. You can do the first on paper in fifteen minutes; the third requires a tool that links one person's visits.
Scroll the table sideways to see all columns.
| Method | What you check | What it cannot determine |
|---|---|---|
| Landing page for inquiries | Which URL began the visits of people who contacted you | It misses people who returned later and arrived directly |
| Returns after reading an article | Whether a visit to an article is followed by another visit and a move to sales pages | It requires an observation window longer than a week |
| Full visit history before contact | All of one person's sessions, including their source, visited URLs, and events | It cannot link a phone to a laptop until the person is identified |
The third method provides an answer you can use to make a budget decision, and it is less complicated than it may seem. You simply reverse the direction of the analysis: instead of starting with articles and looking for conversions, start with inquiries and work backward through everything that preceded them.
- Collect inquiries from one period.Include conversations, callback requests, and tickets from the same date range, without cherry-picking the most impressive ones.
- Trace each person's visits backward.Check which sessions preceded the contact, where they came from, and which URLs they began on.
- Mark every arrival through an article.What matters is the article's presence anywhere in the history, not only as the final visit before the inquiry.
- List the titles that recur most often.The same handful of URLs usually keeps appearing. These are your actual sales assets, regardless of what the page-view ranking says.
- Record cases with no known source separately.Without this information, the list of titles looks more complete and certain than it really is.
- Repeat the analysis for another period before changing your content plan.One review reveals a hypothesis; only the second confirms that the pattern holds.
The penultimate step is more important than it looks. Some visits will never have a recorded source, and no tool can fix that—we explain this more fully in our article on what Google Analytics cannot show you. In Meetlead, such sessions are explicitly marked as uncovered rather than assigned an invented source, so you can see how much of the history remains unknown.
The customer journey in Meetlead shows one person's successive sessions with their source, landing and exit pages, and events, plus links to the conversation, callback request, and ticket. Explore behavior analysis.
When assessing interest in a PDF file, use the guide: PDF download or link click: define what your result proves.
Questions asked from articles as a signal
The fastest signal that your content is attracting the right people is not a number. It is a question asked while reading or immediately afterward. If your chat shows the operator which page the visitor is viewing, you have this information instantly: you can see which article prompted the question and what it concerns. Recording this for a few weeks produces insight that no page-view report can replace.
- Record the article URL together with the question, rather than saving the question without its context.
- Separate questions about the scope and terms of working together from questions about the article's subject—these reflect two different levels of readiness.
- Check whether the person asking belongs to your intended audience or arrived looking for something entirely different.
- Record questions the article should have answered but did not—this is a ready-made list of additions.
- Watch for repetition: one question is an anecdote; the same question for the fifth time reveals a gap in the content.
- Treat an article that regularly prompts questions about terms as a sales page, not a guide.
Meetlead live chat shows the operator the URL the visitor is currently viewing, so you can see which article prompted the question. Explore the product.
That same list of recurring questions has another use: it is the best editorial plan you could ask for. Instead of guessing at topics, you write about what people actually ask. We explain how to organize such topics and measure whether the answer genuinely helps in our article on building a knowledge base and FAQ for your website.
When an article does not work—and what to do with it
Some articles will not appear in any history that ends with an inquiry, and that is normal—not every article has the same purpose. The problem begins when you cannot explain why a particular piece exists on the site. That is when you should diagnose it and choose one of three options: update, merge, or remove it. When you update a piece, also check that Search can access it and that it answers the question directly, as described in our guide to AI search visibility.
Scroll the table sideways to see all columns.
| Symptom | Likely cause | Decision |
|---|---|---|
| People arrive, but nobody goes any further | The article ends without suggesting a next step | Improve the ending and link to the appropriate page |
| Questions from the article concern something else | The topic attracts a different audience from your customers | Narrow the angle or deliberately classify the piece as purely informational |
| Search visibility without visits | The title and description do not match the search intent | Rewrite the title and summary while leaving the body unchanged |
| Two articles cover the same subject | They compete for the same search query | Merge them and redirect the weaker URL |
| The content describes an outdated situation | The terms, prices, or process have changed | Update it; if the topic has expired, remove it and record the reason |
Removing content can be emotionally difficult, but keeping articles that nobody reads or updates has a real cost: it blurs the site's structure and makes effective material harder to find. If you want a firmer signal than visits alone to support these decisions, use the event-selection method described in our article on website micro-conversions. Business goals recorded by the site let you see whether anything happens after someone reads an article.
A content review cadence
This method works only when repeated regularly. A one-off review will reveal curiosities; a quarterly review will begin to shape your editorial plan. The cadence below is light enough to maintain alongside your other responsibilities.
- Once a month, work backward through the visit histories behind recent inquiries and mark the articles that appeared in them.
- Once a quarter, compare those titles with the list of questions asked from individual pages.
- Separate observations from interpretations—record the fact separately from the hypothesis you form from it.
- Choose a few articles to update or merge and decide how you will know whether the change worked.
- Every six months, review articles with neither visits nor questions, and record the reason behind every decision to remove one.
- Before declaring a trend, compare the result with the previous period rather than with your impression from a year ago.
Business goals recorded by your site, visit histories, and conversations in one place let you assess content's contribution without guessing. Book an implementation.
The greatest benefit of this approach comes at the end. When someone asks whether the blog is worth it, you no longer need to reach for somebody else's statistic that you do not entirely believe yourself. You can show concrete histories: which article began the visit, how many days passed before contact, and what question was asked. It is a less rhetorically impressive answer—and an incomparably stronger one on substance.

