Start with a real project and a useful destination

A GitHub backlink may appear in a profile website field, a profile README, a repository description or project documentation. These contexts have different purposes. A profile identifies a maintainer; a README explains a project; documentation helps someone use it. A link belongs where it serves that purpose. Creating unrelated repositories, issues or comments merely to place a URL does not turn them into useful project contributions.

Keep profile fields and Markdown contexts separate

GitHub documents profile information and profile READMEs separately. In a Markdown context, a descriptive label and destination form a link, but the source Markdown does not tell you every attribute of the rendered anchor. If you control an account or repository, use its supported editing flow and check the resulting page. Do not treat a profile website field, free-text bio and README as interchangeable fields. The local sample below represents an authored website reference, not GitHub’s renderer. For your own account, sign in and open https://github.com/settings/profile (avatar menu, settings, public profile). Enter the intended project URL in the website/URL field when available, then update the profile and check its public page. For a repository README you control, open README.md, choose the pencil editor, and add this Markdown: [Read the measurement-tool guide](https://converter.example/guide). Replace the example address with the real guide; converter.example is a placeholder. Preview the change, write a descriptive commit message, then commit on an allowed branch or use the required pull-request workflow. A proposed change is not yet a published default-branch reference. A profile README is a different context: it requires a public repository named exactly like your username and a nonempty README.md at its root; managed user accounts do not support it. Reopen the resulting public profile or repository page and inspect the actual link. The workflow follows documentation; no authenticated editor was operated for this guide.

Choose references for a fictional measurement tool

Our fictional project converts measurements and has a public usage guide. A maintainer’s profile can identify the project’s website, while the README should direct users to the relevant installation or usage instructions. A general promotional landing page is a poor replacement for the unit-conversion explanation promised by the text. The worksheet compares the source context, intended destination and observation needed before counting a reference. The sample link stays within this page and uses nofollow me deliberately for inspection.

  • Profile website: Example observation: Identify a maintainer’s relevant website; Evidence to record: Website field in the exact public profile; Action if it differs: Inspect separately from the bio
  • Profile README: Example observation: Explain work and useful next steps; Evidence to record: Rendered README anchor and destination; Action if it differs: Do not infer attributes from Markdown alone
  • Repository README: Example observation: Help someone use a specific project; Evidence to record: Project version, page context and target guide; Action if it differs: Keep documentation relevant and current
  • Observed attributes: Example observation: Three public contexts checked on 2026-10-27; Evidence to record: Source, target and rel from each captured response; Action if it differs: Do not generalize the sample to all GitHub links
  • Maintenance: Example observation: Documentation and access may change; Evidence to record: Public availability, version and review date; Action if it differs: Repeat the observation when context changes

Read attributes in the exact observed context

On 27 October 2026, a signed-out HTML inspection of github.com/sindresorhus found nofollow me on its website-field link to sindresorhus.com/apps and nofollow on a profile-README link to sindresorhus.com/blog. In github.com/github/docs, a README reference to docs.github.com/en/contributing had no rel attribute in that response. These are three dated context observations, not defaults for every account or proof of ranking credit. The repository reference also stays within GitHub’s broader domain family; it is not an independent SEO experiment.

Make the inspection repeatable

Record source URL, page context, target URL, observed rel tokens, access state and date. Inspect the rendered element when checking a real page, and distinguish it from stored Markdown or a server response captured earlier. If GitHub changes the page or adds access restrictions, repeat the check instead of copying the old result. For your own project, verify that documentation matches the version people use and that the target remains public where intended. Never expose private repository material to manufacture a public reference.

  • Use references relevant to a real project.
  • Separate website fields, bios and READMEs.
  • Inspect the exact rendered anchor.
  • Record the observation date and access context.
  • Keep private material out of public examples.

Avoid turning a sample into a platform-wide rule

This guide supports context-aware inspection and legitimate project documentation. It does not establish universal dofollow behavior, historical behavior in 2025, a free-text bio-link rule or search performance. A missing rel attribute does not prove a link is indexed or contributes ranking credit. The dated examples are observations of public markup, not endorsements or permission to edit those pages. Follow GitHub’s acceptable-use rules and keep unsupported results marked unknown.

Fictional project example with separately dated public observations. No GitHub account, repository or link is created, and no ranking result is measured.