Using Camello on a custom-built site
If a developer made and maintains your site (a framework app, a static site, a theme you can't edit), choose "Custom-built (a developer made it)" when onboarding asks what your site is built with. Camello then writes each change as the values to send your developer, with one sentence on where each goes.
What you send. Open a change on the Changes page and press Done by hand. You see each value with a Copy button and its length, and one line for your developer: the page's title tag, its description tag, the heading to replace, the image whose description changes, the text to add, the file to publish, or the redirect to set. Send them the values and the page's address.
What your developer changes. The same tags any developer knows: the title and description tags in the page's head, a heading, an image's description, a block of structured data, a plain-text file at /llms.txt, lines in robots.txt, a permanent redirect. Every kind of change Camello proposes is possible on a custom-built site, because the developer edits the source.
Then Camello checks it. When your developer has published the change, press I've done it and give the page's address. Camello reads the live page as a visitor would; when the change is there, it counts as applied and is measured like any other change.
Undo. A change made by hand is undone by hand: your developer puts the old value back. The card shows what the field held before, so you can send that too.
If your site turns out to run on a builder. The steps on a card can be switched to Wix, Squarespace, Webflow or another builder, and to the plain HTML steps for whoever edits the site next.