Configuring a custom domain for your Pages site
Who can use this feature?
Pages is available in public repositories with Free and Free for organizations, and in public and private repositories with Pro, Team, Enterprise Cloud, and Enterprise Server. For more information, see ’s plans.
Pages now uses Actions to execute the Jekyll build. When using a branch as the source of your build, Actions must be enabled in your repository if you want to use the built-in Jekyll workflow. Alternatively, if Actions is unavailable or disabled, adding a .nojekyll file to the root of your source branch will bypass the Jekyll build process and deploy the content directly. For more information on enabling Actions, see Managing Actions settings for a repository.
About custom domains and Pages
Pages supports using custom domains, or changing the root of your site's URL from the default, like octocat..io, to any domain you own.
Managing a custom domain for your Pages site
You can set up or update certain DNS records and your repository settings to point the default domain for your Pages site to a custom domain.
Verifying your custom domain for Pages
You can increase the security of your custom domain and avoid takeover attacks by verifying your domain.
Troubleshooting custom domains and Pages
You can check for common errors to resolve issues with custom domains or HTTPS for your Pages site.