Replace Your GitHub Pages Domain for Free (No .github.io)

A custom domain makes a GitHub Pages address easier to remember and share.

username.github.io works immediately, but it can feel generic on a portfolio, product documentation site, or AI demo. A custom domain gives the project a memorable address without changing how you publish it. With AICLUB, you can claim a free subdomain and point it to GitHub Pages with a CNAME record.

This guide uses portfolio.aiclub.ai.id as an example. Replace portfolio with a suitable name and replace username with your own GitHub username. Do not copy the example values literally.

Why replace username.github.io?

Your own domain is easier to say on a CV, README, social profile, or business card. A name such as rio.std.ai.id or docs.aiclub.ai.id tells visitors what the site is for before they open it. It is not an SEO shortcut, but a consistent identity helps people return to the same project.

A custom domain also separates the public address from repository structure. You can reorganize branches, change a static-site generator, or move repository contents without sending a new URL to every visitor. The important part is keeping the GitHub Pages name and DNS name identical.

AICLUB vs is-a.dev: subdomain claim workflow

The difference is workflow, not a claim that one service is always better. The is-a.dev documentation describes forking its repository, adding a configuration file, and opening a Pull Request. ^[3] Use AICLUB when you want a dashboard submission; use is-a.dev when you prefer a fully GitHub-based process.

Set up a GitHub Pages custom domain through AICLUB

1. Add the custom domain in GitHub Pages

In the repository that publishes Pages, open Settings → Pages. Under Custom domain, enter the subdomain you want to use, such as portfolio.aiclub.ai.id, then save it. This name must be identical to the name submitted in AICLUB.

GitHub explains that a custom domain is added in Pages settings and DNS is then pointed at the correct target. For a subdomain, its official documentation uses a CNAME to USERNAME.github.io. ^[1] Confirm that Pages is already enabled and that the default site loads first; a custom domain cannot fix a failed build.

2. Claim a subdomain in the AICLUB dashboard

Open AICLUB.AI.ID, enter the dashboard, and choose an available subdomain. For a portfolio, readable examples include name.is-a.cv or name.std.ai.id. For documentation, docs.aiclub.ai.id is clear. Pick an extension for the project context, not only because it sounds unusual.

Choose CNAME as the initial target type and save the submission. AICLUB offers extensions including aiclub.ai.id, std.ai.id, is-a.eu.cc, and is-a.cv; availability still needs to be checked in the dashboard.

3. Set CNAME to username.github.io

For a GitHub Pages user site, set the CNAME target to username.github.io. For example, if your GitHub username is yanstd888, the target is yanstd888.github.io. Do not add a repository name, path, https://, or a trailing slash.

Use DNS-only mode according to the AICLUB dashboard option. After saving, do not repeatedly change the target just because the page is not live immediately. DNS needs time to propagate, and repeated changes make diagnosis harder.

4. Enable HTTPS after DNS is ready

After GitHub accepts the domain, wait for DNS verification and the HTTPS certificate. When Enforce HTTPS is available in Settings → Pages, enable it. GitHub notes that DNS changes and certificate issuance can take up to 24 hours, so it is normal if the HTTPS option does not appear in the first few minutes. ^[2]

Test the address in an incognito window, then check two things: the page loads over https://, and the old username.github.io URL redirects to the new domain once GitHub has configured the redirect. If it still does not work after 24 hours, check the subdomain spelling and CNAME target before submitting another change.

Tip: increase your quota with GitHub Badge Builder

Need extra slots for a demo, documentation site, and portfolio? Create a badge in the AICLUB GitHub Badge Builder, copy its Markdown, and add it to a public repository README. After installation is complete and verified, the badge can add subdomain quota under the platform rules. Use it on a project you actually show so the README stays useful to visitors.

Checklist before sharing the URL

• GitHub Pages is published without a build error.
• The custom domain in GitHub exactly matches the AICLUB dashboard name.
• The CNAME target is only username.github.io, without a repository name.
• HTTPS is enabled or still within a normal verification window.
• Your README, CV, and social profiles use the same new URL.

Conclusion: use an address ready to share

The safest flow is simple: choose an available name, add it to GitHub Pages first, then claim it at AICLUB using username.github.io as its target, and let HTTPS verification finish. Once it is live, use that URL consistently in your README and portfolio. Visit AICLUB.AI.ID to choose a subdomain, then follow setup updates and free tools on Telegram @aiclub_id.

Technical sources

1. GitHub Docs — Managing a custom domain for your GitHub Pages site
2. GitHub Docs — Securing your GitHub Pages site with HTTPS
3. is-a.dev Docs — Quickstart

Frequently asked questions

Continue learning