credited vs a portfolio site, a README and LinkedIn
All three tell people what you built. None of them prove it. credited's proof is a tag shipped in the client's own site: nobody but the person who deployed it could put it there.
credited vs a portfolio site
- What a portfolio proves
- Nothing but your own word. Anyone can put a screenshot and a case study on a page.
- What credited proves
- The site itself carries your tag. CreditedBot re-checks it, so the proof stays current instead of going stale the day you stop updating a page.
- What you write
- Nothing. Paste one line in the site's
<head>, or let your coding agent do it through the MCP, and your profile builds itself. NDA work still lists, without the name. - What it costs
- A domain, hosting and the hours to design and maintain it. credited is free for up to 5 projects, €29 once for more.
credited vs a GitHub profile README
- What a README proves
- Nothing. It's a text file you edit yourself; a listed repo doesn't mean you shipped anything to production.
- What credited proves
- The tag is fetched from the live client site, not typed into a file in your own repo.
- What you write
- Nothing, and nothing to keep updating by hand. A README also can't show client or NDA work at all; credited lists it without the name.
- What it costs
- Free, and so is credited for up to 5 projects, €29 once for more.
credited vs LinkedIn
- What a LinkedIn post proves
- A claim in a post or the "Featured" section. Nobody checks it, and it scrolls out of sight in a day.
- What credited proves
- A standing profile CreditedBot keeps re-checking against the live site, not a post that ages out of the feed.
- What you write
- Nothing, and no need to post again every time you ship. Client work under NDA still lists, without the name.
- What it costs
- Free, and so is credited for up to 5 projects, €29 once for more.