How does this tool know what's actually deployed?

It doesn't inspect your live site or Cloudflare account, it works entirely from what you tell it via the toggle buttons and text fields. Think of it as a structured checklist you fill in yourself, not an automated scanner.

Why does it flag "src" or "." as a suspicious output directory?

Cloudflare Pages should publish your build's compiled output (commonly dist, build, out, or public), not your source folder. Setting the output directory to your source root or repo root usually means either the build step isn't configured correctly or you're accidentally deploying unbuilt source files.

Is a missing _redirects file always a problem?

Only if your app relies on client-side routing (a single-page app) or you have legacy URLs that need to 301 somewhere. A simple static multi-page site with no routing library and no URL history to preserve may not need one at all, treat that warning as a prompt to double check, not an automatic failure.

What should I do with the warnings this generates?

Work through them one at a time: add the missing file or setting, or make a deliberate decision that it doesn't apply to your project and move on. The report is a starting checklist, not a strict pass/fail gate.

Cloudflare Pages Deployment Checklist Generator

Overview

Introduction

It's easy to deploy a Cloudflare Pages project that technically works but is missing a handful of small, easy-to-forget pieces, a robots.txt, a custom 404 page, or a security headers file.

This tool turns those easy-to-forget pieces into a short checklist: describe your setup, and get back a report of what's covered and what still needs attention.

What Is Cloudflare Pages Deployment Checker?

A deployment self-audit tool: you describe your build command, output directory, and toggle whether robots.txt, sitemap.xml, _headers, _redirects, and a custom 404 page exist, and it generates a pass/needs-attention checklist report.

It also flags a couple of specific common misconfigurations it can detect from the text you enter, like an output directory that looks like a source folder rather than a build output folder.

How Cloudflare Pages Deployment Checker Works

Each toggle and field you fill in maps to one checklist item; anything left off or empty becomes a "needs attention" line with an explanation of why it matters, anything present becomes a passing line.

A couple of items get an extra heuristic check, for example the output directory value is compared against a short list of common source-folder names (src, ., ./) to flag a likely misconfiguration.

When To Use Cloudflare Pages Deployment Checker

Use it right after setting up a new Cloudflare Pages project, before considering the deployment "done", to catch the small things that are easy to forget.

It's also useful periodically on an existing project, to double check nothing regressed after a redesign or migration.

Often used alongside Cloudflare Pages _headers File Generator, Cloudflare Pages _redirects File Generator and Cloudflare Pages robots.txt Generator.

Features

Advantages

Turns a mental checklist you'd otherwise have to remember yourself into a concrete, repeatable report.
Explains why each missing item matters, not just that it's missing.
Flags at least one common misconfiguration pattern (source folder set as output directory) automatically.

Limitations

Entirely self-reported, it doesn't fetch or inspect your actual deployed site, so its accuracy depends on how accurately you describe your setup.
The set of checks is fixed to the items listed; it won't catch issues outside that list (like a broken build command syntax).

Examples

A setup missing robots.txt and a custom 404

Input

build command: npm run build, output directory: dist, robots.txt: no, sitemap: yes, _headers: yes, _redirects: yes, 404 page: no

Output

Passing (3):
  [x] Build command set: "npm run build".
  [x] Output directory set: "dist".
  [x] sitemap.xml present.
  [x] _headers file present.
  [x] _redirects file present.

Needs attention (2):
  [ ] No robots.txt detected...
  [ ] No custom 404 page detected...

Each toggle maps directly to one pass or warning line, giving a quick scan of exactly what's missing.

Best Practices & Notes

Best Practices

Re-run this checklist after any significant framework upgrade or build tool change, output directory conventions sometimes shift between major versions.
Treat the source-folder warning as a prompt to verify, not a guaranteed error, some genuinely static projects do serve directly from a shallow folder.
Use the notes field to record project-specific context (like "no 404 page needed, this is a single static landing page") so future you remembers the reasoning.

Developer Notes

This is a pure, self-reported checklist function; each boolean/text input maps to a fixed warning-or-pass message, and the output directory string is checked against a short denylist of common source-folder names (src, ., ./, /) as the one structural heuristic beyond simple presence/absence.

Cloudflare Pages Deployment Checker Use Cases

Running a pre-launch checklist on a new Cloudflare Pages project
Periodically re-auditing an existing deployment for regressions
Onboarding a new team member to what a "complete" deployment checklist looks like for this project

Common Mistakes

Setting the output directory to the repository root or source folder instead of the actual build output folder.
Assuming a missing _redirects file is fine without checking whether the app actually needs an SPA fallback rule.

Tips

Follow up with the pages-dev Duplicate Content Checker if this deployment also has a public pages.dev URL alongside a custom domain.

Cloudflare Pages Deployment Checker