Three field reports landed on Indie Hackers this week, and none of them was about a traffic tactic. One developer shipped 88 browser tools and search sent him 8 sessions in thirty days. Another published about 6,500 pages in two weeks and watched his impressions fall to zero, including for his own brand name. A third went from 48 to 166 Google clicks in 28 days without writing more guides.
Read together, they answer a question I have been avoiding about my own free PDF tools site: I keep adding tools and calling it marketing. The pages are the problem, not the count.
The short version
- A tool page is a form, not a document. If the HTML that arrives carries 80 words of interface labels, there is nothing for a search engine to match.
- Page count is not authority. Thousands of thin pages can suppress a whole domain, brand query included.
- The pages that move have something only their owner can publish: real data, real tests, real screenshots.
- Retitle from queries you already appear for. Search Console is a list of words people actually used, not a keyword tool.
- Fix the crawl layer before writing anything new: duplicate URLs, overlong titles, pages that render empty.
Three numbers from one week
| Site | What the owner did | What happened |
|---|---|---|
| handytk.com | Built 88 browser tools, each with its own title and keywords | 281 sessions from direct traffic, 8 from organic search; one tool page got 6 views |
| calcbloc.com | Published roughly 6,500 programmatic tax pages in two weeks | Impressions went to zero, brand name included; he noindexed all 6,500 |
| batteryhealthlab.com | Published one page of real battery data, retitled pages to match queries, cleaned up the crawl | Clicks 48 to 166, impressions 7.46k to 21.8k in 28 days |
The first row is the one I recognise. handytk.com had 270 active users, 381 page views and 1.3K events over thirty days; 281 sessions came from people who typed the domain, eight from search. He had written titles for “SVG to PNG” and “PDF merge”, the phrases the established tools own, and Google sent almost nobody.
His own diagnosis is worth repeating: the homepage and the blog got more traffic than any tool page. People were curious about the project, then left without using the thing it exists for.
Why a tool page has nothing to rank with
A tool page has a structural handicap that a blog post does not: the useful part is behaviour, not text. The page says “Select file”, “Merge”, “Download”. Everything that answers a query — what it does, when to use it, what it costs you in privacy, what it does badly — is missing because the tool works, so nobody writes it.
Then add rendering. If the tool is a client-side app, the HTML the crawler receives first can be an empty shell with a title and a bundle tag. Google can execute JavaScript, but on a budget and on its own schedule. A page whose text only appears after JavaScript has to earn that second pass. Most tool pages never do.
That is my own site’s problem. My free PDF tools at pdffold.com run entirely in the browser, which is the honest selling point and also why most of what a visitor sees is drawn by JavaScript. I built the tools and assumed the pages would be found because they existed. The 88-tool report is what that assumption looks like when measured.
What the site that climbed actually changed
The battery site is the useful counter-example because the changes were small and none of them was “publish more guides”. Four moves, in his own account:
He published something nobody else had. Battery reports from four real laptops — his own two, his sister’s Lenovo, his brother’s HP — with a chart and a downloadable CSV, including the odd values: a battery that tripled for a day, 67 years of AC time in a week, a cycle count that was just a dash. That page could not have been written by anyone with a keyword list.
He retitled pages to match real queries. Search Console showed impressions for phrases his titles did not answer, so “Battery Health Percentage” became “How to Calculate Laptop Battery Health: Formula + Calculator”, and he added a page for an exact error message people were searching, because the report saves somewhere they cannot find.
He fixed the boring layer. A crawl found titles and descriptions that were too long, the tools index reachable at two URLs, and a broken link. None of that is exciting. All of it was real.
The caveat matters: after 28 days the data page itself was still “crawled, currently not indexed”, and AdSense had rejected the site three times for low value content. The clicks came from the cluster around the data, not from that page ranking. This is a slow repair, not a switch.
What I am doing to my own tools site
In order, because the order matters. Fixing the crawl layer after writing new pages wastes the new pages.
1. Find out what actually arrives. Fetch a tool page the way a crawler does and count the words in the HTML. Under about 150 and there is nothing to index; everything else is decoration.
curl -sL "https://your-site.com/tool/" \
| sed -e 's/<[^>]*>/ /g' \
| tr -s ' \n' ' ' \
| wc -w
2. Make the page arrive with text. For my site that means pre-rendering each tool page to static HTML at build time: heading, the job explained, limitations, privacy note, and the output of a sample run. Same tool, same interface, but the first response is a document.
3. Pick one page to be the original-data page. Not a new tool. One page of measurements I can run: how much a PDF shrinks at each compression level, how long a 200-page merge takes in a browser tab, which files break. Nobody else has those numbers.
4. Rewrite titles from Search Console, not from imagination. Whatever query already gets impressions is the language to use. Impressions without clicks mean the title is not answering that query.
5. Collapse duplicate URLs. Trailing-slash variants, parameters, print views, the tools index at two addresses. One canonical per page, one sitemap entry.
6. Point the writing at the tools. The 88-tool case shows blog posts outrunning tool pages. Not a reason to stop writing; a reason to write the post that ends with the tool. “How to merge PDFs without uploading them” is a page someone searches for, and it has somewhere to send them.
The one-page test before you build tool 89
If you already run a tools site, run this on a single page this week instead of starting another tool:
- Does the raw HTML contain at least 150 words about the job, in the response, before JavaScript runs?
- Does the title use the words someone would type, in their order?
- Is there one thing on the page that no competitor can copy without doing the work — measurements, screenshots, failure cases?
- Does the page link to the two pages most related to it, and do those pages link back?
- Can it be reached at exactly one URL?
Five yeses on one page beats eighty-eight pages of “Select file”.
This is client work too
When a small business asks why the site is not ranking, the reflex is “add more pages”. The three reports point the other way: fewer pages, each carrying something real, plus a crawl that is not fighting itself — a conversation I can defend with a Search Console screenshot instead of a promise.
What I am doing this week
One page: my merge tool, static HTML with 300 words on what merging in a browser does to file structure, one table of measured times from real documents, and links to two guides that already exist. Then I will wait 28 days and look at impressions, the way the battery site did, instead of adding tool number 89 and hoping.
Two prerequisites: connect Search Console before you touch a title, because a retitle without query data is guessing in a different font, and if a core update is rolling, do not read a bad week as a verdict. Then plan the writing with the one-afternoon plan I use.

Leave a Reply