Fix Library ? GitHub Pages
GitHub Pages troubleshooting

Fix GitHub Pages Custom Domain 404

A custom domain 404 often means DNS points correctly but Pages is serving the wrong branch or no built files. Check Pages source and CNAME together.

Book $50 Deploy RescueGenerate a checklist

Common symptoms

  • github.io URL works but custom domain 404s.
  • DNS appears configured but the page is unavailable.
  • CNAME disappears after deployment.

What to check first

Platform: GitHub Pages
Error: Custom domain 404

A custom domain 404 often means DNS points correctly but Pages is serving the wrong branch or no built files. Check Pages source and CNAME together.

Step-by-step fix

  1. Check repository Settings > Pages source branch and folder.
  2. Commit a CNAME file if your deploy action overwrites output.
  3. Verify A/CNAME records point to GitHub Pages.
  4. Wait for DNS and Pages certificate provisioning.
echo "www.example.com" > docs/CNAME

Common mistake to avoid

Do not store CNAME only in the GitHub UI if your deploy process replaces the output folder.

Still stuck?

Send the deploy log, repository link, target platform, and expected URL. ShipFast Deploy Rescue is a fixed-price debugging service for indie projects and MVPs.

Get Deploy RescueEmail project details