Install one embed on your site, then collect, reorder, and publish directory badges from one dashboard—without another deployment.

The page shows a script embed, while the FAQ describes server-rendered markup. For a static site, which installation keeps new badge links visible to crawlers without rebuilding? A short Astro or plain-HTML example, including what happens if the embed request fails, would make that distinction clearer.
Funny timing. I'm hand-pasting directory badges into my footer right now, which is exactly the problem this solves. I like that the badges render server-side so crawlers can still see the links. Does the free plan's 'Powered by' line count as a link back to you? That would help me decide between the free plan and the $6 one.
This solves a pain we just lived through — our team hand-added the Fazier badge to our footer this week to qualify for launch, and every future badge change would otherwise mean another full deploy cycle. The single-embed approach with collecting and reordering badges from one dashboard is exactly the right fix for that. One suggestion: offering a server-rendered or static markup option alongside the script embed would help sites that care about SEO and first-paint performance.
We did exactly this by hand today on cotlet.dev: hardcoded the StartupBase and Fazier badges into an Astro footer and pushed a redeploy. One thing I'd want to know before switching: some directories verify the badge by crawling your page, and their checker may not run JavaScript. Have you confirmed that Fazier's and StartupBase's verification picks up a badge added through Badge Relay? A short list of directories where verification is known to pass would settle it.
We just went through this: hand-adding directory badges to a homepage that exists in six languages, then redeploying for each one. Two practical questions: does a directory's automated "verify badge" check (like Fazier's) detect a badge served through your embed? And can one embed serve all language versions of a page, or do I install it per page?
Timely: we hand-added directory badges to two sites this week. One thing we ran into: some directories serve the badge image from a host that sets a cookie, which fails Lighthouse's third-party-cookies audit, so we self-host that image. Does Badge Relay hotlink each directory's image or serve it from your own domain? And does it keep the exact href a directory checks for, e.g. a bare https://fazier.com with no UTM parameters?
Funny timing — I'm in the middle of submitting my own product to another directory right now and need to hand-add a badge to my footer, which is exactly this pain. Editing HTML, redeploying, re-checking it renders right... every single time. What I'm curious about: does the embed render badges server-side for SEO, or is it a client-side script? And can I control which badges show on which pages? If it supports per-page rules, this would save a lot of footer maintenance over time.
Timely for me. I just added a directory badge to my footer by hand, using a <picture> tag so it switches between the light and dark badge image with prefers-color-scheme. Two questions: can the dashboard serve light/dark variants of a badge like that? And does the embed still work on a site with a strict Content-Security-Policy, or does the script need to be allowed explicitly?

The page shows a script embed, while the FAQ describes server-rendered markup. For a static site, which installation keeps new badge links visible to crawlers without rebuilding? A short Astro or plain-HTML example, including what happens if the embed request fails, would make that distinction clearer.
Funny timing. I'm hand-pasting directory badges into my footer right now, which is exactly the problem this solves. I like that the badges render server-side so crawlers can still see the links. Does the free plan's 'Powered by' line count as a link back to you? That would help me decide between the free plan and the $6 one.
This solves a pain we just lived through — our team hand-added the Fazier badge to our footer this week to qualify for launch, and every future badge change would otherwise mean another full deploy cycle. The single-embed approach with collecting and reordering badges from one dashboard is exactly the right fix for that. One suggestion: offering a server-rendered or static markup option alongside the script embed would help sites that care about SEO and first-paint performance.
We did exactly this by hand today on cotlet.dev: hardcoded the StartupBase and Fazier badges into an Astro footer and pushed a redeploy. One thing I'd want to know before switching: some directories verify the badge by crawling your page, and their checker may not run JavaScript. Have you confirmed that Fazier's and StartupBase's verification picks up a badge added through Badge Relay? A short list of directories where verification is known to pass would settle it.
We just went through this: hand-adding directory badges to a homepage that exists in six languages, then redeploying for each one. Two practical questions: does a directory's automated "verify badge" check (like Fazier's) detect a badge served through your embed? And can one embed serve all language versions of a page, or do I install it per page?
Timely: we hand-added directory badges to two sites this week. One thing we ran into: some directories serve the badge image from a host that sets a cookie, which fails Lighthouse's third-party-cookies audit, so we self-host that image. Does Badge Relay hotlink each directory's image or serve it from your own domain? And does it keep the exact href a directory checks for, e.g. a bare https://fazier.com with no UTM parameters?
Funny timing — I'm in the middle of submitting my own product to another directory right now and need to hand-add a badge to my footer, which is exactly this pain. Editing HTML, redeploying, re-checking it renders right... every single time. What I'm curious about: does the embed render badges server-side for SEO, or is it a client-side script? And can I control which badges show on which pages? If it supports per-page rules, this would save a lot of footer maintenance over time.
Timely for me. I just added a directory badge to my footer by hand, using a <picture> tag so it switches between the light and dark badge image with prefers-color-scheme. Two questions: can the dashboard serve light/dark variants of a badge like that? And does the embed still work on a site with a strict Content-Security-Policy, or does the script need to be allowed explicitly?
Find your next favorite product or submit your own. Made by @FalakDigital.
Copyright ©2026. All Rights Reserved