Black Friday Sale is Live: Get up to 30% OFF RankReady Pro - the WordPress AI SEO pluginBlack Friday Sale is Live: Up to 30% OFF Get Deal
Getting Started

Disconnect Hatch and Remove the Cloudflare Worker

Disconnect Hatch Connect from Cloudflare: stop the frontend redirect, forget stored tokens, revoke the Application Password and delete the Worker yourself.

Last updated October 30, 2026

By the end of this guide your WordPress site will be disconnected from its Cloudflare frontend, Hatch will have forgotten the tokens it kept, and you will have removed the Worker from Cloudflare.

What Disconnect does

  • The redirect from WordPress to the frontend stops.
  • The saved Cloudflare token is deleted.
  • The frontend account’s user name and encrypted Application Password are forgotten.
  • Permalink, sitemap and robots.txt rewriting for the frontend stops.

Disconnect does not delete the Application Password from the user’s profile, because Hatch did not create it. It also does not delete the Worker, which lives in your own Cloudflare account.

Disconnect step by step

  1. Open Hatch in wp-admin and go to the Connection tab.
  2. Press Disconnect. If a deploy is running, Hatch asks you to wait for it to finish first.
  3. Go to Users, open the frontend’s low-privilege account and revoke its Application Password.
  4. Log in to Cloudflare, open Workers & Pages and delete the Hatch Worker. If you set up a custom domain route, remove it there as well.
  5. Revoke the API token in your Cloudflare profile if you will not reconnect.
Hatch Connection tab
After a deploy, Disconnect is on the Connection tab (shown here before setup).

Reconnect later

Run the setup again with a new token. See create a Cloudflare API token and deploy to Cloudflare Workers.

What to do next