Free tools as link magnets: why a calculator outranks a blog post
A guide explains how to work something out. A tool works it out. When a writer finishes explaining, they link to the tool, because that is what their reader wants next. Building one small tool is the most reliable link asset a product can own, and it keeps earning while you do something else.
By Théophile Louvart, founder of Porteur · Updated 15 September 2026 · Markdown
Why tools get linked and posts do not
Think about what a writer needs at the end of a paragraph. They have just explained how to calculate something, or check something, or convert something. The honest next sentence is: here is a tool that does it for you.
They will not link to your competing explanation of the same thing, because that makes their own page redundant. They will link to a tool, because it completes their page instead of replacing it.
- A tool is a complement to other people's writing, not a competitor to it.
- It stays useful when the article ages, so the link is rarely removed.
- It gets bookmarked, which is a kind of link you cannot buy.
- It ranks on its own searches, which are short, specific and unusually commercial.
How to pick a tool worth building
The tools that earn links share a shape. One job, no account, an answer in seconds.
| Test | Pass | Fail |
|---|---|---|
| How many jobs does it do | One, named in the page title | Six, behind a dashboard |
| What does it ask for | A URL, a number, a paste of text | An email address before the result |
| How long to the answer | Seconds, in the page | A report by email, later |
| Who is it for | Anyone who reads the guides in your category | Only your existing customers |
| Would a writer link to it | Yes, as the next step after their explanation | Not without explaining your product first |
List the calculations in your field
Every category has them: a rate, a conversion, a limit, a checker. Write down ten that people do by hand or in a spreadsheet.
Search each one
If the results are articles explaining the calculation, there is room for a tool. If the first five results are tools, only build if you can be clearly better or clearly simpler.
Check who writes about it
Look at the guides that rank. Do they link out to tools at all. Some categories link generously and some never do, and you want the first kind.
Pick the one you can ship in a week
A small tool live beats a large one planned. You can always add the second.
How to publish it
The tool needs its own page, at its own URL, named after what it does. Not a tab inside your app, and not behind a login.
- The URL says the job: yourproduct.com/tools/status-page-checker.
- The tool is the first thing on the page, above the explanation. A visitor should be able to use it without scrolling.
- The explanation goes underneath: what it checks, how to read the result, what it cannot do, the limits.
- The result is readable and copyable, so someone can paste it into a ticket or a thread.
- No account, no card, no email gate. A gate is the single fastest way to lose the link.
- The page works without JavaScript for the parts that can, because the crawlers feeding AI answers do not run scripts.
Worked example. PingFox builds a status page checker at pingfox.com/tools/status-page-checker: paste a URL, get whether the page is reachable, what it returns and how fast. Under it, six hundred words on what a status page should do and the mistakes it lists. The tool earns the links; the writing earns the search traffic.
Tell the right people once
A tool nobody knows about earns nothing. The launch is small and one-off, and then you leave it alone.
The pages that explain the job
Find the guides that rank for the calculation your tool performs, and write one paragraph to each author: your reader is asking for this at the end of your section, here it is, free, no account.
The resource lists in your field
The pages that collect tools for practitioners. Submit through the form when there is one.
The communities where the question gets asked
Answer a real question with the tool, once, as the person who built it. Not ten threads in a day.
The launch sites, if it stands alone
A genuinely useful free tool is a fair thing to launch on the product and maker communities, separately from your paid product.
After that, stop pushing. Tools accumulate links slowly and from people you never contacted, which is exactly why they are worth building.
The maintenance nobody mentions
A tool is a promise that keeps being made. A broken one is worse than none, because the links point at an error.
- Check it works after every deploy of the main product, automatically if you can.
- Watch what it costs. A tool that calls a paid API needs a limit per visitor and a ceiling per day, or a busy week becomes a bill.
- Rate limit it, so an automated script cannot run it a thousand times an hour.
- Keep the URL forever. Renaming a tool that earned links throws the links away.
- Update the explanation when the underlying rules change, and date the page.
We build free tools for exactly this reason, and the ones that cost money per run sit behind a free account with a small daily allowance, which is the honest way to keep a tool free and alive.
What to measure
A tool has three jobs and each has its own number. Keep them separate or you will conclude the wrong thing.
| Job | What to watch |
|---|---|
| Earning links | Referring domains to the tool page, and whether a person would recognise them |
| Earning search traffic | Impressions and clicks for the tool page in Search Console |
| Earning customers | How many people who used the tool later reached a product page or signed up |
The third number is usually small and that is fine. A tool earns its place on the first two, and the third is a bonus that grows once the tool has been around long enough to be the one people remember.
Questions
They earn them more reliably than articles, because a tool completes somebody else's page rather than competing with it. The links arrive slowly and from people you never contacted: writers finishing an explanation, maintainers of resource lists, and readers answering a question in a thread.
One job, no account, an answer in seconds, and a URL that names what it does. If it needs an email address before it produces the result, writers will not link to it, because their reader would hit a wall.
The version people link to should be, yes. That is what makes the link defensible. If the tool costs you money on each run, put a small free allowance behind a free account and say so plainly on the page, rather than removing the free path later.
On your own domain, at its own path, such as /tools/name-of-the-job. Not on a separate domain, where the links accrue to something you may abandon, and not inside the logged-in app, where a crawler and a curious reader both stop at the login.
One, properly, then judge. A single tool that works and stays up beats five half-built ones, and maintaining each is a standing cost. Build the second when the first is earning links without your attention.
Check my site, free
Paste your URL and the free check reads your site and the searches around it in about thirty seconds, including the tool-shaped searches in your category that nobody has built for yet.
- Free check, no card
- Read-only, your own accounts
- Readable by your agent
Read next
- GuideResource page link building, done without being a nuisance
- GuideOriginal research: the one thing a small product can publish that earns links for years
- GuideHow to get backlinks for a small product site
- GuideThe outreach email that gets a reply
- GuideProgrammatic SEO for a small product: page families that earn
- GlossaryLink building
- GlossaryReferring domain
- GuideSEO for developer tools: docs, comparisons, and the error message