MITARBOT
GUIDE · WEBSITE

How to have the agent maintain your website

You keep your web hosting and give the agent SFTP access. Then you describe what the site should say — it edits the files, checks them and uploads them.

Chat with tool steps: website files read, edited and uploaded over SFTP
From the live demo: opening hours changed, team updated, published over SFTP.

What you need

  • Web hosting with SFTP access (e.g. Hetzner, IONOS, All-Inkl) — Mitarbot does not host the site
  • Host, port, username and password or key
  • The existing files — or permission to write new ones

Step by step

  1. 01

    Keep your web hosting

    The site keeps running at your provider. Mitarbot only needs a path to the files — and almost every host offers that as SFTP.

  2. 02

    Connect the account

    Store the credentials as a connector. They sit in an isolated gateway; the agent and the model never see them in clear text.

    Say it like thisConnect my web host over SFTP — the credentials are stored in connectors.
  3. 03

    Say what the site should say

    Either new content or a change. You do not need HTML: describe what visitors should see.

    Say it like thisChange Friday's opening hours to 9 a.m.–3 p.m. and add Jonas to the team.
  4. 04

    Upload and check

    The agent edits the files, checks the links and uploads them over SFTP. Every step is visible in the chat, including the error if the host complains.

    Say it like thisUpload the changes and then check that all links still work.

Variations

  • Build a page with services, prices and contact.New files, uploaded and linked.
  • Swap the team photo for the new one.Image replaced, page re-uploaded.
  • Check every link on the site.A list of broken links with file and target.

What it is not

No CMS, no site builder: the agent works on HTML files. If your site runs on WordPress you still need the CMS — or a move to static files.

Common questions

Is the old version kept?

The workspace is backed up as automatic snapshots and can be restored from them. For single files: have the agent keep a copy before bigger changes.

What about HTTPS and the domain?

That is your host's job. The agent only changes files, not DNS records.

What if the upload fails?

The step shows the error in the chat. Retry once the cause is fixed.

Might also fit

GUIDE · WEBSITE

A website change in the chat instead of the FTP client.

The live demo shows a full deploy with every tool step.