BETA Shipping weekly
Ship once. Own your badge forever.
Drop one script tag during the build. Edit the badge from your OneBadge dashboard, and every site you have shipped stays in sync, without you touching it again.
It’s not a picture. Click it. That click just became a data point.
That’s the switch. Now point your badge at whatever matters this month.

The problem
Your badge is everywhere. You don’t control it.
Every site you ship adds another badge you will never open again. They go stale where they sit, and not one of them reports back.
| Site | Access | What you're trying | Status | |
|---|---|---|---|---|
dirtygoodco.com | Connected to OneBadge | No login needed. It updated itself. | ✓ Updated | |
ineduverse.com | Emailing the new owner, no reply yet | Whoever runs it now won’t give you access. | — — | |
annalia.beauty | WhatsApp · read 2 days ago | Going to WhatsApp them. | — — | |
activegreens.in | Team took over, no idea it’s yours | Checking if you still have FTP… | — — | |
whitestorkivf.com | The contact info you have is dead | Checking old contact info… | — — | |
portfolio.dev | Sent follow-up #3 | Sending first email. | — — | |
cafedelcorso.it | The business behind it closed | Need to reach whoever runs it. | — — | |
+ 43 more sites | — haven't started — | This is going to take weeks. | — — |
Baked into every page you ship
Your old name is still in the footer
If it broke, nobody would tell you
You have no idea if anyone clicks it
The Solution
Edit the badge. Never the site.
Your badge is served from your dashboard, not baked into the page. Change what it says or where it points, and every connected site follows in seconds.
One dashboard controls every badge
Change it once, everywhere follows
Know the moment one of them breaks
Views and clicks for every single site
The business case
The badge stays. The destination moves.
Most badges point at the same URL for years and quietly go stale. Change the destination once in OneBadge and every connected site follows, whether you shipped it last week or five years ago.
- The day you shipped it/portfolioIt sent people to your portfolio.Every visitor, for years
- Right now/launchNow it sends them wherever you need.One change. Live on every site.
- Whenever you want/anywhereNext month, somewhere else again.You decide when
How it works
One line of code. Nothing after that.
One script tag per site. No integration work, and nothing to maintain afterwards.
Design the badge
Choose a template, then set how it looks and where it sits. Floating or inline, either corner, dot, logo or emoji. The preview follows every change.
Paste one script tag
Copy one script tag into the footer or layout of any stack you use, like WordPress, Shopify, Framer, Webflow or static HTML. The badge appears and stays connected to OneBadge.
Change it without touching the site
Point the badge somewhere new whenever it suits you, from your dashboard. Every connected site follows. The sites themselves are never opened, never redeployed, never logged into again.
Before you install
Fair questions. Straight answers.
A credit badge is the small “Built by”, “Made with” or “Powered by” line in a website’s footer that credits whoever built it. Most are hardcoded into the page, so changing one means opening the site and editing it by hand. OneBadge serves the badge from your dashboard instead, so its text, style and destination can change on every site you have shipped without touching any of them.
If the site was built with OneBadge installed, you change it from your dashboard and every connected site updates. Nothing is republished and no files are edited. If the site does not have the script yet, you need access to it once to paste a single line into the footer or layout. After that one install, you never need the site again.
No. That is the entire point. The badge is served from OneBadge rather than baked into each page, so the text, the style and the link it points to are all changed in one place. A studio with fifty client sites updates all fifty without opening any of them.
No. The badge is a single script of about 8kb — roughly the size of a small logo file. That is the whole delivered payload: 6kb for the loader and base script, plus 2kb only if you switch on instant badge updates. Logos are served separately from storage, so they never bloat the script. The badge renders in its own container and does not affect the surrounding layout.
Your badges keep rendering. The script caches the last version it was served, so if OneBadge is ever unreachable the badge on your client's site carries on showing what it showed yesterday. It does not blank out, and it does not leave broken markup behind. For ordinary outages we notify affected users directly and fix them within a stated timeline rather than leaving you to find out for yourself.
Start here
Ship it once. Control it for good.
Paste the script while you still have access to the site. After that, everything the badge says and everywhere it points changes from your dashboard, on every site at once.
From the beta
What people notice once it is live.
The badge stops being decoration the moment you can point it somewhere new, watch what it sends you and know when it goes missing.