Made by@slashcloneGet found in search and see where sign-ups come from
@slashclone/website-traffic
Get your web app found in Google and AI search, and see which channels bring sign-ups. Sets up sitemap, robots, canonical URLs, share images, and structured data with a page checker, then consent-aware first-touch tracking from UTM tags and referral links, saved at sign-up. Includes a launch channel checklist. Engineering guidance, not legal advice.
- Activity
- New: be the first to try it
- Installs
- 0 installs
- Likes
- 0 likes
- Clones
- 0 clones
- 1# Launch and listing channels
- 3Copy this into the project's docs and fill in one row per channel. Research each channel's own submission docs before you write anything, and note the date you checked. Nothing here gets submitted by the agent: each listing signs in as the company, proves a domain, or accepts terms, so a person does that step.
- 5## Status key
- 7- **met**: the site or repo shows it today.
- 8- **missing**: it does not exist yet.
- 9- **unknown**: it could not be checked from here.
- 11## Before any listing
- 13- [ ] Final privacy policy and terms at stable URLs (reviewed by counsel)
- 14- [ ] A monitored support address
- 15- [ ] Logo in the sizes channels ask for (square, at least 512 px, plus a wide banner)
- 16- [ ] Three to five screenshots at common sizes, no personal data in them
- 17- [ ] One-sentence and one-paragraph descriptions, plain words, no superlatives
- 18- [ ] A demo or test account for reviewers, if the product needs sign-in
- 19- [ ] Share links for each listing carry `?ref=<channel>` or UTM tags, so sign-ups by source shows which channel worked
- 21## Channels to consider
- 23| Kind | Examples of what to look for | Fit | Requirements | Gap check | Owner | Submitted | Live |
- 24| -------------------------------------- | ------------------------------------------------------------------- | --- | ------------ | --------- | ----- | --------- | ---- |
- 25| Official registries for your ecosystem | package or plugin registries the platform itself runs | | | | | | |
- 26| Platform directories and marketplaces | app stores or integration directories where your users already look | | | | | | |
- 27| Community lists | curated "awesome" lists, community catalogs | | | | | | |
- 28| Aggregators | sites that ingest a registry automatically; claim the listing | | | | | | |
- 29| Launch sites | product launch boards, maker communities | | | | | | |
- 30| Software review and comparison sites | category pages where buyers compare tools | | | | | | |
- 31| Forums and newsletters | niche communities, weekly roundups | | | | | | |
- 32| Your own surfaces | README badges, docs footer, email signature, changelog | | | | | | |
- 34## Order
- 361. Free channels you fully control first (a registry entry, README badges).
- 372. The directory where your users actually look, once its blockers are cleared.
- 383. Aggregators that read from step 1; claim each listing.
- 394. Community lists and launch sites, spaced out so each gets attention.
- 405. Paid placements only after the free ones show which audiences convert.
- 42## Watch out for
- 44- Registries that never let you change or delete a published entry. Settle the name first.
- 45- Lists with an age rule (for example, a repo must be some days old).
- 46- Channels that are paused, winding down, or pay-to-play. Check before spending time.