Latest / Found, Trusted, Booked / How to Tell If Content Works Before Anyone Books a Call
Transcript
- Your content has been live for weeks, nobody has booked a call, and you can't tell whether the pages are the problem or something else. Booked calls arrive late and in small numbers, so they can't answer that question. In the next few minutes: three earlier signals you can read, and how each one points to a different fix. In my latest piece, How to Tell If Content Works Before Anyone Books a Call, I wrote about exactly this. I'll use the example from the article, and it's a fictional one. Picture Russell, a hypothetical marketing director at a mid-sized registered investment adviser, or RIA. His firm publishes explainers on how advisory fees work, and every page passes compliance review before it goes live. The pages describe pricing models. They don't recommend one. Why not just wait for calls? Because a call depends on more than the content. It depends on the phone line, the intake form, and how long a household takes to decide. A firm with modest traffic might see only a few calls a month, which is too few to learn from. The earlier signals move sooner, and in larger numbers. The first signal is which pages are being retrieved. That word can mean three things. One is search results. Google Search Console is a free tool that shows the queries a page appeared for, how often it appeared, and how often someone clicked. Two is crawler requests. Your web server logs every request, and several AI companies publish the names their crawlers use, so you can see when one fetches a page. Three is assistant referrals, where analytics records a visit from an AI assistant's domain. Many visits arrive with no referrer, so that count is a floor, not a total. One caution. A crawler fetching a page isn't the same as an assistant citing it. The log shows the fetch and nothing more. Treat it as evidence the page is reachable, not that it's used. Russell looks at his flat-retainer page and sees plenty of impressions but few clicks. That points to the title and description, not the body. The page is being shown, and the snippet doesn't match what the searcher wanted. So he rewrites the title to say plainly what the page compares, and the edit goes back through compliance like any other. The second signal is what visitors ask on the site. Site search, a chat widget if you run one, free-text fields on contact forms, and Search Console queries written as questions. Russell groups a month of site searches by meaning, not spelling, and finds several people asking whether a flat fee covers tax preparation. His explainer never says. Visitors reached the page, looked for that answer, and searched again. The fix is editorial: a short section on what the flat fee does and doesn't include, reviewed by compliance, published with a new review date. Two cautions here. Don't invite visitors to type account balances or personal financial details into a search box or chat. And saved transcripts and form messages may count as firm records, so Russell asks compliance how long they're kept and where. That's a records question, and the answer belongs to the firm. The third signal is how long readers stay on approved material. In Google Analytics 4, engagement time counts only the seconds a page is in the foreground of the browser, so a forgotten background tab adds nothing. Three habits help. Use the median, not the average, because a few long sessions pull an average up. Compare against page length, since a four-hundred-word page and an eighteen-hundred-word page shouldn't share a benchmark. And add scroll events, so you see the heading where readers drop off. Russell's minimums page loses most readers at the third heading, a dense paragraph of definitions. He proposes splitting it in two and adding a small worked table. And because a page edited after review is a different page, he keeps a log of each approved version's date, so he knows which text produced which numbers. What can't these signals tell you? Who the reader is, or whether they became a client. Short time on a page might mean a poor page, or a reader who found the answer in ten seconds. And one week of small numbers shouldn't drive an edit. What they can do is narrow the cause. If a page isn't retrieved, the problem is discovery. If it's retrieved but not clicked, it's the snippet. If it's clicked but visitors leave to search again, it's the answer. Each has a different fix, and a booked call can't separate them. So: waiting for calls tells you too little too late, and three earlier signals, retrieval, visitor questions, and time on approved pages, show you where to look. The article is called How to Tell If Content Works Before Anyone Books a Call, and it's linked in the episode description if you'd like to read it. This episode was produced by the ChoiceDigital™ Engine — reviewed for accuracy, editorial quality, and compliance, then approved by Dr. Adrian McMillian, whose voice you have been hearing as an AI-generated replica.