Why does launch traffic die after two days?
Because a launch is an event and your site is a place, and once the event ends nothing carries people to the place anymore. The traffic didn’t die; it just never had anywhere else to go.
Here is the shape of every small launch I’ve done: post it, spike for a day, half the spike the next day, then a flat line so low it looks like an error in the chart. The launch worked. The problem is what happens after: the site sits alone, disconnected from everything else I’ve made, and every visitor who lands there hits a dead end.
What actually compounds?
Connections, not launches. Say you’ve shipped six things over two years. Each gets a modest trickle: some search traffic, an old backlink, a bookmark. Six trickles, six dead ends. Connect them, so that every site points at one page listing all of them, and the math changes: every visitor to any of the six is now one click from the other five, and the next thing you launch inherits the audience of everything before it. The trickles pool.
That’s the whole trick. It isn’t growth hacking; it’s plumbing. Most makers never install the plumbing because it’s boring, and because on launch day it feels pointless, one site linking to one other site. It pays off on ship number four, and by ship number nine it’s the difference between starting from zero and starting from everyone who ever found any of your work.
Why a corner badge instead of a footer link?
Two reasons. Consistency: a footer is different on every site, hand-edited, forgotten, styled seventeen ways. A badge is the same three lines everywhere, so placing it is a reflex instead of a decision. And identity: a footer link says “here is a URL”; a small pill with your face says “a person made this,” which is exactly the thing people follow. The mechanics of the snippet are in the three-line badge post.
Doesn’t updating all those sites become a chore?
Only if the links carry information. If every badge hardcodes your latest project, you’ve built yourself a maintenance treadmill. If every badge points at one hub page, shipping something new means editing one page, and every badge you placed over the years is instantly current. Old sites you’ve forgotten the passwords to still point to the right place. The badge is dumb on purpose; the hub is where the truth lives.
I built BuiltByBadge to make this a habit instead of a project: an AI skill that sets up the hub once, then asks at the end of every build whether the new site should get the badge. Say yes, and the plumbing extends itself.
Built by