Knowledge base
Connect a Bitbucket access token, or an API token with your username, so a push to a Bitbucket repository deploys your site.
Connecting Bitbucket lets a site deploy from one of your Bitbucket Cloud repositories: push to the branch and the site updates.
A Bitbucket Cloud account with access to the repositories you want to deploy.
Bitbucket offers two kinds of credential, and either works:
project's or workspace's own settings under Access tokens. It is tied to that repository, project or workspace rather than to a person. Give it read access to repositories.
Security → Create and manage API tokens → Create API token with scopes. Name it, set an expiry, choose Bitbucket** as the app, and select read access to repositories. Bitbucket shows the token once; copy it then.
Open Integrations in your dashboard and choose Connect an account. Pick Code hosting as the group and Bitbucket as the account, fill in API token — and, if you created a token on your Atlassian account rather than an access token, Account username as well, 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.
The username decides how we send the token, so enter it only for an account token. An access token entered with a username, or an account token without one, is refused.
site's repository connection, pick the repository and branch, and a push deploys.
live site.
source of the site's code.
A repository is missing. An access token reaches only the repository, project or workspace it was created in. Create one at the level that covers every repository you need.
It worked and then stopped. Both kinds of token can expire. Create a new one and connect it.
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 →