About UneedLists
Why this exists, and the rules we hold ourselves to.
Last updated
The problem
Search a founder's name and you usually get a LinkedIn profile they last updated in 2021, a Crunchbase stub, and three pages about someone else with the same name.
Search their product and you get the product's own site, then a wall of low-quality directory listings — pages with a logo, a tagline, and nothing else — competing for the same query and each one adding a little less than nothing.
Neither result is under the founder's control, and both matter.
What we built
UneedLists is a launch platform where the page is the product.
Every listing is static HTML served from the edge, with the full content in the first response. Every page carries connected structured data — Product, Person, FAQ, Breadcrumb — in a single graph, so a search engine understands how the founder, the product and the category relate rather than having to guess.
Every product generates more than one page: its own, its category, its alternatives page, its comparisons, its launch week. Those pages link to each other and back, so a crawler entering anywhere reaches everything.
The rules we hold ourselves to
Thin pages do not get indexed. A profile with no bio and no shipped product emits
noindex. Publishing thousands of empty pages is how a directory gets classified as a doorway
farm, and that would sink the pages of everyone who did the work.
Paid placements never enter an organic ranking. They are labelled and carry
rel="sponsored". This is not generosity; a ranking that can be bought is not a signal, and a
directory that is not a signal is not worth a backlink.
Do-follow is earned. Verify your domain and you get real do-follow links. Do not, and you
get rel="ugc nofollow". The friction is the point — it makes spam submissions uneconomic,
which is what keeps the links valuable for everyone else.
Archives are permanent. A week page from two years ago is still live, still linked and still ranking. Deleting old pages throws away exactly the URLs that have had longest to accumulate authority.
How it is built
Astro with static prerendering for every page that should rank, server rendering only for authentication, voting and comments. PostgreSQL via Supabase, with row-level security so the database — not application code — is the authority on who can read and write what. Cloudflare for the CDN, WAF and bot protection.
The performance target is not a vanity metric: a page that takes four seconds to render does not rank, no matter how good the content is.