How to Launch a Small Web Tool for Free: One Page, One Query, One Job
A small web tool is one page that does one job, such as a calculator, converter or generator, and it is usually found through the search for that job. Launch it by choosing the query first, giving a result within seconds without sign-up, making each result shareable by link, and describing the tool with structured data. Then share it directly while search takes its time.
What is different when the whole product is one page?
For most products the landing page and the product are separate things. For a small tool they are the same page. Someone types a job into a search box, lands on your page and is either helped within seconds or gone. There is no onboarding, no trial and no second visit to rely on, so every decision in the launch comes back to one question: what will this visitor see in the first twenty seconds?
It also changes where the audience comes from. A tool is found by the query it answers, so choosing that query is the launch strategy, not a marketing step that follows the build.
How do you choose the query before building?
- Write ten phrasings of the job as a person would type it: “convert”, “calculate”, “generate” plus the object.
- Search each one. If the results are mostly tools, the searcher wants a tool, and you have a place to compete. If the results are mostly articles, a bare tool may not match the intent.
- Look at what the existing tools do badly: a sign-up wall, ads over the result, a slow page, no way to copy the answer.
- Pick the query where you can be clearly better on one of those, not on all of them.
What should the first twenty seconds look like?
- The input is on screen without scrolling, with an example value already filled in, so the result appears on arrival.
- No sign-up and no email gate before the answer. Ask for nothing until the visitor has what they came for.
- A copy button on the result, and a download if it is a file. People take the answer and leave; make that satisfying.
- Instant response. If it works in the browser, do the work there, which is quick and also means you hold no data of theirs.
- A plain line on privacy: whether anything the visitor types leaves their browser.
Below the tool, add a short written section: how the result is calculated, a worked example and a note on where it can be wrong. That text is what lets a search engine understand the page, and it is what a careful visitor reads to decide whether to trust the number.
How should you describe the tool to search engines?
Google documents SoftwareApplication structured data, read on 13 November 2026, as a way to mark up software information on a page so that details of the app can show better in Search results. Its page lists the properties, shows examples in several formats and tells you to validate the markup with its Rich Results Test and to inspect the live page afterwards. Not every tool will get a rich result, and nobody can promise one, but accurate markup costs little. See the Google documentation on software app structured data for the current requirements.
The website pre-launch SEO checklist covers titles, descriptions and the other basics, and the SEO from day one playbook explains how to plan content around the tool.
Where do you share it while search catches up?
Search takes time and nobody can say how long, so do not wait for it. Publish a page on the free launch board, where the link to your tool is a normal followed link, and share the tool in communities of the people who face the job, as an answer to a question someone asked. A tool is easy to try, which suits boards that ask for something people can use right now; Show HN’s guidelines say as much. Our own free maker tools are examples of single-job pages, and the free startup directories list more places to submit.
| Number | Source | What it tells you |
|---|---|---|
| Visitors who get a result | Your own event count | Whether the page works |
| Result copies and shared links | Event count on the buttons | Whether people value the answer |
| Impressions and clicks for your query | Search Console, once the page is indexed | Whether the query choice was right |
| Return visits | Analytics | Whether it earns a place in a routine |
Ideas for tools often start as annoyances; the board’s developer tool ideas and the weekend project ideas list include several that fit in one page.
Frequently asked questions
How do people find a small web tool?
Mostly through a search for the job it does, so the query you choose is the strategy. Beyond search, they arrive from shared result links and from communities where someone asked a question your tool answers. Plan a first month of direct sharing, because ranking takes time and nobody can promise a position.
Should a web tool ask for an email before showing the result?
No. Give the answer first. A gate in front of a one-page tool sends most visitors back to the search results, where another tool without a gate is one click away. If you want an email, offer something extra after the result, such as saving it or getting a reminder.
Do I need structured data for a small tool?
It is optional. Google documents SoftwareApplication markup for showing app details in search, and says to validate it with its Rich Results Test. It will not guarantee a rich result or a ranking, so treat it as accurate labelling that is cheap to add.
How many tools should I launch at once?
Start with one, built to be clearly better at something than the existing options. Publishing many near-identical pages that differ only by a keyword is the pattern search engines demote. Add the next tool when the first has users and you know what people wanted from it.
Written by Post your build ideas with AI assistance and edited for this site. Where a page names another product, the facts came from that product’s own pages on the date shown above; terms change, so check them before you rely on them. About the publisher.