Get credited for the work you can't show.
Clients don't allow a footer link. NDAs hide your best projects. One invisible tag in the site proves you built it, on a profile you can send anywhere.
<head>
<meta name="credited" content="cr_7f3kQm2xLp9vT4aZ8nRw1bYe">
</head>How it works
-
1
Add the project
Paste the site's URL and you get a token. Mark it private if the client can't be named.
-
2
Drop one line in the head
A meta tag, invisible to visitors, the same kind Google asks for to verify a site. Nothing to design, nothing for the client to approve twice. Teams and APIs can use a
/.well-known/credited.jsonfile instead. -
3
Deploy. That's the proof.
Nobody gets a tag into a client's site without access to it. We check the site, then keep checking every week. Your profile shows "verified since March 2026".
Why it works when nothing else does
- A screenshot
- can be faked in a minute.
- A GitHub graph
- proves you commit, not what you shipped.
- A testimonial
- needs a client who answers email.
- A tag in production
- needs nothing but the merge you already made.
Under NDA? Mark the project private.
Your profile still lists it, with the category and the dates. The URL and the client's name never appear. The token in their source code says nothing about you.
Private project
fintech, verified January to June 2026
verifiedQuestions clients ask
- "Why is there a strange tag in my site?"
- It's a verification tag, the same mechanism as Google Search Console. It has no script, loads nothing, and changes nothing for visitors. Send them to the crawler page.
- "What if the client removes it later?"
- Your history stays. The profile shows the dates it was live, for example "verified January to June 2026".
- "I work in Laravel, Next, WordPress…"
- Paste the tag in any layout. Packages for npm and Composer are coming, they wrap the same line.
Get credited.
Sign in, add a project, paste one line. Free for up to 5 projects.
Sign in with GitHub