Cloudflare Pages Deployment Checklist

Site: itblogpros.com
Hosting: Cloudflare Pages
Source: GitHub Repository


✅ Pre-Push Checklist

Before pushing to GitHub, verify locally:


🚀 Deployment Verification Steps

Step 1: Verify Git Branch

# Check which branch you're on
git branch

# The branch with * is your current branch
# Make sure it matches Cloudflare's "Production branch" setting

Expected: You should be on main or master (whichever Cloudflare is watching)


Step 2: Check Cloudflare Build Settings

  1. Go to Cloudflare Dashboard
  2. Navigate to Workers & Pagesitblogpros
  3. Click SettingsBuilds & deployments

Verify these settings:

Setting Correct Value
Production branch main or master (must match your git branch)
Build command npx @11ty/eleventy
Build output directory _site
Root directory (blank) or /
Node version 18 or higher

If any are wrong: Update them → Save → Retry deployment


Step 3: Check Latest Deployment Status

  1. Go to Workers & PagesitblogprosDeployments
  2. Look at the most recent deployment

What to look for:

Success (green) = Site deployed successfully
Failed (red) = Build failed, click to see logs
🟡 Building (yellow) = Wait a few minutes

If Failed:


Step 4: Trigger Manual Deployment

If everything looks correct but site isn't updating:

  1. Go to Workers & Pagesitblogpros
  2. Click Create deployment or Retry deployment
  3. Wait for build to complete (2-5 minutes)

Or force from Git:

# Make a tiny change
echo " " >> README.md

# Commit and push
git add .
git commit -m "Force rebuild"
git push origin main  # or master

Step 5: Clear Cloudflare Cache

Cloudflare caches EVERYTHING aggressively:

  1. Go to CachingConfiguration
  2. Click "Purge Everything"
  3. Confirm the purge
  4. Wait 30-60 seconds

Then test:


Step 6: Verify Article URL

After successful deployment, check:

https://itblogpros.com/2025/10/02/your-article-slug/

If 404 Not Found:

If shows old content:


🔧 Common Issues & Fixes

Issue: "Branch mismatch"

Problem: Pushing to main but Cloudflare watches master (or vice versa)

Fix:

  1. Check current branch: git branch
  2. Go to Cloudflare → Settings → Builds & deployments
  3. Change "Production branch" to match your git branch
  4. OR switch your git branch:
    git checkout master  # or main
    git push origin master  # or main
    

Issue: "Build succeeds but article doesn't appear"

Problem: Article not in collections (missing "post" tag)

Fix:

  1. Open article markdown file
  2. Check front matter tags:
    tags:
      - post  # ← MUST BE HERE!
      - wifi
      - router
    
  3. Add "post" tag if missing
  4. Commit and push

Issue: "Old content showing"

Problem: Cloudflare cache

Fix:

  1. Purge Cloudflare cache (see Step 5)
  2. Hard refresh: Ctrl + Shift + R
  3. Wait 2-3 minutes
  4. Try incognito mode

Issue: "Build fails with 'Module not found'"

Problem: Missing npm package

Fix:

  1. Make sure package is in package.json dependencies
  2. Commit package-lock.json:
    git add package-lock.json
    git commit -m "Update package lock"
    git push
    
  3. Cloudflare runs npm ci which needs package-lock.json

Issue: "Articles work locally but not on Cloudflare"

Problem: Case-sensitive file paths or Node version difference

Fix:

  1. Check Cloudflare is using Node 18+:
  2. Check file paths are correct case:

🎯 Deployment Workflow

Every time you publish a new article:

  1. ✅ Test locally: npx @11ty/eleventy --serve
  2. ✅ Commit changes:
    git add .
    git commit -m "Add new article: [title]"
    
  3. ✅ Push to GitHub:
    git push origin main  # or master
    
  4. ✅ Monitor Cloudflare deployment:
  5. ✅ Purge cache:
  6. ✅ Verify live:

📊 Troubleshooting Decision Tree

Article doesn't appear on live site
    │
    ├─ Does it build locally? (npx @11ty/eleventy --serve)
    │   ├─ NO → Fix local build first, then retry
    │   └─ YES → Continue
    │
    ├─ Which branch are you on? (git branch)
    │   └─ Does it match Cloudflare "Production branch"?
    │       ├─ NO → Switch branch or update Cloudflare setting
    │       └─ YES → Continue
    │
    ├─ Check Cloudflare deployment status
    │   ├─ Failed → Read logs, fix error, retry
    │   ├─ Success → Continue
    │   └─ Building → Wait 2-5 minutes
    │
    ├─ Purge Cloudflare cache
    │   └─ Hard refresh browser (Ctrl + Shift + R)
    │
    └─ Still not working?
        └─ Check front matter has "post" tag
            └─ Check date is not in future
                └─ Verify build output directory is "_site"

🆘 Still Having Issues?

If you've tried everything:

  1. Share these details:

  2. Check these URLs:

  3. Verify basics:


💡 Pro Tips

Tip 1: Use Cloudflare Deploy Preview Every push creates a preview URL - check it before going live:

Tip 2: Set Up Build Notifications Get notified when deployments succeed/fail:

Tip 3: Enable Branch Deployments Test changes on a branch before merging to main:

Tip 4: Check Build Logs Regularly Even successful builds might have warnings:


📞 Quick Reference

Cloudflare Dashboard: https://dash.cloudflare.com
itblogpros Deployments: Workers & Pages → itblogpros → Deployments
Build Settings: Workers & Pages → itblogpros → Settings
Cache Purge: Caching → Configuration → Purge Everything

Local Test: npx @11ty/eleventy --serve
Git Branch: git branch
Git Push: git push origin main (or master)


Remember: 95% of deployment issues are:

  1. Wrong branch (Cloudflare watching different branch than you push to)
  2. Cache (Cloudflare needs purge + browser hard refresh)
  3. Build failure (check deployment logs)

Good luck! 🚀