Knowledge base
Create a Cloudflare API token and connect it so we can publish sites to Cloudflare Pages and serve their DNS and cache from your own Cloudflare account.
Connecting your Cloudflare account lets us publish static sites to Cloudflare Pages on your account, and serve your sites' DNS and cache from it. Everything lives in your own Cloudflare dashboard and on your own Cloudflare plan.
A Cloudflare account, with the domains you want to use added to it as zones. The free plan is enough to connect; what you can do on each zone is whatever your plan allows.
In the Cloudflare dashboard open My Profile → API Tokens and choose Create Token, then Create Custom Token. Give it a name, add the permissions below, and under Zone Resources choose the zones you want us to reach — all zones, or only the ones you name. Review it and press Create Token. Cloudflare shows the token once; copy it then.
Add these permissions:
without it still connects and works for DNS and cache.
The older alternative. Instead of a token you can connect with your Global API Key and the email address you sign in with (My Profile → API Tokens → API Keys → Global API Key → View). Cloudflare recommends against it: the Global API Key carries every permission your login has, on every zone, and cannot be narrowed. Use a token if you can.
Open Integrations in your dashboard and choose Connect an account. Pick Cloudflare account (Pages, CDN & DNS) as the group and Cloudflare as the account, fill in API token — or, for the older alternative, API key and Account email, and press Connect account.
We test what you paste before anything is saved. A key that does not work is never stored, and the answer says what was wrong with it. A key that works is kept encrypted in our secrets vault — never in our database — and is never shown again, not even to you.
site, and we publish the build to a Pages project on your account.
The checklist beside the connection shows which of those we could confirm.
If you want to keep CDN and DNS on different Cloudflare accounts, connect them separately as Cloudflare CDN and Cloudflare DNS instead — each has its own guide.
A permission shows as unconfirmed. Cloudflare does not always let a token list its own permissions, so some are confirmed the first time we use them. If an action later fails with a permission error, edit the token in My Profile → API Tokens and add the missing permission — the token value does not change, so nothing needs reconnecting.
A zone is missing. The token's Zone Resources does not include it. Edit the token to include that zone, or all zones.
It says the key was rejected. Almost always one of three things: a space or a line break copied with it, a key that has expired, or a key that was revoked or regenerated after you copied it. Create a fresh one and paste it again.
It connects, but something later fails. The key authenticates but lacks a permission the action needs. Create a new key with the permissions listed above, then disconnect the old connection and connect the new key.
Open Integrations, find the account and press Disconnect. That deletes the stored key at once. Anything that was using it stops at its next action, and the screens that depended on it say so rather than failing quietly.
Disconnecting does not undo what was already done — records, deployments or settings we changed on your account stay as they are. If you think the key itself may have leaked, also revoke it at the vendor; disconnecting removes our copy, not theirs.
What we have been writing about hosting, SEO and running sites at scale.
How hosting shapes indexing and link equity in 2026: keeping pages indexed, vetting aged domains before you build on them, link building without a footprint, and an honest line on what infrastructure can and cannot do for SEO.
Read the post →A practical checklist for fast, secure WordPress: server-level caching, a per-site object cache, the handful of plugins worth running, keeping the stack current, and the WooCommerce pages you must never cache.
Read the post →What actually separates good managed hosting from a cheap box with a control panel — migrations, backups, isolation, real caching and honest scaling — and how to judge it before you commit.
Read the post →Support is included on every plan, the desk is open 24 hours a day, and you can write to us in any of our 58 languages — we answer you in yours.
Contact support → All articles →