LaunchRepoDefinition
A directory badge is a small image with a link back to the directory — “Featured on X”, “Launched on Y” — that the directory asks you to embed on your website. Often it is a condition of the free route or of a particular link treatment; some directories check for it automatically before publishing, others rely on a checkbox you tick.
It is a reciprocal link. The directory gains a backlink from every listed site; you gain the listing.
Why it matters for a directory launch
Badges touch your production website, which is a different kind of permission than filling a form. Adding one means a code change, a commit, a deploy and a public footer that now advertises a third party. Doing it per directory on request, without a rule, ends with a footer of twelve badges — or with a “badge installed” box ticked on a site that does not show one.
How LaunchRepo handles it
WEBSITE-AND-EMAIL.md captures a per-product authorisation once: which repository and branch, whether badges may be added to the footer, committed, pushed and deployed. When a directory requires a badge, the agent reads the live rule, stores the source in badges.json, uses the official asset, checks for duplicates, deploys and verifies the public page before ticking any “badge installed” box. Declined permission means the platform is recorded and skipped, never faked.
See the term in the repository
LaunchRepo is 346 directory playbooks, a product context file and a submission tracker your own agent runs. Pay €99.98 once; use it for every product you own.
See pricing