GitHub Pages → Cloudflare Pages Migration Checklist
The one-page version of Hamza's migration guide: every step and every pitfall from moving a live site to Cloudflare Pages without breaking it.
This is the distilled checklist from Hamza's full guide to moving a website from GitHub Pages to Cloudflare Pages — the exact sequence he used for MythPost in November 2026: 161 files, live the same evening, custom domain the next morning, nothing broken. Print it, work down it in order, and read the full guide for the reasoning behind each step.
Before you move
- Write down, in one sentence, why you are moving (redirects, headers, previews, edge security). If there is no real capability you need, stay on GitHub Pages.
- List everything in your built output folder that must survive: sitemap.xml, robots.txt, ads.txt, favicon, and any verification files.
- Check every internal link before the move, not after.
- Count your files — you will compare the count after deploying.
Set up access, once and properly
- Sign in to Cloudflare with “Sign in with Google”.
- Create a scoped API token with only Pages, Zone, and DNS permissions.
- Store the token in a password manager or secret store — never in chat, email, or a repository.
- Keep a second deploy route ready (git-connected or API upload) in case the dashboard route fails.
Deploy and verify on pages.dev first
- Create the Pages project and deploy your built folder.
- Open the yoursite.pages.dev address like a stranger: homepage, a category page, several inner pages.
- Confirm real 200 responses and that images and stylesheets load.
- Confirm the deployed file count matches your audit count. If it does not, stop and find the gap.
Domain and nameservers
- Add the domain as a Cloudflare zone and attach it — including www — as a custom domain on the Pages project.
- At your registrar, replace the nameservers with the two Cloudflare nameservers for your zone. Confirm you are editing the right domain before you save.
- Expect propagation to take hours (Hamza's took about twelve). Do not keep changing settings while you wait.
- Remember: a CNAME file does nothing on Cloudflare — the domain is attached inside the Pages project.
After the move
- Re-verify on the real domain in a fresh browser: homepage, inner pages, www redirect, HTTPS padlock.
- Fetch sitemap.xml, robots.txt, and ads.txt at their real addresses and confirm each returns its content.
- In Search Console, resubmit the sitemap and request indexing for your most important pages.
- Make sure canonical tags point at the custom domain, not the pages.dev address.
- Learn where Cloudflare's cache-purge button is before you need it in a hurry.
- Keep the old GitHub repository untouched for at least a week as your fallback.
Go deeper
This checklist is the short version. The full story — with the reasoning, the mistakes, and the numbers — is free to read: