Marketing Agent 04 · prepare · observe · verify
The agent writes the change. A person still merges it.
You get a diff bound to a specific commit, the checks that ran on it, and evidence from the live page after deploy. A green check is evidence. It is not permission — merging stays yours.
We run it on our own site before we run it for our clients. humanswith.ai is 327 pages, and since 2026 every change has gone through this loop. Last month we measured a deploy that reported success while the public page still served the old version — the edge had cached it seconds before the origin updated. That check is now part of the workflow.
CHANGE receipt
- Scope
- Diff
- Commit
- Checks
- Deploy
- Live proof
Authority contract
Prepare · exact commit · human review · deploy · live proof
Authority model
The agent prepares evidence. The project grants authority.
On 22 July 2026 we checked eight English routes with Astro, schema, hreflang, link, layout, design, accessibility, and ContentOS gates. We also inspected desktop and mobile output in Playwright.
- Confirm the owned surface. Identify the repository, branch or worktree, target route, current production state, and approved blast radius.
- Prepare a scoped packet. Describe the finding and proposed diff. Add tests, the visual contract, deployment path, rollback, and success anchors.
- Observe the exact commit. Bind build, schema, link, layout, design, and CI evidence to the commit that contains the change.
- Keep the human gate. Passing CI remains human-review-required; merge and deploy follow explicit project authority.
- Verify production behavior. Inspect the target route and its rendered contents after deployment, not only service health.
What the workflow can prove
Technical evidence, without claiming causal attribution.
Discovery
Canonical and crawl surfaces
Canonical, sitemap, robots, llms.txt, hreflang, and internal-link behavior can be inspected in built and live output.
Structure
Metadata and schema
Titles, descriptions, structured data, visible FAQ parity, and source links stay testable.
Experience
Responsive layout proof
Desktop and mobile routes are scrolled and inspected, including revealed content and interaction states.
Code
Exact-commit checks
The diff, tests, static analysis, build, and CI evidence point to the same commit.
Release
Guarded deployment
Expected anchors, forbidden regressions, backup state, and rollback stay part of the release contract.
Outcome
Live behavior observation
The agent can verify what changed on production without claiming that one technical change caused a later ranking or citation.
Honest boundary
A green check is evidence. It is not permission or causality.
The agent that authored a change cannot convert its own checks into permission to merge.
Evidence from stale code, a different worktree, or a later deployment does not prove the proposed diff.
We can verify discoverability and implementation quality without claiming causal attribution for how an external model later answers.
We run this on ourselves
This page went through the workflow it describes.
humanswith.ai is 327 pages. Every change to it goes through this loop before it reaches you. Eight checks run on the build: design contract across 24 route policies, layout across 94 slot checks, accessibility across all built pages, structured data, link integrity, colour contrast, font loading, and outbound link policy.
Then the content itself is scored. This page had to clear 75 out of 100 before it could ship — measured, not estimated.
In August 2026 the loop caught something we would have missed by eye. A deploy succeeded, the new files were live, and the page still served the old version. The edge had cached it seconds before the origin updated. Reading the deployment URL and the public domain separately is now part of the check.
Website Agentic FAQ
What gets automated—and what stays a human decision.
What is Website Agentic Optimization?
It is a project-bound website workflow that scans an owned surface, prepares a scoped change packet, observes checks for the exact commit, and verifies deployed behavior.
Does it merge or deploy changes autonomously?
No. A green check does not grant merge or deploy authority. Those decisions come from the project runbook and the operator.
What can the change packet include?
It can include schema, metadata, canonical and hreflang fixes, internal links, llms.txt and sitemap discovery, layout corrections, performance work, and content-structure repairs within the approved scope.
Why track the exact commit?
Checks from a different commit do not prove the proposed change. The receipt binds code, tests, build output, and deployment observation to the exact commit under review.
Does a technical change guarantee more AI citations?
No. The workflow can verify crawlability, structured data, discovery, links, layout, and live behavior without claiming causal attribution for later AI-engine observations.
How is a live change verified?
The agent inspects the production URL for the new behavior, required anchors, forbidden regressions, metadata, schema, links, and responsive layout. A health endpoint alone is not completion proof.
Bring one owned surface. Leave with a scoped change and proof path.
We will define the exact target, blast radius, checks, human gate, deploy path, and live success anchors before implementation.