How to set up your own domain for GitHub Pages

You can use your own domain for GitHub Pages by purchasing your web domain and pointing it correctly to your repository. This improves your professional image, your Google ranking, and gives you total control over your brand.

Publishing your site with GitHub Pages is free and easy. But using an address like user.github.io doesn’t convey the same thing as your own web domain.

If you want a professional, easy-to-remember, search engine-optimized site, you need a custom domain for GitHub Pages. In this guide, I’ll explain how to do it step by step, without unnecessary technical jargon.

What is GitHub Pages and why use a custom domain?

GitHub offers a service called GitHub Pages that allows you to publish static websites directly from a repository.

It’s ideal for:

  • Personal portfolios
  • Technical documentation
  • Simple institutional sites
  • Project pages

However, the free address includes the GitHub name.

With a custom domain on GitHub, your website can look like this:

1

www.tumarca.com

Instead of:

1

user.github.io

Benefits of using your own domain

  • Better professional image
  • Greater user confidence
  • Better SEO positioning
  • More control over your brand
  • Possibility of migrating in the future without losing your identity

What you need before you start

To set up your own domain for GitHub Pages, you need:

  • A site already published on GitHub Pages
  • A registered web domain (for example, with Neolo)
  • Access to your domain’s administration panel

If you don’t have a domain yet, you can easily register one with Neolo in just a few minutes.

Step by step: how to set up your own domain for GitHub Pages

1. Set up the domain in GitHub

  1. Log in to your repository.
  2. Go to “Settings.”
  3. Find the ‘Pages’ section.
  4. In “Custom domain,” enter your domain (example: yourbrand.com).
  5. Save the changes.

GitHub will automatically create a file called CNAME in your repository.

2. Set up the DNS with your domain provider

This is the most important part.

You must point your domain to the GitHub Pages servers.

Option A: Use a domain without www

You must create A records pointing to these official GitHub addresses:

  • 185.199.108.153
  • 185.199.109.153
  • 185.199.110.153
  • 185.199.111.153

These IPs belong to GitHub’s public infrastructure.

Option B: Use a domain with www (recommended)

Create a CNAME record:

1

www → user.github.io

This option is usually more stable and flexible.

3. Wait for propagation

Changes can take between 10 minutes and 24 hours.

Once propagated:

  • GitHub will detect the domain.
  • The security certificate (HTTPS) will be activated automatically.

Little-known (but very useful) tips

✔ Always enable HTTPS

In the Pages settings, check the “Force HTTPS” option.

This improves your SEO and security.

✔ Use correct redirection between www and non-www

It is recommended to choose a single version:

  • www.tumarca.com
  • or
  • yourbrand.com

And redirect the other version to avoid duplicate content.

✔ Add your domain to Google Search Console

This speeds up indexing and allows you to detect errors.

✔ Configure AAAA records if you want advanced optimization

GitHub also allows you to use IPv6 (AAAA) records.

This is not mandatory, but it improves compatibility on certain networks.

✔ Avoid common mistakes

  • Do not mix A and CNAME in the same root record.
  • Do not point the CNAME directly to the IP.
  • Do not delete the CNAME file from the repository.

Real example

Let’s imagine you purchase the domain:

1

midiseño.dev

You register it with Neolo.

In the DNS panel:

  • You create a CNAME for www pointing to usuario.github.io
  • You configure redirection from the root domain to www

In GitHub:

  • You configure www.midiseño.dev as a custom domain

Result:

Your professional website is up and running with a secure certificate and ready to be positioned.

Is it safe to use your own domain on GitHub Pages?

Yes. GitHub offers a free SSL certificate through Let’s Encrypt.

According to GitHub’s official documentation, certificates are automatically generated when the domain points correctly.

SEO advantages of using your own domain for GitHub Pages

Google prioritizes:

  • Custom domains
  • Sites with HTTPS
  • Recognizable brands

A custom domain conveys authority and improves click-through rates.

Plus, if you ever migrate to another hosting provider, you’ll retain your ranking.

Conclusion

Setting up a custom domain for GitHub Pages is not complicated.

All you need to do is:

  1. Register your web domain.
  2. Configure the DNS correctly.
  3. Activate the domain on GitHub.

This will give you a more professional site that is better positioned and ready to grow.

If you want to register your domain or need help with DNS configuration, the Neolo team can advise you step by step.

Frequently asked questions (FAQs)

How long does it take for the domain to be activated?

Between 10 minutes and 24 hours, depending on DNS propagation.

Can I use any domain extension?

Yes. You can use .com, .dev, .net, .org, and many more.

Will I lose my site if I change providers?

No. The domain is independent. You just need to update the DNS.

What happens if I configure the DNS incorrectly?

Your site will not load until you correct it. The content will not be lost.


Posted