Feature Request: Centralized Account Dashboard for GitHub Pages & Custom Domains

[mchelen]

🏷️ Discussion Type

Product Feedback

💬 Feature/Topic Area

Pages

Body

The Problem

Currently, there is no centralized UI within Account Settings to view or manage active GitHub Pages deployments and their associated custom domains.

This causes significant friction because of the way GitHub handles the primary "User Pages" repository (e.g., <username>.github.io or the legacy <username>.github.com). When a custom domain is set on this specific root repository, it silently cascades that domain to all other project repositories across the account.

Because this behavior operates entirely behind the scenes, developers are left dealing with unexpected side effects without clear visibility into what is causing them.

The Impact

• Invisible Configuration: Users cannot see which domains are active or which repository is currently acting as the account-wide override.
• Wasted Troubleshooting Time: Developers are forced to manually click through the Settings > Pages tab of every individual repository they own, or run global searches for hidden CNAME files, just to hunt down where a domain is being held hostage.
• Legacy Debt: Users with older accounts (who may still have a .github.com repo) often forget that repository exists, making the diagnosis even harder when new project sites suddenly inherit an old custom domain.

The Proposed Solution

Introduce a centralized "Pages" or "Custom Domains" dashboard under the main Account Settings sidebar.

This dashboard should provide a simple, read-only audit log that lists:

1. All active GitHub Pages deployments under the account.
2. The specific URL/Custom Domain assigned to each deployment.
3. A direct link to the specific repository (and its settings page) that is controlling that domain.

Why this matters

As developers accumulate dozens or hundreds of repositories over the years, manual auditing becomes impossible. A centralized dashboard would eliminate the confusing "ghost domain" cascade effect, prevent users from opening redundant support tickets regarding locked domains, and bring GitHub Pages management in line with the transparency expected from modern hosting platforms.

Related Discussions

This is a frequent pain point in the community. Here are just a few examples of users trying to troubleshoot the symptoms of this missing feature:

• The custom domain is already taken. Except it's not (#23569)
• Unknown repo: The custom domain is already taken. (#189332)
• Use GitHub assigned domain instead of custom domain? (#152653)
• Github Pages with single custom (sub)domain for multiple repositories (#22433)
• Github Pages: Some on Github.io and some on Custom Domain (#153007)

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[xusnitdinov]

@mchelen this is a sharp writeup. The user-pages custom domain quietly becoming the "default" for every project Pages site has burned a lot of people, and there's still no account-level place that shows "here's every Pages site + domain + which repo owns it."

+1 on a centralized Pages / domains dashboard in Account Settings. Ideal MVP would just be:

• list of all Pages-enabled repos
• custom domain (if any)
• whether it's inheriting from username.github.io
• a clear warning when the root Pages domain will cascade

Until that exists, the least painful workaround is documenting it in the repo README / team wiki: "root Pages custom domain affects all project sites." Still not great.

Hope product actually catalogs this one. Happy to upvote / add use cases if helpful.

[mchelen]

@mchelen this is a sharp writeup. The user-pages custom domain quietly becoming the "default" for every project Pages site has burned a lot of people, and there's still no account-level place that shows "here's every Pages site + domain + which repo owns it."

+1 on a centralized Pages / domains dashboard in Account Settings. Ideal MVP would just be:

• list of all Pages-enabled repos
• custom domain (if any)
• whether it's inheriting from username.github.io
• a clear warning when the root Pages domain will cascade

Until that exists, the least painful workaround is documenting it in the repo README / team wiki: "root Pages custom domain affects all project sites." Still not great.

Hope product actually catalogs this one. Happy to upvote / add use cases if helpful.

@xusnitdinov Agreed regarding MVP and workaround options. Thank you for the thoughtful reply!