2026-08-03 · Jack Stovell

An AI-readable profile for freelance developers

An AI-readable profile for a freelance developer is one public page carrying the commercial facts GitHub does not: your stack in plain text, your availability, your rates posture and how to reach you. When a founder asks an assistant to find a contract developer with a specific stack, the assistant answers from pages it can read — and GitHub only proves you can code, not that you are for hire. The profile page is the half of your identity a hiring query actually needs.

Is GitHub enough to make you findable by AI?

It is probably your strongest existing AI-readable surface, and it is still not enough. GitHub serves real HTML without JavaScript, stays open to crawlers, and your profile README and pinned repositories are among the best-read pages about you anywhere — the platform-by-platform comparison is in can AI read Notion, Substack, Medium or your PDF CV?. But everything on it is evidence about code. The discovery moment for a freelancer is a query like "find a freelance React Native developer available for a three-month contract" — and availability, engagement type, rates posture and a contact route appear in no repository. GitHub answers "can this person build it?"; the profile page answers "can I hire them this quarter?". You need both, linked to each other.

What should the profile page actually say?

Four things, in plain text: what you build, whether you are available, how you engage, and how to reach you. Precision does the work. A crawler reading "TypeScript, React Native, PostgreSQL, AWS CDK — I build mobile products for early-stage teams" has everything it needs to match a hiring query; a wall of technology logos gives it nothing, because logos are images and images are not text a model matches on. The same goes for rates: you do not have to publish numbers, but state the shape — day rate, fixed-scope projects, retainer — so an assistant can tell a buyer how you work. Logo grids and coy contact pages are designed for humans skimming; you are also being read by machines that only see words.

Why is a portfolio SPA self-sabotage?

Because most AI crawlers do not execute JavaScript, so a client-side-rendered portfolio serves them a near-empty page. This is the developer-specific trap: the people most capable of building an impressive interactive portfolio are the most likely to ship one that is invisible to GPTBot, ClaudeBot and the rest. The failure is silent — the site looks perfect in your browser — and the mechanics are covered in JS shells and soft 404s. Server-render the profile page or pre-render it to static HTML, and confirm what a crawler actually receives with our free checker.

Does a developer need schema markup?

It is a small, cheap addition that makes your stack machine-legible: schema.org Person JSON-LD with a knowsAbout array naming the technologies you want to be found for. A minimal working version to adapt:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Person",
  "name": "Sam Example",
  "jobTitle": "Freelance Software Developer",
  "url": "https://samexample.dev",
  "knowsAbout": ["TypeScript", "React Native", "PostgreSQL", "AWS CDK"],
  "sameAs": [
    "https://github.com/samexample",
    "https://i.hilyt.it/samexample"
  ]
}
</script>

Swap in your own name, URLs and stack, paste it into the head of your profile page, and the sameAs array does double duty: it ties your GitHub identity and your profile into one entity instead of two disconnected fragments.

Beyond that sits the generic layer every profession shares — one canonical open page, a consistent bio across surfaces, identity links pointing in both directions — walked through in how to create an AI-readable profile of yourself.

What won't this fix?

It will not win you the contract or improve the code the client finds when they do look at your GitHub. Being AI-readable is necessary, not sufficient: it removes the failure where a hiring query surfaces other people because your commercial half was invisible, or your portfolio served an empty shell to the crawler. Whether you get the recommendation still depends on retrieval, competition and the model's behaviour — no page controls that, and nobody honest claims theirs does.

Preview your profile in 60 seconds