Does one repo support multiple sub-domains?

[svathyitis]

Select Topic Area

Question

Body

GitHub Pis only allowing me One Custom Domain/Subdomain per Repo. I can't be creating 100 repos for 100 pages/ sub-domains.

[svathyitis]

I shall give JeykII a try.

[EyasuGet]

GitHub Pages: Custom Domain Limit & Workarounds

GitHub Pages only allows one custom domain or subdomain per repository.
This is because GitHub Pages uses a CNAME file and enforces a one-to-one mapping to keep DNS, HTTPS, and deployment secure and simple.

---

1. Use Subdirectories

Instead of creating separate repos for each subdomain, you can:

• Set one custom domain (e.g., example.com)
  Project structure in your repo:
  /
  ├── index.html
  ├── project1/
  │ └── index.html
  ├── project2/
  │ └── index.html

2. Use a Static Site Generator or Framworks

🔚 Bottom Line

You don’t need 100 repos for 100 pages.
Use a single repository with subdirectories and one custom domain to keep things simple and scalable.
GitHub Pages isn't designed to host multiple subdomains per repo — but with the right structure, it can support large multi-page setups with ease.

[svathyitis]

Thanks but I need easy way to manage sub-domains.

[Prameshbasnet]

Yes, one repository can support multiple subdomains.

[Utpal3]

Yes, one Git repository can be used to support multiple subdomains, but it usually requires a bit more configuration. While a single GitHub repository can only be associated with one custom domain, you can use subdirectories within that repository and configure your web server (like Netlify or GitHub Pages) to serve different subdirectories as separate subdomains.

[Macxzew]

Select Topic Area

Question

Body

GitHub Pis only allowing me One Custom Domain/Subdomain per Repo. I can't be creating 100 repos for 100 pages/ sub-domains.

GitHub Pages allows only one custom domain or subdomain per repository. You cannot map many subdomains (like page1.example.com, page2.example.com, etc.) directly to the same repo. You can't natively use multiple subdomains for a single GitHub repo. For multi-site setups, use subfolders or an external reverse proxy.

• Use subdirectories:
  Host multiple pages or sites within the same repo as subfolders
  Example: example.com/page1
example.com/page2

• Static site generators:
  Use Jekyll, Hugo, or similar tools to create multi-page sites in one repo.

• Wildcard subdomain and reverse proxy:
  Set up a wildcard DNS record (like *.example.com) and use a reverse proxy (e.g. NGINX, Cloudflare) to route subdomains to specific subfolders in your repo.
  Note: This requires a server or service outside GitHub.

• Multiple repos:
  If you need every subdomain as a truly separate site, create a separate repo for each one.

References

• GitHub Docs: Managing a custom domain for your GitHub Pages site
• GitHub Community: Multiple subdomains per repository?

[svathyitis]

May I kindly request that future commenters refrain from reiterating points already mentioned above. Thank you.

[Macxzew]

Thank you for not attacking me unnecessarily. I was simply clarifying a point that may not have been fully understood. My intention was never to repeat just for the sake of it, but to help make things clearer.

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬

[syedlabib4]

Yes, GitHub Pages currently allows only one custom domain per repository. To handle multiple pages or subdomains without creating 100 repos, you can:

Use a single repository with folders:

Each folder can host a separate page.

Use gh-pages branch or GitHub Actions to deploy specific folders.

Use a single domain with subpaths:

Example: example.com/project1, example.com/project2 instead of subdomains.

Use a reverse proxy or another hosting provider:

Services like Netlify, Vercel, or Cloudflare Pages allow multiple subdomains or routes from a single repo.

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