Blog · CF Ready overview
What CF Ready Checks Before You Go Live
CF Ready scores migration, security, AI readiness, SEO, and deployment in one local report so a Cloudflare launch has a written checklist.
The questions that delay a launch
Shipping is rarely blocked by the build command alone. The questions that delay a Cloudflare launch are scattered across the repo. Can this framework run on Workers or Pages? Are secrets committed? Will an AI crawler find a usable description of the product? Is the metadata complete? Does the person on call have a rollback note? Teams usually answer those one by one, in different tools, close to the deadline.
CF Ready, short for Cloudflare Go-Live Readiness, collects them into one local workflow. The npm package is @orangecloud/cf-ready. It is a community open-source project maintained by OrangeCloud, and it is not affiliated with Cloudflare, Inc. The output is a Cloudflare readiness report your team can file with the release.
Six areas, one score
A default scan covers migration readiness, security readiness, AI readiness, SEO readiness, and deployment readiness. Migration includes framework detection, a likely Cloudflare target, and runtime blockers such as filesystem access or child processes. Security looks for exposed env files, hardcoded tokens, risky public artifacts, and whether a dependency audit can run. AI readiness looks for robots.txt, sitemap.xml, llms.txt, OpenAPI drafts, and MCP discovery files where they help agents understand the API.
SEO readiness reviews titles, descriptions, canonical URLs, Open Graph, structured data, headings, and image alt text. Deployment readiness checks build scripts, Wrangler configuration, environment documentation, and whether a rollback plan exists. Post-deployment smoke testing is a separate command against the live URL: homepage status, robots.txt, sitemap.xml, and the routes you marked as critical. It is part of the go-live picture, and it does not run inside the local scan.
The default weights are migration 35 percent, security 30 percent, AI readiness 20 percent, SEO 10 percent, and deployment 5 percent. A blocker, including a critical security finding, means the project is not production-ready. AI and SEO gaps do not block by default unless you configure that policy. A missing meta tag should not look like a broken runtime, and a hardcoded token should not hide inside an average.
Who the report is for
CF Ready is built for individual developers, agencies, freelancers, Cloudflare partners, and internal engineering teams. It is especially useful when a project is moving from another host, such as Vercel, Netlify, a VPS, or a container platform, and you want a written gap list. Other platforms remain a sound choice for many applications. The checklist assumes you have already chosen Cloudflare and need to know what must change.
Agencies can attach the same report to a handoff. The scores give a client a shared language for launch risk, and the finding list is specific enough to become tickets. A deployment checklist written after the fact is much harder to defend than one generated from the repository you are about to ship.
Safe by default
The CLI does not deploy your application, does not rewrite source as part of a scan, and does not change secrets. File writes happen only when you run an explicit fix, such as cf-ready fix --seo or cf-ready fix --ai-readiness. Those commands generate safe assets: robots.txt, sitemap.xml, llms.txt, an OpenAPI draft, an MCP server card draft, and similar files.
Review every generated diff before it merges. The drafts are useful defaults, and they are still your repository. The MVP has no silent production change and no required Cloudflare API token for the local scan.
Where to start
Run the CLI from a project root, open the Web Agent at https://ready.orangecloud.vn/app/ and import a repository, or add the CF Ready GitHub Action so pull requests upload SARIF and can fail when blockers are present. The action is a composite workflow in the project repository. Marketplace listing is a separate publishing step.
Start with the product overview at https://ready.orangecloud.vn, run one scan, and keep the generated go-live checklist with the release notes. That single Cloudflare readiness pass is the deployment checklist most teams meant to write by hand.