Choose a transfer method that fits the website
For a Git-based website, give the agent access to the relevant repository and explain the build and publication process. An archive may suit a small static website, but a clear redeployment path is needed after edits. A CMS typically requires access to an editor, theme, extension or supported API sufficient for the specific task. Full administrator access is unnecessary for one page. First identify the changes required: text, metadata, a verification file, routing rules or tracker installation. This helps choose the minimum effective access.
What the agent receives from AURA
After an audit, the agent can read tasks, obtain prepared files and download a patch. The package may include proposals for robots.txt, a sitemap, JSON-LD, website verification and analytics installation. These must be reconciled with the existing project. For example, do not replace a large sitemap with one fragment or remove active robots.txt rules without checking. The executor must study the current structure, merge necessary changes and preserve working routes. A prepared file means readiness for installation, not an automatic write to the owner's server.
Complete the path to public verification
A practical example: showing a snippet in the workspace is not enough to install a tracker. The agent adds it to the shared template for authorized pages, checks the build, publishes using an available method and opens the actual URL. Receipt of a real event is then checked. A verification file similarly needs a public response at the expected address. A local result is useful for development but does not confirm production state. After completion, save the modified files' description, a diff where appropriate and check results in the AURA task so another executor can understand what happened.
If source files cannot be shared
You can start with an external audit and a change list for the developer. For new useful content, consider the managed Answers section: it has its own connection mechanism and does not require giving AURA the entire website codebase. However, the section must also be installed and verified. If a page cannot be changed or a file placed, this must remain a specific blocker. The agent should not mark a task done merely because it wrote instructions. A stage correctly ends with a verifiable published result or a clear next step for the person holding the necessary access.
Conditions and limitations
- MCP does not grant repository access
- A patch must be adapted to the current code
- Without publication, local changes are invisible to search
Explore the details
The change is installed on the website and verified at its public address
Explore file handling