Linkable assets

By Bill Hartzer · Hartzer Consulting · 25+ years in search, domains and expert witness work

What a linkable asset is

A linkable asset is a page on your own site that other people link to because it is useful to their readers, not because you asked. The category covers a handful of recognizable forms:

• Calculators and tools - anything that takes an input and returns an answer the reader would otherwise have to work out.
• Datasets and reference tables - the definitive list, the current rates, the full specification, kept up to date.
• Definitive guides - the page that answers a question so completely that writing a competing one looks like wasted effort.
• Templates, checklists and generators - artifacts people download, use and cite.
• Visual explanations - maps, diagrams and interactive charts that make something legible.

The defining property is not quality. It is necessity. A linkable asset earns links because a writer, mid-sentence, needs to point at something and yours is the best available thing to point at. That is far narrower than "we made something good", and it is why so many expensively produced assets earn nothing.

The other defining property is duration. Unlike a campaign, a working asset does not stop; it accumulates links for as long as it remains the best answer. That is why the successes look absurdly cost-effective in hindsight and the failures look like nothing but a bill.

How to build one that earns, step by step

1. Find the gap by looking for demand, not by brainstorming. Watch what people ask in communities in your sector. Look for questions answered with "you'd have to work it out yourself" or a broken link to something that used to exist. Search the phrases writers use when they need a source - according to, full list of - and see what they currently cite.
2. Check what already exists and be honest about it. If three good tools cover this, you need a decisive advantage - broader coverage, better maintenance, no signup wall - or you should build something else.
3. Identify who would link to it before you build it. Name the sites, the writers, the forum threads. If you cannot list twenty plausible linkers, the asset has no audience and polish will not create one.
4. Build the smallest version that fully answers the question. One clear input, one clear answer. Scope creep turns a six-week asset into a nine-month one that launches too late to matter.
5. Remove every barrier. No email gate, no account, no download to see the result. A gated asset is not linkable, because nobody links their readers to a form.
6. Make it citable. A stable URL, a plain title, a one-line description of what it does, a stated last-updated date, and a source note if it draws on data.
7. Launch it to the twenty people you identified. Assets are not discovered; the first fifty links are earned by telling people, and after that discovery takes over.
8. Maintain it visibly. Update the data, fix the edge cases, show the date. An asset that goes stale loses its links, quietly.

What it costs in time and effort

Cost is dominated by the form. A well-researched reference table costs research time and nothing else. A definitive guide costs writing time from someone who genuinely knows the subject. A calculator costs design and development, plus - and this is what people forget - the obligation to maintain it forever. An interactive dataset costs all of the above plus a pipeline to keep it current.

Three cost drivers dominate. The first is the accuracy requirement: a tool that produces wrong answers is worse than no tool, so anything touching tax, law, medicine or engineering carries a review cost that dwarfs the build. The second is maintenance, a permanent operating cost rather than a project cost; the most common way a successful asset dies is that the person who maintained it moved on. The third is promotion, routinely under-budgeted because teams assume a good tool markets itself. It does not.

Three to six months to meaningful link accumulation is normal, and the curve is slow at first and then compounds. Anyone promising links in the first month is describing a promotion campaign, not an asset.

When it works and when it does not

It works when there is a recurring, specific need that is currently unmet or badly met; when your organization has expertise or data that makes your version credible; and when you can commit to maintaining it. It works especially well in sectors with numbers that change - rates, regulations, specifications, deadlines - because the maintained reference beats the static article every year.

Now the honest part, and it is the most important paragraph on this page. Most linkable assets earn nothing. Not few links - none. I have watched teams spend a quarter building a beautifully designed calculator that attracted a handful of links, all from their own agency's blog and two roundups. The reason is almost never execution. It is that nobody needed it. The idea came out of a brainstorm rather than out of observed demand, nobody checked whether an established alternative already owned the space, and no list of plausible linkers was ever written down.

Specifically, it does not work when:

• The need is imaginary. A tool that solves a problem people happily solve in their heads earns nothing.
• A better version exists and is maintained. Second-best reference pages do not get cited.
• It is gated. Writers will not send readers to a signup form.
• The topic has no writers. Someone has to be producing content that needs to cite something.
• Nobody will maintain it. A stale tool loses trust, then citations, then links.

