## GitHub Pages

GitHub Pages publishes static websites from GitHub repositories on a github.io subdomain or a custom domain. It can host portfolio pages, project docs, small landing pages, and other static content with ordinary outbound links.

- URL: https://pages.github.com/
- Guide: https://backlinkbadger.com/provider/github-pages/
- Link type: dofollow
- Free option: yes
- Backlink value: 2/100
- Spam score: 2/100
- Difficulty: 40/100
- Estimated time: 60 minutes
- Requirements: GitHub account, Public repository (free plan) or paid plan for private, Static page content, Basic Git or web editor access

GitHub Pages is best treated as a way to publish a real static page that happens to include your link. The backlink comes from the renderd `github.io` site, not from a GitHub repository README or issue thread.

## Method 1: Publish a user site on github.io

1. Sign in to GitHub and open [New repository](https://github.com/new).
2. Create a public repository named `username.github.io`, replacing `username` with your GitHub username.
3. Add an `index.html`, `README.md`, or Jekyll site with a useful page about your project, portfolio, docs, or resource.
4. Add your backlink in the page content where it helps the reader. Do not publish a page that is only a list of promotional links.
5. Open the repository's **Settings**, then **Pages**.
6. Under **Build and deployment**, choose the branch or workflow that publishes the site.
7. Visit `https://username.github.io/` after GitHub finishes publishing.

An example public GitHub Pages site with rendered outbound links: [https://chan150.github.io/](https://chan150.github.io/)

[Image: GitHub Pages site showing rendered external links in published page content]

The rendered page can include ordinary HTML links because GitHub Pages serves your static site. That is different from adding a link to GitHub-hosted Markdown on `github.com`, where user-generated content may be treated differently.

## Method 2: Publish a project site

Use a project site when the backlink belongs with a specifc repository, open-source tool, template, documentation page, or demo.

1. Create or open the project repository.
2. Add a static documentation or landing page that explains the project.
3. Put the backlink in the relevant page section, such as a demo, homepage, sponsor, documentation, or author link.
4. Open **Settings** > **Pages** and choose the publishing source.
5. Use the published URL, usually `https://username.github.io/repository-name/`, as the public page.

Project sites are better when the link has context. A bare page made only to point at a commercial homepage is easy to spot and not worth much.

## Link quality notes

For the recommended Pages method, the link is controlled by the HTML you publish and can be dofollow. The real catch is quality and intent: GitHub Pages is a static hosting product, so use it for a portfolio, docs page, project demo, or useful resource. If the page exists only to manufacture a backlink, it is unlikely to earn traffic, trust, or long-term value.

One detail to set expectations: `github.io` is on the [Public Suffix List](https://publicsuffix.org/), so every `username.github.io` site should be treated like its own hosted site. A fresh subdomain does not inherit the authority of the root `github.io` domain that you may see quoted in SEO tools. The link from a brand new Pages site starts effectively from zero, and its value grows with the page's own content, traffic, and inbound links over time.