Connect Your Website
Code-based sites: GitHub or Bitbucket
If your site is built from code, like Next.js, React, Express, or plain HTML, connect its repository during Setup. The agent opens a pull request for each change, and you merge it.
Connect your repository
- 1Start Setup. If Setup is already done, open Chat and say you want to connect your repository.
- 2Tell the agent where the code lives: GitHub or Bitbucket, the repository, and the branch your live site is built from.
- 3Grant access when the agent asks, following the steps it gives you in the chat.
- 4The agent confirms it can read the repository. It changes nothing during Setup.
Access to propose, not to publish
The agent works on its own branch and opens a pull request for each change. Nothing reaches the branch your site is built from until you merge it.
Each change is a pull request
A run that makes a change opens one pull request. It says which page it changes, which searches it's for, and what the agent predicts will happen. Before you merge:
- Check it touches only what it says it does.
- Preview it if your host builds previews for pull requests, as Vercel and Netlify do. Make sure the page looks right.
- Want something different? Say so in the chat, not in a comment on the pull request.
Then merge it. If your site deploys when that branch changes, the change is live. Otherwise, deploy the way you normally do. Last, tell the agent it's live, with the page's address. Why that matters.
Where changes land in your code
You don't need to find these yourself. The agent reads your code and picks the right file. This table is for knowing what you're looking at in a pull request.
| Stack | Title and description | Page content |
|---|---|---|
| Next.js, App Router | The metadata export or generateMetadata in the route's page.tsx or layout.tsx | The route's page and its components, or the Markdown or MDX file behind it |
| Next.js, Pages Router | <Head> from next/head in the page | The page file and its components |
| React single-page app | index.html, or a head manager such as react-helmet-async | The route's components |
| Express | The view template (EJS, Pug, Handlebars), or the values passed to res.render | The view templates |
| Plain HTML | <title> and <meta name="description"> in each file | The HTML file |
If your pages are built in the browser rather than on the server, as in a single-page React app, say so in Setup. Google can take longer to pick up text that only appears after JavaScript runs.
Prefer not to connect?
You can run the whole deal on handoffs instead. Say so in Setup. Each handoff names the page and the exact text to change, and your developer, or your own coding assistant, finds it in the code. Without access to your repository, the agent works from your live pages, so it can't point to files. What a handoff contains.