Add the badge to Framer
Framer's custom code lives in site settings and applies to every page at once, which is what you want for a badge. You are not adding it to a page, you are adding it to a site. There is a start-of-head box and an end-of-body box; the badge belongs in the second.
Where the code goes
Site settings → General → Custom code. Not the per-page code panel. Site-level custom code is what makes the badge appear on every route including ones you add later.
Paste into End of <body> tag. The badge mounts itself onto <body> and carries defer, so it renders after your page has painted either way. The end-of-body box keeps it out of the critical path entirely.
Publish. Framer's editor canvas does not execute custom code. Publish and open the live URL to see it.
The code
<script src="https://maketaksh.com/badge.js" data-taksh="yourname" defer></script>Swap yourname for your handle. It is the one in your dashboard.
Custom code needs a paid Framer site plan
On the free plan the box exists in settings but the code is not injected into the published site, and nothing tells you so. If you have pasted the line, published, and the Network tab shows no request for badge.js at all, check the plan before you check anything else.
Checking it worked
Load the published page and look at the bottom corner. If nothing is there, it is almost always one of four things, in order of how often: the handle has no projects in it yet; the handle is wrong; the platform stripped the tag, as described above; or a content blocker ate it, check the Network tab for badge.js.
Once it is live, the Analytics panel in your dashboard lists every site the badge has been seen on, from the first page load, which is the fastest way to confirm an install on a site you cannot easily open.
Other setups
Webflow · Squarespace · All twelve setups
What the badge is, and why cross-linking your own launches is worth doing at all: the short version.