Common mistakes

• Building before validating demand. The defining error of the tactic. Evidence of demand is people asking, not a team agreeing it would be cool.
• Confusing effort with value. A nine-month interactive experience is not more linkable than a well-made table. Linkers reward usefulness, not budget.
• Gating it. Every barrier between the click and the answer removes linkers.
• Burying it. Assets placed three levels deep with no internal links, no navigation entry, and no promotion behave as if they do not exist.
• Letting it rot. Undated pages with last year's figures get replaced by the competitor who bothered to update.
• Changing the URL. Redesigns that move the asset destroy accumulated links. Links are lost overwhelmingly through editorial change rather than dead pages - on a profile I analyzed, 97.4% of lost links were lost while the source page was still reachable - but a URL change makes you the cause of your own losses.
• Building the asset for the brand rather than the user. Heavy product placement inside a tool reduces the chance an editor will link to it.
• Treating the launch as the finish. The first fifty links are earned by outreach; the next five hundred arrive on their own, but only if the first fifty happened.

A worked example

Two versions of the same decision, at a company selling shipping and logistics software.

The version that fails. The marketing team runs a workshop and decides to build an interactive "supply chain maturity assessment" - twenty questions, a scored result, a personalized PDF report delivered by email. It takes four months and a design agency. On launch it earns links from the agency's portfolio page, two industry newsletters that cover product launches, and nothing else. Nobody needed a maturity score, the result is gated behind an email address, and no writer has ever needed to cite a self-assessment quiz.

The version that works. Someone reads the company's support tickets and notices the same question arriving weekly: which documents are required to ship a given commodity to a given country this month. The answer exists, but it is scattered across regulator sites and changes constantly. The team builds a plain lookup - two dropdowns, a document list, a source citation for each requirement, and a visible last-updated date. It takes six weeks. They send it to the twenty forum threads and trade writers who had been answering that question by hand.

The second version is uglier, cheaper, and earns links every month for years, because freight forwarders, trade journalists, and other people's blog posts all need somewhere to point when the question comes up. The difference was decided before either project started: one began with observed demand, the other began with a workshop.

How to measure it

Measure an asset on a cumulative curve, not a campaign window. The core number is referring domains to the asset URL over time, segmented by Trust Flow so you can distinguish real editorial citations from scrapers and aggregators. A healthy asset shows a small launch spike from your outreach, a trough, and then a slow, persistent climb. If the climb never starts, the asset failed and no further promotion will rescue it - that is your signal to stop spending on it.

Track three supporting measures. Usage, because an asset nobody uses will not be linked for long. Rankings for the question it answers, since organic discovery is what produces links without effort. And unlinked mentions, which for tools are common - people name a tool in a forum post without linking it - and are worth reclaiming.

Calibrate against reality before setting a target. On a twenty-year-old profile of 22,260 referring domains where nothing was bought, only 446 domains reached Trust Flow 41 or above, roughly 22 a year, and 69.3% of all referring domains were Trust Flow 0. An asset that adds a steady handful of strong domains a year is doing well. Also watch for concentration: on that same profile the top 100 referring domains accounted for 84.3% of all links, and a single sitewide link produced 219,159 of them. If your asset's link count is dominated by one directory linking sitewide, you have one link, not thousands.

The verdict

Linkable assets are a genuinely good tactic with a terrible average return, and both halves of that sentence are true at once. The winners earn links for a decade at a cost that eventually rounds to nothing per link. The losers - the majority - consume a quarter of a team's capacity and produce a page nobody ever links to.

The variable that decides which one you get is not budget, design or technology. It is whether you found a real, observed, recurring need before you started building. Teams that begin from support tickets, community questions and the phrases writers use when hunting for a source tend to succeed. Teams that begin from a brainstorm tend not to, however well they execute.

Build small, build fast, build the least glamorous version that fully answers a question people are demonstrably asking, and commit up front to maintaining it. If you cannot name twenty sites that would plausibly link to the thing, do not build it - put the same effort into original research and statistics instead, where the demand is easier to verify in advance.