I run marketing at Storylane, and when the Storylane Buyability Index scanned 529 B2B websites, I expected the homepage to do more of the work. It is where most companies put their best thinking. Yet of the 6,204 buyer questions those sites answered in full, the homepage answered 113. That is 1.8%. The help centre, the docs and the blog answered 38%.
The answers exist. They just sit a long way from where buyers start. I call that gap answer distance, and I think it explains why good websites still lose buyers who had a simple question.
First, a note on the data. The 10,580 questions behind these numbers were generated for each company (what a buyer would plausibly ask, given its profile), not logged from real buyers. The 529 sites were picked by the people who ran scans, so this is not a random sample of B2B. Scans ran from Sep 8 to Oct 20, 2026. Page types were grouped by URL patterns, and a quarter of full answers came from pages that couldn't be classified. Read the shares as a rough shape, not exact counts.
What is answer distance?
Answer distance is the gap between the page where a buyer's question comes up and the page where your website answers it. Say a buyer on your pricing page wonders whether there is a minimum contract term. The answer exists, in paragraph six of a billing article in your help centre. Same website, but the buyer will probably never find it.
Most website reviews ask whether an answer exists. Answer distance asks two more questions. How far does the buyer have to go to find it? And would they ever think to look there?
Where do B2B websites actually answer buyer questions?
For every question a site answered in full (a concrete answer backed by text found on the company's own site), the scan recorded the page it came from. Across all 529 sites:
| Page type | Full answers | Share |
|---|---|---|
| Blog and resources | 872 | 14.1% |
| Help centre and FAQ | 850 | 13.7% |
| Docs and developer pages | 630 | 10.2% |
| Trust, security and legal | 622 | 10.0% |
| Product and feature pages | 478 | 7.7% |
| Pricing page | 369 | 5.9% |
| Case studies | 353 | 5.7% |
| Integrations pages | 223 | 3.6% |
| Comparison pages | 159 | 2.6% |
| Homepage | 113 | 1.8% |
| Other pages (unclassified) | 1,535 | 24.7% |
Blog, help and docs together answered 2,352 of 6,204 questions, or 38%. Leave out the unclassified pages and it is half of everything that could be placed. On 423 of the 529 sites, at least one full answer came from one of those three.
The pattern holds by topic, and it is strongest where the buyer is most specific:
- Integrations: 46% of fully answered integration questions were answered from blog, help or docs. Docs pages (20.3%) slightly beat the integrations pages built for the job (19.6%).
- Comparison: the blog answered 29% of comparison questions. Comparison pages answered 20%.
- Pricing: even here, the pricing page gave only 34% of fully answered pricing questions. The rest came from FAQs, help articles, docs and unclassified pages.
- By buyer role: 47% of full answers to technical buyers came from blog, help or docs, against 32% for procurement and finance buyers.
Why do the best answers end up in the docs?
The easy answer is that marketing pages are short by design. A homepage has room for a promise, not for a list of data regions. That is true, but it doesn't explain everything. Pricing pages exist to answer pricing questions, and they still gave only a third of the full pricing answers. Comparison pages exist to answer comparison questions, and the blog answered more of them.
Here is my guess at why. Specific answers get written down when someone has to answer the same question many times. On most teams, that is support, solutions engineering and product. They write for the reader they have: an existing customer. So the precise answers (how long setup takes, what the integration syncs, what happens at the seat limit) end up in the help centre and docs, written for people who have already bought.
Marketing pages are written for a visitor who hasn't asked anything yet. They describe the product in broad, pitch-level terms. Nobody's job is to carry the precise answer from the help article back to the pricing page, because the two pages have different owners and different goals.
So answer distance is not a content gap. Your website is organized by which team wrote each page. Buyers don't look for answers that way.
If the answer is one search away, does distance matter?
The strongest case against this idea sits in the same data. When an answer existed, the scanning agent usually found it right away: 84% of full answers turned up on its first search. Another 5.5% needed a second search, and 9.3% needed it to read three or more pages in full.
So for a machine, answer distance is close to zero. If buyers can search, why worry about where the answer sits?
Because people and machines now use your site differently, and both have a cost.
People don't search your help centre from your pricing page. Internal Storylane data from our sales team's notes at industry events in October 2026 makes the point. The message that drew the most interest was not about agents. It was that AI assistants now send buyers to your website with your rivals open in other tabs. That buyer has a specific question and a few minutes. If the answer is four clicks deep in a section labelled "Support", they ask the next tab instead.
Machines, on the other hand, read everything and quote what they find. When ChatGPT or an AI browser answers a buyer's question about your product, the source may well be a help article written for customers. It may carry internal jargon or details that were true when it was last edited. The machine found the answer, but nobody checked that it reads well to someone who hasn't bought yet.
Long answer distance means two bad outcomes at once. People don't find your best answers, and machines find them in a form nobody wrote for buyers.
How do you shorten answer distance?
Moving everything onto the homepage is the wrong fix. The help centre is the right home for precise answers. The job is to link to them from the right places and make sure they make sense to a buyer.
- Measure it on your own site. Take the 20 questions your sales team hears most. For each, note the page where the question comes up, the page where the full answer lives, and the clicks between them. More than two clicks, or an answer you can only reach by search, counts as long distance.
- Link, don't move. Put a one-line answer on the page where the question comes up, with a link to the full article. For example, a line like "Typical setup takes X days; here is the guide" on a pricing page, with your real number in it. That brings the distance to zero without copying the docs.
- Write help articles for prospects too. A prospect will read them, or an AI tool will on their behalf. Lead with the answer, put a date on anything that changes, and give each article an owner who knows buyers read it.
- Fill the real gaps. In the scan, 33% of questions were only partly answered and 6% were not answered on the site at all. No page or tool can answer what was never written down, so those need new writing.
- Make sure machines can reach it. Help centres behind a login, on a subdomain blocked to crawlers, or built in a way crawlers can't read are invisible to the tools buyers now use for research. The basics are in our pieces on answer engine optimization for B2B SaaS and whether you need an llms.txt file.
- Let something on the page read the docs for the buyer. This is where a website agent comes in.
Can a website agent close the distance?
We sell a website agent, RepX, so read this section knowing I have a reason to like the answer.
An agent removes answer distance in a simple way. The buyer asks on the page they are on, and the agent answers from wherever the answer lives. RepX draws on websites, FAQs, files, sales transcripts, slides, videos and interactive demos. So the billing article in paragraph six becomes a direct answer on the pricing page. Qualified leads and conversation summaries flow to HubSpot, Salesforce and Slack. Because the agent knows which page the buyer is on, it can also answer with that page in mind. We covered why that matters in page-level context for conversational AI.
RepX is best for teams whose precise answers are spread across docs, help articles and sales material, and who want buyers to get those answers on the page where they ask.
What to remember on Monday
Your website already knows most of what buyers ask. It has filed the answers under the team that wrote them, not under the question that needs them. Pick your top 20 buyer questions, find where each answer lives, and count the clicks. That number tells you more about how easy your site is to buy from than your homepage copy does.
If you want to see an agent answer your buyers' questions from your own docs, on the page where they ask, book a demo of RepX.
