GitHub

Create a public repository named like your username with a README.md — GitHub renders it on your profile. README and profile website links on github.com are nofollow.

1. Create the profile repo

   New repository named exactly your GitHub username (e.g. octocat/octocat), public, with a README.

2. Write the README

   Introduce yourself or your product and include one clear link to your marketing site or docs.

3. Set profile website

   Profile → Edit profile → Website — paste the same primary URL for visitors who skip the README.

Publish a static site or docs on github.io (or a custom domain). Unlike READMEs on github.com, Pages serves your HTML without adding rel=nofollow to outbound links you author.

1. Choose Pages source

   Repository Settings → Pages — deploy from a branch or GitHub Actions workflow.

2. Publish content

   Add HTML or Markdown with contextual copy; place your canonical product URL in header, footer, or About page.

3. Verify rel attributes

   Inspect a live outbound link on your Pages URL — it should not include nofollow unless you added it in your template or markup.

Publish an OCI image to GitHub Container Registry under your user or org. The package page lives on github.com — README and repo links use GitHub’s nofollow sanitizer, similar to profile READMEs.

1. Publish the image

   Push a tagged image to ghcr.io with a workflow or docker push; link the package to the source repository.

2. Set package metadata

   Add description and source-repo metadata; treat external links as discovery for people, not dofollow SEO from github.com.

3. Surface install docs

   In the repo README, link the GHCR pull command and your primary site — expect nofollow on github.com-rendered anchors.