Connecting GitHub and Vercel
Install the GitHub App for your workspace, grant the permission the deploy check needs, link a Vercel project, and read the hosting card correctly.
Builder writes to client websites through GitHub, and reads their hosting state through Vercel. Both connections are made once for the workspace, on the integrations page, and then pointed at individual projects.
Get the GitHub permissions right at install time and most publishing problems never happen.
Before you start
Installing or repairing the GitHub App is an account-owner action, on SettingsIntegrationsGitHub. Non-owners see GitHub as read-only in Builder settings and are told the account owner configures it.
Connect GitHub
Open the integrations page
SettingsIntegrations, then find the GitHub tile.
Install the app for the workspace
The installation is per tenant. It is what gives Builder the ability to see repositories and commit to them.
Choose which repositories it can reach
Grant access to the repositories Builder will publish to. Repositories outside the installation do not appear in the picker.
Grant Actions: Read
Needed so Zyan can read the site repository's own GitHub Actions runs.
Link a repository to each project
In the project's repository picker, choose the owner/repo.
Without Actions: Read, you cannot tell whether a post is live
The site deploy check reads the site repository's Actions runs for a commit. Without that permission the deploy status reads unavailable, no failed run is linked, and a post that never deployed still looks published. Grant it on the installation for each repository you publish to.
What GitHub is used for
| Use | What happens |
|---|---|
| Publishing blog posts | A commit on the publish branch, as a review pull request, an auto-merged pull request, or a direct push |
| Staging technical fixes | A pull request carrying the fix, with a rollback ledger |
| The site deploy gate | Reading the site repo's Actions runs to confirm a commit actually deployed |
| Listing repositories | Populating the project repository picker |
If no valid credential exists, the platform answers with a configuration response rather than failing quietly, and the draft is preserved so Approve & publish can re-commit it later at no extra writing cost.
Connect Vercel
Open the Vercel tile
It sits on the same integrations page as GitHub.
Link the Vercel project
Point it at the Builder project for the same website.
Open the Vercel panel in the workspace
It shows the production URL and the latest deployment.
The Vercel tab only appears for projects that are linked to a Vercel project.
Two states that read like errors and are not
Vercel is disconnected. The link is kept; reconnect it in Settings → Integrations means the link survives — reconnect and carry on. Vercel is paused from the Integrations page means someone stopped deployments on purpose.
Deployments, domains, environment variables and build settings live in the Vercel area itself, not in Builder. The Builder panel is a read-and-open surface, not a second control plane.
Other deployment targets
A project's deployment is set when you create it: GitHub deploy, FTP deploy or Bluehost. FTP credentials are configured per website inside that project's settings.
Bluehost deploy after fix commits is owner-only and dormant
That switch, under the SEO Command Center's SettingsAutomation & budgetAdvanced, is account-owner only, off by default, and stays inert without both the terminal service and tenant FTP credentials. Confirm both before you rely on it.
Troubleshooting
| Symptom | Cause | Fix |
|---|---|---|
| GitHub Not Connected | The app is not installed for the workspace | The account owner installs it on the GitHub tile in Settings → Integrations |
| A repository is missing from the picker | The installation does not have access to it | Add it to the installation's repository access on GitHub |
| Publishing fails mentioning GitHub configuration | No valid per-tenant credential | Install or repair the app, then Re-draft or Approve & publish |
| Deploy status reads unavailable | The installation lacks Actions: Read | Grant it and wait for the next re-check |
| The Vercel tab is missing | The project is not linked to a Vercel project | Link it in Integrations |
| Vercel shows as disconnected | The connection lapsed; the link is kept | Reconnect in Settings → Integrations |
| Vercel shows as paused | Deployments were paused deliberately | Resume from the Integrations page |
| GitHub is read-only in Builder settings | You are not the account owner | Ask the account owner |