Whitepaper

What it is for

The format borrows its authority from government and standards papers: a sober title, a stated method, numbered sections, a reference list. Businesses publish them to show they understand a problem in depth, to earn links and citations from people writing about that problem, and to collect the contact details of readers who want the download. Those three aims pull in different directions. A gated paper collects leads and reaches almost nobody else; an open one reaches everybody and collects nothing.

What a crawler receives

A form is a wall to a crawler. A PDF behind one is not on the web as far as a machine is concerned, and even an openly linked PDF is a weaker object than an HTML page: no headings a parser can rely on, no schema, and its facts sit in a file that is separate from the page that names the business. This site’s own audit of 9,483 small-business sites, described in what 9,483 small business websites serve to an AI crawler, found sites whose most useful content, the price list or the service menu, existed only inside a PDF; the crawler, which fetched pages without executing scripts, read the page around it and nothing of the file.

The fix is not to abandon the format. Put the paper’s findings on an HTML page as well: the central numbers as sentences, the questions the paper answers as headings, the business identified once and consistently, and the PDF as a download from that page. An assistant lifts a passage; the passage has to exist somewhere it can reach.

Whitepaper and case study

A whitepaper argues from general evidence to a recommendation. A case study reports what happened to one named customer. The first establishes that a business understands a problem; the second that it has solved it before. They are often bundled, and they are frequently confused because both arrive as PDFs. The difference is what can be checked: a case study makes a claim about one real engagement, so it must name the customer and be true; a whitepaper can be judged on its sources alone.