Connect Your Website
How changes reach your site
The agent can read your site and your Search Console data. It can't publish to your site. Every change it writes goes live through you, in one of two ways.
Two ways in
| Connect your code | Handoff | |
|---|---|---|
| For | Sites built from code in GitHub or Bitbucket: Next.js, React, Express, plain HTML. | WordPress, Shopify, Webflow, Wix, Squarespace, and other site builders. Or a code site you'd rather not connect. |
| Each change arrives as | A pull request in your repository. | A handoff document in the chat: exactly what to change and where. |
| You | Review it and merge it. | Make the change in your site's editor, or pass it to whoever does. |
| Guide | Code-based sites | WordPress, Shopify, others |
Tell the agent in Setup
Setup asks where the agent can make changes. Answer with your platform and how you publish. For example:
- “Next.js on GitHub. Merging to main deploys to Vercel.”
- “WordPress with Yoast SEO and the block editor. I'll make the changes myself.”
- “Shopify. Products and blog posts are fair game. Don't touch the homepage.”
The agent writes each handoff for the platform you name, so be exact. If you use an SEO plugin or app, say which one. Already past Setup? Tell the agent in Chat.
What a handoff contains
One handoff covers one change. It may touch more than one page: a new internal link lands on the page doing the linking, for example. For each edit it gives you:
| Part | Example |
|---|---|
| Page | https://example.com/blog/choosing-a-crm |
| What to change | The SEO title |
| Now | Choosing a CRM | Example Blog |
| Change it to | How to Choose a CRM for a 10-Person Sales Team |
| Where | Yoast SEO sidebar, Search appearance, SEO title |
| How to check | Open the live page's source and find the new text in its title tag |
The example is made up. You can ask for a handoff at any time: “Give me a handoff document for this change.” If a part is missing or unclear, ask: “Where exactly do I change this in Shopify?”
After you publish, tell the agent
One message closes the loop
Go back to the same chat and tell the agent the change is live, with the page's address: “Live: https://example.com/blog/choosing-a-crm”. If you published something different from the handoff, say what.
That message does three things:
- The agent checks Google has seen it. It won't judge a change until Google has crawled the page. A change judged too early teaches it the wrong lesson.
- The change counts as shipped. Your deal counts shipped changes. If none ship during your window, you pay nothing, and nothing moves either.
- The result is measured and credited to that change, so the next runs learn from it.
Help Google find it sooner
The agent's Search Console access is read-only, so it can't ask Google to look again. You can:
- 1In Search Console, inspect the page's address with URL Inspection.
- 2When the result loads, click Request indexing.
Google says indexing usually takes a day or so, can take longer, and isn't guaranteed. There is a daily limit on requests, so save them for pages you've just changed.
While a change is being measured
- Leave that page alone until the agent says Google has seen the change. Two edits to one page can't be told apart.
- Don't undo a change without telling the agent.
- Tell the agent about other big changes to your site: a redesign, a migration, a new theme or plugin, new addresses for pages. They move clicks too, and the agent needs to know about them to judge its own changes fairly.
- Google may show a title you didn't write. Google rewrites titles it judges unhelpful for a search. The agent treats that as something learned about the search, not as a failure.
Changes that need your yes first
Some changes can't be cleanly undone: redirects, deleting or merging pages, changing a page's address, changing its canonical tag, removing pages from your sitemap. The agent asks before it makes or hands off any of these, and says why.