Gratis Herramientas de GitHub Pages y despliegue

En qué ayuda esta colección

GitHub Pages es simple, pero sus reglas de dominio y publicación no perdonan. Un CNAME en la carpeta incorrecta o un index faltante puede terminar en 404.

Ideal para

• Preparar dominios personalizados.
• Revisar el output antes de hacer push.
• Mantener CNAME, sitemap y robots.txt en la carpeta publicada.

Casos de uso comunes

• Generar contenido CNAME válido.
• Separar notas DNS de ajustes del repositorio.
• Revisar detalles antes de HTTPS y compartir.

Task guide

Use GitHub Pages tools when you set up a new site, move an existing site to a custom domain, or troubleshoot a deployment that is not serving correctly. Start by confirming your site repository settings: the publishing source branch and folder. Use the CNAME helper to prepare a custom domain file and verify your DNS configuration before enabling HTTPS. Add a 404 HTML page for single-page applications that handle client-side routing. Finish with the SEO checklist to verify that your generated output includes essential files like robots.txt, sitemap.xml, and proper metadata.

Publishing checklist

• Confirm the CNAME file exists in the root of your published output, not your project source root, and matches your custom domain exactly.
• Verify that the GitHub Pages publishing source setting points to the correct branch and folder, such as main /root or gh-pages /docs.
• Check DNS records for your custom domain: a CNAME record for www and either ALIAS or A records for the apex domain.
• Test the site URL after HTTPS is provisioned, as GitHub Pages can take several minutes to issue a certificate.
• Enable HTTPS enforcement only after confirming the site loads correctly over both HTTP and HTTPS.